What the Knowledge Graph Mapper Actually Maps — Longtail Analytics
"Entity mapping" gets thrown around loosely in SEO writing, usually as a synonym for "we made a diagram." The knowledge graph mapper is a narrower, more literal tool: it takes the context you give it about your site and produces a structured map of four things — products, audiences, messages, and conversion paths — that most sites never write down anywhere, let alone in a form a search or AI system could parse consistently.
Why those four categories
Search engines and AI answer systems increasingly reason about entities, not just keywords: what does this business sell, to whom, in what language, and what does a visitor do next. Most sites express that only implicitly, scattered across a homepage hero, a pricing page, and a contact form. The mapper asks you to make it explicit — not for a cosmetic diagram, but as a structured artifact the rest of your growth work can reference.
The output is a profile: your products, who they're for, the messages you use to describe them, and the paths a visitor takes from interest to conversion. It's diagnostic input, not published content — it doesn't publish anything to your site by itself.
Where it sits in the funnel
The knowledge graph mapper is a follow-on tool, not the front door. The front door is the free site audit — run a homepage through eight checks, see what's technically broken. The mapper picks up after that, through the diagnostic flow, for visitors who want to go past "is my metadata correct" into "does my site tell a coherent story about what I sell and who it's for."
The status ladder behind the tool
Behind the mapper is a four-step status ladder we track for every visitor who starts the flow: website entered, profile saved, inquiry started, inquiry submitted. Each step is its own event, and each one only overwrites status forward — a profile save can't retroactively look like a submitted inquiry, and a started inquiry that stalls doesn't get silently upgraded either. That ordering is deliberate. A diagnostic tool that's honest about which step someone actually reached is more useful to us than one that rounds every visitor up to the friendliest-looking number.
A distinction we hold on purpose: profile saved is not lead qualified
This is the part worth saying plainly rather than letting the numbers imply something they don't. When someone completes the diagnostic flow and saves a knowledge graph profile, that's a real, measurable signal of engagement — it means someone found the mapping useful enough to finish it. It is not, on its own, a qualified inquiry. We track diagnostic_profile_saved as a distinct event from inquiry_submitted precisely so the two never get conflated in a report. A tool that inflates its own funnel by counting soft engagement as hard demand isn't measuring anything — it's flattering itself.
What we actually watch
The metric we care about isn't profile-save volume in isolation. It's the rate at which a saved profile turns into a started inquiry — a real progression from "I mapped my site" to "I want to talk about fixing it." That's a narrower, harder number than a vanity engagement count, and it's the one that tells us whether the mapper is doing its job as a bridge instead of a dead end.