Rules / ua-content-diverged · ruleset 2026-07
Different User-Agents received different HTML
| Rule id | ua-content-diverged |
|---|---|
| Severity | warning |
| Category | Platform and crawl |
| Platforms | all platforms |
| Needs human | yes — structural fix |
What this is
Different User-Agents received different HTML. OGKit rule ua-content-diverged (warning, needs human). The id is a public API for the docs URL and CI --disable key; do not rename it.
Search phrases that should land on this page:
Different User-Agents received different HTMLua content divergedcloaking social crawlerHTML body hashes differ across User-Agents
Why it matters
When Facebookbot / Twitterbot / browser HTML diverge, you may be cloaking accidentally (A/B, bot challenges, SSR gaps). Cards then show content users never see — or vice versa.
Which platforms are affected
All OGKit platform profiles, including major social, chat, and search crawlers that consume these tags.
Platform-specific crawler budgets and field priority live in the platform behaviour reference.
How to reproduce
- Fetch the same URL with a browser UA and with Facebookbot / Twitterbot UAs.
- Diff the HTML (or body hashes). Divergence triggers this rule.
How to fix
Serve the same OG tags to all crawler UAs. Exempt social bots from heavy bot-fight challenges on public pages. Prefer SSR for share meta.
No single template snippet applies; use the measured and expected values in an OGKit finding.