· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →MaxAEO v0.2.0
Check if AI search cites you
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Audit whether example.com gets cited by ChatGPT Search and Perplexity.
Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Classic SEO asks whether you rank. AI answer engines do not rank - they retrieve a few sources and synthesize one answer, so a site can sit at the top of page one and still never be quoted. This plugin audits the second thing. It runs a citation baseline across buyer-intent prompts, checks whether the AI crawlers that control citations can actually reach your pages, reviews whether your content is written in a form that survives retrieval, and returns a fix list ranked by impact over effort. It also ships a fast robots.txt check for the crawlers that matter, because the single most common cause of total absence from AI answers is an accidental block - and the agent most teams block is not the one that controls citations. A single run is a snapshot; the skill also explains what it takes to turn one audit into a repeatable measurement you can re-run month over month.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: ai-search-visibility-audit description: Audit whether a website can be found, crawled, and cited by AI answer engines such as ChatGPT Search, Perplexity, Google AI Overviews, and Microsoft Copilot. Use when someone asks why their brand is missing from AI answers, whether AI crawlers can read their site, how to get cited by ChatGPT or Perplexity, or asks for a GEO or AEO (generative / answer engine optimization) review. Produces a citation baseline across buyer-intent prompts, a crawler-access check, a citability review of named pages, and a ranked fix list. Not for keyword rank tracking, paid search, or pages behind a login. version: 1.0.0 --- # AI search visibility audit Classic SEO asks "do we rank for this keyword". AI answer engines do not rank. They retrieve a handful of sources and synthesize one answer. A site can sit at the top of page one and never be quoted. This skill audits the second thing. Run the four phases in order. Do not skip Phase 1: without a citation baseline everything after it is speculation. ## Scope and limits - Read only publicly accessible URLs and `robots.txt`. - Respect the target site's `robots.txt` and terms of service. Do not attempt to bypass authentication, paywalls, rate limits, or access controls. - If a page requires a login, stop and say the audit covers public pages only. - Audit sites the user is responsible for, or public competitors for comparison. Do not use this to probe a site the user has no relationship with. ## Before you start Collect from the user, asking only for what is missing: - The domain to audit. - The category the brand wants to be recommended in, in the user's own words (for example "expense management software for startups"). - Two or three named competitors. If the user does not know, derive them in Phase 1 and confirm before continuing. ## Phase 1 - Citation baseline Build 10 to 15 prompts a real buyer would type. Cover all four intents. A set that is all category queries will overstate visibility. | Intent | Shape | Example | | --- | --- | --- | | Category | "best X for Y" | best expense tools for seed-stage startups | | Comparison | "A vs B" | Ramp vs Brex for a 30-person team | | Alternative | "alternatives to A" | alternatives to Expensify | | Problem | symptom, no brand named | how do I stop chasing receipts from my team | For each prompt, search the web and record: 1. Whether the brand is named at all. 2. Whether it is cited with a link, or merely mentioned in prose. 3. Which domain the citation points to - the brand's own site, or a third party such as a review site, a forum thread, or a roundup article. 4. Which competitors appear, and in what order. Report a table plus three numbers: **mention rate**, **cited-with-link rate**, and **share of voice** against the named competitors. State plainly that this is one sample, from one engine, at one point in time. Results vary between engines and between runs. Do not present a single run as a trend. Do not call any percentage "the" visibility score. ## Phase 2 - Can AI crawlers reach the site Fetch `https://<domain>/robots.txt`. Blocking the wrong agent is the single most common cause of total absence from AI answers, and it is usually accidental, inherited from a bot-blocking template. Check at minimum these agents: | Agent | Operator | Blocking it costs you | | --- | --- | --- | | `GPTBot` | OpenAI | model training and background knowledge | | `OAI-SearchBot` | OpenAI | **being cited in ChatGPT Search** | | `ChatGPT-User` | OpenAI | live fetches during a user's chat | | `PerplexityBot` | Perplexity | Perplexity citations | | `ClaudeBot` | Anthropic | Anthropic citations | | `Google-Extended` | Google | Gemini grounding - **not** AI Overviews | | `Bingbot` | Microsoft | Copilot, which rides the Bing index | Crawler names change. Before concluding, check each operator's own published crawler documentation for agents added or renamed since this list was written, and audit th
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
--- name: llm-crawler-access-check description: Check whether a website's robots.txt allows the AI crawlers that decide visibility in ChatGPT Search, Perplexity, Claude, Gemini, and Microsoft Copilot. Use when someone asks whether AI bots are blocked, whether to allow or block GPTBot, why a site never appears in AI answers, or wants a robots.txt review for AI crawlers. Reads only robots.txt, then returns a per-agent allow/block table, the exact rule responsible for each verdict, and the precise lines to change. Distinguishes training crawlers from the search crawlers that actually control citations. version: 1.0.0 --- # AI crawler access check One wrong line in `robots.txt` removes a site from AI answers completely, and no amount of content work can compensate. This check takes under a minute and should run before any other AI-visibility work. ## Scope Read `https://<domain>/robots.txt` and nothing else. Do not crawl the site, do not attempt to access disallowed paths, and do not bypass any access control. This is a read of one public file. ## Procedure ### 1. Fetch Fetch `https://<domain>/robots.txt`. - **404 or empty** - everything is allowed by default. Say so; that is a valid and often correct configuration. Stop and report. - **Non-200 other than 404, or unreachable** - report the status code and stop. Do not guess at contents. - **Served as HTML** (a soft 404 returning the site's error page) - flag it. Crawlers may parse it as garbage. This is itself a finding. ### 2. Resolve each agent For each agent below, apply standard robots.txt matching: the most specific `User-agent` group that names the agent wins, and `*` applies only when no group names it. Within the winning group, the longest matching path rule wins, and `Allow` beats `Disallow` on an equal-length match. | Agent | Operator | Purpose | What blocking it actually costs | | --- | --- | --- | --- | | `OAI-SearchBot` | OpenAI | search index | citations in ChatGPT Search | | `ChatGPT-User` | OpenAI | live fetch during a chat | the model cannot open your page when a user asks about it | | `GPTBot` | OpenAI | training | background model knowledge, not search citations | | `PerplexityBot` | Perplexity | search index | Perplexity citations | | `Perplexity-User` | Perplexity | live fetch during a query | live page reads | | `ClaudeBot` | Anthropic | index and training | Anthropic-side retrieval | | `Googlebot` | Google | main index | **AI Overviews and AI Mode**, plus normal search | | `Google-Extended` | Google | Gemini grounding and training | Gemini grounding only - **not** AI Overviews | | `Bingbot` | Microsoft | Bing index | Microsoft Copilot, which rides the Bing index | | `Applebot` | Apple | index | Apple search surfaces | | `Applebot-Extended` | Apple | training | Apple Intelligence training only | | `CCBot` | Common Crawl | open crawl corpus | an input to many downstream models | Crawler names change and new ones appear. Before finalizing, check each operator's own published crawler documentation for agents added or renamed since this list was written, and include them. State which list you used. ### 3. Report Produce a table with one row per agent and exactly these columns: `Agent | Verdict (ALLOWED / BLOCKED / PARTIAL) | Rule responsible | Impact` - **Rule responsible** must quote the literal line from `robots.txt`, or say `no matching rule - allowed by default`. Never state a verdict without the line that produced it. - **PARTIAL** means important paths are disallowed while the site root is allowed. Name the disallowed paths. Then give: - **Verdict** - one sentence: is this site reachable by AI answer engines, or not? - **What to change** - the exact `robots.txt` lines to add, remove, or edit, as a code block the user can paste. If nothing needs to change, say that plainly rather than inventing work. - **What this check did not cover** - `robots.txt` is only the first gate. Server-side blocking by WAF, CDN bot rules, IP re
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
plugins_6a8e5c844de481919bc9e3f89cd6d9c4
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.