---
title: "OG.json (og.json)"
description: "Open Graph metadata, centralized."
canonical: "https://geordy.ai/formats/og-json"
---
# OG.json

**Open Graph metadata, centralized.**

All social and AI preview metadata in one place - title, description, image, type. Powers chat surfaces, social embeds, and assistant cards from a single source.

OG.json is a JSON-encoded version of Open Graph metadata, providing a centralized, machine-readable format for social preview data that AI systems can parse more easily than dispersed HTML meta tags. Community-driven based on Facebook's Open Graph Protocol and formalized as a JSON standard in 2023.

## At a glance

- File: `og.json`
- First released: 2023
- Specification: https://ogp.me/
- Read by: AI chat surfaces, Social platforms, Preview generators

## Why it matters for AI

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.

## Example

```
{
  "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"
}
```

## Benefits

- 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

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

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

## Use cases

- **Sites with many pages**
- **Dynamic content management**
- **Landing pages**

## Adopters

- IMDb (https://www.imdb.com/title/tt0117500/)
- The New York Times (https://www.nytimes.com/)
- GitHub (https://github.com/facebook/react)
- Wikipedia (https://en.wikipedia.org/wiki/Open_Graph_protocol)
- YouTube (https://www.youtube.com/)
---

Source: https://geordy.ai/formats/og-json
This is a machine-readable markdown version of that page, generated by Geordy.