Service · Technical SEO audit
A technical SEO audit your team can actually ship
A technical SEO audit is a structured review of how well search engines can crawl, render, and index a site, ending in a ranked list of fixes. Ours is built from a real crawl, server log data, and Search Console evidence, then scored by impact and effort so the highest-value work rises to the top. No 90-page PDF. No tool export with a logo on it.
Who it is for
- Sites where organic traffic has plateaued or slipped with no obvious content reason
- Large catalogues or publishers where crawling and indexation feel out of control
- Teams planning a migration who want a clean baseline first
- In-house SEOs who need an external, evidence-backed case to get dev time approved
Who it is not for
- Brand-new sites with little content and no crawl history to analyse
- Teams looking for a cheap automated report to tick a box
- Situations where the real problem is content quality or market fit, which an audit will not fix
- Anyone wanting a ranking guarantee attached to the deliverable
Scope
What the audit actually examines
Every audit covers these areas. Depth varies by site, because a marketplace with faceted navigation needs a very different crawl plan from a 200-page SaaS site.
Crawlability
Robots.txt directives, crawl paths, orphan pages, click depth, and how Googlebot spends its requests according to the logs.
Indexation
Index bloat, soft 404s, Crawled currently not indexed, Discovered currently not indexed, and duplicate handling in the Pages report.
Rendering
Client-side versus server-side rendering, what reaches the initial HTML, and whether primary content survives the render for Googlebot.
Site architecture
URL structure, subfolder versus subdomain decisions, internal linking, and link equity distribution across templates.
Canonicals & duplicates
Canonical logic, parameter handling, faceted navigation, pagination, and duplicate content across regions or variants.
Performance
Core Web Vitals from field data, LCP and INP on core templates, and the render-blocking resources behind them.
Deliverables
What you actually receive
Prioritised findings register
A living spreadsheet, not a static PDF. Each row has the issue, the affected URLs or templates, the evidence, an impact score, an effort score, and a suggested owner. Sorted so the top ten rows are the ten things worth doing first.
Ticket-ready specifications
For the high-priority items, a written spec a developer can pick up: what to change, why, the expected result, and how we will verify it. Framed to survive code review.
Executive summary
One page for the people who approve the roadmap. What is wrong, what it is costing in plain terms, and what to fix first. No jargon wall.
Walkthrough call
A working session with your SEO and engineering leads to go through the register, answer questions, and agree the first sprint of work.
Timelines
Realistic turnaround by site size
The audit is rarely the slow part. Implementation is. These windows cover the analysis and the walkthrough, from the day access is granted.
| Site size | Typical crawl scope | Audit window |
|---|---|---|
| Up to ~10k URLs | Full crawl, sampled log review | 1 to 2 weeks |
| 10k to 250k URLs | Full crawl, log analysis by template | 2 to 3 weeks |
| 250k to ~2M URLs | Segmented crawl, full log analysis | 3 to 5 weeks |
Scroll table horizontally →
A quick note on expectations. The findings that move the needle are usually known within days. Whether they change anything depends on how fast the fixes get through your backlog, which is why we build the register around effort as much as impact. If you want context on that trade-off, our guide on prioritising technical SEO fixes when dev time is limited walks through the scoring we use.
FAQ
Audit questions, answered
What is included in a technical SEO audit?
A full crawl of the site, a review of server log data where available, cross-referencing against the Google Search Console Pages and Crawl Stats reports, and a check of rendering, canonicals, redirects, sitemaps, robots directives, and internal linking. The output is a prioritised findings register, not a raw export.
How is this different from a Screaming Frog export?
A crawl export lists what is technically present. It does not tell you which of 4,000 issues matters for your business, on your stack, at your scale. We read the crawl against your logs and your architecture, then rank findings by impact and implementation effort. The judgement is the service.
How long does a technical SEO audit take?
Two to three weeks for most sites once we have access. Very large catalogues or multi-region sites take longer because crawling and log analysis at that scale is slow. We agree the timeline before starting.
What do you need from us to start?
Read access to Search Console and Bing Webmaster Tools, analytics, and ideally server or CDN log files. Log files are optional but they are where the most useful findings hide on large sites, so we recommend them.
Do you implement the fixes or just report them?
The audit itself is a fixed deliverable, but we do not disappear when we hand it over. We write findings as engineering tickets and can stay through implementation and verification under a separate scope. Most clients keep us involved for exactly that reason.
Related reading
An audit is where most engagements begin. If you want the wider picture first, our work as a technical SEO agency covers migrations, rendering, and Core Web Vitals once the audit shows where to look.
Start here
Want to know what your site is actually leaking?
Send the URL. We will tell you whether an audit is the right first move or whether the problem sits somewhere an audit will not reach.