ContentMapped indexes every post across your WordPress sites, works out what each one actually covers, maps how they connect, and shows you the ground you have left empty.
The first crawl
Read-only access over the WordPress REST API. No plugin, nothing installed, nothing that can break a live site.
Every post placed and grouped into topic clusters with pillar, sub-pillar and supporting tiers. Size is how central a post is, not how long it is.
The full internal link graph, plus the hygiene problems hiding in it: internal nofollows throttling your own pages, outbound affiliate links missing rel="sponsored", dead links, flagged domains.
Orphans nothing links to. Clusters standing without a pillar. Structured data naming the wrong entity. Entities no post yet owns. None of this comes out of a spreadsheet.
The structure on this map is a real crawled site, anonymised. Only the shape left the database.
The blind spot
You can find out what a competitor ranks for in about four seconds. Finding out what your own two hundred posts genuinely cover, which ones are duplicating each other, and which ones nothing links to takes a spreadsheet and a weekend, and it is out of date by Monday.
So the same three things keep happening. You write a post that overlaps something from 2023 you had forgotten about. A cluster sits there with no pillar holding it together. A post that should be pulling weight has three internal links pointing at it and none of them use the words it wants to rank for.
None of that is a keyword problem. It is a knowing-what-you-have problem.
What it does
Every post on every site, indexed and kept current. Posts grouped into topic clusters with pillar, sub-pillar, and supporting tiers. The full internal link graph, with orphans and weakly linked posts surfaced. Change detection, so you can see what moved since last time.
Every entity in your content matched to its Wikidata identifier, held in a registry per site, with salience scoring that tells you how central each entity is to each post. Suspect matches go to a review queue. Your corrections are locked and never overwritten.
Read what each published page's structured data actually claims and verify every identifier in it. Catch undisclosed affiliate links, internal nofollows, dead internal links, and links to flagged domains. Schema problems come with a corrected, paste-ready block; every link problem names the exact post and the exact link.
Entity coverage across a cluster shows you which important entities no post yet owns. Add ideas to a scored backlog that flags duplication automatically, ranked against whatever you are currently focused on. Then export a pre-filled brief for whichever writing tool you use.
How it works
Read-only access over the WordPress REST API. No plugin, nothing installed, nothing to break.
Posts, links, topics, entities, clusters. First scan does the whole portfolio, then it tracks changes.
Every finding ends in a copy-paste fix or a decision you make. Re-scan when you are done and watch it clear.
On purpose
Most of these are things a competitor would sell as a feature. They are absent on purpose.
Your posts are read-only, permanently. Every fix is copy, paste, re-scan. A tool with write access to two hundred posts is one bad inference away from a very long evening.
The one narrow exception is deliberate and in your hands: you can push category and tag changes you have staged and reviewed yourself. It is off by default, it never touches post content, and every batch reverts with one click.
Every AI-assisted call ends at a button you press. If you overrule it, that correction is locked and stays locked.
No made-up entities, no guessed identifiers, no fabricated authors. An identifier is verified against the live source or it is left out. There is no middle setting.
The opportunity scoring is an internal measure of topical authority across your own portfolio. It is not rank data and it is not labeled as if it were. Search Console integration is on the roadmap and will be named as such when it lands.
Where it goes next
The map gets richer from here. These are in motion, and a feature list that hides its gaps is worth nothing, so here they are before they exist.
Pushing article edits into WordPress is not on the roadmap. See above.
Who it is for
Someone running several content sites on WordPress, alone or nearly alone. Enough posts that you have lost track of what is in there. Enough SEO knowledge that words like entity, cluster, and structured data are not new to you. Enough sense to want a tool that hands you a fix rather than making the change itself.
If you run one site with thirty posts, you do not need this. If you manage client sites for a living, not yet.
Questions
Your post content is read-only, permanently. There is no write path for it in the product. The one narrow exception is optional: you can push category and tag changes you staged yourself. It is off by default and every batch reverts with one click. Everything else it finds ends in something you copy, paste, and re-scan.
No. It connects over the WordPress REST API.
No. It measures what your own portfolio covers and how it links together. It does not report positions or keyword volumes, and it will not pretend to.
A record of every named thing your content talks about, matched to a stable public identifier so that different spellings of the same thing are understood as one thing. It is what makes coverage and gap analysis reliable rather than guesswork.
For some judgments, yes, on your own API keys, and always as an opt-in enhancement rather than the default path. The core analysis runs free without it. Nothing an AI suggests is applied without you clicking.
Not today.
Early access
Early access is opening in batches. Leave an email and you will hear when a place is free.