Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
Description
From the marketplace listing
Searcherries gives your AI agent all the data it needs for GEO and SEO in one connection: how AI assistants answer your customers' questions about your market, plus your Google Search Console, Bing Webmaster Tools and GA4 data.
Connect Searcherries once and ask in plain language. The agent can build a prioritized action plan, find the questions where AI answers leave your brand out and see which competitors and sources they rely on instead, spot the pages and search queries with the most growth potential, and check how much traffic AI assistants send to your site and where it lands. When the agent can work with your website's code, the included skill turns these findings into concrete page changes and edits the files once you approve them.
Built for founders, marketers and SEO specialists who want their site recommended in AI answers and found in search.
Limitations: you need a Searcherries account with at least one project. Search Console and GA4 data are available on every Searcherries plan and appear only for the sources you connect; AI visibility tracking (AI answers, competitors, citations) and Bing Webmaster Tools require a paid plan. Access is read-only: the plugin cannot change projects, questions or settings, and it returns the results of Searcherries' scheduled checks rather than running new ones. It only sees the projects of the account you authorize.
Language: English · Automatically detected from descriptions.
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 2, 2026.
Declared capabilities
Build a prioritized GEO and SEO action plan
Read AI visibility metrics
Read stored AI answers and their judgments
Declared limitations
Deleting data is not supported. The plugin is read-only and should say it cannot delete projects, pointing the user to the Searcherries app.
Running checks or editing tracked questions is not supported. The plugin should explain that it reads stored results only and that questions are changed in the Searcherries app.
Projects of other accounts are not accessible. The plugin should say the project is not in the authorized account rather than guess or show data.
Review scenarios; not an exhaustive list.
Cost & access
The plugin does not sell products or process payments. It only reads data from an existing Searcherries account.
Terms may have changed since this observation.
Starter prompt
What should I work on next to get my brand recommended by AI assistants?
---
name: improve-ai-visibility
description: Use when the user wants AI assistants and AI search to recommend their brand more often, asks why competitors appear in AI answers instead of them, or asks which pages of their website to change based on their Searcherries data. Reads the Searcherries tools and turns the evidence into concrete page changes.
---
# Improve AI visibility from Searcherries data
Searcherries tracks how AI platforms answer the customer questions a brand cares about, which competitors and pages they name, and the site's Google Search Console, Bing Webmaster Tools and GA4 AI-traffic data. The Searcherries tools return that data read-only.
## 1. Find the project
- If the user names a brand or domain, call `get-action-plan` with `project` set to it and `audience` set to `marketing` (use `seo` when the user asks about search traffic). It returns dated priorities and the `project_id`.
- If you can read the website's code, look for the site's domain in the repository first (site config, `package.json` `homepage`, `CNAME`, sitemap, canonical URLs).
- If several projects match, or none, call `list-projects` and ask the user which one to use. Never guess.
## 2. Collect the evidence
Use the `project_id` from step 1.
- Gaps in AI answers: `get-ai-answers` with `prominence_max: 1` lists the answers where the brand is missing or only mentioned in passing. Read the full text of at most five of them (`include_answer_text: true`, `limit: 5`).
- Who wins instead: `get-competitors` (default `ranking`) shows the brands the platforms name; `dataset: "detail"` with `competitor` explains one brand.
- Which sources the answers rely on: `get-citations` with `prompt_id` for a gap question shows the cited URLs; `own_site_only: true` shows which of the site's own pages are already cited.
- Search demand: `get-search-performance` with `dataset: "opportunities"` (high impressions, low CTR, long-tail queries) and `dataset: "ai_question_queries"` (question-shaped searches). Use `source: "bing"` for Bing.
If a source is not connected, say so and continue with what is available. Missing data is unknown, not zero.
## 3. Turn the evidence into page changes
For each relevant page, propose specific changes tied to the evidence, for example:
- answer the tracked question directly near the top of the page, in the words customers use;
- state plainly what the product is, who it is for and how it compares, covering the facts the AI answers give for competitors;
- add an FAQ section for question-shaped queries that already bring impressions;
- link to the page from related pages so it is easier to find.
Flag gaps that need a new page rather than an edit.
If you can work with the website's code, find the source file behind each URL (routes, page components, Markdown or MDX content, templates), present the plan first, and edit files only after the user agrees. Otherwise, list the changes by page URL.
## Ground rules
- Searcherries data is read-only and dated. Quote the period of every figure you use.
- Do not invent numbers, rankings or competitors, and do not promise that a change will win a recommendation.
- Visits are not revenue. Do not present AI traffic as sales.
- Keep claims on the site true. Do not add statements the user cannot back up.
Release notes
The listing name is now Searcherries: AI SEO, and the limitations say which data needs a paid Searcherries plan. Tools, skill and data access are unchanged.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.