Entity SEO · Semantic SEO · Competitor research · Python

Entity Intelligence Suite: Entities for Semantic SEO

Three Python tools — entity gathering, entity research and competitor intelligence — built to answer the question a topical map starts with: which entities does this topic contain, and which have competitors already claimed them?

Client
Own tool · open source
Period
2024 — present
Role
Builder & maintainer
Status
Open source · public repositories
Typographic cover card for the Entity Intelligence Suite — entity gathering, research and competitor intelligence.
Entities first, then the map — the vocabulary a topic is built from.

Results at a glance

Modules
3

Gather, research, intelligence

Feeds
Topical maps

Entities become map branches

Built with
Python

API-driven

Access
Public repos

Open source

The problem

Semantic SEO starts with entities: the people, products, laws, places and concepts a topic is actually built from. A topical map with the wrong entities reads fine and ranks badly, because the page ends up using the words the writer knows instead of the vocabulary the topic contains.

Collecting that vocabulary by hand means reading competitor sites, service pages and search results one at a time. It is slow, and it is the step that gets skipped when a deadline moves.

Why we decided to solve it

The topical map is the piece of work that decides everything downstream, so the input to it has to be complete. Entities are also the part of the map that is hardest to guess: you can feel when a sub-topic is missing, but not when a related entity is.

Competitor coverage matters for the same reason. An entity that three competitors already own is a different piece of work from one nobody has written about, and that difference should be visible before the writing starts.

How we did it

Gather the entities

The first tool collects entities for a topic from a defined set of sources, so the starting vocabulary comes from outside the writer’s head. The output is a clean list that can be reviewed, deduplicated and grouped.

Research them for SEO

The second tool works on that list: what each entity is, how it relates to the topic, and whether it has a page of its own or belongs inside a parent page. That is the decision that turns a list of entities into map branches.

Read the competitors’ coverage

The third tool looks at what competitors have covered, so gaps and contested entities are visible in the same view. A branch nobody has written is a different priority from a branch four sites are fighting over, and the map should say which is which.

Hand the result to the map

The tools stop at research. The map is still written by hand, with volume, CPC and the owning page decided per row — the tools shorten the gathering, not the judgement.

The result

Entity research that used to be an afternoon of tab-hopping became a step that runs before the map is drafted, on client work and on my own sites. The three repositories are public: Entities-Gather and the companion tools in the same account.

What the tools do not do is decide the structure. That judgement stays with the map, which is the point — an entity list is evidence, not a plan.

All projects

Cleared · My own tools on public repositories. No client entity sets, competitor lists or map output are published.

Contact

Want to talk through a project like this?

I am open to remote SEO, web design and performance roles. If you need more detail on a specific project, ask — I will share what the client allows.