Technical SEO in the AI Era: The Complete Checklist
On this page
Technical SEO used to mean keeping Google’s crawler happy. In the AI era it means keeping two audiences happy: Google’s crawler, and the AI crawlers that feed ChatGPT, Perplexity, Gemini, and Google AI Overviews. The good news is the checklist is mostly shared. The bad news is mistakes now cost you twice, because a site that AI crawlers cannot read is a site AI engines cannot cite.
The 2026 checklist
Crawlability
- robots.txt allows the crawlers that matter, including the AI crawlers like GPTBot, ClaudeBot, and PerplexityBot. Blocking them guarantees invisibility in AI answers.
- A clean internal link structure: every important page reachable within a few clicks, no orphan pages.
Indexation
- One canonical URL per page; no duplicate or near-duplicate pages fighting each other.
- No noindex tags left behind from a redesign, the single most common finding in Irish audits. Our redesign guide makes this a launch step.
- XML sitemap submitted and error-free in Search Console.
Machine readability
- JSON-LD structured data on every template that deserves it: Organization, LocalBusiness, Product, FAQPage, Article. The how-to is in our structured data guide.
- An llms.txt file at the site root summarizing the site for AI agents.
- Clean HTML: semantic headings, alt text, no content hidden behind JavaScript.
Performance
- Core Web Vitals in the green, especially on mobile, per the speed guide.
- Fast server response and compressed images, because both Google and AI crawlers deprioritize slow sites.
The audit order
- Crawl the site and diff against the sitemap.
- Check the Pages report in Search Console for exclusions.
- Validate structured data page by page.
- Audit speed on the top ten pages.
- Review robots.txt and llms.txt.
Fix in that order: indexation first, structure second, speed third.
Where it fits in the bigger picture
Technical SEO is the foundation layer under everything else we publish: getting cited by AI, GEO, and local search all assume a site that crawlers can read. It ships inside our AI search visibility service, because a technical fix that is not implemented is just a report.
Frequently asked questions
What is technical SEO?
The engineering side of search: making your site crawlable, indexable, fast, and machine-readable, so search engines and AI crawlers can read and trust it.
What changed about technical SEO in the AI era?
The audience doubled. You now optimize for two readers: Google's crawler and AI crawlers feeding ChatGPT, Perplexity, Gemini, and AI Overviews. The checklist below covers both.
Should I allow AI crawlers in robots.txt?
Yes, if you want AI citations. Blocking GPTBot and similar crawlers guarantees you will not be cited. Keep them allowed, and use llms.txt to guide them.
How do I run a technical SEO audit?
Crawl the site, check indexation in Search Console, audit speed with PageSpeed Insights, validate structured data, and review robots.txt and llms.txt. Fix in that priority order.
What is the biggest technical SEO mistake on Irish SME sites?
Accidentally blocking crawlers: a noindex tag left on after a rebuild, or robots.txt rules from a staging environment that went live. We find it constantly.
Do I need a developer for technical SEO?
Most fixes need one, yes. That is why technical SEO lives inside our AI search visibility service rather than being sold as a separate report.