Entity Map
SEO Booster → Tools → Entity Map publishes a curated map of your organization and important content as machine-readable JSON and human-readable HTML. Build a draft from GSC and AI bot traffic, edit entities and relations, then publish live when you are ready.
Part of SEO Booster.
- Yoast SEO
- Rank Math SEO
- All in One SEO (v4+)
- SEOPress
- The SEO Framework (v5+)
AI discovery
Tell AI systems who you are, not only where to start
What is it?
A Pro Tools feature that serves /entitymap.json and /entitymap.html from WordPress, following the open EntityMap v1.0 standard so LLMs and answer engines understand your organization, products, and content relationships.
Who is it for?
WordPress site owners who already use llms.txt or AI bot tracking and want a structured identity layer beyond a link list, especially publishers, shops, and businesses with rich content libraries.
What does it solve?
llms.txt points AI to your best pages. Entity Map explains who you are, how entities relate, and which sources back each claim, with discovery signals in llms.txt, robots.txt, and optional head links.
What you get
Curated from real site data
Build drafts from ranked GSC pages and AI bot traffic, including crawl-gap suggestions from pages bots already fetch.
Editable entities and relations
Review names, descriptions, source chunks, and predicates. Lock entities AI should not overwrite. Pin pages from bot gaps.
Live JSON and HTML endpoints
Publish /entitymap.json for machines and /entitymap.html for humans. Nothing goes public until you enable serving and save.
Discovery and AI Readiness
Optional llms.txt Structured knowledge section, robots.txt EntityMap line, and sitewide AI Readiness checks when the map is live.
Optional AI draft
Generate entity suggestions with WordPress Connectors or SEO Booster Credits when configured; building from GSC and bot data alone works without AI.
EntityMap v1.0 compliant
Output follows the open entitymap.org standard; validate live JSON at entitymap.org/validate before sharing with partners or AI pipelines.
Entity Map in Tools
Build draft → Edit entities → Publish live
Path: SEO Booster → Tools → Entity Map. Three steps match the plugin UI. Free installs see an upgrade teaser on this tab.
- Build draft: set organization name and description; create entities from ranked site data or optional AI draft; sync content rules with llms.txt when recommended
- Edit entities: collapsible rows, relations, source chunks (≤600 chars), locks, and bot crawl-gap pins
- Publish live: enable /entitymap.json and/or /entitymap.html, optional discovery toggles, validate at entitymap.org
Endpoints and validation
Endpoints are served dynamically like virtual /llms.txt. A physical entitymap.json or entitymap.html in the WordPress root may shadow virtual routes until removed. Use the official EntityMap validator to confirm your live JSON before sharing it with partners or AI pipelines.
- /entitymap.json for AI systems and RAG pipelines
- /entitymap.html for human review and internal QA
- Paste JSON or fetch your public URL at entitymap.org/validate
- Live example on this site: /entitymap.json and /entitymap.html
How to publish Entity Map
-
Open Tools → Entity Map (Pro)
Connect GSC and enable AI bot tracking first if you want ranked pages and crawl-gap signals in the draft builder.
-
Build your draft
Set organization details, generate entities from site data or optional AI, and sync llms.txt curation rules when it fits your workflow.
-
Edit and lock
Refine descriptions, add relations, pull source chunks, and lock anything that must stay human-owned.
-
Publish and validate
Enable JSON/HTML serving, save, open live URLs, and validate at entitymap.org. AI Readiness updates on the next analysis run.
Frequently Asked Questions
What is Entity Map?
Entity Map is an open standard for publishing structured knowledge about your organization and website. SEO Booster Pro serves /entitymap.json for AI systems and RAG pipelines and /entitymap.html for human review. The map lists key entities, typed relationships, and extractive evidence chunks with publisher attribution so consumers understand who you are and what you know—not only which URLs exist.
What are /entitymap.json and /entitymap.html?
/entitymap.json is the machine-readable EntityMap v1.0 file at your site root. /entitymap.html is the companion human-readable view generated from the same data. SEO Booster publishes both dynamically from Tools → Entity Map when serving is enabled. Validate live JSON at entitymap.org/validate before sharing with partners or AI pipelines.
How is Entity Map different from sitemap.xml or schema.org?
Sitemaps list URLs; schema.org markup describes individual pages. Entity Map declares site-wide entities, typed relationships, and evidence chunks in one index—what your organization covers and how concepts connect across the site. It complements sitemaps and page-level schema; it does not replace them.
What is the difference between llms.txt and Entity Map?
llms.txt is a curated starting index for AI crawlers (free). Entity Map (Pro) publishes structured organization and content relationships as /entitymap.json and /entitymap.html so systems understand who you are, not only where to begin. SEO Booster can link both via discovery signals in llms.txt and robots.txt.
How do I publish Entity Map on WordPress?
Open SEO Booster → Tools → Entity Map (Pro). Build a draft from GSC and AI bot data (or optional AI), edit entities and relations, enable JSON and/or HTML serving under Publish live, then save. See the step-by-step Entity Map guide for screenshots and validation tips.
Is Entity Map included in the free plugin?
No. Free installs keep llms.txt and AI bot tracking. Pro unlocks the Entity Map Tools tab, build/edit/publish workflow, and live endpoints.
Do I need AI configured?
No. Building, editing, and publishing work without AI. Optional AI drafts use WordPress Connectors or SEO Booster Credits when configured.
How does AI bot tracking help?
Crawl data surfaces pages bots already visit and gaps you can pin into the map, so curation reflects real AI interest on your site.
What standard does the output follow?
EntityMap v1.0 (entitymap.org/spec/v1.0), including chunk publisher attribution, entity types, predicates, and optional robots.txt discovery.
Can a physical file block the virtual endpoints?
Yes. If entitymap.json or entitymap.html exists in the WordPress web root, many hosts serve that file directly. Remove or rename it to use SEO Booster dynamic serving.
Boost your rankings with smarter SEO
Connect Google Search Console, fix pages from real search data, automate internal links, and optionally speed up repetitive tasks with AI.
Get Started