AI workflows / SEO and AEO teams

AI workflows for SEO and AEO: what to hand to AI, and what Google says you can skip

People now get answers from AI as well as from search results, so SEO includes being named in them. Five workflows I'd give to AI first, what Google says you can skip, and where a person stays in charge.

For
In-house SEO and content marketers, and agencies running search for clients
Start with
Search Console queries grouped by intent
Watch for
Pages made in bulk with nothing new in them, AI answers that describe you wrongly, crawlers you blocked by accident
Basis
My SEO and content work at Gaba Healthcare, plus Google, OpenAI, Bing and FTC documentation. I haven't run an AEO programme, so the AEO workflows are plans.

The short answer. Start AI on the sorting work in SEO: grouping search queries by intent, finding pages that are slipping, a weekly check of how AI answers describe your brand, and a crawl-access audit. Google says AI Overviews and AI Mode need no special markup or files, so AEO is mostly good SEO. A person adds what only you know and checks every claim.

Where SEO and AEO get stuck

SEO teams lose hours to sorting: query exports, page lists, decay checks, briefs. AEO adds a new question on top. AEO means getting named when someone asks an AI assistant. If a buyer asks ChatGPT or Google’s AI Mode about your category, what does it say, and does it mention you?

The reassuring part is that Google doesn’t ask for much that’s new. Its documentation says: “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.” A page has to be indexed and eligible to show with a snippet. That is ordinary SEO. So the first gain from AI is time back on the old work.

I did this work at Gaba Healthcare. Organic visitors grew from 5,000 to 9,000 a month, with patient-education articles grouped by topic, and SEO brought in 35% of qualified calls. Several changes ran at the same time, so I can’t split the credit. Sorting and checking is the part I’d now give to AI. I haven’t run an AEO programme, so the AEO workflows below are plans.

What Google says you can skip

Google’s documentation lists things you don’t need for its AI features:

llms.txt or other AI text files. “You don’t need to create new machine readable files, AI text files, or markup.”
Special schema. There is “no special schema.org structured data that you need to add.”
Rewriting or chopping pages into small pieces. Coverage of Google’s May 2026 guide says its systems can find the relevant part of a page. That’s a secondary report, so check Google’s own page.

This site has an llms.txt file. It costs nothing, but Google says you don’t need it, and I haven’t found independent evidence that it changes what other assistants cite. I wouldn’t spend a day on it.

The workflows I’d build first

1. Group search queries by intent

In: twelve months of Search Console queries, with pages, clicks and impressions.
AI does: groups queries by what the searcher wants (learn, compare, buy), flags pairs of your pages that compete for one query, and lists query groups with impressions but no page.
A person checks: someone who knows the product reads every group, merges the bad ones, and rejects any “gap” you already cover under another name.
Measure: hours to produce the content plan, and the share of planned pages that earn impressions within 90 days.

2. A refresh queue for pages that are slipping

In: page-level clicks by month, and the current text of each page.
AI does: ranks pages whose clicks have fallen over three months and, for each, lists what is out of date or thin: old figures, a missing question, dead links. It doesn’t rewrite the page.
A person checks: a writer adds something that only you have: a number from your own data, a real customer question, a screenshot. Coverage of Google’s guide says it asks for “non-commodity content”, meaning more than anyone could write from common knowledge.
Measure: clicks to refreshed pages in the eight weeks after, against the eight weeks before, with a few similar untouched pages as a comparison.

3. A weekly check of AI answers

In: 20 to 30 real questions buyers ask, taken from sales calls, support tickets and Search Console.
AI does: asks each question in the assistants you care about, and logs whether you’re named, which sources are cited and how the answer describes you. Check each tool’s terms before automating this. Where they don’t allow it, do it by hand. It’s a short list.
A person checks: someone reads the log for wrong or stale statements about you, and picks the three that matter most.
Measure: the share of questions where you’re named, and the wrong statements fixed. Answers change from run to run, so I’d read a month of logs as a trend and not trust one run.

I haven’t found an independent study that shows which page features cause a citation. The large citation studies come from companies that sell tracking tools, and their findings suggest that different assistants cite different sites. I use them for ideas and check each assistant myself.

4. A crawl-access audit

In: your robots.txt, the pages that matter most, and the Search Console indexing report.
AI does: reads robots.txt and robots meta tags, and lists which crawlers can reach which pages, plus pages that aren’t indexed or carry a nosnippet rule.
A person checks: each block is a decision someone made on purpose. Two facts to know. For Google’s AI features, a page must be indexed and snippet-eligible. For ChatGPT, OpenAI says OAI-SearchBot is the crawler that surfaces sites in its search results. A blocked site “will not be shown in ChatGPT search answers, though can still appear as navigational links.” GPTBot is a separate crawler for training, and blocking it doesn’t affect search.
Measure: important pages that are blocked or unindexed by accident, which should be zero.

5. Find where the answers get their facts

In: the log from workflow 3, with the URLs each answer cited.
AI does: groups the cited sources by type (your site, review sites, forums, news, competitors), and lists the questions where you’re missing and who is cited instead.
A person checks: whether each gap is real, then picks the honest response: improve your own page, publish your data, correct an outdated listing, or ask customers who really use the product to review it. Never write or buy reviews. The FTC’s final rule bans fake reviews, including AI-generated ones by “someone who does not exist”.
Measure: gaps closed, and questions where you move from missing to named over three months.

Where a person stays in charge

Every claim and number in anything you publish.
What’s new in the page. AI sorts and drafts. The original data and the point of view come from you.
Reviews and testimonials. Only from real customers.
The decision to block or allow a crawler.
What to publish at all.

What can go wrong

Pages made in bulk. Google’s spam policy defines scaled content abuse as many pages generated “for the primary purpose of manipulating search rankings and not helping users”, and says it applies “no matter how it’s created”. Using generative AI to make many pages without adding value is one of its examples. I’d publish nothing in bulk.
Reading citations as traffic. Bing’s AI Performance report shows citation counts, and Bing says they don’t show placement or importance. Google’s new report shows impressions, and its announcement names no click data.
An AI answer that gets you wrong. Find where it learned it. The cause is usually an old page or listing, and you can fix those.
Chasing every new tactic. Much of what’s sold as AEO is what Google says it doesn’t need.

The first 30 days

Week 1: export Search Console, list 25 buyer questions, and read robots.txt.
Week 2: run workflow 1 and the crawl-access audit, and fix any accidental blocks.
Week 3: run the first AI answer check by hand and log it.
Week 4: refresh the five most slipping pages with something original, and repeat the answer check.

How I’d measure it

Hours saved on the content plan, clicks to refreshed pages, the share of buyer questions that name you, and wrong statements fixed. For tools: Google says its Search Generative AI performance reports show impressions in AI Overviews, AI Mode and Discover by page, country, device and date. Bing’s AI Performance report, in public preview since February 2026, shows citations by page and query. Neither shows ChatGPT, so for that I’d use your analytics referral report and the weekly log.

Questions people ask

Is AEO different from SEO?

Mostly not, for Google. Its documentation says there are no additional requirements to appear in AI Overviews or AI Mode, and coverage of its May 2026 guide reports that it calls optimising for AI search still SEO. The new part is measuring: checking what AI assistants say about you, which Google's own reports don't cover.

Do I need llms.txt or special schema to appear in AI answers?

Not for Google. Its documentation says you don't need new machine-readable files, AI text files or markup, and no special schema.org data. I haven't found independent evidence that llms.txt changes what other assistants cite, so I'd treat it as optional.

Will Google penalise AI-written pages?

Not for using AI. Its spam policy targets many pages made mainly to manipulate rankings, 'no matter how it's created', and lists using generative AI to make many pages without adding value as an example. AI-assisted pages with something new in them aren't the target.

How do I know whether ChatGPT or Copilot mentions my brand?

Ask each assistant the questions your buyers ask, write down whether you're named and which sources it cites, and repeat every week. For Copilot, Bing Webmaster Tools has an AI Performance report that counts citations. Search Console's new report covers Google's AI features and shows impressions.

Hi, I’m Aditya.

How do you want to grow?

Up and down to move. Enter to open. Esc to close.