A full site SEO audit is a structured review of every URL and the systems behind it. The aim is not to chase a single health score. It is to identify the issues that stop important pages being discovered, indexed, understood, useful and competitive.
Google describes Search as a process of crawling, indexing and serving results. That sequence is a useful way to organise an audit, because a page cannot perform well if search engines cannot access or index the canonical version in the first place. Google's guide to how Search works explains those stages in detail.
Table of contents
- What a full site SEO audit should deliver
- Before you start: access, scope and tools
- 1. Define what “full site” means for your audit
- 2. Crawl the site and build a reliable URL inventory
- 3. Check crawlability, indexability and canonical signals
- 4. Test technical quality and page experience by template
- 5. Audit information architecture and internal linking
- 6. Review content quality, intent and duplication
- 7. Assess authority and search-result context
- 8. Prioritise fixes, implement them and verify the result
- Full site SEO audit checklist
- Frequently asked questions
- Turn the audit into an operating plan
What a full site SEO audit should deliver
By the end, you should have:
- A clean inventory of indexable, non-indexable, redirected and broken URLs.
- A short list of technical blockers and their affected templates or sections.
- Clear content actions for pages to improve, consolidate, redirect or create.
- Internal-link and authority priorities tied to commercially important pages.
- A sequenced backlog with an owner, evidence and a way to verify each fix.
We recommend auditing one canonical website property at a time, including the preferred protocol and subdomain. If you operate separate country, language or subdomain experiences, audit each one separately and then review their implementation together.
Before you start: access, scope and tools
Prepare these inputs before crawling:
- Read access to Google Search Console and web analytics.
- A site crawler that can follow links, report status codes, render JavaScript where needed and export data.
- Access to your CMS, tag manager, hosting or development team for validation.
- A list of priority pages, products or services, conversion actions and target markets.
- A spreadsheet or task board for the issue backlog.
Do not start by fixing every warning your crawler finds. First decide what matters: revenue pages, lead-generation pages, key category or service pages, high-traffic content and pages that should be visible in search.
1. Define what “full site” means for your audit
Action: Set the audit boundary. Record the canonical host, intended sitemap(s), relevant subdomains, language folders, parameter rules, staging environments and pages that must not be indexed.
Create a simple success statement, such as: “All UK service pages are crawlable, indexable, internally linked and able to generate qualified enquiries.” This stops the audit becoming a generic list of tool alerts.
Expected result: A documented scope and a shortlist of business-critical URLs that you will inspect individually.
Troubleshooting: If teams disagree over which URLs belong in scope, use the XML sitemap, analytics landing-page report and CMS inventory to create an initial list. Mark uncertain sections rather than quietly excluding them.
2. Crawl the site and build a reliable URL inventory
Action: Crawl the preferred canonical domain, starting with the homepage and XML sitemap. Export URLs with their status code, canonical tag, robots directives, title, meta description, headings, word count, internal-link counts and crawl depth.
Segment the export by page type. Typical groups include homepages, service pages, product pages, categories, editorial content, location pages, filters, PDFs and pagination. A crawl without segmentation is difficult to turn into decisions.
Compare the crawler's URLs with your submitted sitemap and a sample of Search Console landing pages. The differences often reveal orphaned pages, old URLs still receiving traffic, sitemap errors or pages that are available only through internal search.
Expected result: One deduplicated inventory where every URL has a page type and an initial indexability status.
Troubleshooting: If the crawler finds far fewer pages than expected, check crawl limits, authentication, robots rules, JavaScript rendering and whether navigation relies on non-crawlable interactions. If it finds far more, isolate parameters, filters, session URLs and other duplicate patterns before interpreting totals.
3. Check crawlability, indexability and canonical signals
Action: For every important URL, test whether it returns a successful response, can be crawled, is allowed to be indexed and points to the correct canonical URL. Then inspect representative examples in Search Console's URL Inspection tool.
Use the Page indexing report to group excluded URLs by reason. Not every excluded URL is a problem. Duplicates, intentionally removed pages and pages deliberately excluded from search can be correct. The question is whether your important pages are indexed and whether each exclusion has an intentional explanation. Google's Page indexing report guidance makes the same distinction and recommends URL Inspection for a specific page.
Check for:
noindex, robots.txt or login barriers on pages that should rank.- Canonicals pointing to irrelevant, redirected or non-equivalent pages.
- Indexable duplicate variants caused by parameters, trailing slashes, HTTP versions or filters.
- XML sitemap URLs that redirect, return errors, are blocked or are non-canonical.
- Orphaned pages with no crawlable internal path.
Expected result: A list of priority pages confirmed as accessible, indexable and canonicalised correctly, plus a separate list of intentional exclusions.
Troubleshooting: Do not use robots.txt as a substitute for noindex when you need a page kept out of Google Search. A blocked URL can still be known to Google, while a noindex directive must be crawlable for Google to see it. Validate the desired control on the live URL before deployment.
4. Test technical quality and page experience by template
Action: Review sitewide technical signals by template, not merely URL by URL. Test a representative set of pages on mobile and desktop for status codes, redirect chains, HTTPS, mixed content, rendering, structured data validity, image delivery and mobile usability.
Use field data where available. Core Web Vitals measure loading, responsiveness and visual stability. Google's published targets are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint below 200 milliseconds and Cumulative Layout Shift below 0.1. Google's Core Web Vitals documentation explains the measures and points to the Search Console report.
Prioritise recurring causes over isolated scores. For example, a single uncompressed image is a page task. A render-blocking script or a heavyweight global component is a template task with wider impact.
Expected result: A technical issue list grouped by root cause, affected page type, severity and development owner.
Troubleshooting: If lab tools and real-user data disagree, use field data to identify the broad pattern and lab testing to reproduce the cause. Test the same URL, device class and page state before deciding a fix has worked.
5. Audit information architecture and internal linking
Action: Map how a user and crawler reach important pages. Review navigation, breadcrumbs, hubs, category pages, related-content modules and in-content links. Identify priority pages that sit too deep in the architecture or receive few relevant internal links.
Every important page should have a clear role. A service page may need links from the navigation, a relevant industry page and supporting guides. A detailed guide may need a link back to its category or service page when that is genuinely useful to the reader.
Review internal anchor text for clarity and intent. “Read more” links are not always wrong, but descriptive anchors help people understand where a link leads. Also check for links to redirects, broken URLs, non-canonical versions and pages blocked from crawling.
For external authority analysis, treat Search Console's Links report as a useful sample, not a complete ledger of every known link. Google's Links report documentation notes that the report can omit URLs and combines duplicates.
Expected result: A map of hub pages, underlinked priority URLs and broken or wasteful internal pathways.
Troubleshooting: If you find an orphan page that deserves organic traffic, first decide whether it should remain. Add it to the sitemap only after it has a meaningful internal route and a clear place in the site's architecture.
6. Review content quality, intent and duplication
Action: Evaluate content at the cluster level. Group pages that address the same problem, service, location or question, then compare their purpose, search intent, evidence, freshness, conversion role and internal links.
For each page, choose one action:
- Keep and improve when the page has a distinct purpose and useful potential.
- Consolidate when two or more pages compete to answer the same need.
- Redirect or retire when a page is obsolete and has no independent value.
- Create when a valuable audience question has no adequate answer.
Quality is more than keyword placement. Google's people-first content guidance asks whether content adds original information or analysis, gives a substantial answer, demonstrates experience or expertise, and leaves readers with enough to achieve their goal. Use those questions as a content-audit rubric.
Review titles and main headings as summaries of the page, then assess the page itself. A rewritten title cannot fix thin, duplicated or misaligned content. Likewise, do not consolidate pages simply because they use related phrases. Consolidate only when their intent and value substantially overlap.
Expected result: A content action plan tied to URL groups, with clear decisions rather than a vague list of “optimisations.”
Troubleshooting: If two pages have similar topics but serve different stages of a buyer journey, keep both and clarify their differentiation. For example, a practical implementation guide and a service page can coexist when one teaches and the other explains how to get help.
7. Assess authority and search-result context
Action: Review the pages that earn links, mentions and search visibility, then compare those patterns with the pages that matter to the business. Look for gaps in evidence, unique expertise, useful tools, original research, case examples and supporting content.
Do not treat a raw backlink count as a verdict. Instead, ask whether relevant, credible sites have reasons to reference your best resources and whether authority flows through sensible internal links to priority pages.
For high-value topics, review the current search results before commissioning new content. Note the dominant format, questions being answered, level of practical detail and what is missing for your audience. Build a page that is more useful for the actual decision, not one that merely repeats a competitor's headings.
Expected result: A short list of content assets, partnership opportunities and page improvements that can strengthen the credibility of priority topics.
Troubleshooting: If a competitor has substantially stronger authority, do not respond with large-scale low-value publishing. Start with the pages where your business has real experience, evidence and a clear reader need, then earn relevant references over time.
8. Prioritise fixes, implement them and verify the result
Action: Turn findings into a backlog with five fields: issue, evidence, affected URLs or template, expected impact and owner. Then sequence work in this order:
- Blocks to crawling, indexing or essential user journeys.
- Technical faults that affect a large template or many important URLs.
- Missing or weak internal paths to priority pages.
- Content consolidation and improvement on proven business topics.
- Longer-term authority and content-asset work.
Assign a verification method before any change ships. That might be a recrawl, a live URL Inspection test, a sitemap validation, a Core Web Vitals trend, or a Search Console check after Google has had time to process the update. Google does not guarantee crawling or indexing for every page, so validation should confirm implementation first and search visibility second.
Expected result: A manageable roadmap that separates urgent defects from valuable but longer-term improvements.
Troubleshooting: If your backlog remains too large, score each item by reach, severity, confidence and implementation effort. Keep uncertain opportunities visible, but do not let them displace confirmed indexing or technical problems.
Full site SEO audit checklist
Before closing the audit, confirm that you can answer these questions:
- Which URLs are meant to be indexed, and are the important ones eligible to appear in search?
- Which crawl, rendering, speed or template faults affect multiple important pages?
- Where can visitors and crawlers fail to reach priority pages through internal links?
- Which pages need improving, consolidating, redirecting or creating?
- Which priorities have owners, deadlines and a verification method?
- Which audit findings are assumptions that still need access to Search Console, analytics or developer validation?
Frequently asked questions
How often should you run a full site SEO audit?
Run a lighter monitoring review continuously and a full audit after major migrations, redesigns, platform changes, significant navigation changes or sustained organic-performance shifts. For stable websites, a thorough review every six to twelve months is usually a practical baseline, with routine checks in between.
Can a small site need a full audit?
Yes. A smaller inventory makes auditing faster, but important failures such as an accidental noindex, broken canonical setup or missing internal navigation can still affect the whole site. Small sites should focus on critical pages and clear implementation evidence rather than generating lengthy exports for their own sake.
What is the difference between a technical SEO audit and a full site SEO audit?
A technical audit concentrates on crawlability, indexation, rendering, performance and implementation. A full site SEO audit includes those areas but also reviews content purpose, search intent, internal architecture, authority and the prioritisation process.
Can automated audit tools replace human review?
No. A crawler can surface patterns and diagnostics quickly, but it cannot reliably decide whether a page supports a business goal, satisfies reader intent or should be consolidated. Use automation to gather evidence, then apply human judgement to the decisions.
Turn the audit into an operating plan
A completed full site SEO audit leaves you with more than a report. You know which pages should be discovered and indexed, which systems need repair, which content needs a decision, and what to verify after each change.
Our next step is to turn the highest-confidence findings into a focused content and implementation plan, rather than attempting every possible SEO task at once. If you want the audit to connect to prioritised opportunities and a publishing workflow, explore how GrowthScout brings website context, audits and content planning together.