We have all watched this happen before. A feature sits behind a paywall for two years, then one morning it is free for everyone. That was never generosity; the early adopters paid a research tax to beta-test something until it was cheap enough to give away. The same machine is now pointed at your website.
For twenty years the deal with search was legible. Make good content, rank, get clicks. Google sold ads against the demand your content created and sent traffic back in return. Lopsided, but a real exchange.
AI Overviews and answer engines have quietly cancelled the return leg. The engine reads your work, composes the answer on its own platform, and keeps the reader there. The demand your content created still gets monetised. The click that used to come back to you does not. Reports of traffic falling sharply in answer-heavy categories are no longer outliers, and the reflex across the industry is still the same three words: how do we optimise?
That is the move that keeps you in the flock. You optimise harder for the machine that has stopped paying you back, feeding it cleaner, more structured, more extractable content so it can answer around you more efficiently. You are paying the research tax on your own replacement.
Here is the part the legacy playbook structurally cannot see, because it is built on Google Analytics, and Analytics only fires when a human browser loads a page. The most valuable thing leaving your server right now is not measured there at all. It is the ingestion: crawlers pulling your content to train and ground the models that will answer in your place. That traffic is invisible to Analytics and lives entirely in your server logs, the one file nobody in the SEO stack ever opens.
So you get a dashboard that says traffic is soft, and no dashboard at all for the underlying issue: your content is now the AI supply chain, and it is being drawn down with no meter on the pipe. You cannot negotiate an exchange you cannot measure. You cannot assert a right over data you cannot prove was taken. You cannot even tell whether the "Googlebot" in your logs is Google or a scraper wearing the same name, which is its own quietly expensive problem.
The shift is small and total. Stop asking "how do I rank inside the answer." Start asking "who is extracting my work, what are they doing with it, and what am I getting back?" That is an evidence question, not an optimisation one, and it is the one Unsourced is built to answer:
You do not get a vote on AI Overviews; that shift is above your pay grade and mine. But you have complete control over who extracts data from your servers, and whether you can prove it. The first step out of the flock is the one nobody takes: open the logs.
Because you are feeding cleaner, more extractable content to a machine that has stopped paying you back, so it can answer around you more efficiently. AI Overviews and answer engines read your work, compose the answer on their own platform, and keep the reader there. Optimising harder is paying the research tax on your own replacement.
Analytics only fires when a human browser loads a page. The most valuable thing leaving your server, crawlers pulling your content to train and ground models, is invisible to it and lives entirely in your server logs. So you get a dashboard that says traffic is soft, and no dashboard at all for the ingestion actually happening.
Stop asking "how do I rank inside the answer" and start asking "who is extracting my work, what are they doing with it, and what am I getting back?" That is an evidence question, not an optimisation one: where you stand in AI citations, who is really crawling you, and both sides of the ledger side by side.
Where you actually stand, per engine.
Read it →What ingestion really looks like: 9,543 verified crawls.
Read it →Check whether the "Googlebot" in your logs is Google.
Read it →Unsourced captures which AI assistants cite you, proves which crawlers really fetched your pages, and re-checks after you act — evidence, not a score.
© Unsourced — the evidence layer for AI search.