Technical SEO
Crawlability, indexation, rendering, structured data and site health, fixed at the root.
- Engagement
- Fixed-scope engagement, monthly monitoring optional
- Typical timeline
- 6 weeks
- Starts with
- A full crawl of the site alongside thirty days of raw server logs.
Google has indexed forty thousand URLs on a site with three thousand real pages, and the duplicates are outranking the originals. Nothing is wrong with your content; the site is telling search engines the wrong things about itself.
Search engines finally seeing everything you publish.
What we build
Concrete artefacts, handed over and documented.
- 01
Crawl and server-log analysis showing which pages Googlebot visits, how often, and which it has quietly given up on
- 02
Indexation control: canonical rules, parameter handling, robots directives, and a sitemap listing only pages you want ranked
- 03
A rendering fix where JavaScript hides your content from crawlers, usually by moving the template to server rendering
- 04
Structured data implemented and validated for the page types you actually have, product, article, organisation, FAQ
- 05
Internal link architecture rebuilt so authority reaches your commercial pages in three clicks or fewer
What changes
Crawl activity concentrates on pages that can earn traffic instead of on filter permutations
The pages you want indexed are the pages that are indexed
Content work starts producing rankings again, because the technical floor stops holding it down
How it runs
01Crawl and logs
A full crawl next to thirty days of server logs, which is the only way to see what Google does rather than what it claims.
02Fixes with your engineers
We write the changes as tickets, pair with your developers on the hard ones, and ship them in batches we can attribute.
03Re-crawl and verify
A second crawl and a Search Console comparison, so every claim we made is checked against the index rather than assumed.
Chosen per project. Named here so you can see the shape of it.
- Screaming Frog
- Sitebulb
- Google Search Console
- Ahrefs
- Cloudflare Logpush
- Google Rich Results Test
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.