Technical SEO audit
For a page to appear in search, Google has to find it, crawl it and index it. The audit finds where that chain breaks and writes up the fixes in priority order, in a form a developer can apply directly.
What is a technical SEO audit?
A technical SEO audit finds the problems that stop search engines from discovering, crawling and indexing a site. It checks crawl and index status, the sitemap, robots.txt, redirects, canonical and hreflang tags, structured data, mobile rendering and Core Web Vitals in turn. The result is a prioritised list with the evidence, affected pages and fix for each issue.
What it covers
Crawl and index status
A full crawl of the site is read side by side with Search Console’s Page indexing report. Pages that should be indexed but are not are listed with the reason.
Sitemap, robots.txt and noindex
The sitemap is left with only the non-redirecting URLs you want indexed. Paths blocked by mistake and blocks left over from a staging site are found.
Redirects and canonical tags
The http, https, www and trailing-slash versions are brought to a single URL. Redirect chains, broken internal links and canonical tags pointing elsewhere are listed.
hreflang and multilingual structure
We check that the language versions point to each other in both directions, that URLs are written in full and that each version carries its own canonical tag.
Structured data
Organisation, product, article and breadcrumb markup is validated with the Rich Results Test. Lines that mark up information not visible on the page are removed.
Core Web Vitals and mobile rendering
LCP, INP and CLS are examined in real-user data, with the biggest items per template. We test whether the main content is visible in Google’s mobile crawl.
How it runs
- Access and scope.
We get read access to Search Console and Analytics. We write down which language versions, subdomains and templates will be audited, and which pages matter most to you.
- Crawl and data collection.
The site is crawled with Screaming Frog; Search Console reports and PageSpeed Insights data are combined in one table. Suspect URLs are checked one by one with URL Inspection.
- Prioritisation.
Each finding is written up with its evidence, the affected URLs, the fix and the effort needed. The order follows discovery, crawling, indexing and appearance; what blocks first is fixed first.
- Walkthrough and fixes.
We go through the list in a meeting with you and, if you have one, your developer. The issues are fixed by your developers or by our team.
- Verification.
After the fixes, the same crawl is run again, validation is started in Search Console and the closed issues are ticked off on the list.
What you hold at the end
- Prioritised issue list: evidence, affected URLs, fix
- Crawl file and URL inventory
- Redirect and canonical fix table
- hreflang and structured data check notes
- Core Web Vitals summary per template
- Verification crawl after the fixes
When this is not the right thing to buy
- If your site has a handful of pages and has not changed recently, working through the nine steps in our technical SEO checklist yourself will most likely be enough.
- If there is no developer to apply the findings, or no permission to change the site, the report will sit on a shelf; that needs solving first.
- If you are going to rebuild the whole site within a few months, preparing the migration plan and the redirect map is more useful than auditing the old structure.
Questions
The questions we hear most about this work. If yours is not here, write to us and we will answer within one working day.
How long does a technical SEO audit take to show results?
How long the audit takes depends on the size of the site and the number of templates; in our SEO service the first month goes on this audit and the prioritised list. The effect of the fixes shows as Google recrawls the pages. Reopening a section that was blocked by mistake can show fairly quickly; speed and structure improvements move more slowly. We give no timescale or guarantee for rankings; we watch together in the Search Console reports which issues have closed.
What do you need from us for a technical SEO audit?
Read access to Search Console and Analytics, a short note on how the site is built (the system it runs on, language versions, subdomains) and a list of the pages that matter most to you. If you have a developer, we would like one conversation with them; to write findings that can be applied, we need to know how the site is published. The audit does not need permission to change the site; that is only asked for if we are making the fixes.
What determines the cost of a technical SEO audit?
The number of URLs and templates on the site, the language versions, whether there is an e-commerce catalogue with filtered pages, whether the content is rendered with JavaScript and who will make the fixes. A ten-page company site and a two-language shop with thousands of products do not take the same effort. Two to three days after the free first meeting we send a proposal that sets out the scope item by item.
How is a technical SEO audit different from an automated tool report?
Automated tools produce hundreds of warnings and give them all the same weight; a missing alt text sits in the same list as a canonical error that keeps a whole section out of the index. In an audit, the crawl data is compared with the real index status in Search Console, each finding is confirmed on sample URLs and everything is ordered by its effect on your business. Instead of a score, you get a work list a developer can close in order.
Do all the “not indexed” pages in Search Console need fixing?
No. Google does not expect every URL to be indexed; for old redirecting URLs, filter parameters or tag archives these lines are normal. The audit looks only at the pages you want to appear in search; if one of them is not indexed, URL Inspection shows why. Where there is no technical block, the issue is usually the content: the page is too similar to another one, or does not answer a question on its own.
Do you make the fixes, or does our developer?
Either is possible. If you have your own developers, each finding is written so that they can apply it directly and the work runs as SEO consulting; we answer their questions and check after release. If you have no team, or your team has no time, our web and software team makes the fixes. In both cases the same crawl is run again after the fixes and the closed issues are ticked off on the list.
How often should a technical SEO audit be repeated?
A full check is needed straight after every major release, such as a change of theme, platform or URL structure. In between, looking regularly at the Page indexing and Core Web Vitals reports in Search Console is enough for most sites. In ongoing SEO work we watch these reports and, when a new issue appears, write it in the Monday report. For large catalogues that publish often, repeating the crawl at set intervals makes sense.
Further reading
- Technical SEO checklist: 9 steps with free toolsWith Search Console, PageSpeed Insights and a browser: auditing your site’s technical footing yourself, from indexing to hreflang.
- Website redesign SEO: how to avoid losing rankingsHow to move to a new site without leaving behind the value your old addresses have built up over the years.
- Why a fast site sells more: LCP, INP and CLS explainedReading Core Web Vitals as a line in your sales, not a line in a report.
- How to choose an SEO agency: seven questions and red flagsQuestion the work itself and what will be reported, not the promise of rankings.
From the same service
- SEOThe whole service: be found where people search
- GEO: AI search optimisationPeople now put some of their questions to Google’s AI summaries, ChatGPT and Perplexity. Nobody can guarantee being cited in those answers; what can be done is to make your site a source that is readable, quotable and unambiguous in name. We apply the same work to our own site first.
- B2B SEO servicesIn B2B, the most valuable searches are made rarely: a product code, the name of a standard, a narrow application. We take the keywords from your sales team before any volume tool, and measure success by the qualified enquiries tied to organic search in your CRM.