Content
03 / 04 · 7 ITEMSModels read your prose. They prefer plain claims, atomic facts, and consistent terminology. Marketing copy is the enemy of accuracy — adjectives confuse, hedge words signal weakness, and superlatives get ignored.
State pricing in plain text on a /pricing page
CRITICAL"Starting at $X" buried in marketing prose. "Contact sales for pricing." Both produce "no pricing information available" in model responses. Plain dollar amounts at the top of a /pricing route work.
priceValidUntil annually.
Use atomic, declarative facts in About
STANDARD"Founded in 2019" beats "established for over half a decade." Models extract facts, not vibes. Vague language gets paraphrased into hallucination.
Consistent terminology for your category
STANDARD"Platform" on the homepage, "tool" in the docs, "service" in the FAQ — models pick one and stick with it. The one they pick is rarely yours.
Name founders and key people
STANDARDBrand identity questions often include "who founded" or "who runs." If your About page hides leadership, the model invents an answer or refuses to engage.
Person JSON-LD with jobTitle for senior leaders.
Publish a clear /contact route
QUICK WINA working email or contact form, indexable. Hidden behind login? Models say "no contact information available." That answer travels.
/contact route, public, with at least one email address in plain text. Add ContactPoint JSON-LD on the Organization block.
Use H1 / H2 / H3 hierarchically
STANDARDModels lean on heading structure to segment context. Skipped levels (H1 → H4) and multiple H1s on one page reduce parsing accuracy.
Date-stamp time-sensitive content
STANDARDModels prefer recent sources. Undated pages lose to dated competitors on the same query. Even a "last updated" footer helps.
datePublished and dateModified to articles and product pages. Display "Last updated" in human-readable form.