In this article
A technical SEO audit in 2026 covers far more ground than it did three years ago. Crawlability, Core Web Vitals, AI crawler permissions, and schema delivery via Rank Math are now baseline requirements, not advanced considerations. This checklist walks through every layer, and closes with the questions you should be asking your agency each month to confirm they are actually doing the work.
Contents
What is a technical SEO audit?
Crawlability: why AI crawlers matter now
Indexability checklist
Core Web Vitals and page experience
Schema and structured data
Rankability: internal links, content clusters, E-E-A-T
What should your agency be showing you?
FAQ
Picture a marketing manager at a growth-stage retail brand opening Google Search Console on a Monday morning. The Coverage report shows 847 pages submitted. Only 591 are indexed. That is 30% of the site’s inventory sitting invisible to Google, generating no traffic, earning no revenue. The site looks fine in a browser, and the developer says nothing is broken; but the technical foundation is quietly leaking.
That scenario plays out across Australian businesses every week, and a proper technical SEO audit is the only reliable way to surface it. The audit does not touch content quality or backlinks; those are separate disciplines. It covers the infrastructure that determines whether search engines and AI models can find, read, and trust your pages at all.
What is a technical SEO audit?
A technical SEO audit is a systematic review of the technical infrastructure of a website (crawlability, indexability, page experience, structured data, and site architecture) to identify issues that prevent search engines and AI models from correctly discovering and ranking the site’s content.
The scope has expanded significantly since 2021. Core Web Vitals became a confirmed Google ranking signal in June 2021. Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. And from mid-2023 onwards, a new category of crawler arrived: AI bots from OpenAI, Anthropic, and Perplexity that index content for citation in AI-generated answers. Your robots.txt now needs a deliberate stance on each of them.
A well-run technical audit in 2026 touches six layers: crawlability, indexability, page experience (including Core Web Vitals), structured data, site architecture, and AI crawler access. Skipping any one of them leaves a gap that compounds over time. The checklist below covers each layer in the order an experienced SEO team would work through them.
Crawlability: why AI crawlers matter now
Crawlability determines whether search engine bots and AI models can physically reach and read your pages. If they cannot get in, everything else on this checklist is irrelevant. The crawlability review covers your XML sitemap, robots.txt file, crawl budget management, site architecture depth, and redirect chains; but in 2026 it must also include an explicit decision about AI crawler access.
Google’s Googlebot remains the primary crawl priority. But three other crawlers now have a measurable effect on brand visibility: GPTBot (OpenAI’s training and indexing bot), ClaudeBot (Anthropic’s crawler, which feeds Claude’s web search), and PerplexityBot (which drives Perplexity’s real-time citation engine). If these bots are blocked (either deliberately or by an overly broad Disallow: / rule written years ago), your brand will not appear in AI-generated answers, even when those answers directly serve your target audience.
AI CRAWLER DECISION: ALLOW OR BLOCK?
The default recommendation for most Australian brands seeking visibility is: allow all AI crawlers. Being in AI training data means AI models learn about your brand at a foundational level. Being indexed by AI search crawlers means your content appears in real-time AI-generated answers. There is no visibility upside to blocking them.
Check your robots.txt for these user-agent strings and ensure none are blocked:
GPTBot: OpenAI training and ChatGPT Search indexingOAI-SearchBot: ChatGPT real-time search resultsClaudeBot: Anthropic training and Claude web searchPerplexityBot: Perplexity real-time citation engineGoogle-Extended: Gemini training and AI OverviewsApplebot: Apple Intelligence and Siri
Beyond crawler access, the crawlability audit checks: XML sitemap accuracy and submission (both Google and Bing Webmaster Tools), crawl budget allocation for large sites with 10,000+ pages, redirect chain length (chains longer than two hops slow Googlebot and waste crawl budget), and site depth (key pages sitting more than three clicks from the homepage are routinely under-crawled). For brands wanting maximum AI citation visibility, Shout Digital also runs a dedicated AI search audit that maps citation gaps across ChatGPT, Gemini, Claude, and Perplexity simultaneously.
Indexability checklist
A page that can be crawled is not automatically indexed. Indexability is a separate layer, and the most common errors here are silent: no error message, no warning, just a page that does not appear in search results.
The indexability audit works through the following in sequence:
Scan every page’s HTML <meta name="robots"> tag and HTTP headers for noindex directives. CMS migrations and staging environments routinely leave noindex rules active on production pages. A single misconfigured template can delist hundreds of category or product pages overnight.
Every page should have a self-referencing canonical tag. Incorrect canonicals (pointing product pages to category pages, or pointing to the wrong domain variant) tell Google to suppress the page you actually want ranking. Audit canonical chains: a canonical pointing to a page that itself has a different canonical is a dead end for Googlebot.
robots.txt controls crawl access at the server level. A syntax error or an overly broad Disallow rule can silently block entire directories. Validate the file against Google’s robots.txt documentation and test specific URLs using Google Search Console’s robots.txt Tester tool.
For sites serving multiple regions or languages, hreflang must be bidirectional: every page it references must reference it back. Broken hreflang loops cause Google to ignore the entire tag set, meaning the wrong regional version ranks in the wrong market. This is among the most commonly broken elements on multi-region Australian ecommerce sites.
Soft 404s are pages that return a 200 HTTP status but display no meaningful content; Google’s quality systems now detect and suppress these. Redirect chains longer than two hops dilute link equity and slow crawling. Both require a full URL-level crawl (Screaming Frog or Sitebulb are the standard tools) rather than a visual inspection.
Google Search Console’s Index Coverage and Page Indexing reports are the fastest way to see indexability issues at scale before running a full crawl. If you are unfamiliar with how to read these reports, our intro to Google Search Console covers the core reports and how to interpret them.
Core Web Vitals and page experience
Core Web Vitals have been a confirmed Google ranking signal since June 2021, and the metric set was updated in March 2024 when Interaction to Next Paint (INP) replaced First Input Delay (FID) as the responsiveness measure. Any technical audit that still references FID as the third Core Web Vital is working from an outdated checklist.
Source: Google Core Web Vitals documentation, updated March 2024.
The audit pulls CWV data from two places: Google Search Console’s Core Web Vitals report (which shows field data from real users) and PageSpeed Insights (which combines field data with lab diagnostics). The field data in GSC is authoritative for ranking purposes: it reflects actual user experience, not a synthetic test. Lab data from PageSpeed Insights tells you why a metric is failing, which is what the development team needs to fix it.
Common failure patterns in 2026 audits: LCP failures caused by unoptimised hero images lacking proper preload hints; INP failures driven by third-party tag managers firing synchronously on interaction; CLS failures from ads, embeds, or fonts loading without reserved space. Each requires a different fix, which is why the audit must diagnose root causes rather than just report scores.
Page experience also covers HTTPS, mobile-friendliness, and the absence of intrusive interstitials. These are not new, but they remain in scope and are checked as part of every audit Shout Digital runs for SEO clients.
Schema and structured data
Structured data (schema markup) tells search engines and AI models what a page’s content means, not just what it says. In 2026, the delivery method matters as much as the schema type itself. The old approach of copying JSON-LD from schema.org and pasting it into a page’s source code by hand is no longer the standard for a professionally managed WordPress site.
Rank Math’s Schema Manager (included in Rank Math Pro, which is the SEO plugin on WordPress sites managed by Shout Digital) provides a visual interface for adding and editing schema without touching code. It supports Article, FAQPage, HowTo, Product, Service, LocalBusiness, and Organization schema types, with each field mapped to a CMS field so schema stays in sync with content edits automatically.
PRIORITY SCHEMA TYPES FOR 2026
- Organization: Must be present on the homepage with name, URL, logo, description, founding date, and sameAs links to LinkedIn, Crunchbase, and Google Business Profile. This is the cornerstone of your entity graph.
- Article / BlogPosting: Every blog post needs headline, author (with Person schema and a LinkedIn sameAs link), datePublished, dateModified, and publisher. This is the primary schema type driving AI citation.
- FAQPage: Google restricted FAQ rich results to health and government sites in 2023, but FAQPage schema is still highly extractable by AI models. Pages with FAQ schema appear more frequently in AI Overviews.
- HowTo: Step-by-step content with HowTo markup gets preferential extraction for procedural queries in both Google and AI search engines.
- Service: Each service page should have its own Service schema with name, description, areaServed, and provider linked back to the Organization schema.
One rule that catches many sites out: every fact in your schema must also appear in the visible HTML content. If you add foundingDate: "2009" to your Organization schema, the page body must also state when the company was founded. AI crawlers extract information from visible text first. Schema reinforces on-page content for search indexes; it does not introduce new facts that AI models will pick up independently.
Rankability: internal links, content clusters, E-E-A-T
Rankability is the layer of technical SEO that sits between pure infrastructure and content strategy: it covers how well your site’s architecture signals authority to Google, and how clearly it communicates expertise, experience, authoritativeness, and trustworthiness (E-E-A-T).
The practical checks in this layer:
| What to check | What good looks like | Common failure |
|---|---|---|
| Internal link structure | Key pages reachable within 3 clicks; pillar pages receive the most internal links | Orphan pages; links only in nav, none in body copy |
| Content cluster integrity | Each cluster topic has one pillar page and 5–10 supporting posts linking back to it | Supporting content that never links to the pillar; siloed topics |
| Author attribution | Named authors with biography pages, credentials, and LinkedIn sameAs in Person schema | Posts with no author, or “Admin” as author with no credentials |
| URL structure | Descriptive slugs that match the target keyword; consistent URL depth | Query-string URLs, random IDs, or slugs that contradict the page’s content |
| Duplicate content | No substantive duplicate pages; parameter URLs excluded via canonical or robots.txt | Faceted navigation generating thousands of near-duplicate category pages |
E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is not a direct ranking factor in the sense that Google has a single score for it. It is a framework Google’s quality raters use to evaluate pages, and it influences how the algorithm treats sites over time. The technical components that support strong E-E-A-T signals: named author markup in schema, a published About page with real credentials, consistent NAP (Name, Address, Phone) data across the web, and HTTPS throughout. For a deeper treatment of how Google evaluates authority, see our post on improving Google rankings with E-E-A-T and topical authority.
What should your agency be showing you?
A technical SEO audit is only as valuable as the reporting that follows it. If your agency delivers a 200-point checklist with no prioritisation, no estimated impact, and no clear owner for each fix, the audit has not done its job. Here are the deliverables and monthly reporting cadence that separates serious technical SEO work from a box-ticking exercise.
A prioritised issue list (P1/P2/P3 severity) with the estimated ranking impact of each fix, the effort to resolve it, and a named owner (agency vs. client dev team). Not a raw Screaming Frog export; a curated, interpreted brief that a non-technical marketing manager can read and action.
Every month, your agency should show you the GSC Page Indexing report: how many pages are indexed, how many are excluded, and which exclusion reasons are growing or shrinking. A rising “Crawled (currently not indexed)” count is a signal worth investigating; a rising “Discovered (currently not indexed)” count may indicate a crawl budget problem.
Your agency should be tracking the percentage of URLs passing all three Core Web Vitals (LCP, INP, CLS) over a 90-day rolling window, segmented by page type. A drop in passing URLs after a site update is a red flag that requires immediate diagnosis. Improvements should be quantified: “URL pass rate improved from 41% to 73% following hero image preload optimisation.”
At least quarterly, your agency should confirm whether GPTBot, ClaudeBot, PerplexityBot, and OAI-SearchBot are permitted in your robots.txt, and whether your brand is appearing in AI-generated answers for your target queries. This is a new reporting category that most agencies are not yet covering. Shout Digital includes it as standard in the AI search service.
An issue logged is not an issue resolved. Your agency should close the loop by re-crawling after each development sprint and confirming (with before/after data) that the issue is genuinely fixed and the fix has not introduced new problems. This is where most technical SEO programmes break down: the audit finds the problems; nobody verifies the solutions.
FAQ
Common questions from marketing managers and heads of digital about technical SEO audits in 2026.
Updated June 2026. Shout Digital is a Melbourne-based digital marketing agency offering SEO, SEM, social media, and AI search visibility services for growth-stage and established Australian brands. For related reading, see our intro to Google Search Console and our guide to improving Google rankings with E-E-A-T and topical authority.
We are digital marketing experts
