OGKit

Rules / og-tags-require-javascript · ruleset 2026-07

OG tags appear to require client-side JavaScript

warningog-tags-require-javascript
Rule idog-tags-require-javascript
Severitywarning
CategoryPlatform and crawl
Platformsall platforms
Needs humanyes — structural fix

What this is

OG tags appear to require client-side JavaScript. OGKit rule og-tags-require-javascript (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:

  • OG tags appear to require client-side JavaScript
  • No Open Graph / Twitter card tags in static HTML
  • SPA no SSR og tags
  • client-side only meta tags

Why it matters

Almost no major social crawler executes JavaScript. Meta tags injected only after hydration are invisible — cards fall back to bare URL.

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. curl -sL the page (no JS). Confirm zero og:* / twitter:* tags in the static HTML.
  2. Open DevTools after hydration — tags may appear only then (invisible to crawlers).

How to fix

Render og:* / twitter:* tags in the initial HTML (SSR, prerender, or static). Verify with curl / view-source, not DevTools after load.

No single template snippet applies; use the measured and expected values in an OGKit finding.