Google's John Mueller says technical SEO still matters in the age of AI search
Google's documentation for AI Overviews and AI Mode keeps the usual indexing requirements and doesn't ask for any AI-only file, markup or structured data.

Google's John Mueller says technical SEO is still relevant for AI systems. In an interview with David Iwanow, he explained why: the new tools are built on the fundamentals of search, even when the purpose of the crawl is different.
According to Conversion, in a piece published on November 10, Mueller also pushed back on strategies that lean on short-lived tactics, such as producing listicles to sway recommendations. In his view, not every list is spam. What counts is what the content actually contributes and whether the site is building a solid foundation.
His comments line up with the documentation Google has already published for AI Overviews and AI Mode. It keeps the SEO fundamentals in place and doesn't add a mandatory technical layer of its own for these experiences.
What the documentation requires
To be eligible as a supporting link in AI Overviews or AI Mode, a page has to be indexed and eligible to be shown with a snippet. The documentation doesn't call for additional machine-readable files, AI-specific text files, special markup or any particular type of structured data.
The guidance is to follow existing best practices: allow crawling, make content discoverable through internal links and put important information in text. Structured data should match the visible content. Meeting all of these requirements doesn't guarantee that a page will appear.
Google Search's technical requirements come down to three minimum conditions: Googlebot can't be blocked, the page has to return an HTTP 200 status code and it needs indexable content. These are eligibility criteria, with no promise of ranking. Pages that require a login aren't available to the crawler as public pages, and server or URL errors can prevent the content from being processed.
Robots.txt and crawlers
Google distinguishes between common crawlers such as Googlebot, which follow robots.txt rules during automatic crawling, special-case crawlers tied to specific products, and user-triggered fetchers. That means not every request hitting your server should be read as a visit from the Search crawler.
Robots.txt controls which URLs a crawler can access, and blocking access doesn't prevent indexing: a URL can still show up in results when other pages link to it. To keep a page out of the results, the documentation points to mechanisms such as noindex and password protection.
What this means for brand teams
To show up in AI-generated answers in Google Search, the path Google describes is the SEO you already know: a crawlable, indexed page that returns HTTP 200 and has its content in text. Search Console's indexing and Crawl Stats reports, along with the URL Inspection tool, help you find whatever is blocking that access. On the content side, Google's guidelines call for originality, clarity, good sources and a title that describes the page without exaggeration, with no set word count.
Key questions
Do I need a special file or markup to appear in AI Overviews and AI Mode?
No. Google's documentation doesn't require machine-readable files, AI-specific text files, special markup or any special structured data.
What does a page need to be eligible for AI features in Google Search?
It has to be indexed and eligible to be shown with a snippet, with Googlebot allowed, an HTTP 200 response and indexable content. None of this guarantees it will appear.
Does blocking a page in robots.txt remove it from the results?
Not necessarily. The URL can still appear if other pages link to it. To prevent indexing, Google points to noindex or password protection.
Source: Conversion.