Technical SEO · Practical guide

A practical technical SEO audit checklist

A useful technical SEO audit starts with whether a page can be reached and understood. Work from the response to its metadata, then examine the signals that guide discovery and indexing. A score can organize findings, but the evidence behind each finding should decide what you fix.

Start with the page people should reach

Audit the intended public URL and check where its redirect chain ends. If you receive a login screen, an error page or a challenge instead of the content, resolve that access question first. Reading the title of the wrong response will not help you improve the intended page.

SiteAudit checks one page and its host; it does not crawl the entire site. Pick representative URLs from different templates, such as a homepage, article and product page. A successful homepage check does not establish that all templates share the same behavior.

Make the page’s purpose clear

Give each important page a descriptive title and a summary that matches its content. Google can use the title element when generating title links and may use a meta description for the search snippet. It can also choose other page text, so those fields are not a guaranteed preview.

Read the actual values in the audit. A title being present is different from it identifying the right page. Check for a copied homepage title, a staging label or a description that promises content the page does not contain.

Reference: Google Search Central: SEO starter guide

Review discovery and indexing signals together

Review the reported canonical reference, robots directives and sitemap evidence in the context of the page’s purpose. A public article and an internal account screen have different indexing requirements. Treat a warning as something to investigate, not an instruction to remove every restriction.

SiteAudit inspects the fetched HTML without rendering JavaScript. It does not establish whether Google has indexed the URL, what canonical Google selected or how the page ranks. Follow up in Search Console and a browser when those questions matter.

Turn findings into specific tasks

Each task should name the URL, observed value, intended result and a way to verify the change. Keep unavailable checks separate from confirmed failures; a timeout is a reason to retry or investigate access.

  1. Resolve access and connection failures that prevent the intended response from being inspected.
  2. Review indexing restrictions and canonical references against the page’s intended audience.
  3. Improve missing or misleading metadata in the responsible template.
  4. Run the same audit again, then sample other pages using the changed template.

Keep reading

Related guides