Content cannot rank if it is never crawled, never rendered or never indexed. Technical SEO is the part that decides whether the rest of the work has any effect at all.
- 01
- Crawl budget
- 02
- Rendering
- 03
- Core Web Vitals
- 04
- Index bloat
- 05
- Migrations
- R/01
Diagnosed from logs, not from a crawler alone
A crawler tells you what a bot could reach. Server logs tell you what Googlebot actually fetched, how often and what it got back. On any site above a few thousand URLs the difference between those two pictures is where the problem lives.
We look for crawl budget spent on faceted URLs, parameter duplicates, paginated dead ends and redirect chains — the pages consuming attention that should be going to the ones you want ranked.
- R/02
Rendering, which is where JavaScript sites lose
If content only exists after a client-side fetch, indexing becomes a second-pass gamble. We check what is in the server response versus the rendered DOM, and move anything that must rank into HTML that arrives with the document.
This is the single most common failure we find on React and Vue sites that were never built with search in mind.
- R/03
Core Web Vitals as engineering, not a plugin
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift are measured on real hardware, not a throttled desktop. Fixes are specific: what is blocking the main thread, which image is oversized, which font swap is shifting the layout.
- R/04
Migrations without the cliff
Replatforming and restructuring are where traffic disappears overnight. We build the redirect map from the live URL inventory before launch, verify every old URL resolves in one hop, and watch the index for the weeks that follow.
Deliverables
06 items
- 01
Log-file analysis
What Googlebot actually crawls, how often, and what it receives — the ground truth a crawler cannot give you.
- 02
Render audit
Server HTML compared against the rendered DOM, so nothing that must rank depends on client-side JavaScript.
- 03
Index hygiene
Thin, duplicate and parameter URLs identified, then noindexed, canonicalised or removed on purpose.
- 04
Core Web Vitals plan
Field data by template with the specific engineering fix for each, prioritised by traffic affected.
- 05
Redirect map
For migrations: every legacy URL mapped to its destination, single-hop, verified before you go live.
- 06
Monitoring
Coverage, crawl stats and vitals watched after the change, so a regression is caught in days.
Queries
Crawl budget, rendering, index bloat, Core Web Vitals and migration safety, diagnosed from logs rather than guessed.
Search Console and analytics access, and server logs if you can get them. Logs are optional but they turn a lot of educated guessing into fact.
Either. We write findings as specific tickets your team can action, and we can implement directly on most modern stacks — this site is Next.js and it is what we build in.
Before the URL structure is decided, not after. Most migration damage is designed in months before launch and only becomes visible the week the redirects go live.
Next
Send us the domain and the queries you want to win. We will come back with what is actually blocking you, whether or not you hire us.
Crawl budget · Rendering · Core Web Vitals · Index bloat · Migrations