---
title: "How to write GEO fact pages"
lang: "en"
canonical: "https://winin.ai/en/answers/how-to-write-geo-fact-pages/"
alternate: "https://winin.ai/zh/answers/how-to-write-geo-fact-pages/"
datePublished: "2026-09-12"
dateModified: "2026-09-12"
section: "answers"
---

# 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](/en/guides/fact-pages/); product semantics live on [Homer](/en/facts/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
| Question | Page |
|----------|------|
| What is fact governance? | [Fact governance for AI answers](/en/answers/fact-governance-ai-answers/) |
| Fact governance + GEO together? | [Fact governance + GEO](/en/answers/fact-governance-plus-geo/) |
| Longer how-to | [Guide: fact pages](/en/guides/fact-pages/) |
| **How do we write them?** | **This page (method)** |

### 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](/en/facts/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](/en/facts/winin-what-is/) and [contact](/en/facts/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](/en/answers/same-conditions-retest-method/) and [retest guide](/en/guides/same-conditions-retest/).

### Fact pages vs marketing pages
| Belongs on fact pages | Stays on marketing / campaign pages |
|-----------------------|-------------------------------------|
| Verifiable definitions, specs, policy, contact, capability bounds | Story, tone, campaign copy, creative headlines |
| Source, version, validity, public permission | Unapproved slogan-style capability claims |
| What is / What is not | Promo rhetoric and unverified comparison flourishes |

**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](/en/facts/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](/en/facts/loop-find-govern-close-retest-operate/). Fact pages are the outward carrier of Govern; expired versions must not feed Friday execution.

## Related facts

- [Homer](/en/facts/homer/)
- [Friday](/en/facts/friday/)
- [What Winin is](/en/facts/winin-what-is/)
- [Case metrics disclaimer](/en/facts/case-metrics-disclaimer/)
- [Contact](/en/facts/contact/)

## Related answers & guides

- [Fact governance for AI answers](/en/answers/fact-governance-ai-answers/)
- [Fact governance + GEO](/en/answers/fact-governance-plus-geo/)
- [Same-conditions retest method](/en/answers/same-conditions-retest-method/)
- [GEO loop five steps](/en/answers/geo-loop-five-steps/)
- [Approve-then-execute GEO workflow](/en/answers/approve-then-execute-geo-workflow/)
- [Guide: how to write GEO fact pages](/en/guides/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](/en/facts/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