Entity Map
Publish a structured Entity Map (/entitymap.json and /entitymap.html) so AI systems understand your organization, key content, and relationships: Pro Tools.
Tools overview · llms.txt · Pro Tools
Admin path: SEO Booster → Tools → Entity Map (Pro)
llms.txt tells AI where to start. Entity Map tells AI who you are.
Entity Map is a Pro Tools feature. Free installs keep the llms.txt generator; Pro adds a curated, editable map of your organization and important content, served as machine-readable JSON and human-readable HTML.
This marketing site publishes a live example at /entitymap.json and /entitymap.html (with discovery via /llms.txt and robots.txt).
Free vs Pro
| Capability | Free | Pro |
|---|---|---|
Curated /llms.txt | Yes | Yes |
/entitymap.json + /entitymap.html | - | Yes |
| Build / edit / publish wizard | - | Yes |
| Optional AI draft (Connectors / Credits) | - | Yes |
| Link from llms.txt (Structured knowledge) | - | When published |
Free installs see an upgrade teaser on the Entity Map tab and a soft upsell on the llms.txt tab.
Workflow
Three steps in the Tools UI. Nothing is public until you publish in step 3.
- Build draft: Set organization name and description. Create entities from ranked site data (GSC + AI bot traffic) or generate an optional AI draft. You can sync content selection with your llms.txt settings.
- Edit entities: Review names and descriptions, add relations and source chunks, lock anything AI should not overwrite. Pin or add pages from AI bot crawl gaps.
- Publish live: Enable serving
/entitymap.jsonand/or/entitymap.html, optional discovery signals (llms.txt Structured knowledge section, front-page head links, HTTP Link headers), then save.
Endpoints
| URL | Audience |
|---|---|
/entitymap.json | Machines / AI systems |
/entitymap.html | Humans reviewing the map |
Endpoints are served dynamically (same idea as virtual /llms.txt). A physical entitymap.json or entitymap.html in the WordPress root may shadow the virtual routes until you remove or rename it.
Curation
- Sync with llms.txt (recommended): reuse post types, directory rules, and pinned pages from the llms.txt tab.
- Own rules: pick content types and directory include/exclude when sync is off.
- Ranking prefers high-value GSC pages and AI bot traffic when that data exists.
- Optional FAQ chunks from Yoast / Rank Math FAQ blocks.
- Cap max content entities (keep the map focused).
AI draft
With WordPress Connectors or SEO Booster Credits configured under Settings → AI / LLM, you can generate a full draft and regenerate individual entities. Lock entities you do not want AI to overwrite. Building and editing work without AI.
AI Readiness
Sitewide AI Readiness and SEO analysis can surface Entity Map status (served, disabled, physical file shadow, or Pro opportunity when the feature is unused on free/Pro installs). Publishing a live map clears related soft improvements on the next analysis.
Discovery
| Signal | When |
|---|---|
| llms.txt Structured knowledge section | When Entity Map is published and linked from llms.txt |
| Front-page HTML head links | Optional |
| HTTP Link headers | Optional |
robots.txt EntityMap: line | Optional (plugin toggle) |
Validate your map
After publishing, open entitymap.org/validate and paste your JSON preview or fetch from your public /entitymap.json URL (Fetch from URL requires a publicly reachable site with CORS).
On local/dev sites, use the Paste JSON tab with the preview from Step 3 in the Tools UI.
Related
- llms.txt generator: curated entry index for AI crawlers
- Pro Tools tabs: other Pro batch workflows
- AI Readiness in the editor
- AI Bots overview: crawl data that feeds Entity Map curation