Enterprise format · Growth plan

JSON Feed

RSS, but JSON-native.

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

JSON Feed delivers the same subscribe-to-updates capability as RSS or Atom but in plain JSON, so any modern client, serverless function, or LLM ingestion pipeline can parse it without an XML library. That low parsing cost makes it especially attractive for AI and agent crawlers that want a clean, typed list of recent posts to summarize or cite.

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 outputfeed.json
{
  "version": "https://jsonfeed.org/version/2.0",
  "title": "Geordy AI Optimization Updates",
  "home_page_url": "https://geordy.ai",
  "items": [{
    "id": "https://geordy.ai/blog/enterprise-formats",
    "title": "New Enterprise Formats",
    "date_published": "2026-10-20T10:00:00Z"
  }]
}
Get it right

How to make this format work for AI.

DoBest practices
  • Always include the four required top-level fields - version (the URL `https://jsonfeed.org/version/1.1`), title, items, and (recommended) feed_url and home_page_url - so consumers can self-identify and re-fetch the feed.
  • Serve the feed as `Content-Type: application/feed+json` and link to it from your HTML with `<link rel="alternate" type="application/feed+json" href="...">` for autodiscovery.
  • Give every item a stable, globally unique `id` (a permalink URL is the conventional choice) so readers can de-duplicate across renames.
  • Prefer `content_html` for rich content and `content_text` for plain text; provide `date_published` in RFC 3339 format and a `url` that points to the canonical post.
AvoidCommon pitfalls
  • Using a non-stable `id` (e.g. a counter that resets when the site is rebuilt), which makes every post look new to subscribers.
  • Setting `version` to a bare string like `"1.1"` instead of the required URL, which breaks strict parsers.
  • Serving the feed as `application/json` only and forgetting `<link rel="alternate">` autodiscovery, so feed readers never find it.
Where it shines

Use cases, scored for AI visibility.

Blog and news updatesGEO 5/5
API-driven contentGEO 4/5
Real-time notificationsGEO 3/5
Used in production by

Real sites already shipping JSON Feed.

Working with it

Tools & resources for JSON Feed.

The trade-offs
Strengths
  • JSON-native - no XML parser needed
  • Developer-friendly API integration
  • Cleaner for modern web apps
Spec sheet
Filename
feed.json
Refresh cadence
weekly
Released
2019 · Brent Ashley, Ben Schwarz, Manton Reece
Written forModern AI agentsDeveloper-built RAG pipelinesJSON-first crawlers

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

Documented support
  • JSON Feed version 1.1A pragmatic syndication format that works like RSS and Atom but uses JSON instead of XML.
Observed requests

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

Other enterprise 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.

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