The Technical SEO Checklist That Still Wins in the AI Search Era

Every conversation about GEO and AEO eventually hits the same wall. An AI tool can't cite a page it can't reach. Google can't feature a snippet from a page it hasn't indexed cleanly. A slow, unstable page loses humans and machines alike.

That's why I still start every engagement with a technical SEO checklist, before any content or AI-search work. Technical SEO is the work of making a site easy for search engines and AI crawlers to find, render, understand and index. It isn't glamorous, but it sets the ceiling for everything built on top of it.

Below is the checklist I run on audits, grouped into six areas, with the official thresholds and documentation for each. Work through it in order: problems in the first sections can cancel out every improvement in the later ones.

1. Crawlability and Indexation

If search engines can't crawl and index a page, nothing else on this list matters for it. Check these first.

• Robots.txt doesn't block important sections. Read it line by line; a stray Disallow: / from a staging site is more common than you'd think. Google's robots.txt introduction explains the rules.
• Robots.txt treats AI crawlers deliberately. Decide which of GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and Google-Extended you allow, rather than inheriting a plugin's defaults.
• The XML sitemap lists only canonical, indexable URLs that return a 200 status, and it's submitted in Search Console. See Google's sitemaps overview.
• No important page carries a noindex tag or an X-Robots-Tag header by mistake.
• Search Console's Pages report shows no unexpected spikes in "Excluded" or "Not indexed" URLs.
• Every important page can be reached through internal links within a few clicks of the homepage. Orphaned pages get crawled less often.

2. Canonicals, Redirects and Duplicates

Duplicate URLs split signals and waste crawling. The aim is one clear URL for each piece of content.

• Every page has a self-referencing canonical tag, and canonicals point to URLs that return 200, not to redirects or 404s. Google's guide to consolidating duplicate URLs covers the options.
• HTTP, HTTPS, www and non-www versions all redirect to one preferred version in a single hop.
• No redirect chains or loops. Each old URL should go straight to its final destination.
• URL parameters for sorting, filtering or tracking don't create indexable duplicates.

3. Core Web Vitals and Page Experience

Google's Core Web Vitals measure loading, responsiveness and visual stability using real-user data. A page passes when at least 75% of visits meet the "good" threshold for each metric.

Interaction to Next Paint (INP) replaced First Input Delay as a Core Web Vital in March 2024, so older audits that only report FID are out of date. Check field data in Search Console's Core Web Vitals report, and test on a mid-range phone, not only on a developer's laptop.

Serve images in WebP or AVIF with explicit width and height attributes, and lazy-load images below the fold. Those three changes alone fix a large share of the slow, shifting pages I audit.

4. Rendering and JavaScript

Google can render JavaScript, but it takes extra work and isn't always immediate. Many AI crawlers don't run JavaScript at all.

• Key content, links and meta tags appear in the HTML the server sends, not only after scripts run. View the page source, not the inspector, to check.
• Links use real <a href> elements rather than click handlers, so crawlers can follow them.
• Important pages don't depend on content loaded only after a user scrolls or clicks.
• Google's JavaScript SEO basics cover the details for single-page apps and frameworks.

5. Structured Data as the Entity Layer

Structured data tells search engines and AI systems what a page is about and who's behind it. Treat it as an accurate description of the page, not a ranking trick.

• Organization or Person markup on the homepage, consistent with your Google Business Profile and social profiles.
• Article, Product, Service or LocalBusiness markup that matches what the page visibly says, and nothing more.
• Breadcrumb markup that mirrors your site structure.
• Validated in Google's Rich Results Test, not assumed correct because a plugin generated it.

Don't build plans around FAQ or HowTo rich results. Google limited FAQ rich results and phased out HowTo rich results in 2023.

Technical SEO is the plumbing. GEO and AEO are what you build on top of it. Skip the plumbing and the building doesn't stay up.

6. Security, Mobile and Site Architecture

• The whole site runs on HTTPS with a valid certificate, and no pages load mixed HTTP content.
• HSTS is enabled so browsers always use the secure version.
• Pages work fully on mobile: readable text, tappable buttons, no content hidden on small screens. Google indexes the mobile version of your site.
• A clear heading structure on every page: one H1 that states the topic, with H2 and H3 headings nested logically beneath it.
• A flat, logical URL structure that tells people and crawlers where they are.
• A custom 404 page that helps visitors find their way, and that returns a real 404 status code.

How to Run This Technical SEO Checklist

You don't need expensive software to start. A practical order:

1. Open Search Console and review the Pages, Sitemaps and Core Web Vitals reports. They show what Google actually sees.
2. Crawl the site with a desktop crawler to find redirects, broken links, missing canonicals and duplicate titles across every URL.
3. Read robots.txt and the sitemap manually. Both are short, and both cause outsized damage when wrong.
4. Test your five most important templates, such as the homepage, a service page, a blog post and a product or location page, in PageSpeed Insights and the Rich Results Test.
5. Fix in the order of this checklist: indexing problems first, polish last.

For a quick first pass on your homepage, the free SEO audit checks robots.txt, the sitemap, canonical tags, structured data and AI crawler access in about a minute. It won't replace a full crawl, but it shows where to look first.

Read more: Free SEO Audit: How It Works and What It Tells You

Frequently Asked Questions

What is included in a technical SEO checklist?

A technical SEO checklist covers crawlability and indexation, canonical tags and redirects, Core Web Vitals and page speed, JavaScript rendering, structured data, HTTPS, mobile usability and site architecture.

What are the Core Web Vitals thresholds?

A page is rated good when Largest Contentful Paint is 2.5 seconds or less, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift is 0.1 or less, measured at the 75th percentile of real visits.

Does technical SEO matter for AI search?

Yes. AI search tools can only cite pages they can reach and read. Blocked crawlers, content that only appears after JavaScript runs, and pages missing from the search index all reduce your chances of being cited.

How often should I run a technical SEO audit?

Run a full audit at least once a year and after any redesign, CMS migration or major template change. Check Search Console's indexing and Core Web Vitals reports monthly to catch problems early.

Fix the Foundation First

AI search has changed where answers appear, but not what they depend on. Pages still need to be reachable, indexable, fast and clearly described before any search engine or AI tool will trust them.

Start with section one this week. Read your robots.txt, check the Pages report in Search Console, and confirm your most important URLs are indexed. Once the foundation holds, every content and GEO improvement you make has room to work.