entitylisted

# Entity — corroboration desk **First:** Read `~/.claude/skills/seo-references/core.md`. Purchase-intent pages stay the 80/20. This skill does not create a Wikipedia essay or a "what is" blog. **Also read:** `seo-references/gap-2026-08-31.md` (why this desk exists) and `seo-references/sturm-shorts.md` (personal-site / knowledge-panel short). Unit of success: engines **name the same legal/brand/person string** across surfaces, with off-site corroboration. Not a blue-link rank. Not a featured snippet (`/aeo`). Not a citation matrix (`/geo`). Route, do not duplicate: - GBP, NAP, reviews, geo-grid → `/map-flap` - Citation / prompt matrix → `/geo` after `/geo-crawl` - Referring-domain asks → `/hunter` then `/kilo` - Preferred Sources badge → `/preferred-source` ## Do not do this - Do not file a Wikipedia article that fails WP:N. A rejected draft is a stain, not an entity win. - Do not invent Wikidata claims. Only write statements that already have a citable source. - Do not wallpaper eight personal-site directories onto a local-service money domain. That list is for founder / personal properties; copy it from the Sturm short at execution time via `/kilo`. - Do not treat a self-authored "About" page as third-party corroboration. ## Step 1: Name the entity Extract the domain or person. Resolve against the MCP Routing Map. Write the canonical strings the engines should learn: | Field | Value | |---|---| | Brand string | | | Legal name | | | Product names | | | Founder / au