How to Perform a Website SEO Audit

Identify the public site, important business tasks, and people responsible for content and technical changes. Record whether you are reviewing a handful of priority pages or an entire set of templates. Include examples of each relevant page type. A homepage-only review should be labeled as such; it cannot establish the condition of every product, article, or localized page.

Set a deliverable before collecting data. A useful issue record includes the affected URL, observed behavior, evidence, likely scope, owner, priority, and acceptance check. Preserve private account areas and customer information outside the public audit. If access is required for a diagnostic tool, use authorized reporting access and avoid placing sensitive details in a shared editorial worksheet.

Build a list from the site's content inventory, navigation, sitemap, and available search reports. Compare these sources rather than treating any one as complete. Mark the intended purpose of each important URL. This reveals discrepancies such as a published guide absent from navigation or an old destination still referenced by several service pages.

Check a representative sample manually before scaling the process. Confirm that the addresses resolve to the expected content, identify unexpected redirects, and note errors. Distinguish an intentionally removed page from a broken link to a page that should exist. The remediation differs: one may need links updated, while the other may require restoring an approved destination.

For the next part of this investigation, see a page improvement workflow.

For approved public pages, inspect whether internal links provide a path to the content and whether indexing instructions match the intended publication state. Where available, use the site's verified search tools to investigate specific indexing questions. An XML sitemap is a discovery aid, not evidence that every listed page has been indexed or will receive search traffic.

Check the preferred URL when duplicate or alternative addresses exist. Redirects, canonical declarations, navigation, and sitemap entries should tell a coherent story. Do not remove intentional restrictions from login, account, or draft pages to make a crawler report appear cleaner. An audit must preserve the distinction between discoverable editorial material and information that should remain private.

Review the visible heading, introduction, sections, and next action. Ask whether the page answers the task described by its title. Look for incomplete instructions, outdated service details, unexplained terminology, and unsupported claims. Automated checks can flag missing elements, but a present heading or a long body does not prove the information helps somebody.

Examine the actual HTML delivered in the browser as well as content settings. Confirm that the title, description, and canonical belong to that page, and that structured data describes what is visible. A publishing form may contain the correct values while a template renders something else. Record the discrepancy at the rendered URL so the responsible developer can reproduce it.

Follow links within the article and through the header and footer. Check fragments that jump to sections as well as links that open another page. A destination returning an error is a different defect from a valid destination answering the wrong question; both deserve a clear description. Avoid treating a successful status code as a complete content review.

At narrow and wide screen sizes, inspect headings, breadcrumbs, lists, cards, and calls to action. Watch for clipped text, oversized media, and controls that interfere with reading. Verify that meaningful images load. If performance needs investigation, use measurements suited to that question and retain their conditions. A single scanner request is not a substitute for a broader assessment of real visitors' experience.

To connect this finding to a specific decision, use the search measurement workflow.

Look for repeated template problems before creating one task per URL. A missing canonical across a page family may need a shared rendering fix, whereas an inaccurate explanation on one service page may need an editor. Grouping by cause makes the backlog smaller and helps avoid contradictory repairs by different owners.

Prioritize confirmed obstacles to a useful public page, then issues affecting important reader tasks, then lower-impact refinements. Include uncertainty in the assessment. A severe-sounding warning without reproducible evidence should trigger investigation, not immediate destructive changes. For each priority, state the consequence in plain language: a reader cannot reach the guide, distinguish the offer, or complete the promised instruction.

Write what will demonstrate that the issue is resolved. For a broken internal link, verify both the corrected reference and the receiving page. For a template metadata repair, inspect examples across the affected family. For a publication restriction, verify approved pages remain public and excluded pages remain excluded. This prevents a narrow fix from creating a different problem elsewhere.

Keep a rollback artifact for changes that affect routing or rendering. After deployment, repeat the checks on the live site and retain the result alongside the task. Close the implementation issue when those conditions are satisfied. Any later assessment of search performance belongs in a separate observation window, with the release date and other relevant events attached.

For the related planning question, read which SEO metrics to select.

Present the scope, the most consequential confirmed findings, unresolved questions, and the next owners. Include examples and evidence without burying the team in every raw crawler line. A good summary makes clear what was not inspected so a limited review is not mistaken for a complete technical certification.

BrandLens can contribute selected website observations to an initial review; verify important findings at the affected page and use additional tools when the audit question requires them. Finish by scheduling the first repair and its acceptance check. An audit earns its value when the findings become verified improvements, not when the report contains the largest number of warnings.

For the wider brand context, consult How to Perform a Brand Visibility Audit.