Technical SEO Audit Checklist (2026 Edition)

A technical SEO audit checklist gives you a repeatable way to find the problems that stop search engines from crawling, indexing and understanding your pages. Good content cannot perform if Google never sees it or picks the wrong URL to show.

After reading, you will be able to run a full audit area by area, record each issue with evidence, and sort your findings into a fix list your developer can act on.

We will use a hypothetical example throughout: InvoiceLeaf, a fictional B2B SaaS invoicing tool with a marketing site, a blog, a help center and a JavaScript-heavy pricing page.

What you need before you start

• Google Search Console with full access to the property, ideally a domain property that covers every subdomain and protocol.
• An SEO crawler that can export URLs, status codes, titles, canonicals and links.
• GA4 to see which pages earn traffic and conversions.
• A spreadsheet with columns for issue, affected URLs, evidence, impact, effort and owner.

Run one full crawl and save the export for every check below.

Crawlability: robots.txt, crawl errors and internal links

Check robots.txt

Open yoursite.com/robots.txt and read every Disallow rule. Confirm nothing important is blocked, including CSS and JavaScript files Google needs to render pages.

Robots.txt controls crawling only. Google's robots.txt introduction explains that a blocked URL can still be indexed if other pages link to it, so use noindex for pages that must stay out of search.

For InvoiceLeaf, the audit finds Disallow: /help/ left over from a staging setup. Google has not been able to crawl any help article.

Review crawl errors and server responses

In Search Console, open Settings, then Crawl stats. Look for spikes in server errors (5xx), timeouts and DNS problems. Repeated server errors can lead Google to slow down its crawling.

Audit internal links and orphan pages

Pages need internal links so crawlers can find them and understand how they relate. Check that:

• Important pages are reachable within a few clicks from the homepage.
• Links are standard HTML anchor links with an href attribute. Google may not follow links that only work through click handlers.
• No important page is an orphan, meaning nothing on the site links to it.

To find orphans, compare the URLs in your sitemap and GA4 landing pages against the URLs your crawler discovered through links. URLs in those lists but missing from the crawl are likely orphans.

Indexing: noindex, canonicals and duplicates

Read the Page indexing report

In Search Console, open Indexing, then Pages. The report lists why URLs are not indexed, such as "Excluded by 'noindex' tag," "Alternate page with proper canonical tag," "Duplicate without user-selected canonical" and "Crawled - currently not indexed."

Focus on excluded pages you want in search.

Check noindex tags

Export every URL with a noindex robots meta tag or X-Robots-Tag header from your crawl. Confirm each one is intentional. A noindex only works if Google can crawl the page, so do not also block those URLs in robots.txt.

Check canonical tags and duplicates

Each indexable page should have a self-referencing canonical, or point to the preferred version of a duplicate. Look for canonicals that point to redirected, broken or noindexed URLs.

Then use URL Inspection on key pages to compare your declared canonical with the Google-selected canonical. Google's guide to consolidating duplicate URLs describes a rel="canonical" annotation as a strong signal, so Google can still pick a different URL.

Control URL parameters

Sorting, filtering and tracking parameters can create large numbers of near-duplicate URLs. Search Console no longer has a URL Parameters tool, so handle this on the site: canonical parameter URLs to the clean version, keep parameter URLs out of internal links and sitemaps, and avoid linking to endless filter combinations.

Site architecture and URL structure

Review:

• Hierarchy. Group related pages under logical sections, such as /features/, /blog/ and /help/.
• URL format. Use short, readable, lowercase words separated by hyphens. Avoid session IDs and long strings of parameters.
• Consistency. Pick one version of each URL (HTTPS, with or without www, with or without a trailing slash) and redirect the others to it.

Page-level work such as titles, headings and internal anchor text belongs to on-page SEO. Our guide to on-page SEO elements covers that layer in detail.

Redirects and broken links

Filter your crawl by status code.

1. Redirect chains and loops. A chain is A redirects to B, which redirects to C. Update links and redirects so A points straight to the final URL.
2. Redirect type. Use permanent server-side redirects (301 or 308) for moved pages. Avoid JavaScript or meta refresh redirects where you can.
3. 404 errors. For internal links to missing pages, fix the link. For removed pages with backlinks or traffic, redirect to the closest relevant page.
4. Soft 404s. These are pages that return a 200 status but show "not found" or near-empty content. Search Console flags them in the Page indexing report. Return a real 404 or 410, or add useful content.

Avoid redirecting every deleted page to the homepage; Google may treat those as soft 404s.

XML sitemaps

Your sitemap should list the canonical, indexable URLs you want in search, and nothing else. Check that:

• It contains no redirected, 404, noindexed or non-canonical URLs.
• Each file stays within Google's limits of 50,000 URLs or 50 MB uncompressed, as described in Google's sitemap documentation. Larger sites use a sitemap index.
• The lastmod date reflects the last significant update; Google uses it only when consistently accurate. Google ignores priority and changefreq values.
• It is submitted in Search Console and referenced in robots.txt.

Compare the sitemap URL count with indexed pages in the Page indexing report. A large gap points to quality, duplication or crawl issues.

Page experience: Core Web Vitals, HTTPS and mobile

Core Web Vitals

Check the Core Web Vitals report in Search Console, which uses field data from real Chrome users. According to web.dev, a page passes when the 75th percentile of visits meets these "good" thresholds:

The report groups similar URLs, so one template fix can improve many pages. For InvoiceLeaf, every blog post shows poor CLS because ad slots and images have no reserved space.

HTTPS and mobile

Confirm every page loads over HTTPS with a valid certificate, HTTP URLs redirect to HTTPS, and no pages load mixed content.

Google uses the mobile version of a site's content, crawled with its smartphone agent, for indexing and ranking. Check that mobile pages show the same main content, headings, structured data and links as desktop.

JavaScript rendering

If content or links appear only after JavaScript runs, confirm Google can see them. In Search Console, run URL Inspection, click Test live URL, then open View tested page to check the HTML and screenshot.

InvoiceLeaf's pricing table loads from a script that is blocked by robots.txt, so the rendered HTML shows an empty table. Unblocking the script, or rendering the table on the server, fixes it.

Structured data validation

Test key templates with Google's Rich Results Test and review the enhancement reports in Search Console. Fix errors first, then warnings on properties that matter to you.

Structured data must match visible content on the page. Valid markup makes a page eligible for rich results, and Google decides whether to show them.

International SEO and hreflang

If you have localized versions, follow Google's localized versions guidance:

• Each language or regional version lists itself and every alternate.
• Annotations are reciprocal. If page A points to B, B must point back to A.
• Language codes follow ISO 639-1 and optional region codes follow ISO 3166-1 Alpha 2, such as en-us or es-mx.
• An x-default version is set for users who match no listed locale.
• Alternate URLs are fully qualified, including https://.

How to prioritize your technical SEO audit checklist findings

Score each finding on impact and effort, then work in this order.

1. High impact, low effort. Fix now. Examples: a robots.txt rule blocking a key section, a noindex on a money page, a broken main navigation link.
2. High impact, high effort. Plan and schedule. Examples: template-wide Core Web Vitals work, server rendering for JavaScript content, a URL restructure.
3. Low impact, low effort. Batch together. Examples: cleaning redirected URLs out of the sitemap, updating internal links to skip redirects.
4. Low impact, high effort. Defer or drop.

Judge impact by business value. A canonical error on ten pricing and product pages matters more than one on two hundred thin tag archives. GA4 conversions and Search Console impressions help you decide.

Summary checklist

After the audit

Turn the findings into work your team can ship:

1. Write each fix as a ticket with the issue, affected URLs, expected behavior and how to verify it.
2. Assign an owner and a target date, starting with the high-impact, low-effort group.
3. Run the full checklist again after major site changes, such as a redesign, CMS migration or URL restructure.

Our technical SEO audit service delivers a prioritized fix list ranked by impact and effort, with specs your developer can work from. Once the technical base is sound, on-page SEO work on existing pages and steady publishing, covered in how often to publish blog posts, give your content a better chance to be found.