Migration Guide
Migrating from internal aigeo-page-card-v1 to public AI Page Manifest (AIPM) v1.1.1.
What changed
| v1.1.0 (legacy) | v1.1.1 (AIPM) |
|---|---|
"spec": "aigeo-page-card-v1" | "specification": { "shortName": "AIPM", ... } |
$schema`: .../aigeo-page-card-v1.json | $schema`: .../aipm/1.1/page-manifest.schema.json |
"version": "1.1.0" | "version": "1.1.1" |
Auto-extracted keyFacts | Editorial keyFacts only |
claims without type | claims[].type: internal | external |
| — | manifestType, maintainer, purpose |
Backward compatibility
- Sidecar URLs unchanged:
{path}.ai.json - Legacy schema at
/schemas/aigeo-page-card-v1.jsonremains available (deprecated) - All v1.1.0 fields retained; v1.1.1 is additive
Implementation checklist
- Update
$schemaURL to AIPM schema - Replace
specwithspecificationblock - Add
manifestType: "page" - Add
maintainerblock - Write editorial
purposefor each page - Author 3–7 editorial
keyFactsper page - Classify
claimsasinternalorexternal - Update
<link rel="alternate">title to "AI Page Manifest (AIPM)"
AigeoRadar WordPress Connector
Customer deploy support for AIPM is planned. Currently AIPM is published on aigeoradar.com marketing pages only.