Justin Bartak · AI Org · · 6 min read
Prose Is Paint. Data Is Load-Bearing.
Originally published on Orbyt Labs
TL;DR
Answer engines lift passages, but what they trust is the data underneath them. Prose without a data layer contradicts itself within days: my own queue had 42 stale figures three days after writing. AEO is a data discipline. One tested source of truth, enforced parity across every surface, resolvable identity, and posts that heal themselves.
Everyone optimizing for answer engines is polishing sentences. The sentences are the paint. What holds the weight is the data layer underneath: the tested, single-sourced, machine-checkable figures and identity that make a passage safe to quote. Most sites have none, which is why their beautiful prose contradicts itself within days.
I know exactly how fast, because I measured it on my own site.
Why does prose alone fail?
Because prose is a snapshot and the world it describes is a stream.
I write about a running system. Orbyt gains code, tests, incidents, and agent runs every week. A blog post about it is written on one day and publishes up to five months later, and every figure in it is a present-tense claim aging toward wrong.
Three days after one batch of posts was written, 42 phrases across 9 queued posts were already stale. The failure corpus they cited had grown from 49 recorded incidents to 51. The portfolio had grown from 531,000 lines to 532,000. Three days.
No editor catches that. No style guide catches that. A reader might, once it is too late and the contradiction is public.
A figure nobody tests is a rumor with typography.
What does an answer engine actually evaluate?
Not your paragraph. The claim inside it, and the entity behind it.
An engine deciding whether to lift your sentence is deciding whether to attach its own credibility to your number. If your homepage says one thing and your blog says another, the machine does not average them. It trusts neither. Self-consistency is the cheapest trust signal there is, and almost nobody engineers it.
That reframes the job. Writing decides whether a passage is quotable. The data layer decides whether it is still true at read time. Both matter, and only one of them is a craft problem.
What does a content data layer look like?
Mine has four parts, all boring, all load-bearing.
One source of truth. Every citable figure on this site lives once, in a single facts module: launch numbers, current numbers, career figures, and the canonical sentences that carry them. Pages reference it. Nothing restates a number by hand.
Tests that fail on drift. Unit tests compare that module against every surface repeating its figures, the metrics, the GEO index, the stats page, and the build fails on disagreement. Consistency is not a policy here. It is a compile error.
A registry of phrasings. Every live figure in a queued post is registered with the exact phrases that carry it. A checker compiles those phrasings, compares prose against the source, and rewrites the number in place when the change is mechanical. A pattern that matches nothing fails the test too, because dead coverage reads as coverage.
A weekly heartbeat. A scheduled job pulls the live numbers from Orbyt's own generated stats payload, the same artifact its public build log renders, then heals the queue and commits through the full test gauntlet. Figures that change what a sentence means are flagged for a human, never auto-edited. Published posts are never touched, because a live post's numbers are a dated claim, and rewriting them silently is rewriting history.
The result: a post written in August and publishing in December states December's numbers, or it does not ship.
How does identity fit underneath the prose?
The same way the figures do. Declared once, referenced everywhere, anchored outside my control.
This site asserts exactly one Person node, and every page references it by a stable identifier. It points outward to Wikidata and ORCID, registries I do not own. And the compensation dataset behind my salary figures is deposited on Zenodo under DOI 10.5281/zenodo.19653006, which makes me the origin of those numbers rather than one more page repeating them.
A quote needs a who. Seven of my pages once redeclared the author inline with no identifier, which reads to a parser as seven strangers sharing a name. That is a data bug, not a writing bug, and no amount of voice fixes it.
What is the honest caveat?
The data layer has not earned me a citation yet, and I publish that. My citation probe reads zero, every run.
The strongest external evidence says the biggest lever is off-site: brand mentions correlate with AI visibility far more strongly than backlinks. A site can be perfectly consistent and still lose to being unmentioned.
So what does the layer actually buy? It keeps me from disqualifying myself. Self-contradiction, orphaned identity, and stale claims are the errors that remove a site from consideration before the contest starts. Structure is the qualifying lap, not the trophy. I built the full argument for the passage side in Built to Be Quoted, and the skeptical read of the whole evidence base is its own post.
You cannot write your way out of a data problem.
What to do Next
Count your load-bearing figures. Most companies state fewer than 30 numbers they would want quoted: pricing, scale, outcomes, benchmarks. Small enough to engineer.
Put them in one place. A facts file, a table, anywhere singular. Make every page, deck, and doc reference it instead of restating it.
Add the tripwire. A test, a script, a weekly diff against the system of record. The mechanism matters less than the property: a figure cannot change in one place and survive in another.
Then check the figure most likely to be quoted about you today, everywhere it appears. If two surfaces disagree, you have found the real AEO work, and it was never the prose.
Paint is what people see. Beams are why the house stands. Write beautifully, and build the layer that keeps it true.
Related reading:
-
Built to Be Quoted. the passage-level implementation this layer sits under
-
AEO, GEO, and llms.txt: The New SEO the definitional playbook
-
I Built the Scoreboard. It Says Zero. the instrument keeping this post honest
-
Every Fable Has a Moral. Mine Has Data. why first-party data is the only durable content moat
-
Your Next Customer Is an Agent. what happens when the customer stops being human
Originally published on orbytlabs.ai on Oct 18, 2026.
Frequently asked questions
Why is AEO a data discipline rather than a writing discipline?
Because answer engines lift claims, and a claim is only as trustworthy as the figure inside it. Writing decides whether a passage is quotable. Data infrastructure decides whether it is still true when the engine reads it. A site whose numbers disagree with themselves loses the trust no headline can buy back, so the work that matters is parity, not prose.
What is a content data layer?
A single tested source of truth for every figure a site states. Mine is one facts module: every citable number lives there once, every page references it, and unit tests fail the build when any surface drifts. A second registry tracks the phrasings that carry live figures in queued posts, so a weekly job can rewrite the numbers before they publish wrong.
How fast do figures in written content actually go stale?
Faster than any editorial calendar. Three days after one batch of posts was written, 42 phrases across 9 queued posts were already stale, because the system they described had moved: the failure corpus had grown from 49 incidents to 51 and the portfolio from 531,000 lines to 532,000. Nothing catches that except infrastructure.
Does structured data alone earn AI citations?
No, and I publish the evidence against my own build: my citation probe still reads zero. Structure is the qualifying lap, not the win. What the data layer buys is never disqualifying yourself: no self-contradiction, no orphaned identity, no stale claim served to the one crawler that mattered. The biggest lever, brand mentions, sits off-site.
