Website Audit Checklist: SEO, Technical, Performance & UX

Define the audit scope before looking for problems.

A useful SEO audit starts with a question: what are we trying to improve? An ecommerce migration, a local-service site that has stopped growing, and a content site losing impressions need different levels of investigation. If you start with a crawler and no business context, you can easily produce hundreds of warnings without knowing which ones matter.

Before touching the site, record a baseline. In Google Search Console, note organic clicks, impressions, average position, the queries that already produce visibility, and the pages receiving that visibility. If lead or ecommerce tracking is available, note the pages that contribute to conversions as well. This gives you a way to judge whether a technical issue is actually connected to search performance.

• Define the market, language and locations being audited.
• List the pages that generate leads, sales or qualified organic traffic.
• Identify any recent migration, redesign, CMS change or large content release.
• Record Search Console and analytics baselines before changes are made.

Check crawlability, indexability and canonical signals first.

Google cannot rank a page it cannot properly access or index. This is why technical eligibility comes before title rewrites, content expansion or link building. For important URLs, verify that Googlebot can reach the page, the server returns a successful response, the content is indexable, and the intended URL is the version being treated as canonical.

Review robots.txt, meta robots directives, HTTP status codes, redirects, canonical tags and XML sitemaps together. These signals can conflict. For example, blocking a URL in robots.txt does not reliably remove it from search, and a sitemap is only a supporting signal for canonical selection. For duplicate or near-duplicate pages, use a consistent preferred URL across internal links, canonicals, redirects and sitemaps.

• 200 pages: important indexable pages should normally resolve successfully.
• 3xx redirects: remove unnecessary chains and update internal links to final destinations.
• 4xx / 5xx: identify broken internal targets and server errors affecting useful pages.
• Robots / noindex: confirm that the rules match the intended search visibility.
• Canonicals: check self-referencing canonicals on primary pages and conflicting canonical signals.
• Sitemap: include the canonical URLs you actually want search engines to discover and index.

Audit site architecture and internal linking.

A technically indexable page can still be weakly connected to the rest of the site. Internal linking helps users discover related information and gives search engines context about page relationships and relative importance. The goal is not to put every page in the main navigation; it is to make important content easy to reach through logical paths.

Look for orphan pages, deep click paths, repeated generic anchors such as “learn more”, and clusters where supporting pages do not link back to the main commercial or cornerstone page. For an SEO content cluster, the structure should be obvious: a broad page introduces the topic, supporting pages answer narrower questions, and relevant service or tool pages receive contextual links where the reader naturally needs the next step.

• Important pages should receive links from relevant parent, category or supporting pages.
• Anchor text should describe the destination naturally.
• Breadcrumbs should reflect a sensible hierarchy where they help users navigate.
• Remove internal links to redirects or broken pages when the final destination is known.
• Use contextual links between related articles instead of relying only on footer navigation.

For this cluster, the checklist should connect naturally to what a website audit should include, the free Professional Website Audit, and deeper off-page guides such as how to find competitor backlinks.

Make sure every important page has one clear search job.

On-page SEO is less about inserting a keyword in specific places and more about making the page's purpose unmistakable. A page should answer a coherent search intent, use a descriptive title and H1, and provide enough evidence and explanation for the reader to complete the task that brought them there.

Compare the title, H1, opening paragraph, main sections and internal anchor text. They should point in the same direction. If two pages are targeting essentially the same query with similar content, investigate cannibalisation: one stronger page may be better than two weak pages competing for the same role.

• Write a unique title that accurately describes the page rather than repeating a template.
• Use one clear H1 and descriptive H2/H3 sections that help scanning.
• Answer the primary intent early, then add depth for secondary questions.
• Remove filler written only to increase word count.
• Check whether another URL on the site serves the same intent more effectively.

Evaluate content quality, evidence and trust.

A page deserves visibility when it is genuinely useful, not simply because it is long. Review whether the main content adds original value: practical examples, first-hand knowledge, clear comparisons, original analysis, transparent limitations, or a tool that helps the reader make a decision. Thin rewrites of information already available everywhere are difficult to defend as the best result.

For service and expert websites, trust also comes from clarity about who is responsible for the content and what experience supports it. That does not mean filling every page with credentials; it means making authorship, business identity, contact information and claims easy to verify.

• Remove outdated claims or examples that can mislead a reader.
• Update pages when the underlying guidance changes, not merely to change the date.
• Use original screenshots, calculations, examples or observations where they add value.
• Explain uncertainty instead of presenting estimates as guarantees.
• Strengthen pages that receive impressions but fail to earn clicks or engagement.

Google's current guidance is explicitly people-first: content should leave users feeling they learned enough to achieve their goal. That is a useful standard for an audit because it focuses the review on usefulness rather than arbitrary length.

Review performance and page experience without chasing a single score.

Speed matters because it affects how quickly users can see and interact with a page, but a Lighthouse score is not a complete diagnosis. Use field data where available, then inspect the actual causes of poor experience: oversized images, render-blocking resources, excessive JavaScript, unstable layout, slow server response or interaction delays.

Google's Core Web Vitals “good” targets are currently LCP within 2.5 seconds, INP under 200 ms and CLS under 0.1. Treat these as user-experience targets, not as a promise that passing them will produce a ranking increase.

• Check Core Web Vitals in Search Console for real-user patterns.
• Compare mobile and desktop rather than assuming one represents both.
• Compress and correctly size hero and content images.
• Reserve image and embed dimensions to reduce layout shift.
• Review intrusive overlays, tap targets, navigation and readability on small screens.
• Prioritise fixes on templates that affect many important URLs.

Check how the site can appear in search results.

An SEO audit should also review the information search engines may use to present a result: page titles, snippets, breadcrumbs, images, favicons and relevant structured data. Structured data does not replace good content and it does not guarantee a rich result, but valid markup can help search engines understand eligible page types more clearly.

Use structured data only when the visible page genuinely matches the schema. Validate the markup, remove obsolete properties, and avoid adding types simply because they are available. For articles, products, organizations, local businesses and FAQs, accuracy is more useful than volume.

• Check that titles and headings describe the visible page accurately.
• Review snippets for misleading or duplicated meta descriptions.
• Validate structured data and confirm that marked-up information is visible to users.
• Check image quality, alt text where meaningful, and whether important images can be crawled.

Verify measurement and the conversion path.

SEO traffic is only useful if the business can understand what happens after the click. Check whether analytics and conversion tags are present, whether key events fire correctly, and whether the main user journey works on real devices. Code presence alone is not proof that measurement is accurate.

For a lead-generation site, test the form, booking flow, phone links and thank-you state. For ecommerce, test add-to-cart, checkout and purchase events. An SEO audit does not need to become a full analytics implementation project, but it should clearly state what was verified and what requires account-level access.

Review authority and backlink gaps after the site itself is sound.

Technical cleanup cannot manufacture authority. Once the important pages are accessible, useful and internally connected, compare the site's external link profile with the competitors that already rank for the target queries. The objective is not to copy every backlink; it is to find credible sites, pages and resource types that repeatedly support competitors but not you.

Start with the competitors that actually rank for the queries you care about, then identify the domains and specific pages linking to them. Our guide on finding competitor backlinks explains the research process, while backlink gap analysis focuses on prioritising missing opportunities.

• Separate relevant editorial links from low-quality directory noise.
• Look for repeated sources that link to several competitors.
• Compare the target pages receiving links, not only domain-level totals.
• Use the gap to guide outreach, digital PR, partnerships or genuinely link-worthy resources.

Turn findings into a prioritised roadmap.

The deliverable should not be a dump of crawler warnings. Every meaningful finding needs context: what is wrong, which URLs are affected, why it matters, how confident you are, what should change, and how you will verify the fix.

After implementation, crawl again, retest representative URLs, confirm Search Console behaviour and compare performance with the baseline. An audit is complete only when the important fixes can be verified.