You can publish the best content in your market and rank nowhere if Google cannot crawl it, render it or decide which version to index. Technical SEO is the unglamorous work that makes everything else possible.
Our technical team works from crawl data and server logs rather than tool scores. A site health grade of 74 tells you nothing actionable; knowing that 61% of your crawl budget is being spent on parameterised URLs that return near-duplicate content tells you exactly what to fix on Monday.
We also write tickets developers can actually implement — with the specific file, the current behaviour, the expected behaviour and a way to test it. Most technical audits fail not because the findings were wrong but because nobody could turn a 90-page PDF into deployable work.
Six workstreams, each with defined outputs. Nothing here is a placeholder line item.
Full-site crawl compared against server logs to see what Googlebot actually requests, how often, and where crawl budget is wasted. We find the parameter URLs, infinite calendars, faceted combinations and redirect chains consuming your crawl allowance.
Systematic reconciliation of Search Console coverage data with crawl data: conflicting canonicals, accidental noindex, robots.txt blocks on assets Google needs to render, sitemap inaccuracies, soft 404s and duplicate clusters. The goal is a crawlable, indexable set of URLs that matches your intended architecture.
LCP, INP and CLS diagnosed from field data (CrUX and your own RUM where available) rather than lab scores alone. Typical work: prioritising the hero image, eliminating render-blocking resources, deferring third-party scripts, reserving layout space and breaking up long tasks on the main thread.
We compare raw HTML against the rendered DOM to confirm what Google sees, verify that critical content and internal links exist without JavaScript execution, and recommend SSR, prerendering or hydration changes where required.
Organization, LocalBusiness, Service, Product, Article, FAQ, HowTo, BreadcrumbList and Review markup implemented via templates, validated, monitored for errors in Search Console, and mapped to the rich results each type can earn.
Pre-migration crawl and ranking baseline, complete URL-to-URL redirect mapping, staging QA with crawl comparison, launch-day monitoring and a 30-day watch on indexation, Core Web Vitals and rankings. We have recovered enough botched migrations to be paranoid about this.
Crawl, log analysis, rendering tests, CWV field data review, prioritised technical findings with developer tickets.
Critical fixes shipped: indexation conflicts, redirect chains, robots and canonical corrections, sitemap rebuild.
Core Web Vitals work, structured data rollout, crawl budget optimisation, internal link depth fixes.
Deploy monitoring, monthly crawl comparison, regression alerts, support for new templates and features.
| Cadence | Deliverable |
|---|---|
| One-off | Technical audit with prioritised, developer-ready tickets (effort × impact scored) |
| Monthly | Crawl comparison, index coverage report, Core Web Vitals field trend, schema error monitoring |
| Monthly | Implementation hours — we ship the fixes ourselves or pair with your developers |
| Per release | Pre-deploy SEO QA on staging for new templates, features or migrations |
They are a confirmed but comparatively light ranking signal — a tie-breaker between pages of similar relevance rather than a way to outrank stronger content. The more compelling case is commercial: mobile conversion rates fall measurably as LCP rises past about 2.5 seconds. We treat CWV as a revenue project with an SEO bonus, not the reverse.
Crawl budget is how much crawling Google is willing to do on your site. If you have a few hundred pages, it is almost never your problem. If you have tens of thousands of URLs — especially an e-commerce site with faceted navigation — it matters a great deal, because crawl spent on duplicate parameter URLs is crawl not spent on your new products.
Generally yes, but with caveats: rendering is queued and can be delayed, client-side-only internal links may not be discovered, and anything requiring user interaction to load will not be seen. We verify empirically by comparing raw HTML to the rendered DOM and checking live index coverage rather than assuming.
Usually, and quickly, because the causes are predictable: missing or chained redirects, changed URL structures without mapping, a staging noindex left in production, blocked resources, removed content, or lost internal links. We run a forensic comparison against the pre-launch state and prioritise by traffic lost. Most recoveries we handle land within 60 to 90 days.
Yes, and it is usually the fastest path. We write tickets in your tracker with reproduction steps, acceptance criteria and test instructions, attend sprint planning if useful, and review staging before release. Where you have no development resource, we implement directly.
Send us your URL and we will review it manually — no automated PDF. You will receive the three highest-impact opportunities we can see, plus anything that looks like it is actively costing you traffic.
If Technical SEO is not what your site needs right now, we will tell you which of our services is — or that you do not need an agency yet.
Book a free 30-minute call with the strategist who would run your account. You will leave with three concrete actions whether or not you hire us.
