A practical technical SEO audit for service businesses, prioritised around crawlability, indexation, internal linking, performance and lead-generation pages.
- Technical SEO should remove constraints from important pages, not become an endless checklist exercise.
- Prioritise crawl/indexation, canonicalisation, redirects, internal links and performance before cosmetic warnings.
- Tie every issue back to affected landing pages and commercial impact.
1–2. Check whether important pages can be crawled and indexed
Start with the basics: can search engines access the page, and is the page allowed to be indexed? Review robots directives, meta robots tags, canonical tags and status codes on the pages that matter commercially.
A service page blocked by a noindex tag is urgent. A minor validation warning on a low-value archive page is not. Technical audits become useful when issues are prioritised by business impact.
3–4. Validate canonicals and redirect behaviour
Each indexable page should have a clear preferred URL. Look for canonicals pointing to the wrong page, redirect chains, temporary redirects that should be permanent, and legacy URLs that still receive internal links.
During migrations or redesigns, map old URLs to their closest new equivalents. Our redesign SEO checklist covers that process in more detail.
5–6. Crawl the internal-link structure and find orphan pages
Important commercial pages should be reachable from navigation or contextual links, not hidden several clicks away with no meaningful anchors. Find pages with very few internal links, pages receiving links only from boilerplate areas, and articles that never point toward a commercial next step.
Internal links are one of the easiest technical and editorial improvements to coordinate because they do not require new pages.
7–8. Review performance and rendering on the pages that generate leads
Measure real-user performance where possible, then use lab tools to diagnose the causes. Large hero images, heavy third-party scripts, font loading and bloated page builders can all slow the moments that matter.
Do not optimise performance in isolation. A fast page that removes useful proof or breaks forms is not an improvement. See our Core Web Vitals guide for lead-generation sites for prioritisation.
9–10. Check metadata, headings and structured data for consistency
Titles, descriptions and headings should match the visible page and the search intent. Structured data should describe content that is actually present; it should not invent reviews, addresses, services or facts simply to produce richer markup.
Use the most specific schema that accurately represents the page, validate the JSON-LD and keep organisation identifiers consistent across the site.
11–12. Verify sitemaps and measure the index, not just the crawl
Your sitemap should contain canonical, indexable URLs that you actually want in search. Remove noindex pages and obsolete URLs. Then compare sitemap URLs with indexed pages and search performance so the audit ends with a measurable baseline.
After fixes, request recrawls for high-priority URLs and monitor Search Console for indexation and structured-data changes rather than assuming the crawler will interpret everything immediately.
Prioritise the audit by revenue exposure
Create three buckets: issues blocking important pages, issues degrading performance or clarity, and low-risk housekeeping. Fix the first bucket first. A technical audit should help the team decide what to do next, not generate a 200-row spreadsheet with no commercial order.
