Atlaven v1.0.4
AI search visibility tracking
Developer declarations; not independently tested. Listing last checked Nov 4, 2026. Package observed Nov 4, 2026.
No commerce: the plugin reads and manages data in an existing Promvia account and processes no payments.
How visible is my site in AI search right now?
From the marketplace listing
Promvia measures whether AI assistants name and cite your website. Connect your existing Promvia account and ask, in plain language, how your site shows up in the AI answers Promvia checks across the major AI assistants and search engines: your AI Visibility Score, which of your tracked questions cite you and which cite other businesses, the sources those answers rely on, your GEO readiness findings and action plan, and the AI-referred visits and revenue Promvia has measured on your site. With write access you can also track or archive questions, queue a new citation check or deep site scan, set the status of an action item, and keep the FAQ answers of your tracked questions in sync. Write access is opt-in: each write permission is unticked on the consent screen until you choose it, and every write runs under the same limits as the Promvia dashboard. An account that has read access only connects without these permissions: the consent screen then offers the read permissions alone. Who it is for: marketers, SEO and content teams, and agencies who already use Promvia. Limitations: you need an existing Promvia account with MCP access, and you sign in with OAuth. Promvia reports what it has measured: shares come with their sample size and a 95% confidence interval, and results reflect the most recent completed checks, not a live query of each engine at the moment you ask.
Language: English · Automatically detected from descriptions.
· 3 observations
Long description: added “An account that has read access only connects without these permissions: the consent screen then offers the read permissions alone.”. Version changed from “1.0.3” to “1.0.4”.
View comparison →Package or technical metadata updated
View technical comparison →Find competitors to follow as you develop your plugin.
Pineprompt measures how often AI search engines and assistants mention your brand in their answers.
Shared terms: tracking, visibility, search, cite
AEO/GEO by VibeSEO tracks brand visibility in AI search. Monitor answer engine optimization (AEO) and generative engine optimization (GEO...
Shared terms: tracking, visibility, search, cited
Connect to RankZero for AI search visibility, competitors, prompts, citations, GA4, and Google Search Console insights.
Shared terms: visibility, search, citation, cite
See how AI search engines mention and cite your brand, how you compare with competitors, and what to publish next, using your live Thrive...
Shared terms: visibility, search, citation, cite
Findable checks a public business website for search and AI answers, then suggests the first useful changes and reviewable content drafts...
Shared terms: visibility, search, citation, traffic
--- name: ai-visibility-check description: Answer how a website shows up in AI search answers from the user's own Promvia account - its AI Visibility Score, which tracked questions cite it, which other businesses and sources are cited instead, and what to fix next. --- Use this skill when the user asks how visible their website is in AI assistants' answers, whether AI answers cite or recommend them, who is cited instead, or what to change to be cited more often. Explicit instructions from the user take priority over these steps. 1. Call `list_sites` to find the user's sites. If there is more than one and the user did not name one, ask which site they mean. If the site they name is not in the list, say that it is not on their Promvia account and stop; never answer about a site that is not theirs. 2. For an overall picture, call `get_visibility_score`. For individual questions, call `get_citations`. For the domains AI answers rely on, call `get_sources_report`. For what to fix, call `get_geo_actions`. 3. Report only what the tools return. Quote every share or rate together with the sample size and 95% interval the tool gives, and repeat any warning the tool attaches (such as a thin basis or a tie between two businesses). Do not compute a new rate, invent a trend, or name an engine, question or competitor the tool did not return. 4. Results are from the most recent completed checks, not a live query of each engine. Say when they were checked if the tool gives a date. 5. Only change something in the account (tracking a question, starting a check run or scan, setting an action item's status or an FAQ answer) when the user asks for that change. Those tools need write access; if they are not available on this connection, say that the connection is read-only rather than suggesting a workaround.
Listing text: an account with read access only can now connect, and its consent screen offers the read permissions alone. No tool, permission or behaviour changed. Unchanged since the first directory release: Read tools for AI visibility scores, citation results and history, cited sources, GEO audits, deep site scans, action plans and AI-referred traffic and revenue; opt-in write tools to track or archive questions, queue citation checks and site scans, set action item statuses and keep FAQ answers in sync. OAuth 2.1 sign-in with PKCE, using a client ID metadata document or dynamic client registration.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 4, 2026.
plugin_asdk_app_6ae77088781881919bc4fa61e639e946
Download plugin data (JSON)