technical seoseo auditwebsite auditingai visibilitycore web vitalsstructured data

Technical SEO Audit Checklist: 24 Website Bugs to Catch

A 24-check technical SEO audit checklist for documenting crawl, indexation, performance, structured-data, tracking, and AI answer-engine visibility issues with clear validation steps.

· 13 min read

A production Disallow: / rule, a homepage canonical inherited by thousands of pages, or a sitemap that lists redirected URLs can suppress visibility without changing a single page of copy. This technical SEO audit checklist gives SEO teams a defined set of 24 checks, so they can find affected templates, prioritize business-critical defects, validate fixes, and include AI answer-engine visibility in the same review.

The framework is based on a 24-day technical SEO and site-bug calendar shared in r/TechSEO. Its themes include crawl and indexation problems, canonical and redirect defects, sitemap hygiene, structured data, performance, and tracking. This article turns those themes into a numbered working checklist; checks 21–24 are clearly marked as broader audit additions, including AI visibility, rather than claims about the original calendar.

How to use this 24-point technical SEO audit checklist

Each of the 24 checks should produce an evidence record, not just a pass or fail. At minimum, record the URL or template tested, the observed response or markup, the number of affected pages where known, the owner, and the post-release validation method.

For example, “127 sitemap URLs redirect” is useful only when it is evidence from a real crawl. In this guide, all numerical scenarios are explicitly hypothetical unless stated as a source-backed fact. A real finding should identify the sitemap file, the redirect status, and the final destination URL.

The checks are arranged in four practical passes:

  1. Crawl and indexation: Can search engines access and select the intended pages?
  2. URL signals and rendering: Do canonicals, redirects, sitemaps, and templates agree?
  3. Experience and eligibility: Are pages performant, usable, and eligible for relevant search features?
  4. Measurement and AI visibility: Can the business measure outcomes and understand how its pages appear in answer-engine results?

Google differentiates crawl controls from index controls: robots.txt manages crawler access, while noindex is the supported mechanism for preventing an accessible page from appearing in Google Search. A blocked crawler may not be able to see a noindex directive placed in the HTML. Google’s robots and indexing documentation should be the reference point when these signals conflict.

Checks 1–6: crawlability and indexation controls

The first six checks cover faults that can remove otherwise valuable pages from organic discovery. A site with excellent content and a fast template still has a visibility problem if its core URLs cannot be crawled or indexed as intended.

  1. Check the live robots.txt file. Test the production file at /robots.txt, including user-agent groups, Disallow paths, and sitemap declarations. A Disallow: / rule is appropriate on many staging environments but is a critical production defect unless deliberately required.
  2. Check robots rules against important directories. Review paths such as /products/, /services/, /blog/, and locale folders. A rule blocking /product/ on an ecommerce site is more consequential than a rule blocking an internal search path.
  3. Find unintended meta noindex directives. Crawl key templates and compare their intended indexation state with <meta name="robots" content="noindex"> and related directives.
  4. Inspect X-Robots-Tag HTTP headers. Headers can apply noindex to HTML, PDFs, and other files even when page-source checks look clean. Google documents X-Robots-Tag as a supported indexing control.
  5. Identify contradictory robots and noindex signals. A page blocked in robots.txt but marked noindex cannot reliably communicate that indexation instruction to a crawler. Resolve the intended access and indexation state first.
  6. Compare intended pages with Search Console coverage. Review priority URL groups in Google Search Console to distinguish “not indexed” from pages intentionally excluded, redirected, or blocked.

A hypothetical example illustrates the evidence standard: if 40 service pages carry an unexpected X-Robots-Tag: noindex, the report should list the affected template, sample response headers, whether the tag is injected by the origin or CDN, and a re-crawl test after removal. It should not imply that all 40 pages were audited unless that occurred.

For CMS-specific causes, configuration matters. A WordPress plugin can output a page-level robots directive, while a Webflow collection template can apply an unintended setting across an entire collection. Auditors working in those systems can use Audra’s platform guides for WordPress SEO audits and Webflow SEO audits alongside this checklist.

Checks 7–12: canonicals, redirects, and XML sitemaps

Canonical tags, redirects, and XML sitemaps should tell a consistent story about each preferred URL. Google treats canonicalization as a set of signals, not an absolute instruction, but contradictory signals create avoidable ambiguity and often expose template or migration errors.

  1. Verify self-referencing canonicals on indexable pages. A canonical should generally identify the page’s intended primary URL, using the correct protocol, host, trailing-slash convention, and parameters.
  2. Find cross-page or homepage canonicals. A canonical that points every product or service page to the homepage is a high-risk template issue. Confirm whether consolidation is intentional before changing it.
  3. Check canonical destination health. Canonical URLs should not return 4xx errors, redirect, or carry noindex unless there is a documented special case.
  4. Identify redirect chains and loops. The source calendar highlights a three-hop redirect chain. In practice, investigate chains of two or more hops, then update internal links and sitemap URLs to the final 200-status destination.
  5. Review temporary versus permanent redirect use. A 302 or 307 may be appropriate for a short campaign or test, while a permanent URL move generally needs a 301 or 308 strategy. The intended duration, not the status code alone, determines whether it is a defect.
  6. Clean XML sitemap entries. Sitemaps should normally contain final, canonical, indexable URLs that return 200 status codes, rather than redirects, errors, noindexed pages, or duplicate parameter variants.

For a hypothetical sitemap with 5,000 URLs where 800 redirect, the action is not merely “fix redirects.” The team should identify the sitemap generator, replace stale entries with final URLs, update internal links where they still target old addresses, resubmit the file, and confirm the revised sitemap contains the expected final canonicals.

These checks are especially significant during a domain consolidation. Google’s site-move guidance calls out redirects, crawl blocks, noindex directives, crawl errors, and sitemap updates as items to monitor. For a step-by-step migration context, see how to consolidate two domains without losing SEO.

Checks 13–16: rendering, performance, and mobile templates

The original calendar includes performance defects. This section expands that theme into four repeatable checks, because a URL can be crawlable but still provide a poor rendered experience or fail to expose key content promptly.

  1. Confirm important content renders without fragile dependencies. Test a representative page with JavaScript enabled, and inspect whether the primary heading, body content, internal links, and key product or service details appear in the rendered HTML. The exact impact of JavaScript rendering varies by implementation and should be tested rather than assumed.
  2. Measure Largest Contentful Paint (LCP). Core Web Vitals defines good LCP as 2.5 seconds or less at the 75th percentile of page visits. Identify the actual LCP element: it may be a hero image, a heading, or a prominent product image.
  3. Investigate Interaction to Next Paint (INP). Long JavaScript tasks, expensive event handlers, and third-party scripts can delay interaction. Field data is more representative of visitors, while lab tools help reproduce and diagnose specific causes.
  4. Check Cumulative Layout Shift (CLS) and mobile layouts. Late-loading images, fonts, cookie banners, embeds, and injected promotions can cause layout movement. Review the most valuable templates at mobile viewport sizes, not just a desktop homepage.

Google’s Core Web Vitals documentation identifies LCP, INP, and CLS as the current metrics for loading, responsiveness, and visual stability. A performance report should separate lab data from field data and avoid promising that one score change will produce a ranking gain.

A hypothetical diagnosis might read: “The category template’s LCP element is a 2.1 MB hero image discovered late because it is injected by client-side JavaScript.” That is actionable because it points developers toward image delivery and discovery. “Performance score is low” is not.

These four checks include two themes in the original calendar—structured data and tracking—plus adjacent technical checks that make the audit more useful. Broken links and accessibility are broader additions to the source calendar, not represented here as its specific entries.

  1. Validate structured data against visible content. Test representative URLs in Google’s Rich Results Test and inspect JSON-LD for syntax, required properties, and consistency with what users can see. Valid markup creates eligibility, not a guarantee of a rich result.
  2. Check internal links and critical assets. Find 4xx and 5xx links, links to redirects, missing CSS or JavaScript, and failed image resources. Prioritize global navigation, breadcrumbs, category hubs, sitemap links, and high-traffic landing pages.
  3. Review accessibility defects as a separate quality workstream. Missing form labels, low contrast, invalid heading order, and incomplete alternative text affect users and can reveal weak templates. They should be reported clearly as accessibility findings, not misrepresented as a direct output of the 24-bug source calendar.
  4. Test analytics, consent, and conversion events. Confirm that analytics tags load once, consent handling behaves as intended, and essential events such as form submissions, phone clicks, purchases, or downloads fire correctly.

A hypothetical retailer may have valid Product markup on 1,000 URLs but outdated Offer prices on 50 pages. The issue is not “schema missing”; it is a mismatch between the product data source and visible price fields. Google’s structured-data policies require markup to represent page content accurately.

Similarly, a duplicated browser-side and server-side conversion event can double reported newsletter leads. That is not a direct ranking issue, but it can distort the evaluation of organic search performance. Record the browser, consent state, test URL, event name, and observed result so another person can reproduce it.

Checks 21–24: AI answer-engine visibility additions

The final four checks are Audra-oriented additions to a conventional technical audit. They are not presented as items from the r/TechSEO calendar. They matter because a website can be technically accessible to traditional search crawlers while its brand, pages, or claims have weak visibility in AI answer-engine responses.

  1. Test priority questions in relevant answer engines. Use real commercial, informational, and comparison queries that a prospective customer would ask. Record whether the brand is mentioned, whether a first-party page is cited or linked, and which competing sources appear.
  2. Compare cited pages with intended landing pages. If an answer engine cites an old blog post instead of a current product or service page, assess whether the intended page clearly answers the same question, is internally prominent, and presents current evidence.
  3. Check factual consistency across high-value pages. Review pricing qualifiers, product specifications, service areas, policies, and organization details across the pages most likely to support AI answers. The exact way any answer engine selects sources is not fully disclosed and varies by product, so results should be treated as observed visibility data rather than a ranking guarantee.
  4. Track changes after material releases. Re-run the same query set after a migration, major content revision, template change, or structured-data rollout. Compare brand mentions, cited URLs, competitor presence, and the accuracy of the generated answer.

Audra is designed as a local desktop auditing app that combines answer-engine visibility checks with technical SEO, performance, accessibility, best-practice, and link findings. That combined view helps an agency explain, for example, that a page absent from answer-engine citations may also have an indexation conflict, weak internal linking, an outdated canonical target, or simply insufficiently direct content for the tested query.

AI visibility results should be documented with the date, answer engine, exact query, country or language settings where available, response text, cited URLs, and screenshots. As of November 2026, answer-engine outputs can vary over time and by context, so a single query run is evidence of an observation, not proof of a permanent position.

Prioritize fixes by scope, visibility, and business value

A 24-item checklist should not become a 24-item queue with equal priority. The sensible order depends on scope, commercial importance, user impact, confidence in the diagnosis, and the safety of the proposed fix.

A practical triage model uses these four dimensions:

  1. Scope: Does the defect affect one URL, one template, or an entire domain?
  2. Visibility impact: Does it block crawling, indexing, rendering, canonical selection, rich-result eligibility, or answer-engine source selection?
  3. Business impact: Does it affect revenue pages, lead journeys, established organic traffic, or a key customer question?
  4. Effort and confidence: Can the owner implement and validate the fix safely in the current release cycle?

For example, a hypothetical homepage canonical inherited by 2,000 location pages is likely high scope and high visibility risk. A missing image dimension below the fold may be lower priority unless it creates measurable CLS on a heavily visited template. Similarly, a missing brand citation for a strategic AI query deserves investigation, but it should not outrank a live sitewide noindex directive.

The resulting issue statement should name the action and evidence: “Remove the unexpected X-Robots-Tag from 83 commercial URLs” is stronger than “indexability issue.” Counts such as 83 should only be included when measured in the audit; otherwise describe the issue as a template-level risk. For more detail on assigning order and ownership, Audra’s guide to technical SEO audit prioritization provides a complementary framework.

Turn the 24 checks into release controls

The checklist becomes more valuable when it is reused before and after releases. A redesign affecting six templates, a plugin update, a CMS migration, or a domain move can all reintroduce robots, canonical, rendering, schema, performance, and analytics defects.

For each release, select the relevant checks rather than rerunning every test blindly. A sitemap generator change should trigger checks 10–12; a product-template change should trigger checks 13–18; a new consent platform should trigger check 20. Material changes to key landing pages should also prompt the answer-engine comparison in checks 21–24.

Maintain an issue log with the discovery date, sample URLs, template or system owner, severity, evidence, expected fix date, and validation result. The client-ready report can then show all 24 checks as passed, failed, not applicable, or awaiting validation. This makes the central promise of the checklist concrete: teams know exactly which of the 24 checks were completed and what remains.

FAQ

How do you work through all 24 technical SEO audit checks?

Start with checks 1–6 for crawlability and indexation, then complete canonicals, redirects, and sitemaps in checks 7–12. Continue through rendering, performance, structured data, links, and tracking before running the four AI visibility additions. Mark every check as passed, failed, not applicable, or awaiting validation, with at least one URL or template sample as evidence.

Which of the 24 checks should be fixed first?

Fix sitewide crawl and indexation failures first, including production robots blocks, accidental noindex, and broken canonical templates. Next address redirect loops, invalid sitemap entries, and defects on revenue-generating or high-traffic templates. Performance, schema, tracking, accessibility, and AI visibility findings should then be prioritized by measured scope, user impact, and commercial importance.

Are the AI answer-engine checks part of a standard technical SEO audit?

Not traditionally. Checks 21–24 are an explicit expansion of the 24-bug source calendar because AI answer-engine visibility has become relevant to how audiences discover brands and pages. They do not replace crawl and indexation work; they add query-level evidence about brand mentions, cited pages, competitors, and answer accuracy.

Does robots.txt prevent pages from appearing in Google?

Not reliably. Robots.txt manages crawling, while noindex is used to request that an accessible page not be indexed. If crawling is blocked first, Google may not see a page-level noindex. Private content should use suitable authentication or access controls rather than relying only on robots.txt.

Does valid structured data guarantee rich results or AI citations?

No. Valid structured data can make a page eligible for certain Google search features, but Google does not guarantee display. It also does not guarantee citation or mention in an AI answer engine. Markup should match visible content, meet the relevant guidelines, and be retested after template changes.

Sources