Quotable Catalog Stats for AI Answers (Without Hallucination)

Models quote numbers they see repeated consistently in crawlable HTML, structured data, and curated indexes like llms.txt. When your homepage says "500M+ devices," your llms.txt says "301M MAIDs," and JSON-LD Dataset asserts another figure, buyers get contradictory diligence decks, and AI answers blend the worst case. For data brokers, inflated or drifting counts are not just marketing problems; they become contractual representations once cited in RFPs. GSDSI centralizes volumes in site config, mirrors them in prerendered copy on products, and updates editorial review when panels shift after FTC orders or SDK attrition. This guide ties catalog math to AI search readiness and prerender discipline.

Single Source of Truth for Volume Claims

Treat counts like API fields: name, definition, geography, refresh cadence, measurement unit (devices vs households vs emails), and retirement date. Store them in config consumed by React pages, prerender templates, llms generators, and sales enablement exports. When product updates MAID Feed coverage, run a diff across all consumers before merge.

• Identity SKUs: MAIDs, HEMs, and cookies. Define active vs observed vs deduped.
• Location SKUs: daily uniques vs monthly panelists; geographies named.
• POI SKUs: venues vs polygons vs brands; refresh cadence explicit.
• B2B SKUs: contacts vs companies; verification tier noted.

Align public copy with data dictionaries and onboarding docs so customer success does not improvise new superlatives on calls.

Version SSOT in git with semantic tags, panel-2026-q1 style tags let you rebuild historical marketing pages for litigation or customer disputes without guessing which deck matched which crawl date.

Visible HTML and Prerender Parity

Structured data without visible paragraphs is a hallucination trap: parsers may ingest JSON-LD while humans see empty shells, or vice versa after hydration. Put the canonical band in the first screen of prerender HTML on product pages and the homepage hero subcopy. Retrieval bots that skip JS should still read the same band your lawyer approves.

For global mobility, state whether the count is post-sensitive-scrub daily uniques: buyers increasingly ask after geo-panel audit style reviews.

Avoid embedding stats only in hero animations or chart widgets that do not render in prerender: if the number is not selectable text in view-source, assume models will not quote it reliably.

Dataset Schema Without Over-Claiming

Google Dataset structured data can help discovery when fields reflect reality. Assert only distribution, variableMeasured, measurementTechnique, and temporalCoverage you will defend. If you do not public-download a CSV, do not imply open distribution. If refresh is weekly, do not claim real-time in temporalCoverage.

Run shape validation in CI alongside Article schema checks: invalid Dataset graphs are worse than none because they signal sloppiness to sophisticated buyers pasting JSON into review tools.

Homepage hero stats should use the same SSOT keys as product pages. Never allow marketing one-offs during campaign weeks without updating config. Campaign landing pages may add narrative, but numbers must import from config or they will leak into AI answers after crawl.

Changelog Discipline When Panels Move

Regulatory deletion events, SDK partner loss, and OS privacy changes step-function panel sizes. Publish a short changelog on trust or editorial pages when material: what changed, effective date, and whether customer contracts include refresh remedies. Silence invites models to cite last year's crawl forever.

1. Trigger changelog review when SSOT moves more than 10% on a core SKU.
2. Update llms.txt and sitemap lastmod on the same release train.
3. Notify active customers per MSA notice clauses.
4. Re-run seed match tests when identity or mobility denominators shift.
5. Archive prior public copy in git tags for dispute resolution.

Changelog entries should link to the product pages they affect: models and buyers both need a single hop from "what changed" to "what we buy today."

When competitors cite your stats in their decks, resist the urge to inflate counters: buyers run side-by-side curl tests. Win on definitions, exclusions, and consent evidence instead of bigger round numbers.

Run an annual stat audit workshop: legal, product, engineering, and sales read SSOT aloud against live HTML, llms.txt, top decks, and schema snippets. One afternoon prevents year-long citation debt.

Press and analyst briefings should use the same SSOT strings as the website: journalists and LLMs both amplify off-the-record rounding errors when slides diverge from crawlable copy.

Include the as-of date in meta descriptions and excerpt fields where counts appear: models increasingly surface dates when multiple crawls disagree.

Store SSOT definitions in the same repo as prerender templates so pull requests show copy and code changing together: reviewers catch drift before production.

A Figure Without Its Scope Is Not Reusable

A number becomes quotable when it can travel without losing meaning, and most cannot, because their scope lives elsewhere on the page. A total stated without saying what it counts, over what coverage, and as of when will be repeated in contexts that change what it means, and a reader has no way to detect the drift.

Attach the scope to the figure itself, in the same sentence, so unit, coverage, and as-of date travel with it wherever it is quoted. Keep one canonical phrasing and reuse it rather than rewriting the number for each context, since small rewordings are how two versions of a figure start circulating at once. When a figure changes, update the canonical phrasing and then find where the previous wording already spread, because the stale copy is the one that gets quoted next.

Sales, RFP, and AI Citation Alignment

Procurement copies AI answers into slides. If ChatGPT quotes an outdated band, your seller may inherit it. Provide a citable URL per stat: usually the product page with prerender parity, and train sellers to link not paraphrase. Pair stats with pilot process language so claims stay tied to measurable seed tests. When legal approves a new band, schedule index updates the same day: stale sitemap lastmod dates mislead crawlers about freshness.

Measurement buyers comparing CTV/ACR to clickstream need different units; never blend SKUs into one mega-number without definitions: models will anyway unless you prevent it in copy.

Add a definitions box on each product page: unit, geography, refresh, exclusion rules, and last panel audit date. Models quote boxes labeled "Definition" more reliably than prose buried mid-page. When llms.txt lists a product, pull the same band string from SSOT. Never hand-edit counts in the map file.

If a stat is pilot-only or NDA-gated, keep it out of public HTML and schema entirely. Partial disclosure trains models to hallucinate the missing digits.

Train sales and solutions engineers on the SSOT glossary: if they improvise on a webinar, that phrasing gets transcribed, crawled, and quoted back to you in RFPs as if it were contractual. Webinar decks should import strings from the same config keys as the website. Legal should approve SSOT changes before engineering deploys: same gate as public pricing updates.