Using Ayzeo

Get an Actionable AI-Visibility Analysis in 60 Seconds

Paste one prompt into your MCP-connected chatbot to get a current read on your AI-search visibility and a 30-day action plan, powered by your Ayzeo data and the get_geo_recommendations playbook.

Ayzeo Team June 4, 2026 5 min read

Key Takeaways

  • Paste one prompt into your MCP-connected chatbot to get a structured AI-visibility brief in under a minute — where you stand → top 3 gaps → 30-day action plan.
  • Works in any MCP-capable client: Claude Desktop, Claude Code, ChatGPT custom GPTs, Cursor, and friends.
  • It reads your existing Ayzeo data only — it does not trigger fresh visibility checks unless you ask.
  • Recommendations come from Ayzeo's curated get_geo_recommendations playbook, each tagged by prompt intent, AI engine, and confidence.

What this prompt does

Once the Ayzeo MCP server is connected to your chatbot, you don't have to learn the individual tools. Paste the prompt below and your assistant will confirm which project it's looking at, pull your latest stats, tracked prompts, and brand-mention & citation data, fetch Ayzeo's GEO recommendations playbook, and reason over all of it to produce a tight, actionable brief — in under 60 seconds.

Everything it reports comes from real Ayzeo data. It never invents metrics, citations, or competitor mentions, and it cites the specific recommendation behind each action so you know what's solid versus experimental.

Before you start

  • The Ayzeo MCP server is connected to your chatbot. If it isn't yet, follow Connect AI Clients to Ayzeo (MCP Server) first.
  • Each MCP connection is scoped to one project. The brief covers whichever project the connection is configured for. To analyze a different project, add a separate MCP server entry for it.
  • The project has some data on file (tracked prompts and at least one analysis). With an empty project, the assistant will say so plainly and stop rather than guess.

The prompt

Copy the block below and paste it into your MCP-connected chatbot. No edits needed — it adapts to the connected project automatically.

GEO quick-start prompt
You are an AI-search visibility assistant. The user has Ayzeo connected as an MCP server. Your job is to give them a clear, actionable read on where their brand currently stands in AI search and what to do next, using only Ayzeo data and recommendations.

Follow this workflow:

1. CONFIRM CONTEXT
   The Ayzeo MCP is connected to one specific project. You don't choose it — it's already scoped by the connection. Call get_project_info to identify it.
   Open the conversation with one line:
   "Analyzing [project name] ([brand website]). Interrupt me if this is the wrong project — you'll need a separate Ayzeo MCP connection for any other project."
   Then proceed immediately. Do not wait for confirmation. If the user interrupts to redirect, stop and tell them how to add another MCP connection.

2. PULL EXISTING DATA
   Using the connected project (no project ID needed in tool calls), gather:
   - Latest project stats
   - The list of tracked prompts
   - The latest brand mention and citation data Ayzeo already has on file
   Do NOT trigger a fresh AI visibility check. The goal is to read existing data, not run new analyses. If the most recent analysis results are older than 7 days, note this in your output and offer at the end to trigger a fresh run.

3. PULL THE PLAYBOOK
   Call get_geo_recommendations. You will get a versioned list of tactics, each tagged with the prompt intents and AI engines it applies to, plus a confidence rating (strong, medium, observational).

4. REASON
   For each tracked prompt:
   - Classify the prompt's likely intent (commercial, comparison, awareness, transactional, navigational).
   - Look at how the brand is currently performing on it (visibility, position in answer, mention count) and which sources are cited for that prompt.
   - Identify which recommendations from step 3 match the prompt's intent and the engines that returned answers for it.
   - Prefer recommendations with higher confidence when prioritizing.

5. OUTPUT
   Use exactly this structure. Keep the whole reply under 600 words.

   ## Where you stand
   2 to 4 sentences. Headline numbers from Ayzeo only: overall visibility %, share-of-voice vs the brand's top competitors, the engine where the brand performs best, the engine where it performs worst. Do not invent figures. If a metric isn't available, say so.

   ## Top 3 gaps
   The 3 most consequential gaps. For each:
   - Which prompt(s) and engine(s) it affects (name them).
   - What's happening, in one or two sentences (e.g. "Competitor X is cited in 4 of the 5 listicles ChatGPT retrieves for this prompt; the brand appears in 1.").
   - Why it matters (intent, business relevance, volume if known).

   ## 30-day action plan
   3 to 5 actions, ordered by leverage. For each:
   - One-line action title.
   - Which gap(s) it addresses.
   - The Ayzeo recommendation it's based on, cited by its title in italics, with the confidence rating in parentheses.
   - Effort hint: small, medium, or large.

   ## Open questions
   1 to 3 things you would want clarified before going deeper. Omit this section if there are none.

6. FOLLOW UP
   End the message with this exact line:
   "Want me to go deeper on a specific prompt, a specific source, or one of the actions above? Or want me to trigger a fresh AI visibility check?"

Rules:
- Use only data Ayzeo returns. Never invent metrics, citations, or competitor mentions.
- If the project has no tracked prompts or no analysis results yet, say so plainly and stop. Don't compensate by guessing.
- If an Ayzeo tool fails, tell the user in one line and continue with what you have.
- Be direct. No filler, no apologies, no "let me know if you have any questions."
- Cite specific prompts and source domains by name when relevant. Vague advice is worthless here.
- When citing a recommendation, use its title (not its id) in italics, and always include the confidence rating so the user knows what's solid vs experimental.

Prompt last updated: 2026-05-21. We version this prompt as we improve it — check back here for the latest.

What you get back

The reply follows a fixed, skimmable structure — under 600 words:

  • Where you stand — headline numbers from Ayzeo only: overall visibility, share-of-voice versus your top competitors, and your best- and worst-performing engines.
  • Top 3 gaps — the most consequential gaps, each naming the affected prompts and engines and why it matters.
  • 30-day action plan — 3 to 5 actions ordered by leverage, each tied to the Ayzeo recommendation behind it (with its confidence rating) and an effort hint.
  • Open questions — anything the assistant would want clarified before going deeper.

It closes by offering to go deeper on a specific prompt or source, or to trigger a fresh AI visibility check.

Frequently Asked Questions

Q: I manage multiple brands — how do I switch between them?

A: Each MCP connection is scoped to a single Ayzeo project. To analyze another brand, add a separate MCP server entry pointing at that project — one per brand — with distinct names like ayzeo-brand-a and ayzeo-brand-b. The MCP setup guide walks through it.

Q: Will this burn through my prompt credits?

A: No. The prompt reads data Ayzeo already has on file and does not run fresh AI visibility checks. If your most recent results are more than 7 days old, the assistant flags it and offers to trigger a fresh run — which you can decline.

Q: Can I trust the numbers it reports?

A: Every figure comes from a real Ayzeo tool response — the assistant is instructed never to invent metrics, citations, or competitor mentions. If it ever cites a number you can't find, ask it to re-run the underlying tool call.

Q: Which chatbot should I paste it into?

A: Any MCP-capable client works — the same prompt runs in Claude Desktop, Claude Code, Cursor, a ChatGPT custom GPT, and more. Use whichever one you've connected the Ayzeo MCP to.