| Field | Minimum | Description |
|---|---|---|
mapDirectory | required | Website directory for the map, for example /facts/ or /fakten/. |
mapIndexUrl | required | Absolute URL of the Grounding Map Index Page. |
groundingPageUrl | required | Stable Grounding Page URL for the entity or concept. |
entityName | required | Human-readable public entity or concept name. |
entityType | required | Person, Organization, Concept, Method, Product, Topic, Dataset or Standard. |
canonicalReference | required | Main canonical reference, usually the Grounding Page URL. |
editorialExplanationUrl | recommended | Main article, guide or blog post that explains the Grounding Page. |
evidenceUrls | required | Supporting URLs separated by a pipe in CSV. |
relatedGroundingPages | recommended | Related Grounding Page URLs or IDs, separated by a pipe in CSV. |
relationshipType | required | Controlled relationship role from the spec. |
machineReadableUrl | recommended | .md.txt, JSON, registry or resource URL. |
status | required | Lifecycle state: active, emerging, parked or deprecated. |
stability | required | Change model: stable, evolving, parked or replaced. |
lastReviewed | required | Date of the last editorial review. |
openGaps | recommended | Missing evidence, unclear boundary or maintenance gap. |
Grounding Map Template
Start with the website location: map directory, map index URL and the Grounding Pages that belong to it.
The template is designed for a /facts/ or /fakten/ architecture where stable pages
define entities and a central index page connects them.
Fields
Template structure
The minimum version records where the map lives, which Grounding Page defines the concept, which editorial explanation contextualizes it and which evidence or related pages support it.
Map one directory first
A useful first map can cover one directory and a small set of stable Grounding Pages. Each row should show where the page lives, which article explains it and which evidence or related pages support it.
- Start with the map index page before adding many entities.
- Prefer stable Grounding Pages over incidental article mentions.
- Mark missing evidence or unclear relationships as open gaps.
Governance-ready
Add JSON Schema validation, .md.txt text twins, llms.txt, registry exports,
review dates, owners and machine-readable relationship edges when the map becomes part of maintenance.
The template provides structure only: no score, certification mark, ranking promise or result claim.
Example rows
Reference implementation pattern
| mapDirectory | groundingPageUrl | entityName | editorialExplanationUrl | relationshipType | status | stability |
|---|---|---|---|---|---|---|
/fakten/ | https://marcdeboer.de/fakten/grounding-map/ | Grounding Map | https://marcdeboer.de/blog/grounding-map/ | structures | active | evolving |
/fakten/ | https://marcdeboer.de/fakten/seo-entropie/ | SEO-Entropie | https://marcdeboer.de/blog/seo-entropie/ | defines | active | stable |
/fakten/ | https://marcdeboer.de/fakten/search-reality/ | Search Reality | https://marcdeboer.de/blog/search-reality/ | explains | active | evolving |