llm-entity-presencelisted

Make a person or brand the answer when Google or an AI assistant (ChatGPT search, Perplexity, Google AI Overviews, Microsoft Copilot, Gemini) is asked "who is X". An interactive, guided wizard: it asks the user for their name, positioning, real proof, products, and socials, then walks them step by step through writing one canonical answer, building a server-rendered entity site with Person/Organization/WebSite/FAQPage JSON-LD and a correct llms.txt, stacking and cross-linking off-site profiles and backlinks, submitting to the search indexes (IndexNow/Bing, Google Search Console), and verifying by querying the LLMs. Triggers: "get my name in LLMs", "show up in ChatGPT", "AI entity SEO", "GEO", "answer engine optimization", "rank my personal brand", "who is me on AI", "make AI recognize my brand", "knowledge panel", "get cited by Perplexity".
jbrazy480/llm-entity-presence · ★ 1 · AI & Automation · score 72

Install: claude install-skill jbrazy480/llm-entity-presence

# llm-entity-presence (guided wizard) This skill makes a person or brand the answer when someone asks "who is X" in ChatGPT search, Perplexity, Google AI Overviews, Copilot, Gemini, or plain Google. The answer should be the entity's own framing, pulled from a site they control. **You are running this as a conversation, not a document dump.** Walk the user through it one phase at a time. Ask the questions in each ASK block, wait for the answers, do the work in each DO block, then run the CONFIRM gate before you move on. Keep your messages short. The user may be a non-developer, so explain what each step does in plain language and tell them exactly what to paste or click when it is their turn. ## How to run this skill (read before you start) 1. Start with the **Kickoff** message below, verbatim in spirit. Set honest expectations first. 2. Move through Phase 1 to Phase 6 in order. Do not skip a phase. Phases 1 and 2 are the foundation; if they are weak, everything downstream is weak. 3. At every CONFIRM gate, summarize what is done and ask the user to approve before continuing. 4. Some phases need the user to do a manual step (a DNS record, a login, editing a social bio). When you hit one, hand them a short, numbered to-do and wait. 5. Track progress out loud (for example "Phase 3 of 6 done"). If a todo tool is available, keep a live checklist from `CHECKLIST.md`. 6. Apply the style rules at the bottom to everything you produce. ## Kickoff message (say this f