Request for Comments
RFC AIPM-001: AI Page Manifest Core Specification
Status: Stable
Version: 1.2.0
Author: AigeoRadar
Framework: AI Discovery Framework (ADF)
1. Problem
AI assistants and crawlers must parse HTML to understand web pages. HTML mixes content with navigation, ads, scripts, and layout. This creates ambiguity: AI systems guess page intent, topic, entities, and freshness instead of reading structured facts.
2. Solution
Publish a sidecar JSON manifest at {page-path}.ai.json for each HTML page. The manifest reduces
ambiguity by providing pre-structured metadata optimized for machine consumption.
3. Specification
3.1 File location
Path-adjacent to the HTML page: /blog/my-post → /blog/my-post.ai.json
3.2 Discovery
HTML <head> MUST include:
<link rel="alternate" type="application/json" href="{sidecar-url}" title="AI Page Manifest (AIPM)">3.3 Identity
Every manifest MUST include:
"specification": {
"name": "AI Page Manifest",
"shortName": "AIPM",
"version": "1.1.1",
"rfc": "AIPM-001"
},
"manifestType": "page",
"maintainer": { "name": "...", "url": "...", "specification": "..." }3.4 Purpose
purpose (string, required) — one sentence explaining why the page exists.
3.5 Summaries
Hierarchy: abstract (meta description) → summary50 → summary150 → summary500.
3.6 Claims
Each claim MUST include text, type (internal|external), evidence (URI), and confidence.
3.7 Key facts
keyFacts MUST be editorially authored. Automatic extraction is not permitted in v1.1.1.
4. JSON Schema
https://aigeoradar.com/schemas/aipm/1.2/page-manifest.schema.json
5. Security considerations
Manifests are public. Do not include secrets, PII, or unreleased pricing in keyFacts or claims.
6. Changelog
See version history.