AI Visibility Audit

AI Visibility Audit

Goal

Find the work most likely to get a brand named or cited in AI answers about its market, and explain it so a non-expert can act on it. Research broadly; recommend selectively. The report leads with one to three recommendations, each tied to the answers and cited pages that justify it.

This skill reads saved answers, adds the pages behind them, and decides what to do. For demand research alone, use ai-prompt-research.

Project context

The project-context tools are free and shared with the app and other agents.

1. External MCP clients: resolve the project with list_projects, ask only if the match is ambiguous, then call get_project_context. In SAM, use the current project and context already injected into the conversation; SAM has no get_project_context tool and needs no project selection or connection setup.
2. This skill needs business_overview, the website and the main competitors. If the overview is empty, infer it from the site, confirm it in one question, and save it with update_project_context.
3. Read get_ai_visibility_tracker. Its prompts, competitors, engines, market and latest runs decide which path below applies. Check the tracker's own brand, the brands row with own: true. Its name is the project name. If that is not how people write the brand (for example a project named "Acme website"), answers that name the brand are not counted as mentions and brand questions are not treated as branded. Ask the user to rename the project in the app before collecting or interpreting answers.
4. Reuse research-log findings under 30 days old for discovery. A claim that drives a recommendation still needs evidence from a run or a page read during this audit.
5. On finish, write back the pages the report names with addKeyPages and append { updates: [{ appendResearchLog: { summary: "AI visibility audit: <run id>. Verdict: <conclusion>" } }] }.

OpenSEO MCP tools

• get_ai_visibility_results, get_ai_visibility_sources, get_ai_visibility_answer: the evidence. Read one run-wide results call, one run-wide sources call with the same runId, then answers you need to verify.
• get_ai_visibility_trend: whether visibility is moving, when the tracker has comparable history. Never compute a trend yourself from separate result calls.
• research_ai_visibility_prompts: the questions around a prompt group and the sources ChatGPT cites for them (US English only).
• explore_prompt: asks ChatGPT one prompt through its API and returns the answer, citations and fanOutQueries, the web searches the model ran before answering. Charged at actual usage per uncached answer; cached answers are free for seven days. Requires a paid plan in hosted mode.
• estimate_ai_visibility_cost, save_ai_visibility_tracker, set_ai_visibility_schedule, run_ai_visibility_check, get_ai_visibility_run: only for the first-run path below.
• get_ranked_keywords, get_serp_results, get_backlinks_overview: optional context when an owned page's search performance or authority could change a recommendation.
• Web reading (fetch, scrape or search): robots.txt, the owned pages that should be cited, and the pages AI answers cite instead.

Workflow

1. Get evidence

• Tracker with a completed run: use the latest completed baseline or scheduled run, or the latest completed manual check when recentRuns has no other. Do not buy new answers.
• Run in progress: when recentRuns shows a pending or partially finished run, follow it with get_ai_visibility_run, respecting pollAfterSeconds. Do not start another. A failed or partial run still supplies whatever answers it completed; report its coverage.
• Tracker with active prompts but no runs: saved prompts that were never collected, for example because the schedule was never enabled. Estimate one check of the saved active prompts with estimate_ai_visibility_cost, get approval once, then call run_ai_visibility_check with the approved runNowCostUsd as maxCostUsd. Follow the returned run. Do not change the schedule.
• Tracker with no active prompts (every topic or prompt paused or archived): ask whether to resume the existing prompts or add new ones, then take the matching path. Do not unpause anything without the user's direction.
• No tracker: propose 10–15 neutral prompts across two or three topics the business sells into, preferring real prompts from research_ai_visibility_prompts. Show one plan with the check cost and the monthly cost from estimate_ai_visibility_cost, and say that a new tracker runs weekly, with its first scheduled check a week later. Get approval once, save through save_ai_visibility_tracker with each prompt's topic, and run one check with the approved runNowCostUsd as maxCostUsd. If the user wants this audit only, pause the schedule with set_ai_visibility_schedule and enabled: false. If the user declines the spend, run the audit on prompt research alone and say the report has no observed answers.

2. Read where the brand stands

Results and sources return 25 rows by default. Pass limit: 50, and when totalCount is larger than the rows returned, follow nextCursor before counting.

The default results and sources reads cover only baseline and scheduled runs. When the evidence is a manual check, including one this skill started, pass its runId to every results and sources read; otherwise the read returns no rows.

Read neutral prompts (the default) for the run. For each topic and engine record: answers collected, brand mentioned, own site cited, and which competitors appear. Rates count answered collections only. Report failed and no-answer collections separately; they are not absence.

Then derive the gap: prompts where a competitor is named and the brand is not. These are the main material for recommendations.

3. Follow the citations

Call get_ai_visibility_sources once for the run, grouped by URL. For the 10–15 sources that recur most in answers where the brand is absent, classify each:

• List or review article: "best X tools", review sites, directories.
• Forum or community: Reddit, Quora, community threads.
• Competitor page: a competitor's own product, comparison or pricing page.
• Owned page: the brand's site.
• Reference or editorial: documentation, news, encyclopedic pages, video.

Read the five or six that decide the recommendations. For a list article: is the brand listed, and is there a way to be added (submission form, author, update date)? For a competitor page: what question does it answer that no owned page does? For a forum thread: is the brand named, and is the thread still active?

Read two or three of the gap answers with get_ai_visibility_answer (each results row's id is the observationId that get_ai_visibility_answer takes.) to confirm what the engine says and which citations sit next to the competitor's name.

Tracked answers show what gets cited but not why. For the one or two gap prompts that lead the recommendations, call explore_prompt with the exact prompt text, the default ChatGPT model and highlightBrand set to the brand. Its fanOutQueries are the searches ChatGPT ran to find sources. Tell the user it uses a small amount of credit before the first call. If it returns an error, such as no paid plan, continue without it and say so.