Technical SEO Checklist 2027: 105 Checks for AI Search

Ishant
Published on November 12, 2026
Ishant
Ishant Sharma is the Founder and CEO of Hustle Marketers, a Google Partner digital marketing agency. Working in Google Ads, Meta Ads, SEO and ecommerce PPC since 2013, he has helped 2,500+ brands generate $780M+ in trackable sales. Upwork Top Rated Plus with 100% Job Success Score. Ishant Sharma is the digital marketing specialist, not the Indian cricketer of the same name.

Summarize this article with:

Most technical SEO checklists still audit for one reader. That reader is Googlebot. But your pages now get judged by a second group as well, and that group behaves nothing like a search crawler. For example, GPTBot, OAI-SearchBot, PerplexityBot and ClaudeBot arrive with less patience, weaker rendering and different goals. Some of them never arrive at all, yet still quote you. This checklist covers all 105 checks we run on client sites, split across 18 categories. Every item tells you why it matters and how to check it, so you can hand the list straight to a developer. For the strategy sitting on top of these fixes, see what Google documents about AI search and what it stays silent on.
The shift nobody has priced in yet is this: AI systems are not simply crawlers you allow or block, they are users who have to read your page, render it, and increasingly act on it.

Updated for 2027: we rechecked this list against Google and Microsoft documentation changes published through October 2026. The count is still 105 checks in 18 categories. What moved is in the new section on what changed in technical SEO for 2027, including the new Search Console control and report for AI Overviews and AI Mode. This edition also corrects how Google treats 404 and 410 responses and what blocking ClaudeBot does, and it adds hreflang checks, platform notes and a symptom-to-check troubleshooting table.
Key Takeaways
- 105 checks, 18 categories, 4 priority levels. Every item states why it matters and exactly how to check it, and the first 75 are infrastructure checks while the last 30 cover keyword, content and link diagnostics.
- Fix these four first: the four-variant redirect test on a deep URL, the
filetype:search for exposed documents, each AI user agent line in robots.txt, and your crawled-but-not-indexed ratio. Under an hour combined, so start there. - Ten things here appear in no other published technical SEO checklist we audited, including the log file method for finding rendering gaps, accessibility tree testing, agent commerce readiness, and why you get cited by bots that never visit you.
- llms.txt is not robots.txt for AI. Three widely-shared checklists get this wrong, while Google now says Google Search ignores the file. Add it if you want, but do not count it as strategy.
- Do not noindex thin pages. Noindex still leaves them crawled and still counted in sitewide quality. Instead, remove them or improve them.
- Short on time? The 50-item version for small sites is near the end, and it still covers roughly 90% of the risk.
What Is a Technical SEO Checklist and Who Needs One
A technical SEO checklist is a repeatable list of infrastructure checks that confirm search engines and AI systems can reach, read, render and trust your website. It sits underneath content and links. When it breaks, nothing above it works.
You need one in four situations. First, before a migration or replatform. Second, when organic traffic drops without an obvious content cause. Third, when you inherit a site and have no history on it. Fourth, on a fixed cadence, because technical debt accumulates quietly as a site grows.
In general, run the full 105 checks quarterly on a large site. On a small brochure site, however, run the 50-item short version twice a year. Then use SEO automation tools to monitor the critical items monthly.
How This Checklist Is Prioritised
Every check carries one of four labels. So treat them as a work order, not a suggestion.

| Priority | What it means | Fix window |
|---|---|---|
| Critical | Blocks crawling, indexing or revenue right now | Same week |
| High | Costs rankings or crawl efficiency at scale | Within 30 days |
| Medium | Compounding drag, but cheap to fix in batches | Within the quarter |
| Low | Housekeeping or speculative upside | When capacity allows |
Technical SEO vs On-Page SEO: Where Does Each Check Belong?
Technical SEO covers whether search engines and AI systems can reach, render, index and trust your pages, while on-page SEO covers what each page says and targets. In this checklist, checks 1 to 75 are technical infrastructure, and checks 76 to 105 are the keyword, content and link diagnostics that sit on top of it.
We keep all 105 in one list because an audit fails when two teams run the halves and never compare notes. For example, a page can pass every crawl check and still miss, simply because it targets the wrong intent. So the table below shows where each group sits and who usually fixes it.
| Layer | Categories | Checks | Usually fixed by |
|---|---|---|---|
| Access and crawling | Setup and access, crawlability, indexation, robots and directives, duplicate content and canonicals, site architecture | 1 to 39 (39 checks) | SEO lead and developer |
| Rendering, speed and security | Rendering and JavaScript, speed and Core Web Vitals, server and security, mobile | 40 to 50 (11 checks) | Developer and hosting team |
| Templates and markup | On-page technical, structured data | 51 to 61 (11 checks) | Developer and SEO lead |
| AI and agent layer | Logs and monitoring, AI search, agent readability | 62 to 75 (14 checks) | SEO lead and developer |
| Beyond technical | Keyword and intent, content quality, off-page | 76 to 105 (30 checks) | Content and outreach teams |
That split also explains the count: the title says 105 because every numbered row on this page is a check you can pass or fail, and 75 of them are strictly technical. If you only need the infrastructure audit, stop after check 75. However, when a page is indexed but still not winning, the last 30 usually tell you why. For a shorter view of what Google itself requires, see our page on technical SEO requirements.
What Changed in Technical SEO for 2027?
Three things changed how this checklist runs going into 2027. Google added a site-wide Search Console control and a performance report for AI Overviews and AI Mode, Google published guidance that rules out several popular AI tactics, and Microsoft added Copilot citation reporting to Bing Webmaster Tools. However, none of them adds a new crawl or index requirement. Instead, they change how you run checks you already have.
Here are the dated changes that matter most, as well as the checks on this list each one touches. After that, a second table lists the smaller documentation changes.
| Date | What changed | Checks affected | What to do |
|---|---|---|---|
| February 10, 2026 | Microsoft launched the AI Performance report in Bing Webmaster Tools (public preview): Total Citations, Average Cited Pages, Grounding Queries and page-level citation activity across Copilot, Bing AI summaries and select partners | 2, 16, 71 | Claim the site in Bing Webmaster Tools and record a citation baseline before you change anything |
| May 7, 2026 | FAQ rich results stopped appearing in Google Search. Google then removed the documentation on June 15, 2026 | 56, 61 | So stop counting FAQPage as a deliverable, as the structured data section explains |
| May 15, 2026 | Google published its guide to optimizing for generative AI features. It also says you do not need AI text files, special markup or Markdown, and you do not need to break content into tiny pieces | 66, 72 | Keep llms.txt at Low priority, and also do not split pages into fragments for AI |
What Changed for Spam, AI Controls and Reporting?
| Date | What changed | Checks affected | What to do |
|---|---|---|---|
| May 15, 2026 | Google clarified that its spam policies also apply to generative AI responses in Search | 89, 95 | Treat content made only to steer AI answers as a spam risk rather than a shortcut |
| June 3, 2026 (all websites by August 31, 2026) | Google announced a Search generative AI control in Search Console that includes or excludes a site from AI Overviews, AI Mode and generative AI features in Discover, plus a Generative AI performance report that shows impressions by page, country, date and device | 25, 67 | When you check AI access in robots.txt, confirm the control is set to include, then use the report to see which pages appear in AI answers |
| October 26, 2026 | Google updated its guidance on preventing user-generated spam, such as blocking indexing of link-shared content and monitoring abuse in Search Console | 8, 10 | Also add user-generated and link-shared URL patterns to your spam URL review |
| Current definition | GA4’s default channel group includes an AI Assistant channel for referrals from sources such as ChatGPT, Gemini, Deepseek, Copilot and Grok. However, it does not include Google’s AI Overviews or AI Mode | 3 | Confirm the AI Assistant channel shows up in your acquisition reports, but do not expect Google AI features there |
The full list of Google’s dated changes is on the Search Central documentation updates page, which is worth a monthly look if you run audits for a living.
Which of These Changes Should You Add to Your Audit First?
The June 3 row is the one to add to your audit today. After all, a site-wide switch that removes you from AI Overviews and AI Mode is the kind of setting one person changes once and everyone forgets. Google says the control is not used as a ranking or inclusion signal for other parts of Search, and that changes generally take a few days to apply, so record its state every time you run check 25.
Similarly, the reporting rows matter for the same reason. Search Console’s Generative AI performance report shows impressions only, for AI Overviews and AI Mode combined, with no clicks or queries, and it may not appear at all on a site with too few AI impressions. So your AI visibility picture still has to be built from several sources. Our guide on how to improve brand visibility in AI search shows how to combine them, and tracking brand mentions in AI search covers the manual prompt method.
Which Other Google Documentation Changes Touch These Checks?
Smaller documentation changes matter too, because each one shifts how a specific check runs. Google’s Search Central changelog and blog list these (checked October 29, 2026).
| Date | What changed | Checks | What to do |
|---|---|---|---|
| December 15 to 18, 2025 | Google may skip rendering when a page has a noindex tag or a non-200 status | 22, 41, 59 | Set robots tags and canonicals in raw HTML rather than with JavaScript |
| March 31, 2026 | Googlebot reads only the first 2MB of an HTML file, and Google moved its crawler IP range files | 40, 48 | Keep key tags high in the HTML, then use the new IP files before you block bots |
| April 13, 2026 | Back button hijacking became an explicit spam violation, enforced from June 15, 2026 | 46 to 49 | Review ad and library scripts when you run the security pass |
| June 15, 2026 | Google said Google Search ignores llms.txt files | 72 | Keep llms.txt at Low priority, since only other services might use it |
| June 17, 2026 | Site move guidance now covers Change of Address for every www and non-www variant | 27, 29 | When you move a domain, file it for each verified variant |
| July 10, 2026 | Google may hold pages in a duplicate cluster for up to two weeks after a fix | 27, 30 | Wait two weeks before you judge a duplicate fix |
| October 21, 2026 | The control what you share page now lists the Search generative AI control too | 25, 67 | Review it together with robots meta, data-nosnippet and X-Robots-Tag |
| October 23, 2026 | URL guidance now explains why hyphens beat underscores | 55 | Use hyphens rather than underscores in new slugs |
Setup and Access: The Three Checks That Come First
You cannot audit what you cannot measure. So before anything else, confirm you actually own the data.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 1 | Set up and verify Google Search Console | Because it is the only first-party record of how Google crawls, indexes and ranks the site | Verify the domain property in GSC rather than just the URL prefix | Critical |
| 2 | Create and submit an XML sitemap | Tells search engines which URLs you consider important enough to crawl, as long as it lists only canonical URLs | Yoast, RankMath or a generator, then submit in GSC and Bing Webmaster Tools and split any file over 50,000 URLs or 50MB uncompressed | High |
| 3 | Set up Google Analytics 4 | Shows engagement and behaviour signals that a crawl report cannot see, such as AI Assistant referrals | GA4 property plus a working tag, then confirmation in DebugView | Medium |
Also add Bing Webmaster Tools to that list. It costs ten minutes and it matters more than it used to, because ChatGPT leans on the Bing index for live answers. We cover that properly in our guide to ranking in ChatGPT search.
Crawlability: 12 Checks Before Anything Else Counts
Crawlability is the first prerequisite. After all, without a crawl there is no index, and without an index there is no ranking and no AI citation. So this section runs before every other section in a real audit.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 4 | Score overall crawlability before anything else | If Google cannot crawl efficiently, then the rest of the audit is theoretical | Semrush Site Audit crawlability score, then Screaming Frog crawl completion rate as a cross-check | Critical |
| 5 | 301 redirect retired posts when they hold backlinks | Because deleting a page without a redirect throws away link equity you already paid for | Check backlinks first, then 301 to the closest replacement | High |
| 6 | Run a full site crawl in order to catch domain-level issues | A crawler checks 100+ predefined issues that accumulate as you add pages, so it catches what manual checks miss | Screaming Frog, Ahrefs Site Audit or Semrush Site Audit | High |
| 7 | Schedule an on-demand crawl instead of relying on search operators | Google does not recrawl low value pages often, so operator results go stale | Weekly scheduled crawl in your audit tool, then a diff against last week | High |
| 8 | Serve 410 for spam or fabricated parameter URLs | Any 4xx gets junk URLs dropped once Google recrawls them, and 410 also records that the removal is deliberate | htaccess or server config rule matched on the injected pattern, then a test on sample URLs | High |
How Do You Catch Crawl Waste and Broken Pages?
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 9 | Track crawl requests per day, then improve them | Crawl capacity decides how quickly new and updated pages get seen, so a falling line is an early warning | GSC Crawl Stats report, then server logs for the detail | High |
| 10 | Watch for parameter bloat as well as unexpected URL count growth | A sudden jump in discovered URLs usually means an attack or a faceted nav bug, so investigate it the same week | Compare GSC indexed count trend with crawl totals, then repeat month over month | High |
| 11 | Count 3xx redirect chains and 404 pages from the crawl | Chains waste crawl budget and are invisible unless you crawl for them | Site Audit redirect report, then the broken page report | Medium |
| 12 | Fix broken landing pages, 404s and 403s | A high broken response rate damages perceived site quality because users and crawlers hit dead ends | Screaming Frog status code report, then a cross-check with logs | Medium |
| 13 | Fix internal and external broken links | Broken links waste equity and also frustrate users mid-journey | Site Audit report for pages linking to broken pages, then a fix list | Medium |
| 14 | Use custom crawl queries in order to find template-level issues | Lets you export every affected URL and hand the developer one fix instead of fifty | Screaming Frog custom extraction or Ahrefs Data Explorer | Medium |
| 15 | Do not rely on XML sitemaps for LLM discovery | LLMs build no index of their own, so they have no reason to read your sitemap | Keep sitemaps for search engines, while treating AI discovery separately | Low |
How Far Crawl Budget Can Actually Move
Crawl budget gets treated as a fixed constraint. In fact, it is not. For example, in one case reported by Jairo Guerrero of AirOps, a client site went from roughly 8,000 crawl requests per day to about 1.2 million. As a result, a full-site crawl fell from an estimated thirteen years to around a month.
That is a single practitioner account rather than a published study, so treat the exact figures as directional. The mechanism behind it, however, is not in dispute. Crawl capacity responds to server speed, internal link structure, response codes and the ratio of useful pages to junk. All four are things you control, so the ceiling moves when you fix them.
Then track the number in the Search Console Crawl Stats report month over month. A flat line while you publish is a warning. A falling line while your URL count grows is the shape that usually precedes a ranking drop. Still, most sites under 10,000 pages never hit a crawl budget limit, as the FAQ below explains.
Why 410 Beats 404 for Injected URLs
This one deserves more than a table row, because almost every other checklist recommends robots.txt or noindex for parameter junk. That advice fails when the URLs were never yours.

A negative SEO attack or a compromised plugin can generate hundreds of thousands of fabricated URLs overnight. In one case we reviewed, a site went from roughly 10,000 known pages to over 500,000 discovered URLs, and rankings fell within days. However, blocking those URLs in robots.txt makes it worse. Google can no longer crawl them, so it cannot see that they are gone, and they linger in the index, which matches Google’s crawl budget guide (checked October 29, 2026): blocked URLs stay in the crawl queue much longer.
What Should Junk URLs Return Instead of a robots.txt Block?
Serve 410 Gone instead, because a 404 says the page might come back while a 410 says it will not. However, Google treats both the same way, and its HTTP status code guide (checked October 29, 2026) says every 4xx code except 429 gets the URL removed from the index. So 410 beats 404 on clarity, in your logs and for the next developer, not on speed. Match the injected pattern at server level rather than page by page, because you cannot hand-edit half a million URLs.
Blocking junk URLs in robots.txt is the most common wrong answer in a spam cleanup. You are not hiding the problem from Google, you are hiding the solution.
Indexation: 8 Checks That Decide If You Exist
Crawling gets you read. Indexing then gets you eligible. And because AI systems retrieve from search indexes first, an unindexed page cannot be cited even by a chatbot that has never visited your server.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 16 | Verify money pages are indexed in Google and Bing | AI assistants retrieve from search indexes, and several also lean on Bing | GSC Pages report, Bing Webmaster Tools URL Inspection, site: operator | Critical |
| 17 | Look for indexed pagination and sort parameter URLs | Faceted URLs waste crawl budget and also create near-duplicates at scale, which is why our ecommerce SEO checklist makes this its own step | site:domain.com inurl:page and site:domain.com inurl:sort | High |
| 18 | Measure the crawled-but-not-indexed ratio | A high ratio means Google is reading pages and then choosing to reject them | GSC Page indexing report, divide indexed by total known | High |
| 19 | Find insecure pages still sitting in the index | Reveals http URLs that never redirect and still compete with your https set | site:domain.com -inurl:https | High |
| 20 | Treat site quality as a bulk judgement, not a page judgement | A strong page on a weak site inherits the site score, and vice versa | Compare indexed URL count against total URL count | High |
| 21 | Check WordPress footprints that should not be indexed | Tag, author and paginated archives get indexed by default and also duplicate content | site:domain.com inurl:tag OR inurl:author | Medium |
| 22 | Do not noindex thin content, remove it or improve it | A noindexed page is still crawled and still counted in sitewide quality | View source for noindex, then cross-check against traffic data | Medium |
| 23 | Find leftover default WordPress install pages | Indexed sample pages signal an unfinished, low care site, so delete them | site:domain.com inurl:hello-world OR inurl:sample-page | Low |
How to Read Your Crawled-But-Not-Indexed Ratio
Most guides tell you to open the GSC Page indexing report. Very few tell you what the number means, or why automated reports never match Search Console when you cross-check it. So here is the version we use with clients.
To begin with, take indexed pages and divide by total known pages. Then band the result.
| Indexation rate | What it usually means | What to do next |
|---|---|---|
| Above 80% | Healthy, because Google broadly agrees with your URL set | Monitor quarterly, no action |
| 50% to 80% | Bloat is forming, usually parameters or thin archives | Find the pattern, then remove or consolidate it |
| Below 50% | Google is actively rejecting most of what it crawls | Treat as a quality problem rather than a crawl problem, then prune first |
The reason the low band is a quality problem rather than a crawl problem is worth spelling out. For instance, Guerrero describes a client where roughly 80 percent of crawled pages carried no value at all, and the effect was not confined to those pages. As a result, the junk dragged down the whole-site assessment, including the pages that were fine.
The instinct at that point is to noindex the weak pages. Resist it. Noindex removes the page from results but Google still crawls it and still weighs it when judging the site. Instead, deleting or genuinely improving the page is what changes the sitewide picture. We go deeper on this in our programmatic SEO guide, where the problem shows up fastest.
Robots and Directives: 3 Checks With Outsized Consequences
In fact, one wrong character in robots.txt can switch off an entire site. This is the shortest section in the checklist, yet also the most dangerous.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 24 | Check for Allow versus Disallow typos in robots.txt | A single wrong directive silently blocks every bot, and nothing alerts you when it happens | Read the file manually, then check the GSC robots.txt report | Critical |
| 25 | Confirm robots.txt does not block AI user agents | Blocking the agent sets your AI crawl budget to zero even if you rank in Google | Open domain.com/robots.txt, then check each named agent line and your firewall rules | Critical |
| 26 | Confirm robots.txt exists and returns plain text | Controls where bots go, for example cart, search and feed URLs | Visit domain.com/robots.txt, then confirm a 200 plain text response | High |
The AI User Agents Worth Naming Individually
Blocking AI crawlers is a real business decision, not a default. But most sites block them by accident, through an inherited rule or a security plugin. So check each agent separately, because they do different jobs.
| User agent | Operator | What it does | Consequence of blocking |
|---|---|---|---|
| GPTBot | OpenAI | Collects content used for model training | You lose training presence but not live citations |
| OAI-SearchBot | OpenAI | Indexes content for live ChatGPT search answers | You lose live ChatGPT citation eligibility, though navigational links can still appear |
| ChatGPT-User | OpenAI | Fetches a page when a user action requires it | OpenAI says robots.txt rules may not apply, so a block may not hold |
| PerplexityBot | Perplexity | Indexes for Perplexity answers | You lose Perplexity visibility |
| ClaudeBot | Anthropic | Collects content that may be used for model training | Future content is left out of training, not out of Claude search |
| Google-Extended | Controls Gemini and AI training use, separate from Googlebot | You keep Google Search, but you lose Gemini grounding |
Note the split in that last row. Google-Extended is not Googlebot. Blocking it does not affect your Google Search rankings, which is exactly why so many teams get the decision wrong in both directions.
Which AI Crawlers Can You Actually Block With robots.txt?
You can block the training and search crawlers with robots.txt, but the fetchers that act on a user’s request may not obey it. OpenAI says robots.txt rules may not apply to ChatGPT-User, and Perplexity says Perplexity-User generally ignores them, because a person asked for the page (both checked October 29, 2026).
Anthropic works differently. Its help center (April 2026) lists three agents, and it says blocking Claude-User stops Claude from fetching your pages for user questions. So check every agent you care about, not just the famous ones.
| Operator | Training crawler | Search crawler | User-triggered fetcher |
|---|---|---|---|
| OpenAI | GPTBot | OAI-SearchBot | ChatGPT-User, where robots.txt may not apply |
| Anthropic | ClaudeBot | Claude-SearchBot | Claude-User, which you can block |
| Perplexity | None listed, since PerplexityBot is not used for model training | PerplexityBot | Perplexity-User, which generally ignores robots.txt |
| Google-Extended token for Gemini training and grounding | Googlebot, which also feeds AI Overviews and AI Mode | User-triggered fetchers, which generally ignore robots.txt |
Both OpenAI and Perplexity say a robots.txt change can take about 24 hours to reach their systems. In addition, robots.txt is only half the picture. If your firewall blocks an operator’s published IP ranges, the bot fails even when robots.txt allows it, so review check 48 alongside check 25.
For Google, blocking Google-Extended does not remove you from AI Overviews or AI Mode. Instead, Google’s AI features guide (checked October 29, 2026) names robots.txt rules for Googlebot and snippet controls as the way to manage those features, alongside the Search generative AI control in Search Console.
A Straight Answer on llms.txt
Several checklists now recommend llms.txt as if it were robots.txt for AI. That framing is wrong, and it is worth saying plainly.
llms.txt is a proposed plain-text file listing your key pages for language models. No major AI provider has committed to reading it. Google’s guide to optimizing for generative AI features also says, in a note added on June 15, 2026, that Google Search ignores these files, so they neither help nor hurt your visibility there. More importantly, it does not match how these systems actually work, because they retrieve through search indexes rather than browsing a directory of your choosing.
So add it if you like. After all, it takes ten minutes and costs nothing. Just do not count it as an AI visibility strategy, and do not let it displace the checks in this list that genuinely move the needle.
Duplicate Content and Canonicals: 5 Checks
Duplicate content rarely arrives as a copy-paste problem in the first place. It arrives as an architecture problem, and the fix is usually a redirect rule rather than a rewrite.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 27 | Pick one canonical version: http vs https, www vs non-www | Four live variants split signals and also leave insecure duplicates indexed | Load all four variants, then confirm each 301s to the same target | Critical |
| 28 | Apply the chosen redirect site-wide, not only on the home page | A home-page-only redirect still leaves every inner page duplicated | Test a deep product or blog URL across all four variants rather than the root | High |
| 29 | Check whether an old domain still has indexed pages | Redirecting only the home page leaves the old domain competing with you until every URL redirects | site:olddomain.com | High |
| 30 | Hunt keyword cannibalisation by sorting URLs and title tags | Two pages on one intent split clicks, so both underperform | Screaming Frog crawl filtered by title, then compare GSC query overlap | High |
| 31 | Delete useless tag archives on small sites | Tag pages add crawl depth and duplication but no ranking upside | Site Audit crawled pages sorted by crawl depth | Medium |
The Four-Variant Test Almost Nobody Runs Properly
Here is the check itself, and it takes two minutes. First of all, pick a deep URL, not your home page. For example, a product page or a blog post is ideal. Then request all four of these and record the response.
http://domain.com/deep-page/https://domain.com/deep-page/http://www.domain.com/deep-page/https://www.domain.com/deep-page/
Three of them should return a single 301 to the fourth. If any of them returns a 200, then you have a live duplicate. Similarly, if any of them returns a chain of two or more redirects, you are leaking crawl budget on every request.
We test the deep URL rather than the home page because home-page-only rules are the single most common miss. A server rule that redirects the root correctly can still pass inner paths through untouched.
How Do You Check Hreflang and International SEO Setup?
Hreflang checks only apply when you publish the same page in more than one language or for more than one country, which is why they sit outside the 105 numbered checks. If that is your site, add the five checks below to the duplicate content pass, because hreflang is how Google learns which version to show in each market.
| Hreflang check | What Google’s guidance says (checked October 29, 2026) | How to check |
|---|---|---|
| Every version lists itself and all others | Each language version must list itself as well as all other language versions | Crawl one URL per language, then compare the hreflang sets |
| Links point both ways | If two pages do not both point to each other, Google ignores the tags | Use your crawler’s hreflang report to find missing return links |
| Fully qualified URLs | Alternate URLs must include the protocol, such as https://example.com/foo, not /foo | Search the hreflang values for relative paths before launch |
| One method, used consistently | HTML tags, HTTP headers and sitemaps are equivalent, so using all three gives no benefit | Pick one method, then remove stray duplicates |
| A fallback for unmatched users | Use x-default for language selectors or for home pages that redirect by language | Confirm one x-default URL per set of pages, then test a selector |
Also note that Google treats localized pages as duplicates only when the main content is left untranslated. So a translated template with untranslated body copy is a duplicate content problem, not an hreflang problem.
Site Architecture and Internal Linking: 8 Checks
Internal links are how discovery actually happens, and they are the cheapest ranking lever most sites still ignore.
To see which links on a page are followed, including a page-level meta robots nofollow, run it through our free dofollow link checker.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 32 | Add internal links from relevant existing pages to each new post | Passes equity and also speeds up discovery of the new URL | site:yourdomain.com + keyword, then add contextual links | High |
| 33 | Avoid nesting a keyword-optimised page as a folder for child pages | Structures such as /city-attorneys/wrongful-death/ raise cannibalisation risk | Review folder depth in Screaming Frog | High |
| 34 | Investigate pages blocked from crawling and confirm the reason | Some blocks are intentional, while others silently hide pages you want ranked | Site Audit blocked list, then view source for noindex | High |
| 35 | Keep every important page within three clicks of the home page | Deep pages read as low priority, so crawlers may never reach them | Site Audit crawl depth report | High |
| 36 | Automate internal linking and pruning with agents or purpose-built tools | Because it scales two tasks that directly affect crawl efficiency and relevance | Internal linking tool or a scripted candidate-scoring pass | Medium |
| 37 | Build internal links to new and important pages deliberately | Search engines discover pages through links before sitemaps | Internal link report in your crawler | Medium |
| 38 | Find and fix orphan pages | No internal links means poor discovery and also no user path to money pages | Crawl output cross-referenced against sitemap and logs | Medium |
| 39 | Link out to relevant high authority external resources | Correlation work suggests pages that cite strong sources tend to rank better | Manual review during content production | Medium |
Rendering and JavaScript: The Section Most Checklists Skip
Googlebot renders JavaScript. However, most AI crawlers do not, or they give up far sooner. So a page that looks complete in your browser can reach an AI system as an empty shell. That is why this layer gets two checks of its own, numbers 40 and 41.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 40 | Keep HTML lean and avoid bloated markup | Heavy DOMs waste the limited patience and budget of AI crawlers, and Googlebot also stops reading an HTML file after its first 2MB (Google, March 2026) | Lighthouse DOM size and page weight metrics | High |
| 41 | Move client-side rendering to server-side rendering | Simpler AI crawlers miss anything that needs JavaScript to appear, even though Googlebot renders it | Compare view-source HTML with the rendered DOM, then fix any gaps | High |
The Two-Minute Raw HTML Test
Open the page, then use view-source rather than inspect element. View-source shows what the server sent. Inspect, by comparison, shows what your browser built afterwards.
Then search that raw HTML for your H1, your first paragraph, your price and your primary call to action. If any of them is missing from view-source but visible on screen, JavaScript is producing it. Googlebot will probably still see it. An AI crawler, however, often will not.
The Log File Check That Finds Rendering Gaps
This is the check we have not seen in any competing checklist, and it is the one that finds problems the other 104 checks miss.
When a bot fetches a page, it requests the HTML document. If it then also renders, it requests the JavaScript and CSS assets that page depends on. So you can compare the two counts directly in your server logs.
To begin with, filter your logs by user agent. Count HTML document requests. Then count requests for the JS bundles those pages load. If a bot fetched a page template 10,000 times but pulled the associated JavaScript only a few hundred times, that bot is not rendering your pages. As a result, whatever your JavaScript produces is invisible to it.
So that single ratio tells you whether server-side rendering is a nice-to-have or an emergency. And it is measurable today, because you already have the logs.
| What you see in logs | What it means | Action |
|---|---|---|
| HTML fetches high while JS fetches stay near zero | So the bot reads raw HTML only | Move critical content to server-rendered HTML |
| HTML and JS fetches roughly proportional | The bot renders | No rendering action needed |
| No fetches at all for a named agent | Blocked, or never discovered | Check robots.txt, then internal links and index status |
Speed and Core Web Vitals: 4 Checks
Speed stopped being purely a ranking conversation. It is now also a citation conversation, because a crawler on a budget abandons slow responses.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 42 | Find and fix slow-loading pages | Page experience affects conversion rate as well as rankings | PageSpeed Insights, GTmetrix, then real user data in GSC | High |
| 43 | Improve server response time specifically | Time to first byte governs whether a crawler waits or moves on | Server response time in PageSpeed Insights as well as hosting logs | High |
| 44 | Review the Core Web Vitals section of your site audit | Google has confirmed Core Web Vitals as a ranking input, so a failing URL group is worth fixing | GSC Core Web Vitals report by URL group | Medium |
| 45 | Use CWV as the 28-day baseline and site speed as the instant check | CWV is a rolling field-data window, whereas lab speed is immediate | GSC for CWV, while PageSpeed Insights gives the instant read | Medium |
Does Site Speed Affect AI Citations?
There is emerging evidence that this now affects citations as well as rankings. A study of more than 2,000 sites, cited in the AirOps session, reported that faster sites were referenced roughly 20 to 30 percent more often in AI answers, with one slide putting the gap at 1.47 times. We have not reviewed the underlying methodology, so treat those numbers as a direction of travel rather than a benchmark.
The mechanism is intuitive enough. In short, a crawler working through a large candidate set on a fixed budget abandons slow responses. Googlebot usually comes back later. In contrast, an AI crawler often does not.
Google’s published Core Web Vitals thresholds are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. Measure against field data where you have it, because lab scores flatter you. web.dev adds (checked October 29, 2026) that a page passes only when it meets all three targets at the 75th percentile of page loads, split by mobile and desktop.
How Many Sites Pass Core Web Vitals Today?
Fewer than half of mobile sites pass. The HTTP Archive Web Almanac 2025, published in January 2026, found that 48% of mobile websites and 56% of desktop websites had good Core Web Vitals in its July 2025 data, up from 44% and 55% in 2024.
So a pass is still an edge on mobile. Also, INP replaced First Input Delay as a Core Web Vital on March 12, 2024, according to web.dev, so any audit template that still grades FID is out of date. In that case, swap the FID column for INP before you run checks 44 and 45. Our Core Web Vitals and INP guide covers the fixes for WordPress and Shopify themes.
Server and Security: 4 Checks That Are Really Business Risk
This section is short, and every item in it is Critical. That is not padding. Each one can take a site off the map in a week, so treat them as emergencies.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 46 | Investigate strange outbound links on indexed pages | Unrelated outbound links usually mean the site has been compromised, so act the same day | site: search plus manual review, then a malware scan | Critical |
| 47 | Monitor server uptime and 5xx error rate | During downtime crawlers get nothing and you lose citations for that window | Uptime monitor as well as 5xx rate in server logs | Critical |
| 48 | Put bot protection in front of the server | Spoofed crawler floods can crash the origin and kill visibility, so verify real Googlebot against Google’s published IP ranges before you block anything | Cloudflare or an equivalent WAF with bot challenge rules, while allowing verified crawlers | Critical |
| 49 | Search indexed file types for exposed private documents | Indexed PDFs and spreadsheets routinely leak salaries, addresses and client data, so treat any hit as a breach | site:domain.com filetype:pdf, then repeat for xls, doc, csv | Critical |
Run the Exposed File Search Before Your Client Does
Check 49 is the one that changes the temperature of a client meeting. So run these four searches on any site you take over.
site:domain.com filetype:pdfsite:domain.com filetype:xls OR filetype:xlsxsite:domain.com filetype:doc OR filetype:docxsite:domain.com filetype:csv
Most of the time you find old brochures. Occasionally, though, you find an internal payroll sheet or a client contact export sitting in an uploads folder. Fix it by removing the file and serving 410, then requesting removal in GSC. Do not simply noindex it, because the file itself remains publicly downloadable.
Mobile: 1 Check, Still Non-Negotiable
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 50 | Confirm pages are genuinely mobile friendly | Google indexes the mobile version, so mobile is the version that counts | URL Inspection in GSC plus manual device testing, since Google retired the Mobile Usability report in December 2023 | High |
On-Page Technical: 5 Checks at Template Level
These are on-page items, but you audit them technically. In other words, you are looking for template errors that affect hundreds of pages at once, not for one weak title.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 51 | Write title tags and meta descriptions that earn the click | Exact-match keywords do not correlate with position, but clicks still bring traffic | SERP preview tool, then GSC CTR by query | High |
| 52 | Run an on-page checker per target page and keyword | Surfaces concrete gaps such as missing variations and weak readability | Semrush On Page SEO Checker in manual mode | Medium |
| 53 | Skim your site: results for title tag problems | Wrong brand or domain in titles hurts CTR and also looks broken | site:domain.com, then read the SERP titles | Medium |
| 54 | Use intitle: to count pages carrying a wrong or outdated title | Finds template-level title errors at scale instead of one at a time | site:domain.com intitle:"old brand name" | Medium |
| 55 | Use short, descriptive URLs | Shorter URLs correlate with better rankings and are also easier to cite | Set the slug to the primary keyword, drop stop words and use hyphens rather than underscores (Google, October 2026) | Medium |
Structured Data: 6 Checks After Google Removed FAQ Rich Results
Structured data is the one area where a 2027 checklist has to be more careful than a 2023 one. Google removed FAQ rich results from Search on 7 May 2026. HowTo went the same way in 2023. Plenty of checklists still tell you to add both. Six checks below, then two things worth saying plainly.

| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 56 | Map every template to a schema type that still earns a Search appearance | Markup built for a retired feature costs dev time but returns nothing | Compare each template against Google’s structured data gallery, one template at a time | Critical |
| 57 | Make structured data match the visible text on the page | Google states this outright, so a mismatch risks a manual action for spammy markup | Rich Results Test, then read the rendered page beside the output | Critical |
| 58 | Validate with the Rich Results Test and the Schema.org validator | The first tells you what Google can use, whereas the second shows what is syntactically broken. They answer different questions | Run both on one representative URL per template | High |
| 59 | Confirm your JSON-LD survives rendering, not just view-source | Schema injected by a tag manager or by JavaScript is invisible when the page is judged on raw HTML | Compare view-source against the rendered DOM, the same test as check 41 | High |
| 60 | Keep one Organization block with sameAs, consistent sitewide | Conflicting entity blocks across templates weaken the entity you are trying to establish | Crawl for duplicate Organization nodes on the same URL | Medium |
| 61 | Watch the Enhancements reports in Search Console for silent drops | Valid items fall off after a template release while nobody files a bug | GSC, Enhancements, per type, month over month | Medium |
The Schema Types That Stopped Paying in 2026
FAQPage and HowTo are two of the most commonly recommended types in technical SEO checklists. However, neither produces a result in Google Search any more.
| Type | Current status | What to do |
|---|---|---|
| FAQPage | Rich results stopped appearing on 7 May 2026. The appearance filter, rich result report and Rich Results Test support were dropped in June 2026, and Search Console API support ended in August 2026 | Leave existing markup in place if removing it is costly, because it causes no harm. Also stop counting it as a deliverable and stop reporting FAQ impressions that no longer exist |
| HowTo | Removed from mobile in August 2023 and desktop in September 2023. No Search appearance since | Remove it from new templates. Also, do not add it to a 2027 build |
| Speakable | Still in the gallery, still beta, still aimed at news publishers in a limited set of locales | Skip it unless you are a news publisher inside that set |
The wider point is that markup follows Google’s feature list, not schema.org’s vocabulary. Schema.org publishes hundreds of types. In contrast, Google renders a couple of dozen. So build for the second list.
In addition, the same clean-up hit other types. Google’s documentation updates page (checked October 29, 2026) shows course info, estimated salary, learning video, special announcement and vehicle listing documentation removed on September 9, 2025, and practice problem documentation removed on January 6, 2026. Google also clarified in November 2025 that Dataset markup is used only by Dataset Search, not Google Search.
A Straight Answer on Schema and AI Search
You will read everywhere that schema is how you get cited by AI. Google’s own documentation on AI features says the opposite in one line: there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode.
What Google does ask for is that the page is indexed, eligible to be shown with a snippet, and that its structured data matches the visible text. That last part is the useful instruction. Schema does not buy you a citation. However, inaccurate schema can cost you one.
The studies reporting large citation lifts from schema are correlational. In other words, sites that mark up properly tend to be sites that do everything else properly too. Mark up for the Search features you are genuinely eligible for, keep it accurate, and treat any AI benefit as a side effect rather than the business case. Our restaurant schema markup guide shows what that looks like for one business type, with Google’s support status for each restaurant feature.
Logs and Monitoring: 4 Checks Nobody Else Teaches
Search Console reports only on Google. So your server logs are currently the only reliable source of truth on AI crawler behaviour. As a result, this section is the highest-leverage part of a modern audit.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 62 | Analyse logs for absence of signal | Because important pages with zero bot hits effectively do not exist | Screaming Frog Log Analyser, OnCrawl or JetOctopus | High |
| 63 | Identify which AI bots hit your server and how often | GSC reports Google only, so logs are your sole AI crawler dataset | Filter logs by user agent string per bot, then verify the IPs against each operator’s published ranges | High |
| 64 | Compare bot HTML fetches against JavaScript file loads | A large difference shows that this specific bot does not render, so it misses JavaScript content | Cross-reference HTML and JS asset entries per user agent, then compare the ratio | Medium |
| 65 | Prefer a platform that gives you raw server log access | Some hosted platforms block log access entirely, so you cannot see AI crawling at all | Ask your host or platform for raw access logs before you commit | Medium |
What to Do When Your Platform Will Not Give You Logs
Hosted ecommerce platforms are the usual problem here. Shopify, for example, does not expose raw server logs, so you cannot confirm whether an AI crawler ever reached a product page.
Even so, you still have options. Three workarounds get you most of the way.
- Put the site behind a CDN such as Cloudflare and read the CDN logs instead. The request still passes through it.
- Use GSC Crawl Stats as a proxy for Googlebot behaviour, then treat it as a floor rather than a full picture.
- Finally, add lightweight server-side logging through an app or middleware layer where the platform allows it.
If none of those is possible, then factor it into your platform decision. Losing log visibility is a real cost, and it is worth naming at the point of choosing a stack rather than two years later.
AI Search, GEO and AEO: 7 Checks
This is where a 2027 checklist earns its title. In fact, these items are not content advice, they are infrastructure decisions about how retrieval works.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 66 | Cover topics and entities, not only exact keywords | Retrieval works on semantic similarity, then reranks candidates | Entity and subtopic coverage audit, then a comparison with the SERP | High |
| 67 | Expect the impressions-up, clicks-down pattern | AI answers raise impressions while cutting clicks on informational queries | GSC Performance, then compare impressions and clicks trend lines | High |
| 68 | Optimise beyond Google: YouTube, Reddit, Amazon, TikTok, LinkedIn | Demand is fragmenting, and AI systems also cite those platforms heavily | Map where your audience searches, then build for each surface | High |
| 69 | Optimise the title and snippet that the search API returns | That short extract is frequently all the model ever sees of your page, so put the answer in it | SERP preview plus GSC, then check what text actually gets pulled | High |
| 70 | Plan for organic click decline while still harvesting it | Click share is compressing on informational intent, so diversify in parallel | Track click share trend by intent type rather than sitewide | High |
| 71 | Accept that citations can happen without a crawl | When the index snippet answers the prompt, no AI bot ever visits your server | Compare AI citation tracking with your server log hits, then note the gap | Medium |
| 72 | Implement llms.txt but keep expectations low | Cheap to add but unproven in practice, and Google Search ignores it (Google, June 2026) | Add /llms.txt in root, then measure nothing from it | Low |
How Retrieval Picks Candidates Before It Picks an Answer
Check 66 tells you to cover topics and entities rather than exact keywords. The reason sits in how retrieval works, and it runs in two stages. Our guide to generative engine optimization covers what to do with that on the content side.
First the system finds candidates by meaning rather than by string match. In effect, your query becomes a numerical representation, and passages that sit close to it in meaning get pulled in. That is why a page can be retrieved for a phrasing it never literally contains.
Then it reranks that pool before choosing what to quote. Guerrero puts the size of that shortlist in the region of 150 results. We have not found published documentation confirming that specific figure, so treat it as a practitioner estimate. The two-stage shape, retrieve broadly then rerank, is well established regardless of the exact number.
The practical instruction is the same either way. Name the entities. Then list the tools, standards, competitors, regulations and adjacent concepts a knowledgeable person would expect. Breadth of coverage gets you into the candidate pool. In contrast, repeating one phrase does not.
Why You Can Get Cited by a Bot That Never Visited You
This is the most misunderstood mechanic in AI search, and it changes what you should optimise.
When someone asks an AI assistant a question, the system does not usually crawl the open web in that moment. Instead, it queries a search index, gets back a set of results, and each result arrives as a title plus a short text extract. If that extract already answers the prompt, then the model can write its answer and cite you without ever requesting your page.
Two consequences follow. First, your server logs will under-report AI visibility, because many citations leave no trace there. Second, the snippet is the artefact being judged, not your full page.
So the practical move is to make the first 200 characters of the relevant section carry the answer. Front-load the fact. Put the number, the definition or the direct response near the top of the passage rather than after three paragraphs of setup.
The scale of the click compression is worth naming, even though the numbers move around by study. Eric Siu cites work putting the organic traffic reduction from AI Overviews at more than 37 percent on affected queries. Published figures in this area vary widely, so use it to size the risk rather than to forecast your own result. Segmenting your own Search Console data by intent gives a far more useful answer than any industry average.
We got this wrong on our own site for most of 2025. We optimised full pages for depth and buried every direct answer under context. Impressions climbed, citations did not.
How Much Do AI Overviews Cut Clicks to Classic Results?
By a lot on informational queries, although the exact share varies by study. Ahrefs found that an AI Overview correlated with a 58% lower average click-through rate for the top-ranking page in December 2025 data, up from 34.5% in its April 2025 study. Pew Research Center found that users who saw an AI summary clicked a traditional result in 8% of visits, against 15% without one.
Questions trigger these summaries most. In the same Pew data from March 2025, 60% of searches that began with who, what, when or why produced an AI summary, compared with 18% of all searches. As a result, question-led informational pages feel the cut first, which is why checks 67 and 70 ask you to segment clicks by intent.
The audience is large, too. On its Q2 2025 earnings call, as reported by TechCrunch, Google said AI Overviews had 2 billion monthly users and AI Mode more than 100 million in the US and India. However, Google’s AI features guide (checked October 29, 2026) says clicks from results pages with AI Overviews are higher quality, so track engaged sessions and conversions next to clicks before you judge a drop.
Agent Readability: 3 Checks for the Web That Clicks Back
AI agents are starting to complete tasks rather than just summarise pages. That means your site now needs to be operable by software, not only readable by it. No other technical SEO checklist we audited covers this at all.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 73 | Test key conversion flows in the accessibility tree | Because it shows exactly what an agent understands as a button, link or plain text | Chrome DevTools, Elements panel, Accessibility pane | High |
| 74 | Use real semantic tags for interactive elements | A styled div has no role and no accessible name, so agents cannot act on it | Compare the accessibility tree with the visual UI, then fix any unnamed control | High |
| 75 | Track agent commerce protocols from Google, Shopify, PayPal and Stripe | Agent-led purchasing is being built now, so it needs machine-readable checkout | Follow the published protocol documentation for your platform, such as the Universal Commerce Protocol that Google names | Medium |
How to Read Your Own Accessibility Tree
The check takes about five minutes and needs no tools beyond Chrome.
- Open the page and press F12 to launch DevTools.
- Go to the Elements panel, then open the Accessibility pane on the right.
- Then enable the full-page accessibility tree view.
- Find your primary action, for example Add to Cart or Request a Quote.
- Finally, read its role and its accessible name.
You want to see a role of button or link with a clear name. What you often see instead is a generic node with no name at all. That happens when the element is built like this:
<div class="btn" onclick="submitOrder()">Add to Cart</div>
Visually that is a button. Structurally, however, it is a rectangle. An agent reading the accessibility tree sees no interactive control, so it cannot complete the task. The fix is genuinely this simple:
<button type="submit">Add to Cart</button>
Same appearance with the right CSS, completely different machine meaning. Run this on your cart, your quote form and your booking flow first, because those are the pages where failure costs money.
What Does Google Say About AI Agents Using Your Site?
Google now gives the same advice as this section. Its guide to optimizing for generative AI features (checked October 29, 2026) says browser agents may analyze screenshots, inspect the DOM structure and interpret the accessibility tree when they complete tasks such as booking or comparing products.
The guide also names the Universal Commerce Protocol as one of the emerging protocols that will let Search agents do more, which is the kind of standard check 75 asks you to track. In addition, web.dev’s guide to agent-friendly websites (April 2026) lists screenshots, raw HTML and the accessibility tree as the three main ways agents read a page, and it calls WebMCP a proposed standard that is still in active development.
Keyword and Intent: 13 Checks
Technical work gets you eligible. Intent work, in turn, decides whether eligibility turns into traffic. These checks belong in a technical audit because they are diagnostic, not creative.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 76 | Assess search intent before writing anything | When the SERP shows blog posts, a product page will not rank there | Search the keyword, then study page type and format of the top ten | Critical |
| 77 | Pull keywords ranking in positions 2 to 15 | Small gains here move traffic fastest, so start the campaign here | Organic Research positions report, then a custom range of 2 to 15 | Critical |
| 78 | Check the organic keyword trend before diagnosing anything | Because a sharp decline points to a penalty or link problem that outranks all else | Semrush or Ahrefs organic overview, then a 24-month view | High |
| 79 | Collect related queries from autocomplete and People Also Ask | These reveal the questions the page must answer in order to satisfy intent | SERP features as well as the questions report in your keyword tool | High |
| 80 | Filter keyword lists by city or region for local businesses | Prioritises high transactional local terms rather than national noise | Keyword filter on the location modifier, such as a city name | High |
| 81 | Find intent mismatches on pages that already rank badly | A commercial page cannot rank for informational intent, however good it is | Compare your page type with the SERP result types, then fix the mismatch | High |
Which Checks Cover Targeting, Difficulty and Position Bands?
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 82 | Find subtopics from what the top pages already rank for | A winning page typically ranks for hundreds of related terms, so its profile maps the topic | Keyword tool, then filter competitor keywords to positions 1 to 5 | High |
| 83 | Only create a new page when the intent is genuinely different | Same intent belongs on one page, whereas different intent needs its own | Compare the two candidate SERPs by hand before you build | High |
| 84 | Pick one primary keyword target per page | Every page needs a single main target so the topic is unambiguous | Keyword mapping sheet, so each URL has one primary | High |
| 85 | Target long tail queries of four or more words | Lower volume but far higher conversion, and AI queries run much longer | Filter your keyword set by word count, then screen for intent | High |
| 86 | Assess difficulty using competitor metrics rather than just a KD score | KD is a rough estimate, so never use it alone | Backlink and referring domain counts of the top ten pages | Medium |
| 87 | Audit positions 16 to 50 as existing opportunities | Fixing the strongest pages usually lifts this band as a knock-on effect | Organic Research positions 16 to 50 | Medium |
| 88 | Treat positions 51 to 100 as clustering opportunities | Ranking that low usually means no focused page exists for the intent, so build or merge one | Organic Research positions 51 to 100 | Medium |
Why the Page Above You Has Already Done Your Research
Check 82 is the cheapest research method on this list, and the scale of it surprises people. Ahrefs analysis of roughly 3 million searches found that the page ranking first typically also ranks for close to 1,000 other keywords.
So the page beating you has already mapped the topic. Then pull its full keyword profile, filter to positions 1 to 5, and read the result as a coverage map. You are not copying the page. Instead, you are reading the evidence of what the topic actually contains.
The same body of work also sits behind check 55. A study of around 2 million keywords found shorter URLs correlate with better positions, which is why the slug should carry the primary keyword and nothing else. Similarly, check 39 comes from correlation work suggesting pages that link out to high authority resources tend to rank better, not worse.
The Position Band Framework
Most guides stop at low-hanging fruit and mean positions 2 to 10. We widen the first band and add two more, because SERP features and AI answers have pushed the click cliff further up the page.
| Position band | What it usually means | First action |
|---|---|---|
| 2 to 15 | Google already trusts the page, but it is not the best answer yet | Improve on-page depth, add internal links, then refresh the data |
| 16 to 50 | Relevance is recognised but authority or coverage is thin | Expand coverage, fix intent match, then add supporting internal links |
| 51 to 100 | No focused page exists for this intent, so you are ranking by accident | Build a dedicated page, or fold the term into the right cluster |
Content Quality: 10 Checks
Quality is a technical concern because it is measured in bulk. So a hundred weak pages will drag down the twenty good ones sitting beside them.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 89 | Keep content, links and E-E-A-T as the core building blocks | First-hand experience and named authorship matter more now that AI content floods the web | Author bios, sourced data and real case studies, as well as named reviewers | High |
| 90 | Make sure the content solves the searcher’s actual problem | Generic advice fails, whereas practical and measurable advice wins | Compare your page with the PAA questions on the SERP, then fill the gaps | High |
| 91 | Run a content audit against GA4 and GSC data | Sorting pages into rewrite, remove, update and review makes the site leaner and also easier to crawl | Content audit tool with GA4 and GSC connected | High |
| 92 | Apply a business lens before deleting any page | Some low-traffic pages still serve sales, legal or proof functions a tool cannot see | Manual review of every flagged page with the commercial owner | Medium |
| 93 | Check engagement and traffic together before keeping a page | Low dwell time as well as no traffic marks a losing page that needs a decision | Content audit table view, then sort by both metrics | Medium |
How Do You Check Readability and Page Polish?
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 94 | Check reading comprehension level | Complex writing loses readers regardless of how correct it is | Hemingway Editor or Yoast readability analysis | Medium |
| 95 | Define writer guidelines before generating anything with AI | Style-matched output reaches usable quality, whereas generic output does not | Have the model extract patterns from your best existing posts before it writes | Medium |
| 96 | Improve visual readability with short sentences and useful images | A wall of text drives readers away, while charts add meaning stock photos cannot | Manual review, then remove filler imagery | Medium |
| 97 | Search for placeholder text still live on the site | Indexed placeholder text signals an unfinished, low quality site, so remove it before launch | site:domain.com "dolor sit amet" | Medium |
| 98 | Write an introduction that confirms the reader is in the right place | A weak intro loses the reader before the useful part arrives | Resonate, build credibility, then promise the specific outcome | Medium |
Two Content Quality Numbers Worth Holding On To
Check 94 exists because reading level is a distribution problem, not a matter of taste. Around half the adult population in the United States reads below an eighth grade level. A page written at graduate reading level is therefore not more authoritative. Instead, it is less accessible to half of its audience.
Check 95 is the one most teams skip when they start generating with AI. Eric Siu’s framing is that output reaches roughly 95 percent of usable quality when the model has learned your house style first, against generic output when it has not.
The method is straightforward. Have the model read ten of your strongest existing posts and extract the patterns: typical length, sentence rhythm, how you use tables, how you cite data, where links sit, how you open and close. After that, save it as a standing instruction. Then generate.
Off-Page: 7 Checks
Links are still the clearest external trust signal, and they now feed AI citation patterns as well as rankings.
| # | Check | Why it matters | How to check | Priority |
|---|---|---|---|---|
| 99 | Audit the backlink profile for toxic and unnatural links | Public network patterns and spammy web 2.0 links still cause real problems | Semrush Backlink Audit or Ahrefs referring domains review | Medium |
| 100 | Check that anchor text is mostly branded and generic | Aggressive exact match anchors are still the classic over-optimisation signal | Backlink Audit anchors report | Medium |
| 101 | Prospect links from sites already linking to top-ranking pages | Because they have already shown they will link to content on this topic | Top ten pages, then their backlinks report | Medium |
| 102 | Treat citations broadly: links, reviews and unlinked mentions | AI systems weigh brand mentions, not only hyperlinks | Backlink tools as well as a brand mention and local citation audit | Medium |
| 103 | Expand prospecting with a content database filtered by referring domains | Finds pages with genuine link pull beyond the current top ten | Content Explorer style search, then a filter of at least 20 referring domains | Low |
| 104 | Only disavow for genuinely nasty links such as negative SEO | Disavow is rarely needed but very easy to misuse | Disavow tool, treated as a last resort | Low |
| 105 | Build the prospect list before you publish, not after | Prospecting first means you have people to promote to as soon as you publish | Outreach list assembled during the research phase | Low |
Full Comparison: What Every Major Technical SEO Checklist Covers
Before writing this, we audited fourteen published technical SEO checklists, including the ones from Semrush, Ahrefs, Backlinko, DebugBear, Sitebulb, seoClarity, Yotpo and Page One Power. We logged what each one covers and, more usefully, what none of them do.
Here is the whole comparison. Everything below reflects those pages as published in August 2026, and every one of them is a genuinely useful resource. The point is not that they are weak. Rather, the point is that the field has a shared gap.
| Checklist | Approx words | Items | AI crawler robots.txt | Log file analysis | HTML vs JS fetch gap | Accessibility tree | Agent commerce | Citation without crawl |
|---|---|---|---|---|---|---|---|---|
| Hustle Marketers (this page) | ~14,500 | 105 | Yes, per agent | Yes, with method | Yes | Yes | Yes | Yes |
| DebugBear | ~6,800 | 74 | Yes, full table | No | No | No | No | No |
| Yotpo | ~6,800 | Narrative | Yes | Named, not taught | No | No | No | No |
| Semrush | ~3,700 | ~21 | Yes | No | No | No | Mentioned, no protocol | No |
| NoGood | ~4,800 | ~60 | Partial | No | No | No | No | No |
| Wellows | ~5,300 | ~50 | No | Googlebot only | No | No | No | No |
| Page One Power | ~3,000 | ~60 | Yes, training vs retrieval | Yes | Gestures at it | No | No | No |
| Ahrefs | ~4,200 | 82 | Yes, one line | No | No | No | No | No |
| Backlinko | ~4,800 | 35 to 40 | Yes | Named, not taught | No | No | No | No |
| GWContent | ~3,800 | 47 | Yes | No | No | No | No | No |
| cognitiveSEO | ~9,500 | 31 | No | No | No | No | No | No |
| Shortlist.io | ~3,000 | 50+ | No | Googlebot only | No | No | No | No |
| DashThis | ~2,900 | 11 | No | No | No | No | No | No |
| seoClarity | ~5,000 | 16 | No | No | No | No | No | No |
| Sitebulb | ~850 | Sheet only | No | No | No | No | No | No |
The Ten Things No Other Checklist Explains
Four of the columns above are empty across all fourteen competitors. Five more items are covered so thinly elsewhere that they may as well be. Here is the full list, with an honest note on who else touches each one.
| # | What we cover | Who else covers it | Find it in |
|---|---|---|---|
| 1 | Comparing bot HTML fetches against JavaScript loads to find rendering gaps | Nobody. One competitor gestures at raw HTML differences without a method | Logs section |
| 2 | Reading your accessibility tree in Chrome DevTools to see what an agent understands | Zero of fourteen | Agent readability |
| 3 | Agent commerce protocols from Google, Shopify, PayPal and Stripe | Zero of fourteen. One names the concept without naming a protocol | Agent readability |
| 4 | Why you get cited by AI systems that never request your page | Zero of fourteen. All assume a crawl happens | AI search section |
| 5 | Serving 410 for injected and spam URLs, not just dead products | Three mention 410, all for discontinued products only | Crawlability |
| 6 | The crawled-but-not-indexed ratio as a banded quality metric | The GSC status is common, but the ratio with thresholds appears nowhere | Indexation |
| 7 | Site quality judged in bulk, built into audit steps rather than mentioned | Two glancing mentions, no action attached | Indexation |
| 8 | llms.txt with its actual limitations stated plainly | Two are honest about it. Three recommend it uncritically and one describes it incorrectly | Robots and directives |
| 9 | The four-variant redirect test run on a deep URL rather than the home page | Canonical choice is universal. Testing inner URLs across all four variants is not | Duplicate and canonical |
| 10 | That FAQPage and HowTo markup no longer earn a Search appearance, with the dates | Zero of fourteen. One still recommends adding both types in a 2026 checklist | Structured data section |
What Do the Ten Gaps Have in Common?
The pattern underneath all ten is the same. Every other checklist treats an AI system as a crawler you either permit or block. None of them treats it as a user that has to read the page, render it, and increasingly act on it.
The 50-Item Short Version for Small Sites
Running all 105 checks on a twelve-page site is a poor use of a morning. So here is the reduced set. Run these, and skip the rest until the site grows past a few hundred URLs.
First of all, keep every Critical item: 1, 4, 16, 24, 25, 27, 46, 47, 48, 49, 56, 57, 76 and 77. Then add these High items: 2, 5, 6, 8, 9, 10, 17, 18, 19, 20, 26, 28, 29, 30, 32, 33, 34, 35, 40, 41, 42, 43, 50, 51, 62, 63, 66, 67, 68, 69, 70, 73, 74, 78, 79 and 89.
That is 50 checks, and it covers roughly 90% of the risk on a small site.
How Do You Run a Technical SEO Audit Step by Step?
Run it in nine passes, in the order the data depends on itself: access first, then quick tests, the crawl, the index, rendering and logs, performance and security, templates, the AI and agent layer, and finally intent, content and links. The numbering on this page is a category order, so use these passes as the work order.
Which Checks Belong in Each Audit Pass?
Every one of the 105 checks sits in exactly one pass, so no check is run twice.
| Pass | What you do | Checks | What you should have at the end |
|---|---|---|---|
| 1 | Confirm access: Search Console domain property, sitemaps, GA4, and Bing Webmaster Tools alongside them | 1 to 3 | Verified data sources you can trust before the crawl |
| 2 | Run the four quick tests from the key takeaways: deep URL redirects, exposed files, AI user agents, crawled but not indexed ratio | 18, 25, 28, 49 | A same-day list of the most expensive problems |
| 3 | Crawl the site, read robots.txt, then map the internal link structure | 4 to 15, 24, 26, 32 to 39 | Status codes, redirect chains, broken links, crawl depth and orphan pages |
| 4 | Reconcile the crawl with the index and the canonical set | 16, 17, 19 to 23, 27, 29 to 31 | Your indexation band and the duplicate patterns behind it |
| 5 | Test rendering, then read the server logs | 40, 41, 59, 62 to 65 | Which bots read raw HTML only, and which pages they never fetch |
| 6 | Check speed, server health, security and mobile | 42 to 48, 50 | Critical security findings as well as the slowest templates |
| 7 | Audit templates: on-page elements and structured data | 51 to 58, 60, 61 | One fix per template rather than one per page |
| 8 | Audit the AI search and agent layer | 66 to 75 | Snippet quality, AI visibility baseline and agent-readable controls |
| 9 | Check intent, content quality and links | 76 to 105 | Pages to fix, merge, remove or promote |
How Should You Prioritize What the Audit Finds?
Then sort every finding by its priority label, not by pass. Across the list, the labels split like this:
| Priority | Number of checks | Which ones | Fix window |
|---|---|---|---|
| Critical | 14 | 1, 4, 16, 24, 25, 27, 46, 47, 48, 49, 56, 57, 76, 77 | Same week |
| High | 47 | Spread across 16 of the 18 categories | Within 30 days |
| Medium | 38 | Largest groups: Content Quality (7), then Crawlability, Site Architecture, On-Page Technical and Off-Page (4 each) | Within the quarter |
| Low | 6 | 15, 23, 72, 103, 104, 105 | When capacity allows |
Two patterns are worth knowing before you start. All four Server and Security checks are Critical, so pass 6 can produce emergencies even on a site that looks healthy. And none of the seven Off-Page checks is above Medium, so link work never jumps the queue ahead of access, indexing and rendering. If you want this run for you, the ranges and what drives them are in our breakdown of what an SEO audit costs.
What Are the Most Common Technical SEO Issues and How Do You Fix Them?
Most technical SEO problems show up as one of a few symptoms, from pages missing in Google to content AI tools never quote. So start from the symptom you see, then run only the checks that diagnose it.
| Symptom | Likely cause | Checks | First fix |
|---|---|---|---|
| Pages missing after a launch or migration | A leftover noindex, a robots.txt block or a root-only redirect | 22, 24, 26 to 28 | Remove the block, then test a deep URL |
| Crawled, currently not indexed keeps rising | Thin, duplicate or parameter pages | 17, 18, 20, 22 | Remove or improve pages rather than noindex them |
| Discovered, currently not indexed keeps rising | Weak internal links or a slow server | 9, 35, 37, 38, 43 | Link from strong pages, then speed up the server |
| Sudden jump in discovered URLs | Injected spam or a faceted navigation bug | 8, 10, 17 | Return 410 or 404 at server level instead of blocking |
| Ranks in Google but never cited by AI tools | An AI agent blocked in robots.txt or by the firewall | 25, 48, 63 | Allow the search agents, then confirm hits in logs |
| Visible on screen but missing from AI answers | Content that only JavaScript produces | 41, 59, 64 | Run the view-source test, then server-render it |
| Poor URLs in the Core Web Vitals report | Slow server, heavy scripts or layout shifts | 42 to 45 | Fix by URL group, then wait 28 days |
| Rich result impressions drop | A template release or a retired feature such as FAQ | 56, 57, 61 | Compare each template with Google’s gallery |
| Old domain or http pages still ranking | Redirects only at the root, or a missed variant | 19, 27, 29 | Redirect every URL, then file Change of Address |
| Impressions up while clicks fall | AI answers absorbing informational clicks | 67, 70 | Segment by intent, then check the Generative AI report |
How Do You Confirm a Fix Worked?
Rerun the same checks after the fix ships. For example, a robots.txt or noindex fix shows up in the URL Inspection tool on the next crawl, while a Core Web Vitals fix needs the full 28-day field window before the report changes. If the symptom stays after that, move to the next likely cause in the row.
Which Tools Do You Need for Each Technical SEO Check?
Google Search Console is the most used tool on this list: it appears in the how-to of 17 of the 105 checks. A site crawler comes next at 14, then keyword and backlink tools and Google search operators at 12 each. And 9 of the 14 Critical checks need nothing more than Search Console, the Rich Results Test, search operators or a plain browser.
We counted every tool named in the How to check column of the tables above. A check can name more than one tool, so the counts overlap.
| Tool | Who provides it | Checks that use it | Count |
|---|---|---|---|
| Google Search Console | Google, free | 1, 2, 9, 10, 16, 18, 24, 30, 42, 44, 45, 50, 51, 61, 67, 69, 91 | 17 |
| A site crawler or site audit tool | Third party | 4, 6, 7, 11, 12, 13, 14, 30, 31, 33, 34, 35, 37, 38 | 14 |
| Keyword and backlink research tools | Third party | 77, 78, 79, 80, 82, 86, 87, 88, 99, 100, 102, 103 | 12 |
| Google search operators (site:, inurl:, filetype:, intitle:) | Google, free | 16, 17, 19, 21, 23, 29, 32, 46, 49, 53, 54, 97 | 12 |
| Server or CDN logs | Your host or CDN | 9, 12, 38, 43, 47, 62, 63, 65, 71 | 9 |
| Chrome DevTools and view-source | Built into Chrome, free | 22, 34, 41, 59, 73, 74 | 6 |
| PageSpeed Insights or Lighthouse | Google, free | 40, 42, 43, 45 | 4 |
| Bing Webmaster Tools | Microsoft, free | 2, 16 | 2 |
| Google Analytics 4 | Google, free | 3, 91 | 2 |
| Rich Results Test and Schema.org validator | Google and Schema.org, free | 57, 58 | 2 |
Which Critical Checks Need Paid Tools?
The five Critical checks that need more than free tools are 4 (a crawler), 46 (a malware scan), 47 (an uptime monitor), 48 (a firewall with bot rules) and 77 (a keyword tool positions report). In contrast, everything else on the Critical list can be done today with what Google gives you for free. To validate markup quickly while you work through pass 7, use our free schema checker.
Bing Webmaster Tools only appears twice, but do not read that as low importance. After all, it is the only free first-party source of Copilot citation data, which is why it sits in pass 1 next to Search Console.
Which Checks Change on Shopify, WooCommerce and Magento?
The 105 checks stay the same on every platform, but the weak spots move. Shopify limits what you can see, while WooCommerce and Magento give you more control and more ways to create duplicate URLs. So run the full list, then spend extra time on the checks below for your platform.
| Platform | Checks that need extra care | Why | Deep dive |
|---|---|---|---|
| Shopify | 10, 17, 26, 62 to 65 | Duplicate product URLs, soft 404s and the default robots.txt, plus no raw server logs | Shopify SEO issues |
| WooCommerce | 2, 17, 21, 26 | Filter URLs that multiply, archives without canonicals and also an indexable cart and account area | WooCommerce technical SEO |
| Magento | 10, 17, 27 | Layered navigation creates faceted URL bloat unless filters are controlled | Magento layered navigation SEO |
| Any large store | 9, 35, 41 | Category architecture, variant URLs and pagination, as well as headless JavaScript storefronts | ecommerce technical SEO |
How Often to Run a Technical SEO Audit
Cadence depends on site size and on how much changes between audits. If you are budgeting for one rather than running it yourself, our breakdown of what an SEO audit costs covers the ranges and what drives them.
| Site size | Full 105-point audit | Critical items only | Log analysis |
|---|---|---|---|
| Under 500 URLs | Twice a year | Quarterly | Twice a year |
| 500 to 10,000 URLs | Quarterly | Monthly | Quarterly |
| Over 10,000 URLs | Quarterly | Monthly | Monthly |
| After any migration | Immediately, then at 30 days | Weekly for a month | Weekly for a month |
Where the Data in This Checklist Comes From
Most technical SEO checklists cite nothing. In fact, of the fourteen we audited, four of the highest-authority pages carry no external statistics at all. So it is worth being explicit about where the numbers on this page came from.
The field observations quoted throughout are drawn from five practitioner sessions, each linked below. Where a figure is a single practitioner’s reported client result rather than a published study, we have said so in the text rather than dressing it up as research.
| Source | What it contributed to this checklist |
|---|---|
| AirOps and Jairo Guerrero, Tech SEO Checklist for AI Search Visibility | Crawl budget scaling, the 410 spam fix, log file analysis for AI bots, rendering gaps, accessibility tree, agent commerce, citation without crawl |
| Ahrefs, A Basic Yet Powerful Technical SEO Audit for Beginners | Search operator recipes, the four-variant redirect test, exposed file discovery, WordPress footprints, title tag auditing at scale |
| Ahrefs, SEO Checklist: How to Get More Organic Traffic | Intent assessment, subtopic discovery, URL length, readability, internal and outbound linking, link prospecting |
| Semrush and Nathan Gotch, Comprehensive SEO Audit Guide | Position band analysis, cannibalisation auditing, intent mismatch, content audit decisions, backlink and anchor auditing |
| Eric Siu, Complete Guide to AI SEO in 2026 | Impressions up clicks down, multi-platform search, long tail strategy, AI automation of internal linking, citations as a broad category |
Google’s own documentation is the source for the Core Web Vitals thresholds, how Google treats 404 and 410 responses and the sitemap size limits, while the AI crawler rules come from OpenAI, Anthropic and Perplexity documentation.
Frequently Asked Questions
What is the difference between a technical SEO checklist and a technical SEO audit?
The checklist is the list of things to check, the audit is the act of checking them on a specific site. A checklist is reusable and generic. An audit produces findings, priorities and owners for one property at one point in time. Use this checklist as the input to your audit template.
How long does a technical SEO audit take?
Between four hours and three weeks, depending almost entirely on site size and log access. A small brochure site running the 50-item version takes a focused morning. A large ecommerce site with faceted navigation, multiple templates and log file analysis realistically takes two to three weeks including the write-up.
Do I need to fix every item on the checklist?
No, and trying to is the fastest way to fix nothing. Clear every Critical item first, because those block crawling, indexing or revenue outright. Then work through High items over the following month. Medium and Low items are batch work you schedule, not emergencies.
Should I block AI crawlers like GPTBot in robots.txt?
Only if you have a specific commercial reason, and even then, block selectively. GPTBot collects training data while OAI-SearchBot powers live answers. Blocking the second one removes you from ChatGPT citations entirely. Most businesses that want AI visibility should allow the retrieval agents and decide separately about the training ones.
Is llms.txt worth adding to my site?
It is cheap to add and currently unproven, so treat it as optional housekeeping rather than strategy. No major AI provider has committed to reading it, and it does not reflect how retrieval actually works. Add it if you want, then spend your real effort on indexation, snippets and rendering.
How do I know if AI systems can actually read my page?
Use view-source rather than inspect element, then check whether your key content is present in the raw HTML. If your headline, price or main answer only appears after JavaScript runs, most AI crawlers will miss it. Follow that with a server log check comparing HTML fetches against JavaScript loads for each named AI agent.
Why do my server logs show no AI crawler visits even though I get cited?
Because many citations never require a visit. AI systems query a search index first and receive a title plus a short snippet for each result. When that snippet answers the prompt, the model writes its answer without fetching your page. Your logs will therefore always under-report AI visibility.
Can an AI agent complete a purchase on my website?
Only if your interactive elements are real semantic HTML. Open Chrome DevTools, view the accessibility tree, and check whether your primary action has a button or link role with a clear accessible name. A styled div reads as an inert rectangle to an agent, so the flow fails silently.
What is the most commonly missed check on this list?
Confirming that the http to https and www redirect applies site-wide rather than only on the home page. We find this on a meaningful share of audits. The root redirects perfectly, every inner URL stays reachable on all four variants, and the whole site quietly runs as duplicates.
Does schema markup help you get cited in AI search?
Not directly. Google’s own documentation on AI features states there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode. What it does ask is that the page is indexed, eligible to be shown with a snippet, and that its structured data matches the visible text. Accurate schema will not win you a citation on its own, but inaccurate schema can cost you one.
Should I remove FAQ schema now that Google has dropped FAQ rich results?
No need to rip it out. Google stopped showing FAQ rich results on 7 May 2026 and confirmed the markup causes no problems if it stays. Just stop treating it as a deliverable, remove it from new templates, and stop reporting FAQ impressions that no longer exist.
Can you opt your site out of AI Overviews and AI Mode?
Yes. Search Console has a Search generative AI control, under Settings, that excludes your site’s links and content from AI Overviews, AI Mode and generative AI features in Discover. Google says it is not used as a ranking or inclusion signal for other parts of Search, and changes generally take a few days. Page-level controls such as nosnippet, data-nosnippet, max-snippet and noindex also limit what Google shows.
Do you need to break content into small chunks for AI search?
No. Google’s guide to optimizing for generative AI features, added in May 2026, says there is no requirement to break content into tiny pieces for AI to understand it, and that there is no ideal page length. Write sections that answer their heading directly, because that helps readers and snippets, but do not split pages into fragments for AI.
What should a technical SEO checklist include?
A technical SEO checklist should cover setup and access, crawlability, indexation, robots.txt, canonicals, site architecture, rendering, speed, security, mobile, template-level on-page elements, structured data and server logs. In 2027 it also needs AI crawler access, AI search visibility and agent readability. This one adds keyword, content and link diagnostics, for 105 checks in total.
Is a 410 better than a 404 for SEO?
Not for Google rankings. Google’s HTTP status code guide (checked October 29, 2026) treats every 4xx code except 429 the same way, and Google’s John Mueller said in 2024 that the difference is too small to matter for SEO. Still, use 410 when a removal is deliberate, because it reads more clearly in logs, and never block junk URLs in robots.txt instead.
Do you need hreflang checks in a technical SEO audit?
Only if your site has versions of the same page for different languages or countries. In that case, check that every version lists itself and all the others, that each pair links both ways, that URLs are fully qualified and that an x-default page exists for unmatched visitors. Otherwise, single-language sites can skip hreflang entirely.
Does blocking Google-Extended remove you from AI Overviews?
No. Google says Google-Extended controls whether your content is used to train Gemini models and to ground answers in the Gemini apps and Vertex AI, and that it has no effect on Google Search. Instead, AI Overviews and AI Mode follow your Googlebot rules, your snippet controls and the Search generative AI control in Search Console.
Does crawl budget matter for a small website?
Rarely. Google’s crawl budget guide (checked October 29, 2026) is written for sites with more than a million pages that change weekly, sites with more than 10,000 pages that change daily, or sites with many URLs stuck in Discovered, currently not indexed. For smaller sites, Google says an up-to-date sitemap and regular Page indexing checks are enough.
Where to Start This Week
Pick three things. Run the four-variant redirect test on a deep URL. Also run the filetype searches for exposed documents. Then open your robots.txt and check each AI user agent line individually. Those three take under an hour combined and they surface the most expensive problems in this list.
After that, work the Critical items in order, then move to High. Do not start at item one and grind forward, because the numbering is a category order, not a priority order.
If you want a second pair of eyes on the results, we run this exact 105-point process for clients. Grab a Free ROI Audit and we will send you the findings with owners and priorities attached.











