Technical SEO audit checklist

Use this free checklist to find where a page becomes hard to discover, crawl, render, or index. Start with public checks you can run in Chrome, then use Search Console for the pages you manage.

Pick pages and record their expected behavior

Choose the homepage, an important landing page, and a page from each major template. Add an older URL that should redirect, a page meant to stay out of search, or a missing URL where those cases matter. For each URL, write down its intended final URL, which page should be canonical, and whether it should be eligible for indexing. Keep this list for the retest.

Run the public checks in order

  1. Check the response and redirect chain. Open the URL in a signed-out browser. In Chrome DevTools, open Network, enable Preserve log, and reload. Filter to document requests. Record the response codes and final URL. A page you want indexed should be accessible and return 200. On pages that have moved, check that the chain ends on the expected live page. Confirm that genuinely missing pages return 404 or 410. A missing-page message with a 200 response can be treated as a soft 404. Google’s HTTP status guidance
  2. Check crawl rules and indexing directives. Open /robots.txt on the final origin and look for rules that apply to Googlebot and the path you tested. In Network, inspect the final document’s X-Robots-Tag header. Check raw HTML and the rendered document for a robots or Googlebot meta tag. A blocked crawl can prevent Google from seeing a noindex directive, so record crawl access and indexing directives separately. Google’s robots directives
  3. Check what Chrome can render on mobile. Use the device toolbar and reload the same page. Compare the document response in Network with the rendered DOM in Elements. Look for the main text, headings, and links that should be there. Record missing content and failed script or data requests. A successful local render tells you what your browser saw. If you manage the site, use URL Inspection to see what Google’s fetch rendered. Google’s JavaScript SEO guidance
  4. Compare canonical signals. Open the declared canonical URL and confirm it resolves to the intended, indexable page. Check whether the canonical found in HTML or the HTTP Link header agrees with your intended URL, internal links, and sitemap entries. On sites you manage, note both the declared canonical and the Google-selected canonical from the stored URL Inspection result. Google’s canonical guidance
  5. Check discovery from links and sitemaps. Follow an internal link from an existing page to each important URL. Inspect it in Elements and check for an anchor with a usable href. Open the XML sitemap or sitemap index and spot-check that important intended canonical URLs appear and resolve successfully. Investigate unexpected redirects, errors or noindex pages in the sitemap. This shows how a page can be discovered. Search Console can tell you whether Google has indexed it. Google’s crawlable link guidance · Google’s sitemap guidance
  6. Check page-type signals once access and rendering work. For a page that uses product or article markup, run the URL in Google’s Rich Results Test and compare key fields with the visible page. Look for markup errors that matter to that page type. For a loading problem, use a Chrome performance trace or Lighthouse for diagnosis and check real-user data in PageSpeed Insights when available. Record the lab result and field data separately. Google’s structured data guidance · Google’s Web Vitals guidance

Keep the finding and the retest together

Use one worksheet row per URL, check, and audit round. Save an evidence reference such as the public URL, response header, screenshot, or inspection date. Compare the result with the expected state and mark it pass, issue, unknown, or not applicable. Start with issues that affect important intended indexable pages, especially accidental blocks or missing rendered content across a template.

After an approved fix, repeat the same check on the same URL and a representative unaffected page. Keep the original row and add a retest row with the change reference. When you have access to the matching Search Console property, compare its live test with its stored result. The live test describes access and rendering now. The stored result is the evidence for Google’s last recorded state. A successful retest can precede Google’s next crawl and index update. Search Console URL Inspection

Choose an audit workflow

The Browser SEO Audit Kit runs 11 read-only public-page checks through Chrome and saves local evidence. The Technical SEO & Indexing Kit adds more diagnostic tasks and read-only Google inspection workflows for an authorized Search Console property.

To study brand mentions, source links, and what the linked pages support, use the AI search visibility audit.