Prompt Visibility Heatmap, Brand Aliases, and Brand Book for AI Search Monitoring
A visibility heatmap without aliases will miss the name your buyers actually type. The Brand Book is the context layer Content Agents and scoring should share, not a PDF in Drive.
Prompt rows in a table are easy to ignore. A visibility heatmap is the same data in a shape a human will actually argue with: which prompts you own, which you share, which you never appear on. The trap is the brand string. If the model says "PW" or a former product name and your tracker only matches the legal entity, the heatmap is green in the wrong cells.
Aliases and a Brand Book sound like branding hygiene. They are measurement settings. Get them wrong and every downstream agent works off a misspelled company.
Heatmap and the charts around it
Promptwatch's visibility score, mentions over time, and position chart are how you see movement instead of a single scrape. Stacked competitor charts show who took the cell. Period compare is the "did this ship do anything" view. The heatmap is the overview that tells you where to open a row.
Use it after you have a stable prompt list. Twenty purchase questions beat two hundred curiosities. Fan-outs will expand the list; you still pick what is money.
Trends that explain what changed between checks matter more than a prettier heatmap. A cell that went cold because a Reddit thread appeared is not a "we need more content" cell until you look at citations.
Aliases: the unglamorous matching layer
Brands accumulate strings. Legal name, spoken name, old product, common misspelling, abbreviation sales uses on calls. Highlighting those in answers is how you stop undercounting. It is also how you avoid overcounting a generic word that is not you.
Set aliases when you create the project, then again after the first week of answers. You will discover a nickname in Claude that never appears in ChatGPT. Personas can change which name shows up. Do not merge persona rows into one average and then wonder why the heatmap looks stable.
This is not a map-pack rank tracker. Country is on paid plans; state and city are on Professional and above. Local GEO is still prompts plus Google Business Profile, not this heatmap pretending to be BrightLocal.
Brand Book as the shared brain
The Brand Book is project context: who you are, how you sound, claims you will stand behind. Content Agents read it so drafts do not invent a tone. Monitoring still needs it so "the brand" in an answer can be scored as you, a competitor, or a generic category.
Keep it short enough that a model will use it. A 40-page manifesto becomes ignored context. Put the forbidden claims in writing (no invented funding, no fake customers). Review inbox exists because the Book will still be incomplete.
Jasper Brand Voice is a cousin for writers. It is not a visibility heatmap. Otterly.AI will monitor mentions from $29 without this workspace. Fine. Different object.
How this turns into work
Unified Actions should not fire "write article" on every red cell. Red plus no ChatGPTBot fetch is a technical ticket. Red plus a competitor URL in citations is a page-level fight. Red plus an alias miss is a settings ticket, and those are the cheap wins.
Explore (free, 10 ChatGPT prompts) is enough to see whether aliases were wrong. Essential at $95/mo is the first paid heatmap that includes more than ChatGPT. Professional at $245/mo adds the city layer and 25M crawler logs.
A heatmap is a reporter until aliases are true and the Brand Book is the same document the agent writes from. Then it is a control panel. That is the agentic reading of a feature that looks like a pretty grid.