The pages search engines can crawl, load & trust

Technical SEO is the engineering layer of search — everything that decides whether a search engine can crawl, render, and index your pages before it ever judges your content. We work across crawl budget, render paths, Core Web Vitals, indexation, redirects, status codes, canonicals, and structured data. The goal is simple: make sure the page a crawler receives is fast, clean, and indexable so the content you publish can actually rank.

We typically start with a fixed-fee audit scoped to your site’s size and stack, then move into a retainer or project for the implementation. Pricing tracks the real surface area — the number of templates, the CMS or framework, and how much of the fix work your engineering team owns versus ours. After the audit we give you a prioritised remediation plan with the effort and impact spelled out, so you’re never approving a blank cheque.

The audit and a prioritised fix list land in the first few weeks. Render and Core Web Vitals improvements show up in Lighthouse and field data almost immediately once shipped, while indexation and ranking changes follow the crawl cycle — usually weeks, not days, as search engines recrawl and reprocess the corrected pages. We sequence the highest-impact fixes first so the curve moves early rather than waiting for everything to be done.

Content and link-led SEO decide what you rank for; technical SEO decides whether you can rank at all. You can publish the best page on the topic and still lose if it’s blocked by robots rules, buried under render-blocking JavaScript, or served behind a redirect chain. We focus on the foundation — crawl, speed, indexation, and schema — so the content and authority work your team does isn’t wasted on pages search engines can’t properly see.

We measure against what search engines actually see, not what the page looks like in a browser. That means Google Search Console’s index and Core Web Vitals reports, log-file and crawl data (Screaming Frog, Sitebundle-style crawlers), Lighthouse and field CrUX data, and the rendered DOM Googlebot receives. Schema is validated with the Rich Results Test. Every fix is verified against the live crawl rather than assumed.

Migrations are where rankings get lost, so we treat them as a controlled handover. Before launch we map every URL to its destination, preserve or correct canonicals and redirects (301s, never silent 302s), and freeze a baseline of indexation and vitals to compare against. After launch we monitor crawl errors, index coverage, and Core Web Vitals with alerts, so if a deploy quietly undoes a green pass we catch it before it costs traffic.