Run one workflow, not two: Google states that SEO best practices remain relevant for its AI features and that no additional requirements or special optimizations are needed (1). Recala's scope covers content strategy, articles and on-page preparation for SEO, GEO and AEO, so we treat AEO as an editorial layer worked on alongside SEO.
How do I optimize for SEO and AEO at the same time?
Start with the fundamentals and treat AEO as additions to them (1). A page can be shown as a supporting link only if it is indexed and eligible to appear in Google Search with a snippet, and Google names no further technical requirements.
In practice that means allowing crawling in robots.txt and by any CDN or hosting layer, making the page findable through internal links, putting important content in text, and giving users a good page experience (1). Support text with high-quality images and video where they fit, and keep structured data matching the visible text. You do not need new machine-readable files, AI text files or special schema.org markup.
Shared SEO and AEO foundation: what to do and what to confirm (1) Google also says that both AI Overviews and AI Mode may use a query fan-out technique, issuing multiple related searches across subtopics and data sources, and that its models identify more supporting web pages and so can display a wider and more diverse set of links than a classic web search. Google's guidance is that these fundamentals already cover AI features, so the work for AEO begins on top of the same page.
Recala's scope covers content strategy, articles and on-page preparation for SEO, GEO and AEO. Recala's current mission explicitly excludes guaranteed rankings and guaranteed AI citations, so the decision here is whether one workflow can carry both goals, and the shared SEO foundation is the basis for that choice.
Shared SEO and AEO foundation: what to do and what to confirm
| Step | Google's rule | What to confirm |
|---|---|---|
| Make the page indexable with a snippet | A page must be indexed and eligible to be shown in Google Search with a snippet to be a supporting link in AI Overviews or AI Mode | The page is indexed and eligible to show a snippet in Search |
| Allow crawling | Ensure crawling is allowed in robots.txt and by any CDN or hosting infrastructure | Neither robots.txt nor the CDN or host blocks the page |
| Link the page internally | Make content easily findable through internal links on your website | The page is reachable through internal links |
| Keep key content in text | Make sure important content is available in textual form | The key answer appears as text on the page |
| Match structured data to the page | Make sure structured data matches the visible text on the page | Every marked-up fact is visible on the page |
| Skip special AI files and markup | You don't need new machine-readable files, AI text files or markup, and no special schema.org structured data is required | No AI-only file or markup was added for AI features |
What do I add on the page for AEO without breaking SEO?
Recala uses AEO to mean structuring content so an answer engine can extract a direct, citable answer. This is Recala's working definition rather than an official standard. Give each section a direct answer to a real buyer question, written in the buyer's language.
A question-shaped heading helps when it fits the reader's task, but a forced label does not. A heading that resembles a search query is not enough if the section beneath it never resolves that question. Recala treats clear answers as editorial practice, not as a promised citation lift.
Any structured data you add must describe content a reader can see (2). Google's guidelines say not to mark up content that is not visible on the page, so the markup you add for AEO must match the article you publish. Google's documentation says no special schema is required for AI features (1). Google's structured data guidelines also say that a page can lose eligibility for rich results through a manual action, although a structured data issue does not change how the page ranks in web search (2). Image URLs referenced in structured data must be crawlable and indexable, and you can check this with the URL Inspection tool in Search Console.
How do I track organic rankings and AI citations in one reporting setup?
For Google, sites that appear in AI Overviews and AI Mode are included in overall search traffic in Search Console, and they are reported in the Performance report under the Web search type (1). Rankings and Google AI traffic therefore already share one report. In Recala's baseline, ChatGPT and Gemini answers were captured separately from Google organic and AI Overview results, each through its own scraper or SERP task.
Recala's baseline of 2 October 2026 used anonymous DataForSEO captures in English for market Spain, covering 81 buyer questions and 648 captured answers across Google organic results, AI Overviews, ChatGPT and Gemini. recala.co, measured before its first article aimed at those questions, was cited 0 times and named 0 times in the answer text. Failed captures were recorded as unknown, not as not cited.
Keep rankings, explicit answer citations and internal quality scores in separate rows, because internal scores are not observed search outcomes. This baseline describes one domain on 81 questions at one point in time, not traffic, leads or revenue.
Google's robots.txt specification says the rules apply only to the host, protocol and port where the file is hosted, so a crawl rule on one host does not govern another (3). Google may index a URL blocked for crawling and still show it in results without a snippet, so a blocked page can appear without its content being used.
Next step
Continue with Recala to turn this plan into a concrete next step.
Sources
AI features and your website, Google Search Central (Google for Developers), last updated 10 December 2025developers.google.com
General Structured Data Guidelines / Google Search Central / Documentation / Google for Developers, Google, last updated 10 July 2026developers.google.com
How Google interprets the robots.txt specification, Google for Developers, last updated 23 October 2026developers.google.com