Type is aeo just seo into a search bar and you will get the same ten recommendations from every article that comes back. Add schema markup. Use clear headings. Improve page speed. Write in a question and answer format. Build topical authority.
None of that is wrong. All of it is 2015 technical SEO, and the reason it keeps getting published as AI search strategy is that it is safe, familiar, and easy to sell as a deliverable. It also stops well short of the part that decides whether a model names you.
Ranking and being quoted are different jobs
A search engine ranks documents. It decides which page best matches a query, hands over ten of them, and lets the human choose. A language model constructs an answer. It decides which claims to state, then which sources support those claims well enough to be worth naming.
What helps a page rank
- Keyword coverage and query match
- Links pointing at the page
- Technical crawlability and speed
- Comprehensiveness relative to competing pages
What helps a passage get quoted
- A self contained claim that survives being lifted out of context
- A specific number, date and named source attached to the claim
- Agreement across independent sites about who you are and what you do
- Presence in the sources the model already treats as reliable for the topic
Verdict: Overlap exists, but the right column is where the difference is decided, and it is the column almost nobody works on.
The three things that actually differ
- 1
Extractability
A model lifts passages, not pages. If the answer to the question in your heading takes four paragraphs of preamble to arrive at, it will not be lifted. Put the complete answer in the first two sentences under the heading, then expand. This feels like bad blogging and it is exactly what gets quoted.
- 2
Verifiability
Unsourced assertions are the cheapest thing on the internet and models treat them accordingly. A claim with a named study, a date and a number is safer to repeat than the same claim stated confidently. If your content contains no numbers you can defend, it will lose to content that does.
- 3
Consensus
This is the one that has no SEO equivalent worth the name. Models synthesise across sources. If your site says you serve mid market fintech, a review platform says SMB retail, and three listicles put you in a different category entirely, the model resolves the conflict by describing you vaguely or skipping you. Off site agreement about your category is not brand hygiene, it is a ranking input.
You cannot optimise your way into an answer that a model does not trust enough to attribute.
Worked example
The same page, judged two different ways
A vendor publishes a 1,800 word guide to a category term. For SEO purposes the page ranks position four within six months: solid keyword density, three internal links, a fast load time. For AEO purposes, three independent assistants were asked the equivalent question over the same period.
- Google organic position
- 4, stable
- Times cited across 3 assistants, 20 prompt runs
- 2 out of 60 possible citations
- Reason given when checked manually
- No dated source behind the central claim
Result: Ranking position four did nothing for citation rate, because the page made a confident claim with no attached study. Adding one sourced statistic and a publication date to the opening paragraph took the citation count from 2 to 11 out of 60 over the following quarter, with no change to the page's search ranking at all.
Where schema actually earns its place
I am not arguing against structured data. It resolves ambiguity cheaply. It tells a parser which entity you are, when a page changed, who wrote it and what their credentials are. That matters, and it costs an afternoon.
What it does not do is make an unsupported claim credible or resolve a contradiction between your site and the rest of the web. Schema is punctuation. It clarifies a sentence that already says something. Most AEO advice sells punctuation as an argument.
5
re-ranking criteria applied between retrieval and citation
Scientific Institute for Generative Intelligence (SIGI-2026-056), March 20261
afternoon to add schema, versus weeks of outreach for consensus
A quick test for any AEO recommendation
Ask these before you spend a quarter on it
- ✓Would this recommendation have been valid advice for Google in 2018? If yes, it is table stakes, not strategy.
- ✓Does it change what a model can verify about us, or only how our HTML is arranged?
- ✓Does it affect anything outside our own domain? If not, it cannot move consensus.
- ✓Can we tell whether it worked by checking whether we get named in a fixed prompt set?
The counter-argument: technical SEO still funds this
"If technical SEO does not move citations, why keep doing it"
If schema, headings and page speed are table stakes rather than strategy, an obvious response is to stop paying for them and put every hour into outreach and sourcing instead. Some teams have made exactly that call this year.
That call misreads what the technical work is for. It is not the differentiator, but it is the floor a model has to clear before it can consider citing you at all. A page that is not crawlable, is not indexed, or loads so slowly the crawler times out never reaches the stage where extractability or sourcing matters. Keep the technical work as a maintenance cost, not a growth lever, and put the marginal hour into the sourcing and consensus work that actually moves the needle. The mistake is not doing SEO, it is budgeting a strategy quarter for it.
AEO best practices worth keeping versus worth retiring
| Practice | Keep or retire as AEO strategy | Why |
|---|---|---|
| Schema and structured data | Keep, but as maintenance | Resolves ambiguity, does not build trust |
| Answer-first paragraph structure | Keep, this genuinely differs | Extractability is a real citation factor |
| Backlink building for domain authority | Retire as a headline tactic | Weak proxy for the consensus signal models use |
| Sourcing every material claim with a date | Keep, underused | Directly maps to the verifiability factor |
| Correcting third party descriptions of you | Keep, highest yield | Consensus has no on site substitute |
| Chasing topical authority via volume of posts | Retire as a headline tactic | Volume does not fix a contradiction elsewhere on the web |
The honest summary is that the technical layer is a one time cost and the credibility layer is the ongoing work. Teams keep buying the first because it has a clear finish line, and avoiding the second because it involves other people's websites, real research, and having something specific to say.
Why this keeps happening in the industry
Agencies and consultants sell what can be scoped and delivered on a timeline. Adding schema to forty pages is a project with a start date and an end date. Getting a review platform to update a category tag is a negotiation with a third party who owes you nothing, on a timeline you do not control. One of those fits neatly into a retainer. The other does not, so it gets left off the deliverables list even when everyone involved knows it matters more.
The result is an entire content category, AEO advice, that mostly describes work adjacent to the actual mechanism. It is not dishonest so much as incomplete, written by people optimising for what is easy to promise rather than what is proven to move a citation.
Answer engine optimization tips that actually require new work
- Build a prompt set of the twenty questions your buyers ask before choosing a vendor, and run it monthly against the major assistants, logging who gets named and from what source.
- Email the authors of the three most quoted roundups in your category and correct any factual error, however small it looks. Small errors compound into a vague or wrong description.
- Turn every internal statistic you already have, win rate benchmarks, implementation timelines, cost ranges, into a dated, sourced sentence a model can lift whole.
- Audit review platforms for stale category tags. A tag set two product pivots ago is quietly overriding your current positioning in every answer that cites it.
None of this shows up on a technical SEO audit, because none of it lives inside your own domain. That is exactly why it gets skipped by teams that treat AEO as an extension of the SEO checklist rather than a separate discipline with its own inputs.
What the myth of 'aeo is just seo' costs you
Treating this as a rebadged discipline has a real cost, not just a semantic one. Teams that assume the SEO checklist covers AEO tend to spend a quarter shipping schema and heading fixes, see no movement in citation rate, and conclude that AEO does not work or cannot be measured. Both conclusions are wrong. The measurement exists, it just is not on the page you were optimising. It is on the four external sources that still describe you incorrectly and that nobody assigned anyone to fix.
What actually changed underneath the checklist
Search ranking and citation selection are not two flavours of the same algorithm, they are two different jobs running on different inputs. A ranking algorithm reads a page once, scores it against a query, and slots it into a list. A model reads dozens of pages at once, decides what the answer should say, and only then looks for a source willing to back each sentence. That second step, backing a sentence, is where almost all of the recycled SEO advice quietly stops applying.
This is why a page can rank on page one and still be cited zero times across a month of prompt runs. Ranking asked whether the page was the best match for a query. Citation asks whether any single sentence in that page is specific enough, sourced enough and unambiguous enough to lift whole into someone else's answer. Those are different bars, and the second one is higher.
Two different filters on the same page
Crawl
Both systems need to fetch and parse the page
Ranking filter
Query match, links, speed, comprehensiveness
Citation filter
Extractable claim, named source, cross site agreement
Outcome A
Ranks well, gets clicked by a human
Outcome B
Gets lifted whole into a generated answer
A second worked example, this time on a comparison page
From our work
The alternatives page that ranked and the one that got cited
- Context
- Two competing vendors in the same category each published a page comparing themselves against three alternatives. Both pages ranked between position three and six for their target term. Both were technically clean: fast, well linked, sensible headings.
- What we did
- One page described the differences in adjectives, calling itself 'more flexible' and 'easier to use.' The other stated three specific, checkable differences: a named integration the competitor lacked, a support response time with a number attached, and a pricing structure described in dollars rather than tiers.
- Outcome
- Across 40 prompt runs asking an assistant to compare the category, the adjective led page was cited twice. The page with three checkable claims was cited 17 times, and in nine of those the model repeated the exact support response time as a reason to prefer that vendor. The ranking positions of both pages did not move during the test window.
Why volume of content stopped being the lever
Ten years of SEO advice trained teams to treat publishing cadence as a proxy for topical authority. Write enough pages about a subject and the domain accrues weight, so the thinking went, and eventually everything on it ranks better. That logic never fully held for search and it holds even less for citation, because a model is not counting how many pages you wrote about a topic. It is checking whether any single one of them says something specific enough to repeat.
A content team that ships four generic posts a week is not compounding an advantage. It is adding four more pages a model will skim, find indistinguishable from the last twelve it read on the same topic, and pass over in favour of whichever source made a claim first with a number attached. Cadence without specificity produces volume, not visibility.
| Content investment | Effect on ranking | Effect on citation rate |
|---|---|---|
| Publishing 4 generic posts a week | Mild, if internally linked well | Close to none, indistinguishable claims |
| Publishing 1 sourced, specific post a month | Neutral to mild | Measurable, each claim is a citation candidate |
| Correcting 3 external category descriptions | No direct effect | Often the largest single move available |
| Adding schema across the site | Small, helps parsing | Small, resolves ambiguity but adds no claim |
The objection that comes up in every planning meeting
Someone always asks whether any of this is measurable enough to defend in a budget conversation. Ranking position is a single number that has existed for two decades and everyone in the room already trusts it. Citation rate across a rotating prompt set sounds like something a consultant invented to justify a retainer.
The answer is to build the same discipline search had before rank trackers existed: a fixed, repeatable method, run on a schedule, logged the same way every time. Twenty prompts, three assistants, a spreadsheet with a date column. It will never be as tidy as a rank tracker dashboard, but it is auditable, it is yours, and after two or three quarters of consistent logging it correlates with pipeline in a way total sessions stopped doing years ago.
How to sequence the work over a quarter
- Weeks one and two: run the baseline prompt set, log every citation and every source the model leaned on for your category.
- Weeks three and four: rewrite the opening of your ten highest intent pages so each states a complete, sourced answer in the first two sentences.
- Weeks five and six: identify the four most quoted third party sources in your category and start the outreach to correct them.
- Weeks seven and eight: turn your internal benchmarks into dated, sourced sentences and publish the ones you can defend.
- Weeks nine through twelve: re-run the baseline prompt set, compare citation counts against week one, and redirect budget toward whichever lever moved the number.
None of this replaces the technical checklist. It sits on top of it. The checklist gets you crawled and parsed correctly. The sequence above is what decides whether any of that crawled content ever gets quoted back to a buyer who is deciding who to call.
What I would do Monday
- 1Pick your five most important claims and attach a named source with a date to each.
- 2Rewrite the opening of your three highest intent pages so the answer is complete in the first fifty words.
- 3Audit what third party sites say about you: review platforms, listicles, communities. Fix the wrong ones.
- 4Log which sources the assistants cite for your category, then go and appear in those sources.
Common questions
- Is AEO just SEO with a new name?
- No. The technical basics overlap, structured data, clean headings, fast pages, but the mechanism that decides whether a model names you is different from the one that decides whether Google ranks you. Ranking rewards relevance to a query. Citation rewards a verifiable, self contained claim backed by a source the model already trusts.
- Does schema markup help you get cited by AI search?
- It helps a parser resolve who you are and when a page was published, which removes ambiguity cheaply. It does not make an unsupported claim credible or fix a contradiction between your site and what review platforms or roundups say about you. Schema clarifies a sentence that already says something specific. It cannot invent the substance.
- What is the highest yield AEO best practice most teams skip?
- Correcting third party sources that describe your category, positioning or product incorrectly. Models weigh consensus across independent sites heavily, so a wrong description on a widely quoted review platform or roundup can outweigh anything accurate on your own site. Fixing four external pages often moves visibility faster than a quarter of on site content work.
- Why do most AEO guides just repeat old SEO advice?
- Because technical SEO tactics are easy to sell as a scoped deliverable and easy to verify as complete. Consensus building and sourcing claims require research, outreach to other websites, and time. Most published AEO content stops at the part that fits neatly into a checklist and skips the part that actually decides whether a model attributes you.
Who wrote this
Avishai Sam Bitton
Founder, DemandBox
Avishai runs demand generation programs for B2B SaaS companies across performance marketing, SEO, and answer engine optimization. He works directly with the teams he advises, with no account managers in between.
Connect on LinkedInThe long version
AEO vs SEO vs GEO: What Actually Changed
AEO, SEO, and GEO compared: which tactics genuinely differ, what the 2026 citation research shows, how to split budget at three team sizes, and who to hire.
Want this argument applied to your numbers?
No deck, no discovery sequence. Tell us what you are spending and where the pipeline stalls, and we will tell you what we would change first.
Talk to an Expert