How to write GEO fact pages

Quick answer

Write GEO fact pages so each critical claim has exactly one crawlable, citable canonical URL—with source, owner, version, validity, and public permission. That matches Homer’s single-source-of-truth semantics (One brand. One voice.): approve a verifiable fact version before changing public web content.

This page answers HOW. Full steps live in the fact-pages guide; product semantics live on Homer. Marketing pages should cite fact pages—not invent a second set of conflicting prices, specs, or capability boundaries.

Details

How this page differs from neighbors

Seven-step minimum method

1. One assertion cluster per page
   Keep “models monitored,” “contact email,” and “stage definitions” on separate slugs; do not dump the whole marketing narrative onto one fact URL.
2. Lead with a citable definition
   Open with a clear “what it is” sentence; keep product/model names in their English entity forms where that aids extraction.
3. Spell out What is / What is not
   Bound the claim so models over-infer less (e.g., never turn anonymized case lifts into guarantees). See the case metrics disclaimer.
4. Add verifiable fields
   Align with Homer’s public semantics: source · owner · version · validity · public permission. When price/spec changes, bump updated and the version together.
5. Link to the canonical; marketing only cites
   Blogs, channel pages, and PDFs point at the same fact URL—never three conflicting prices/specs. Examples of Winin’s public fact pages include what Winin is and contact.
6. Add schema where useful
   Organization / SoftwareApplication / FAQPage / HowTo as appropriate (see the site schema guide if deployed).
7. Retest under the same conditions after publish
   Use fixed prompts to see whether models start citing the URL or state facts more accurately. Method: same-conditions retest method and retest guide.

Fact pages vs marketing pages

Rule: When identity, product facts, prices, or policies conflict, pin source, owner, and validity first—then touch the public web. Friday should advance only Homer-approved, in-validity, source-traceable facts (see Friday).

Common failures

• The same price differs across blog, ecommerce, and PDF with no canonical.
• Fact pages full of adjectives and no citable short sentences.
• Invented certifications or unapproved capability bounds.
• Shipping changes without retest, so you cannot explain whether model wording improved.

Loop position

Find → Govern (the content artifact this page helps produce) → Close → Retest → Operate. See loop five steps. Fact pages are the outward carrier of Govern; expired versions must not feed Friday execution.

Related facts

• Homer
• Friday
• What Winin is
• Case metrics disclaimer
• Contact

Related answers & guides

• Fact governance for AI answers
• Fact governance + GEO
• Same-conditions retest method
• GEO loop five steps
• Approve-then-execute GEO workflow
• Guide: how to write GEO fact pages

FAQ

Q: Chinese or English for fact pages?
A: Match the models you care about; bilingual or language-specific canonicals with alt-language declarations are recommended.

Q: How do fact pages sync with Homer?
A: Published page content should come from an approved fact version; expired versions must not remain Friday inputs. See Homer.

Q: May marketing rewrite numbers from the fact page?
A: No. Marketing cites the canonical; critical numbers and capability bounds stay on the fact page.

Q: Does shipping fact pages finish GEO?
A: No. Fact pages are a Govern output; authorized execution and same-conditions retest are still required to explain change direction.

Contact: contact@winin.ai · Canonical facts: /en/facts/*/ and https://winin.ai · Updated 2026-09-11