You've probably sat through some version of this standup already. The team spent two quarters reshaping content for AI answers, the citation tracker has finally turned green, and the traffic chart next to it is red. Someone asks the question in this post's title, and the room splits into two stories: you're winning the new game, or you broke the old one to play it.
Both stories are true some of the time, so I'd rather run a diagnosis than referee the argument. It starts with telling ambient decline apart from damage you did yourself, then gets to where AEO really does cost traffic, why the AEO-versus-SEO split is mostly false anyway, and how to rebalance so you stop reading one scoreboard with two games on it.
First, separate the two losses
The first loss is ambient, and it isn't yours. About two-thirds of Google searches now end without a click to any website. AI answers stack on top of that: AI Overviews trigger on nearly half of queries, and where an AI answer sits above the results, measured click-through falls somewhere between 58 and 79 percent, depending on the study.
AI Mode is harsher still, with one analysis finding clicks to sites down about 93 percent against a classic results page. You didn't cause any of that by restructuring your FAQ page. It hit everyone at the same moment, including sites that have never heard the word AEO.
Every industry benchmark shows this pattern at once, and the calmest companies are the ones that wrote down a baseline before touching anything. If you haven't, do it today. Each diagnosis below gets easier with a dated starting point, and arguments about causes get a lot shorter.
What you want to know is how much of your drop is that ambient weather and how much you did yourself. Two checks settle it for most sites.
The first is a cohort comparison. Put the pages you rewrote for AI answers in one group and comparable pages you never touched in another, then compare their traffic curves over the same window. If both fell together, it's weather. If the rewritten group fell harder, pull its rankings before you conclude anything, since that's where the most common self-inflicted wound shows up first.
The second check happens in Search Console, where answer absorption leaves a signature. Impressions hold flat or climb while clicks sink, and the new AI performance report goes up while sessions don't. Your pages are still being seen, just inside surfaces that no longer hand out visits. On pages whose rankings held, that pattern is the era itself, and no rollback of your AEO work will reverse it.
It's a different story if rankings dropped on the pages you touched. That loss is fixable, and you probably caused it.
The four real ways AEO costs traffic
The split between the two is mostly false, though not entirely, and knowing where it breaks is what lets you rebalance instead of rolling back. Four failure modes do the damage.
The most common is what I call answer-stub gutting. Someone hears that machines like concise pages, and a 2,000-word page that ranked gets rewritten into a terse Q&A skeleton. Answer-first was meant to move the conclusion to the top, and this rewrite strips out the evidence too. The page loses the depth signals that ranked it, the rankings go and retrieval goes with them, and the citations leave last, because engines cite from what they retrieve.
Prompt-string sprawl starts with a team mining its logs for AI-flavored queries and spinning up a thin page for every phrasing, until forty stubs orbit one intent. They cannibalize each other, none of them builds authority, and the cluster does worse than the single deep page it replaced. It's the overfitting failure in its purest form.
Rank abdication begins with a strategy memo that assumes you can AEO your way around not ranking. It declares rankings a legacy metric, so the link work stops and technical debt piles up. Six months later the citations sag too, which looks mysterious until you remember that retrieval is rank-gated everywhere and the "legacy metric" was carrying the new one all along.
The encyclopedia trap is the subtle one, and a widely shared practitioner post put numbers on it. That team celebrated months of rising citation counts, then pulled their referral data and found 73 percent of their cited pages had driven literally zero traffic in 90 days. Your percentage won't match theirs exactly, but I think their diagnosis holds up: many citations are factual support, the engine borrowing a stat or a definition to build its answer, and the reader's need ends inside that answer.
Position made it worse. Their pages cited first or second in a response drew an order of magnitude more clicks than ones buried third or later. And informational queries have a ceiling that no optimization lifts, since a reader whose curiosity is satisfied has no reason to click.
73% of our AI citations drove zero traffic in 90 days — we were optimizing the wrong thing
Here's something I don't see talked about enough: getting cited by AI and actually getting traffic from those citations are two completely different games. We spent the first 4 months of our GEO work chasing citation counts. Every week we'd...
Line the four up and each one is a trade, where a team gave up an asset that fed both games. None of them comes from optimizing for answers as such, and that shared asset base is how the two acronyms really relate.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
A worked diagnosis
The cohort test is easier to trust once you've watched it run, so here it is on an illustrative 200-page B2B site. I invented the numbers for the walkthrough, and the shapes come from real ones.
Say the team rewrote 60 pages for AI answers in Q2. Organic sessions are down 24 percent year over year, and the AEO project is getting the blame. Pulling the cohorts takes an afternoon. The 60 rewritten pages are down 26 percent and the 140 untouched ones are down 22 percent, so the gap is four points and most of the decline is shared. At that stage the verdict is overwhelmingly weather.
The rankings check on the rewritten group is where the useful finding turns up. Of those 60 pages, 49 held or improved their positions, and 11 fell off page one entirely. All 11 turn out to be the long guides that got compressed hardest in the rewrite, which is answer-stub gutting in miniature, and between them they account for nearly the whole four-point gap.
Two more numbers finish the picture. Impressions on the pages that held are up 18 percent while their clicks fall, the absorbed-by-answers signature from the first section. And the citation tracker now shows 14 of the rewritten pages appearing in ChatGPT or AI Overview answers for money queries, something no page on the site managed a year ago.
The story the afternoon produces fits in four sentences, and none of them asks anyone to abandon an acronym. The era took its cut everywhere. Eleven specific guides were over-compressed and need their depth restored. The project also bought real presence that the traffic chart alone would have called a failure.
The dichotomy is mostly a budget fight
Take away the vendor decks and AEO versus SEO is barely a technical disagreement. The evidence keeps showing the same assets winning both: pages that rank are the ones that get retrieved, and the structure that wins a featured snippet wins citations too.
Concrete stats and quotable claims lift a page on both surfaces, and entity trust feeds Google's systems and the answer engines' source selection alike. Research on generative engines found citation-style content improvements lifting visibility by double digits, and none of those improvements would hurt a page's rankings. Most would help.
Where they actually differ is where the payoff lands, and that's a question of query intent more than tactics. Run every page through one question: what does winning look like for the query it answers?
You get paid in both currencies on commercial queries, the comparisons, alternatives, pricing and "best X for Y" searches. Buyers still click through from these answers, because the answer is a shortlist and the click is their diligence, so a citation here is a traffic event and a pipeline event at once. For this slice of your content, the classic SEO playbook and the answer playbook are the same document.
Informational queries pay in presence instead. On a "what is X" or "how does Y work" search, the zero-click ceiling from the 73-percent post is permanent. A citation there puts your name inside the market's understanding of the category, which is worth something real but isn't worth sessions, so I'd file those pages as brand infrastructure. The resentment in the "are we just unpaid content writers for Google's AI" threads comes from funding them on a traffic budget and getting paid in a currency nobody agreed to.
Are we optimizing for traffic anymore or are we just becoming unpaid content writers for Google's AI Overviews?
I have been analizing my clients GSC data recently and I noticed a weird thing which is impressions and entity base questions are way up but sit here is down by almost 25% on information keywords even though we are sighted directly in Ai su...
That resentment deserves a straight answer, and it's yes: informational content increasingly feeds machines that keep the reader. Publish it anyway if, and only if, presence in your market's answers is worth the production cost. For most B2B categories it is, because shortlists form inside those answers. Make it a conscious purchase, never an accidental one, and if you can't afford it, shrink that portfolio without shame and move the budget to commercial intent.
The rebalance, concretely
Citations up and sessions down rarely calls for a rollback. Reassigning pages to the right jobs usually fixes it, and one working session gets you there.
Start by writing down a job for every meaningful page. Traffic pages serve commercial intent and are expected to rank and turn their clicks into conversions. Presence pages serve informational intent and exist to be cited and to seed the brand into answers, while the dual pages, a rare few deep assets, manage both. Put each job on the content inventory, since every failure mode above is a page being graded on the wrong job.
With jobs assigned, fix the self-inflicted wounds in order. Gutted pages come first, with the depth back in and the answer-first opening kept. Then merge stub sprawl into one deep page per intent with redirects, and restart the rank work the memo paused. These fixes recover both currencies together, so they're the highest-yield hours you have.
The sharpest finding in the 73-percent post was the click gap between first-slot and buried citations, and your commercial rewrites should be built around it. First-slot sources usually open with lines that answer the question outright with a fact worth quoting. On those pages, getting cited is the low bar, and being the source the answer leads with is the target, because that slot is where the remaining clicks live.
Your CFO needs a dashboard with a separate scorecard for each class. Traffic pages report rankings and clicks alongside conversions. Presence pages report citation presence and position per engine, weekly, plus the slower signals of branded search drift and direct traffic, and the one I like best is a prospect saying "the AI mentioned you."
Across the portfolio, one number matters most: of the queries that precede your deals, how many show your brand anywhere in the answer? It can rise while sessions fall, and when it does, you're winning the transition rather than losing the old game.
Here's the metric-per-class cheat sheet for whoever builds that dashboard:
| Page class | Primary metrics | Ignore |
|---|---|---|
| Traffic (commercial) | Rankings, clicks, conversions, citation position | Citation count alone |
| Presence (informational) | Citation presence and position per engine, branded-search drift | Sessions |
| Dual (deep flagship) | Both columns, reviewed quarterly | Neither |
If your team wants it sequenced, the rebalance fits in 90 days. Month one is diagnosis and triage: pull the cohorts and check the rankings, write the jobs onto the inventory, and restore depth to the worst-gutted pages.
In month two you consolidate. Stub sprawl gets merged into deep pages with redirects, the paused rank work restarts, and weekly per-engine tracking goes live on the queries that precede deals.
The third month is offense. Do first-slot rewrites on the commercial pages that already get cited, just late in the answer, and ship one genuinely deep presence asset on purpose. Then present the new two-schedule dashboard against month one's baseline, with nothing rolled back.
How often does ChatGPT mention your brand?
Most founders have no idea. The answer might surprise you.
The answer to the title
So, are you optimizing for AI answers while losing website traffic? Probably yes, but mostly the two aren't causing each other. The traffic loss belongs to the era: answers absorb clicks, and they would have absorbed yours whether or not you ever restructured a page. Your optimization is the response to that era, and done right it doesn't speed the loss up. It converts some of it into presence inside the answers your buyers actually read, which I'd argue is the only visibility that still compounds.
The teams handling this well have stopped choosing between acronyms. They run one portfolio with two payout schedules and read each page against the schedule it was built for.
You can recognize the version of AEO that does cost traffic on sight: stubs where the depth used to be and sprawl where the focus used to be, often with the rank work shelved as legacy. If that's what happened to you, roll back those specific choices and keep the answer-first structure. Both games share one asset base, and those choices are what burned it. Then split the scoreboard and fund presence on purpose, and stop asking informational pages for sessions they were never going to collect.
15 hours a week manually. Or 15 minutes with RankControl.
Track citations, monitor competitors, and fix content gaps across every AI search engine. Automatically.
