Different User-Agents received different HTML

Name

Different User-Agents received different HTML ua-content-diverged

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.

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.

Copy or download

# ua-content-diverged — Different User-Agents received different HTML

- **Name:** Different User-Agents received different HTML

## Description

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.

## 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.

## Rule docs

https://ogkit.akr.moe/rules/ua-content-diverged

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 HTML
• ua content diverged
• cloaking social crawler
• HTML 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

1. Fetch the same URL with a browser UA and with Facebookbot / Twitterbot UAs.
2. Diff the HTML (or body hashes). Divergence triggers this rule.

Related rules

• og-url-relative — og:url is a relative path
• og-url-not-https — og:url is not HTTPS
• og-url-canonical-mismatch — og:url does not match canonical
• og-url-final-url-mismatch — og:url does not match final URL after redirects
• robots-blocks-social-crawlers — robots / X-Robots-Tag blocks social previews
• og-tags-require-javascript — OG tags appear to require client-side JavaScript