Build an entity graph
of your own site
Answer engines retrieve fragments of your content and infer who you are, what you offer and how it connects. Moose builds that graph from the pages already crawled on your computer, marks which connections your pages state and which he inferred, and reads it in any later chat.
SamPremium
On it, Sam. Let's map how Fathom's entities connect across the site.
I can build an entity graph for this project. Choose how deep the run should go, then start it below.
Hi, Moose maps the people, products, places, and topics across this project's crawled pages, plus how they connect.
One card, and two exports
It is built from the pages already crawled for this project, so every number traces back to a URL you own.
People, organisations, products, services, places, events and topics, each with the number of pages it appears on, plus a count by type.
A score per entity, weighted by where the name appears: structured data counts more than a title, and a title more than a heading. The score is compressed so one page repeating a name cannot dominate.
The connections your pages state, the ones that keep appearing on the same pages, and the ones whose names sit close in meaning. The card counts all three separately.
Entities with their type, aliases, page count, score and up to three source URLs each. Relations with their kind, source and confidence.
Quick and Full
Both run against the crawl already on your machine, and both map the connections at the end. The difference is whether a model reads your body text.
Reads the JSON-LD on your pages plus the names in your titles and headings. Seconds on most sites, no model involved, and nothing leaves your computer.
Pick the top 100, 250, 500 or 1,000 pages, ranked by Search Console clicks where it is connected. A model reads the body text and pulls out the things and connections you name in prose but never mark up. It runs on your local model, your OpenRouter key, or your monthly allowance on a managed plan.
How to read the card
A handful of numbers on the card each point at a different piece of work.
Crawl once, then build it from chat
The pages are already on your computer from the site crawl, so the graph is built from your own site.
Site Monitoring crawls the project and keeps the pages locally. The graph runs on those pages, so it waits until one crawl has finished.
Ask for an entity graph, pick it from the Tools menu, or use the button on a new chat. Same card either way: choose Quick or Full, then start.
Which type dominates, which entity carries the salience, and how many connections your pages state themselves. Take the CSV or PDF into the schema work, or ask Moose: he keeps the graph and reads it in any later chat.
Three kinds of connection
Every connection carries its kind, and the card counts them separately, so you can tell what your site states from what Moose inferred.
Author, publisher, brand, founder, works for, parent organization and a few more. Quick takes these from your JSON-LD and follows the @id references inside it. Full adds the ones a model finds stated in your prose. If no page says who founded the company, there is no founder relation.
Entities that appear together on at least two pages, labeled "appears with" and carrying the number of pages they share. That is a pattern on your site, not a claim about the world.
A small embedding model runs on your computer, compares entity names, and keeps the three closest per entity above a similarity floor. Labeled "related to" and scored. This gives a site with no markup a usable graph.
Case, punctuation and a trailing Inc, Ltd or GmbH fall away, so "NinjaOne, Inc." and "Ninjaone inc" become one entity. Two different types stay two entities, which is why a brand can appear as both a product and an organization.
Questions people ask
What is an entity graph, in plain terms?
A list of the things your site talks about, and the connections between them. Not keywords, and not pages. Seeing yours lets you decide whether it says what you meant.
Why are most of my relations shared-page or semantic?
Because those two are the ones Moose can work out on his own. Labeled relations come from your markup, plus anything the Full pass reads out of your prose, and on most sites the markup stops at the article template. So the labeled number starts low.
Do I need schema markup for this to work?
No. Without it you still get entities from your titles and headings, and connections from shared pages and name similarity. What you will not have is a labeled relation.
What does the Full pass cost?
Nothing beyond time on a local model. On a cloud model it spends your OpenRouter key, or your monthly allowance if you are on a paid plan. You choose how many pages it reads: 100, 250, 500 or 1,000. Quick needs no model at all and is free on every plan.
What do I need before I can build one?
A project with a website, and one site crawl that finished. The graph reads pages already stored on your machine, so if no crawl has run the card sends you to Site Monitoring first.
Can Moose use the graph after he builds it?
Yes. The graph stays with the project, and Moose can read it in any later chat. Ask which internal links to add or which schema gap to close first, and he answers from the graph. He keeps what your pages state separate from what he inferred. If the project has no graph yet, he offers to build one.
How is this different from a coverage check?
Coverage answers whether you have written about a topic. The graph answers what your site says you are.
How big does the graph get?
The card shows the true totals. The table and the exports carry up to 2,000 entities and 2,000 relations. If the AI pass was skipped, stopped or failed, the card says so.
More things to ask Moose
All use casesAsk before you brief, and get the pages, the verdict and what is missing.
Ask why traffic moved and get an answer with the tables under it.
The searches Google writes for itself before it answers, and who it cites.
Twelve searches behind one prompt, including the ones naming brands it trusts.
One question, five engines, about a minute. Free on every plan.
The full list, and what Moose does step by step in each one.
Crawl your site once,
then build the graph.
Download Hi, Moose, crawl your site once, and build the graph in seconds. Quick runs on the free plan.