Switching from an SEO retainer to AEO is not a rebrand of the same work. It is a change in what you pay for, what you measure, and who does the doing. An SEO retainer buys rankings work: keywords, links, and pages that climb a results list. AEO buys readability work: pages, files, and markup that let AI assistants find your brand, state its facts correctly, and recommend it in an answer. The two overlap, and Google itself says optimizing for its generative AI features is still SEO, because those features run on the same ranking systems as classic search. But the overlap is not the whole job. The parts that do not overlap are the parts that decide whether an assistant can read you at all.
The switch works best as a staged move, not a hard cut. Keep the SEO work that still earns its keep, move the budget toward the AEO work that SEO never covered, and change the reporting so the new work is judged on its own terms. A switch done in one meeting usually ends with the old retainer wearing a new name and doing the old work.
Where it goes wrong
Most failed switches fail the same way: the name changes and nothing else does.
- The retainer is renamed and the deliverables stay the same. The agency sends the same keyword report with a new header, and the brand pays AEO prices for SEO work. If the monthly deliverable does not change, the switch did not happen.
- The brand drops SEO before AEO is ready. Google's own guidance says a page must be indexed and eligible to show in search with a snippet before it can appear as a supporting link in AI Overviews or AI Mode. Dropping the work that keeps pages indexed and snippet-eligible removes the foundation the AI features stand on.
- The new scope has no owner for the technical fixes. AEO work lands in code: robots.txt rules, llms.txt files, structured data, server-side rendering. A retainer that only produces documents and advice will report on the same gaps every month without closing them.
- The reporting still measures rankings only. Rankings tell you where a page sits in a list. They say nothing about whether an assistant cites your brand, states your price correctly, or recommends a competitor instead. A switch that keeps rank as the only metric cannot see whether the AEO work is working.
- The budget moves before the baseline is set. Without a scan of the current state, there is no way to tell what the new scope fixed. The brand pays for three months, asks what changed, and nobody can answer with anything but a feeling.
- The contract keeps paying for links that AI never reads. Link building is a classic SEO lever, and it still matters for the search index. But a link budget that eats the whole retainer leaves nothing for the files and markup that assistants actually read. The mix has to change, not just the label.
- The brand buys a tool instead of the work. Dashboards that track AI mentions are useful, and they are not a substitute for fixing the site. A monitoring subscription without a fix budget reports the same unreadable pages every month.
The steps
Step 1. Run a scan and keep the result as the baseline. The marketer runs the free scan at aizii.ai/aeo-scan before any contract changes, and saves the full fix list. This is the before picture. Every claim the new scope makes later is measured against it. Do not sign a new scope without it, because without it the agency can report activity forever without ever showing a change.
Step 2. Audit the current retainer line by line. The marketer lists every deliverable in the SEO retainer and sorts it into three piles: keep, because it feeds the search index that AI features draw on; move, because it is AEO work wearing an SEO name; and drop, because it serves neither. Keyword research, technical SEO, and content that answers buyer questions usually stay. Reporting on AI visibility, crawler access, and structured data usually moves into the AEO scope. Work that has produced the same report for a year with no change is a candidate to drop.
Step 3. Write the AEO scope around the gaps, not around a package. The marketer writes the new scope from the scan's fix list: crawler access for the search crawlers, llms.txt and the files that map the store, product schema with price and availability, category and guide pages that answer the questions shoppers ask assistants, and a routine for keeping prices and availability current. A scope written from a vendor's package list buys whatever the vendor sells. A scope written from your fix list buys what your store needs.
Step 4. Put a technical owner on the scope. The marketer confirms who writes the code: the agency's developer, your developer, or a freelancer with access to the theme and the server. AEO fixes that live only in a slide deck do not change the score. The contract should name the person who ships robots.txt changes, llms.txt publishing, and schema fixes, and it should state how many fixes ship per month. Advice without a shipper is a report, not a retainer.
Step 5. Change the reporting to match the new job. The marketer agrees on a monthly report that shows the scan score moving, the fixes shipped, the pages AI assistants cite, and the wrong answers corrected. Rankings stay in the report, because the search index still matters, but they stop being the only number. Ask the agency to show, each month, which fixes from the baseline are now closed. If the report cannot show that, the scope is not being delivered.
Step 6. Move the budget in stages. The marketer shifts a share of the retainer to the AEO scope in the first month, and the rest over the next two, as fixes ship and the score moves. A staged move keeps the SEO foundation funded while the AEO work proves itself, and it gives both sides a clean point to stop if the fixes are not shipping. Do not pay the full AEO price in the first month for work that has not been done yet.
Step 7. Set the renewal test in writing. The marketer writes one sentence into the agreement: the retainer renews if the scan score has moved, the fix list has shrunk, and the brand appears in AI answers for its core questions. The test is the same baseline from Step 1, re-run at renewal. A renewal decided on a feeling is a renewal decided by the agency.
The machine-readable piece
This is the llms.txt skeleton the new AEO scope should deliver in the first month. It follows the proposal format, and it is the first machine-readable file the switch should produce. It is a skeleton, not a finished file: the marketer fills in the real collections and guides, and the developer publishes it at the site root. Replace the placeholders with your own pages, replacing yourdomain.com with your actual domain.
# Harbor Furniture Co
> Harbor Furniture Co sells solid wood tables, chairs, and storage, made to order in its own workshop and shipped across the country. Lead times run six to eight weeks for made-to-order pieces.
## Shop
- [Dining tables](https://[yourdomain.com]/collections/dining-tables): Solid wood dining tables, listed with dimensions, wood species, and seating capacity.
- [Chairs](https://[yourdomain.com]/collections/chairs): Dining and lounge chairs, listed with seat height, wood species, and finish.
- [Storage](https://[yourdomain.com]/collections/storage): Sideboards, bookcases, and cabinets, listed with dimensions and shelf layout.
## Guides
- [Wood care guide](https://[yourdomain.com]/pages/wood-care): How to clean and oil solid wood furniture, with steps and products to avoid.
- [Lead times and delivery](https://[yourdomain.com]/pages/lead-times-delivery): How made-to-order lead times work, delivery options, and white glove service.
## Policies
- [Shipping and returns](https://[yourdomain.com]/pages/shipping-returns): Delivery windows, returns on stocked pieces, and the made-to-order policy.
If the agency cannot produce this file in the first month, that tells you more about the switch than any pitch deck will. It is one file, it takes a single sitting to draft, and it is the clearest early proof that the new scope is real work and not a renamed report.
What it looks like when it works
A working switch looks boring from the outside. The same brand, the same site, the same monthly meeting. What changes is what the meeting is about: fixes shipped, score moved, wrong answers corrected, and the next fixes in line. The SEO foundation keeps running underneath, and the AEO work builds on top of it instead of replacing it.
Say you run a furniture brand on a monthly SEO retainer, paying for keyword reports, a blog post, and a link report. Your brand rarely appears in AI answers, and when it does, the assistant quotes a discontinued table and a price from two seasons ago. The marketer runs the scan and saves the baseline. The retainer audit shows the blog post answers buyer questions well, so it stays, while the link report has shown the same numbers for a year, so its budget moves. The new scope is written from the fix list: crawler access, an llms.txt file, product schema with price and availability, and a routine that updates the catalog when a piece is discontinued. The agency names a developer who ships the fixes, and the monthly report shows the score moving and the fix list shrinking. Three months in, the assistant answers with the current table, the current price, and the current lead time. Nothing about the brand changed. The site became readable, and the retainer paid for the reading, not the reporting.
The fundamentals
These mechanics are shared across every engine and covered in full in their own guides:
- •The llms.txt format and a complete sample, see our guide to writing a good llms.txt file
- •The markup AI systems read to verify facts, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
What this guide does not cover
This guide covers moving a retainer from SEO to AEO. It does not cover choosing an agency, which is a separate decision with its own checks, and it does not cover the full technical audit that checks every crawler and every page, or the transaction layer that lets an agent complete a purchase. It does not cover what to do if your current agency cannot do the technical work, beyond the plain advice to find someone who can ship it. Those are separate jobs, and this guide is the map, not the whole trip.
Check your own store now
Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan
Run the free scanSources
- Google Search Central, Optimizing your website for generative AI features on Google Search (specific): https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
- Google Search Central, AI features and your website (specific): https://developers.google.com/search/docs/appearance/ai-features
- llms.txt proposal (specific): https://llmstxt.org
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Schema.org, Product type (specific): https://schema.org/Product
- RFC 9309, Robots Exclusion Protocol (specific): https://www.rfc-editor.org/rfc/rfc9309.html
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
