← Searcherries: AI SEOCONTENT HISTORY
WHAT CHANGED
Update to Searcherries: AI SEO
Snapshot Oct 24, 2026 · 13:38 UTC · version 1.0.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Searcherries: AI SEO and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [],
"name": "improve-ai-visibility",
"skill_md_contents": "---\nname: improve-ai-visibility\ndescription: 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.\n---\n\n# Improve AI visibility from Searcherries data\n\nSearcherries 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.\n\n## 1. Find the project\n\n- 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`.\n- 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).\n- If several projects match, or none, call `list-projects` and ask the user which one to use. Never guess.\n\n## 2. Collect the evidence\n\nUse the `project_id` from step 1.\n\n- 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`).\n- Who wins instead: `get-competitors` (default `ranking`) shows the brands the platforms name; `dataset: \"detail\"` with `competitor` explains one brand.\n- 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.\n- 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.\n\nIf a source is not connected, say so and continue with what is available. Missing data is unknown, not zero.\n\n## 3. Turn the evidence into page changes\n\nFor each relevant page, propose specific changes tied to the evidence, for example:\n\n- answer the tracked question directly near the top of the page, in the words customers use;\n- state plainly what the product is, who it is for and how it compares, covering the facts the AI answers give for competitors;\n- add an FAQ section for question-shaped queries that already bring impressions;\n- link to the page from related pages so it is easier to find.\n\nFlag gaps that need a new page rather than an edit.\n\nIf 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.\n\n## Ground rules\n\n- Searcherries data is read-only and dated. Quote the period of every figure you use.\n- Do not invent numbers, rankings or competitors, and do not promise that a change will win a recommendation.\n- Visits are not revenue. Do not present AI traffic as sales.\n- Keep claims on the site true. Do not add statements the user cannot back up.\n"
}SHA-256 of public snapshot: 1700bc75887086ef8a9ff6f3fad89c48cdb75d8c1d482af339dd036426078f5e