We build the systems behind your site — and make sure search engines can read them.
Short answer: quietmason builds the systems behind a site: data collection and pipelines, technical SEO that starts from the client's own Search Console data, and the structured markup that gets a page quoted rather than skipped. Work runs to fixed scope with a written handover, in European hours with US Eastern mornings covered, and replies inside one business day. Published ranges for the common jobs are on the pricing page, so you can decide whether to write before you do.
Checked on 2026-10-20
Collection and pipelines that keep running, technical SEO that starts from your own Search Console data, and the structured markup that gets a page quoted rather than skipped.
European hours in full · US Eastern mornings · replies within one business day
What kind of work do we take?
Four kinds, and most engagements combine two of them: collecting data that has no export, automating a job that is still done by hand, making a site readable to search and answer engines, and small storefronts. The split below is by frequency, not by difficulty.
Scraping, cleaning and pipelines that keep running
Collection from sites and APIs, normalization, storage, scheduled runs, failure alerts. Built to survive rate limits and layout changes.
Automation services →Indexation, structured data, Core Web Vitals
An audit built on Search Console data, fixes applied in priority order, then a before/after read you can check yourself.
Technical SEO services →Getting cited, not merely crawled
One consistent entity, markup that matches the page, and sentences an assistant can lift without distorting them.
How we approach it →Stores, landing pages, migrations, speed
When the site itself is the blocker. Plain HTML and PHP by default, so nothing needs a subscription to stay alive.
Website work →What do we hand over?
Two artifacts speak for the work better than a slide: the running system, and the markup a machine reads.
sources
├─ https://catalog/… paginated, 429-aware
└─ api/items token bucket, retry 3
↓
clean normalize units · dedupe by sku
↓
store mysql upsert → report.csv
↓
notify on failure: email + log tail
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Technical SEO",
"provider": { "@type": "Organization",
"name": "quietmason" },
"areaServed": "Worldwide"
}
How does a project run?
Every project runs the same five steps whatever the scope: a written brief, a fixed number, a build in the open, a handover with the source, and two weeks afterwards where we fix what we got wrong. Nothing starts before the number is agreed.
Scope in writing
You describe the outcome. We write down what is included, what is not, and what we need from you before anything starts.
Fixed price, short cycle
One number and a delivery window agreed up front. Most work lands in days, not quarters. You watch it on a staging URL.
Handover you can keep
Source, credentials, run instructions and a plain-language note on how to change things later. You are not locked to us.
No account manager layer and no offshore handoff: the person who scoped the work is the person who builds it.
Systems we built and still maintain
Three systems are still running in production: a branch operations API, a publishing pipeline and a storefront. They are listed because the code is the reference - each entry says what it replaced and what it now does.
Booking & inventory system
A multi-branch studio moved off spreadsheets onto a web admin and a customer Mini Program over one API.
Build notes →Dataset to finished pages
Drafting, formatting and release steps automated behind quality gates, with failures reported instead of shipped.
Build notes →A store that had to be cheap to run
Catalog generated from one data file, order capture wired to email, no monthly platform bill, redirect map kept intact.
Build notes →What you can hold us to
You own the output
Code, data and credentials are yours from the first commit. We keep no license to your work and we do not reuse it elsewhere.
Claims you can reproduce
Any number we quote comes from a source you can open: Search Console, a public URL, or the same input data.
One address, verifiable
Every message comes from [email protected] on a domain with SPF and DKIM configured. You can check the DNS yourself.
Send the URL, or the task
One email is enough to start. You get a scope and a fixed number, or a plain "we are not the right fit".