Core format · included on every plan

OG.json

Open Graph metadata, centralized.

4 / 5GEO score
JSON · Geordyog.json
Why it matters

Open Graph turns any web page into a structured object that social platforms, messengers, search previews and AI summarisers consume to render rich link cards - title, type, canonical URL, image, description and site name - without parsing the page's full HTML.

Geordy generates this format for every page on your site that warrants it - auto-detected by page type, served from your subdomain, and refreshed on the cadence below.

Sample outputog.json
{
  "title": "Geordy - AI visibility starts here",
  "description": "AI-readable versions of every page, generated automatically",
  "image": "https://geordy.ai/og.png",
  "url": "https://geordy.ai",
  "type": "website",
  "site_name": "Geordy"
}
Get it right

How to make this format work for AI.

DoBest practices
  • Always include the four required properties on every public page: og:title, og:type, og:image and og:url (canonical, absolute URL).
  • Add og:description, og:site_name, og:locale and an og:image:width / og:image:height (recommend 1200x630 PNG/JPG under 5 MB) for reliable rendering across crawlers.
  • Use the correct og:type per page (website, article, video.movie, profile, etc.) and add the type-specific properties (article:published_time, article:author).
  • Declare the namespace once on `<html prefix="og: https://ogp.me/ns#">` and keep og:url identical to the page's <link rel="canonical">.
AvoidCommon pitfalls
  • Using a relative or non-canonical og:url, which causes share counts and previews to fragment across URL variants.
  • Pointing og:image at an HTTPS-blocked, hot-linked or oversized asset, so platforms fall back to no preview.
  • Setting og:title or og:description that disagree with the visible page or with <title> / meta description, which AI summarisers may flag as misleading.
Where it shines

Use cases, scored for AI visibility.

Sites with many pagesGEO 5/5
Dynamic content managementGEO 4/5
Landing pagesGEO 4/5
Used in production by

Real sites already shipping OG.json.

Working with it

Tools & resources for OG.json.

The trade-offs
Strengths
  • Centralizes social metadata in one parseable file
  • Easier for AI systems to extract than HTML meta tags
  • Provides ready-to-use summaries for AI-generated previews
Limitations
  • Relatively new with limited adoption
  • May require maintaining HTML meta tags for compatibility
  • Not universally recognized by all platforms
Spec sheet
Filename
og.json
Refresh cadence
weekly
Released
2023
Written forAI chat surfacesSocial platformsPreview generators

Written for these readers. Which of them actually request it is measured, not assumed: see how we measure.

Documented support
Observed requests

Not measured yet. Geordy will publish which crawlers request this file once enough independent sites are covered. See how we measure.

Other core formats

Generate every format at once.

Geordy emits 8 formats on every plan and 16 on Growth, auto-selected per page type and live on Geordy the moment they are written.

OG.json (.json) format - spec, examples and AI readers | Geordy