Technical health
We crawl the whole site the way a search bot does. Broken routes, slow pages and duplicate URLs come out first. Then we fix them in your repo or CMS.
You get A ranked fix list with an owner and a date on every line.
Most search work stops at a document. Ours starts there. We crawl the site, rank each fix by impact, then do the work in your stack. Then we crawl again to prove it held. No slide decks.
One row per fix. An owner, a state and a date on each. You always know what is moving.
Search is not one job. It is six, and they feed each other. Each area below states the method and the work you get back.
We crawl the whole site the way a search bot does. Broken routes, slow pages and duplicate URLs come out first. Then we fix them in your repo or CMS.
You get A ranked fix list with an owner and a date on every line.
We map what buyers type to what your site can honestly answer. Some terms are worth a page. Most are not. We say which.
You get A term map, grouped by page, with the intent behind each group.
Search reads structure before it reads prose. So we set the hub and spoke shape. Each page has one job and one clear route in.
You get A page tree, plus the internal links to build it.
Rankings hold when the page answers the question better than the next one. We brief, write and edit on one shared format.
You get Briefs, drafts and a calendar your team can run without us.
Titles, headings and markup do quiet work. We set the rules once at the template level. Then every new page ships correct by default.
You get Template rules for titles, headings and structured data.
We report on the fixes and the pages, not on impressions. You see what shipped, what moved, and what we would do next.
You get A short monthly read: shipped, moved, next.
The method is the same. The scope is not. Pick the one that matches where you are stuck today.
| Track | Best fit | Covers | Ends with |
|---|---|---|---|
| 01 Audit and fix list | You suspect something is broken and want proof. | Crawl, templates, on-page | A ranked list you can hand to any developer |
| 02 Fix sprint | The list exists. Nobody has the hours to ship it. | The fixes, in your stack | Shipped work, then a second crawl to check it |
| 03 Embedded SEO | You want search to compound month over month. | Fixes, content, structure, links | A rolling calendar and an open status thread |
Search rarely travels alone. Pair it with content marketing or web and conversion work, and read how a project runs.
Four stages, in order, on every engagement. You can see the state of each one at any time.
We pull the whole site, then read it as a bot does. Nothing is guessed.
Each issue gets an impact score and a cost. The cheap wins go first.
We do the work in your stack. Pull requests and CMS edits, not advice.
We crawl again. The fix either held or it did not. You see which.
Four answers, straight. If yours is not here, ask us on the call.
Technical fixes can register within weeks. Content and links take longer. We will not promise a date we cannot hold.
Both, in that order. The audit is the map. The sprint is the build. Most teams want the build.
Yes. We ship pull requests or CMS edits, and your team reviews them. Nothing goes live without your merge.
Then start with the audit. It is a second read on the same site. Keep what stands up. Drop what does not.
Send one URL and the term you want it to win. We will read it, then tell you what we would fix first and what we would leave alone. You decide what happens next.
Prefer email? Write to [email protected] with the URL and the term. We reply with a first read.