WC Entity Mapper

EntityMap is an open standard for publishing a structured knowledge index of your website, designed for AI systems, large language models, and retrieval-augmented generation (RAG) pipelines. Where sitemap.xml tells crawlers what pages exist, entitymap.json tells AI systems what concepts your site covers, how they relate, and where the evidence is. The standard was created by Fred Laurent and Dixon Jones and is published at entitymap.org . This plugin is inspired by the EntityMap v1.0 spec.

No. The plugin handles all the JSON generation. You review and edit your entities through a point-and-click admin interface.

When you click “Re-extract from site content,” the plugin scans your published posts and pages. For each post, it uses the title as the entity name, pulls the meta description from your SEO plugin (or the excerpt/content if no meta description exists), and builds evidence chunks from the post content. Relationships between entities are suggested based on shared tags and categories.

Chunks are short evidence passages (up to 600 characters each) extracted from your post content. The EntityMap spec allows up to 5 chunks per entity. Each chunk carries the source URL, page title, and your publisher name – so AI systems know exactly where the information came from and who published it.

Relations are typed connections between your entities – for example, PART_OF, DEPENDS_ON, or RELATES_TO. The plugin auto-suggests RELATES_TO relations between posts that share tags or categories, marked with a ✦ symbol so you know which ones were machine-generated. You can edit, change the predicate, or delete any relation.

The spec defines three levels: generator-draft (AI-generated, not yet human-reviewed), self-declared (you’ve reviewed and approve the content), and third-party-verified (certified by the EntityMap registry, launching Q3 2026). The plugin defaults to generator-draft . Once you’ve reviewed your entities, you can upgrade to self-declared in Settings.

No – they serve different purposes. Schema.org markup helps search engines with rich results. EntityMap is specifically designed for AI retrieval systems and RAG pipelines. They complement each other and you should use both.

Yes. The entitymap files are served dynamically via WordPress’s query system. If you use a caching plugin that serves static files, you may need to exclude /entitymap.json and /entitymap.html from caching, or flush the cache after publishing.

No. The discovery signals (head link tag, robots.txt directive, footer reference) add a negligible amount of output to each page. The entitymap files themselves are only loaded when specifically requested.

Update it in WC Entity Mapper → Settings . The plugin will automatically update the publisher name on all chunks to keep attribution consistent. The EntityMap spec requires the publisher field on every chunk to exactly match the root publisher name – case, spacing, and all.