Best Practices

Guidelines for authoring high-quality AI Page Manifests.

0. Unique semantic role contract

Each orientation field has one job. Do not clone the same sentence across them:

• purpose — why the page exists (reader outcome)
• abstract — what the page teaches (workflow / summary)
• speakable.summary — voice one-liner (may paraphrase, must not be a byte-clone of abstract)
• summary50 / 150 / 500 — retrieval hooks at different depths

1. Write a clear purpose

purpose answers "why does this page exist?" in one sentence. It should describe the reader outcome, not repeat the title or abstract.

// Good
"purpose": "Help WordPress owners publish GEO discovery files for AI assistant visibility."

// Avoid
"purpose": "Blog post about WordPress."

2. Use abstract as the teach summary

abstract explains what the page covers (assets, deploy path, scope). It may align with a strong meta description but must stay distinct from purpose.

3. Author editorial keyFacts

Write 3–7 atomic, generalizable facts. Each should stand alone as a citable statement.

// Good
"GEO optimizes content for AI citation, not just traditional search rankings."

// Avoid (raw H2 text)
"When users ask: What is the best AI visibility platform?"

4. Classify claims by evidence type

• internal — evidence on your own site (features page, docs, this article)
• external — third-party sources (Schema.org, llmstxt.org, research papers)

5. Keep contentFreshness accurate

Update dateModified when facts change. Stale manifests reduce AI citation confidence.

6. Link related pages

Use relatedPages to build a topic graph. Prefer extends and tutorial relationships over generic links.

7. Declare discovery assets

Point to site-level files (entity.json, llms.txt) in the assets block so AI systems can traverse your discovery layer.

8. Set citation policy

Use citationPolicy to tell AI systems how to handle conflicts — e.g. prefer entity.json over marketing copy.