SkillResearch a marketPublic data only

Check if AI assistants recommend you

Logs what ChatGPT, Claude, Perplexity and Google AI say to your buyers' questions, checks crawler access and ranks the fixes.

Works inClaudeClaude CodeCodexCursorGemini CLIGitHub CopilotChatGPTNeeds: Web searchv1.0 · November 20, 2026
ai-visibility-check/SKILL.mdDownload
name
ai-visibility-check
description
Use this skill when you want to know whether ChatGPT, Claude, Perplexity and Google's AI answers recommend your company for the questions your buyers ask. It logs every answer (named or not, competitors named, sources cited), checks whether AI crawlers can read your site, and returns a ranked list of fixes.
license
CC-BY-4.0

Check if AI assistants recommend you

This skill shows what AI assistants say when a buyer describes the problem you solve: whether you are named, who is named instead, and which pages the answer leans on. Then it checks your site's technical side and ranks the fixes. Run it for a baseline, then monthly: one answer is a sample, not a ranking.

Inputs

  • Company, website and category, in the words a buyer would use.
  • Buyer: role, industry and country. Ask in the buyer's language.
  • Three to five competitors you lose to or meet most.
  • Engines to test. Default: ChatGPT, Claude, Perplexity, and Google's AI Overviews and AI Mode.

Steps

  1. Write 12 buyer questions, without your brand. Four about the problem ("how do I [job to be done]"), four about the category ("best [category] for [industry]"), two comparisons ("alternatives to [competitor]") and two local ones ("[category] vendors in [region]"). Add two questions with your name in them, kept separate: they only show what the engines know about you.
  2. Run each question in a fresh chat with web search on, in every engine. You cannot ask other assistants on the user's behalf: give the user the question sheet and log the answers they paste back, with dates. If you are one of the engines, you may answer as yourself, labeled as one engine.
  3. Log four things per answer: named or not, position (first, in a list, last), competitors named, and every cited URL. Also note anything the answer gets wrong about you.
  4. Repeat on another day with new wording. Count patterns across answers, not single answers.
  5. Check crawler access. Open /robots.txt and look for these user agents. OpenAI: OAI-SearchBot is for search, and sites that block it "will not be shown in ChatGPT search answers"; GPTBot is for model training; ChatGPT-User acts on a user's request. Anthropic: Claude-SearchBot indexes for search, and blocking it "may reduce your site's visibility"; Claude-User fetches for a user's question; ClaudeBot collects training data. Perplexity: PerplexityBot builds its search results; Perplexity-User fetches for a user. Blocking a training bot does not remove you from search. After a robots.txt change, OpenAI says its systems take about 24 hours to adjust, and Perplexity says up to 24 hours.
  6. Check that the site is readable to a crawler that does not run scripts:
    • The homepage text is in the raw HTML, not drawn only by JavaScript.
    • /sitemap.xml exists; note whether /llms.txt does.
    • Organization structured data is present and complete: name, url, logo, sameAs, description, address, contactPoint. Google says it must match the visible text.
    • One clear title, one main heading and a one-line description.
    • Visible dates, an author, a link to About or Contact.
    • Questions answered directly, near the top of a page.
  7. Read the citations. Group cited URLs: your site, competitors' sites, directories and review sites, media, forums. Where the engines read about your category is where you need to be present.
  8. Rank the fixes by effort and expected effect, using the order in the output.

Output

# AI visibility check: [company], [date]

## Answers
| Engine | Date | Question | Named? | Position | Competitors named | Cited URLs |
|---|---|---|---|---|---|---|

Summary: named in [x] of [y] answers. Most named competitor: [name], [n] of [y].
Most cited sources: [domains]

## Site access
| Check | Result | Fix |
|---|---|---|
| OAI-SearchBot, Claude-SearchBot, PerplexityBot allowed | ... | ... |
| Text visible without JavaScript | ... | ... |
| Sitemap, llms.txt | ... | ... |
| Organization structured data | ... | ... |
| Title, heading, description, dates, author, About | ... | ... |

## Fixes, in order
1. Unblock the search crawlers (low effort).
2. Make page text visible without JavaScript.
3. Add Organization structured data that matches the visible text.
4. Publish one page per buyer question, answer first.
5. Publish fair comparison and "alternatives to" pages.
6. Get present on the third-party sources the engines cite: directories, reviews, trade media.
7. Add an llms.txt file (cheap; not a requirement for Google).
8. Run this check again in 30 days.

Guardrails

  • Reads: the answers the user pastes or the agent can produce itself, and the public files of the user's site.
  • Writes: nothing on the site; fixes are proposals.
  • Asks before: changing robots.txt or any site file, and publishing anything on a third-party site.
  • MUST record the engine and date of every answer, and keep "named" separate from "cited".
  • MUST say that results are samples: nobody outside these companies sees how answers are chosen.
  • NEVER claim a ranking or a share of voice from a handful of answers.
  • NEVER write fake reviews or post undisclosed promotion in forums to get cited.
  • NEVER promise that a fix will make an assistant recommend the company.

Sources

Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/toolkit