1---2name: ai-search-risk3description: >-4 Checks a B2B SaaS company's planned or live AI visibility tactics against Google's spam policies and its guidance5 on generative AI features, before they cost the site: self-ranking best-of lists, pages scaled from a template, AI6 text at volume, hidden instructions to AI, cloaking, paid or fake mentions, fake reviews and sock-puppet posts.7 Scans the site's page list for the patterns, maps each tactic to the policy it meets, gives the safer move and8 returns PASS, PASS WITH NOTES, FAIL or BLOCKED. Use it before launching a GEO or AEO tactic, or when visibility9 drops after one. Not for crawler access (use agent-readiness) or measuring visibility (use ai-answer-panel).10license: MIT11compatibility: >-12 Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Reads the sitemap and pages if the agent13 can browse, otherwise a page list and the tactics the reader describes. Python 3 is optional, for the pattern scan.14metadata:15 author: SHAKEUP16 version: "1.0.0"17 stage: check18 plugin: seo-ai-search19 homepage: https://www.shakeuphq.com/skills/ai-search-risk20---21 22# AI search risk check23 24Flags the AI visibility tactics that Google treats as spam, or that published data ties to lost visibility, before they ship or while they can still be undone.25 26## Purpose27 28- One job: check planned or live tactics and the site's pages against the spam policies and Google's AI guidance, and give each finding a severity and a safer move.29- Stage: check. It ends in PASS or FAIL with severities.30- It never helps carry out a critical tactic: no hidden instructions to AI, no fake reviews, no sock-puppet posts, no undisclosed paid mentions. It says why and offers the move that works.31- It never claims a penalty it can't see. A pattern is a risk; a manual action is shown in Search Console.32 33## Use when / not34 35| Situation | Use |36| --- | --- |37| An agency, tool or teammate proposes a GEO, AEO or "LLM optimization" tactic | this skill, before it ships |38| Visibility or traffic dropped after a content push | this skill, on the live pages |39| Planning outreach to cited pages | `cited-pages` (it routes risky plays here) |40| AI crawlers can't reach the site | `agent-readiness` |41| A single page's claims need checking | `claim-check` |42 43## Inputs44 45| Input | Required | Ways to provide, in order | If missing |46| --- | --- | --- | --- |47| The tactics: planned or live, in the reader's words | yes, or pages | the reader's request; an agency proposal; a content plan | check the pages only |48| The site's pages: URL, title, published date; for lists, the first item; text where available | yes, or tactics | a crawl or sitemap if the agent can browse; a CMS or crawl export; a pasted list | judge the described tactics only; coverage `partial` |49| The same page fetched as a browser and as an AI crawler | no | 2 fetches if the agent can make them; 2 HTML files the reader saves | the cloaking check is skipped |50| Search Console messages and traffic around a drop | no | a connected Search Console; a screenshot of Manual actions; a Pages export | say whether a manual action is known or not |51 52## Profile read53 54From `company-profile.md`: `## Company` (website and brand terms, to spot self-ranking lists), `## Competitors` (mention policy, for comparison pages), `## Content` (site sections, authors, to check author claims), `## Claims and proof` (what comparison pages may claim), `## Channels` (who runs outreach and community work), and every `## Learnings` entry for `ai-search-risk` with status `noted`, `fact` or `accepted`.55 56No profile: ask for the website and brand terms, in one message. Say that `company-profile` saves this next time.57 58## Steps59 601. **Apply learnings.** Read them first: tactics already reviewed and the decision, and any accepted threshold change.61 622. **List what is being checked.** Each tactic in one line (what, where, how many pages, live or planned), and the page list if there is one.63 643. **Map each tactic** to the table in `references/tactics.md`: the policy or guidance it meets, the default severity, the safer move. A tactic not in the table: judge it by the 2 questions the spam policies turn on, and say you did. Is it made mainly to manipulate rankings or AI answers rather than to help a user? Would a user, seeing how it was made, feel misled?65 664. **Scan the pages.** With Python, write the page list to JSON and run:67 68 ```69 python3 scripts/risk_scan.py site --json pages.json70 python3 scripts/risk_scan.py compare --browser as_browser.html --bot as_bot.html71 ```72 73 Without Python, check by eye: list titles that start "best", "top" or end "alternatives" and see which put the brand first; sort titles and look for runs that differ by a word or 2; count pages published per month; search page text for lines addressed to AI and for hidden text. Say which way you ran it.74 75 | Pattern | Threshold | Why |76 | --- | --- | --- |77 | Self-ranking lists | any is a warning; 10 or more, or 10% of pages, is critical | at scale it reads as a scheme, and sites that leaned on them lost visibility across the domain |78 | Template groups | 10 or more titles that differ by 2 words or fewer | the shape of programmatic pages; each must add something the others don't |79 | Publishing spike | 3x the usual 30-day output | a scaled push; check what each page adds |80 | Near duplicates | 5-word overlap of 0.6 or more between 2 pages | thin variants of one page |81 | Instructions to AI, hidden text | any | an attempt to steer AI answers with content users don't see |82 | Crawler gets different content | word overlap under 0.7 between browser and crawler fetches | cloaking, if on purpose |83 845. **Judge value where the scan only finds a pattern.** For each template group or spike, open 3 pages: does each carry data, an example or advice the others don't? Yes, the group drops to a suggestion. No, it stays a warning, and becomes critical when the pages were made in bulk with generative AI and nobody added anything.85 866. **Write each finding:** the tactic or pages, the severity, the policy or guidance it meets (named, linked), the evidence (counts, URLs), and the safer move. For a critical tactic the reader asked to carry out, decline that part plainly and give the safer move in its place.87 887. **Order the fixes** for anything live: critical first, then by the number of pages. Removal, noindex or redirects are the reader's call.89 90## Check and verdict91 92| Verdict | Condition (first match wins) |93| --- | --- |94| `BLOCKED` | No tactic described and no page list after asking |95| `FAIL` | 1 or more critical findings |96| `PASS WITH NOTES` | Warnings or suggestions only |97| `PASS` | No findings |98 99No named stops: the reader decides what to remove. A request to carry out a critical tactic is declined in the output, not paused.100 101## Learn102 103Append a learning to the profile when:104 105- the reader decides on a flagged tactic (a `fact`: what was decided, so the next run doesn't relitigate it);106- a drop or a recovery is measured after a change (a `fact` with dates and the source);107- the reader marks a template group as valuable after review (a `proposal` to exempt that page type, applied once accepted).108 109Example: `- 2026-10-24 | ai-search-risk | fact | 14 self-ranking "best" pages set to noindex and replaced with 1 fair comparison page | Why: FAIL on 2026-10-24; reader approved | Status: noted`110 111## Output112 113```114Verdict: <PASS | PASS WITH NOTES | FAIL | BLOCKED> · Coverage: <complete | partial (what's missing)> · Scan: <script | by eye>115Counts: <n> critical, <n> warnings, <n> suggestions · Pages scanned: <n>116 117| Tactic or pages | Severity | Meets | Evidence | Safer move |118(critical first)119 120Declined: <any part of the request the skill won't carry out, and why>121Fix order (live tactics): <list>122Manual action known: <yes, no, or not checked>123Learnings applied: <list, or none>124```125 126Then the handoff block.127 128## Hand off129 130```handoff131skill: ai-search-risk132version: 1.0.0133verdict: FAIL134coverage: partial (no page text, so near duplicates not checked)135for: <site or proposal>136outputs:137 critical: 2138 warnings: 1139 self_ranking_pages: 14140 declined: [undisclosed paid placement]141next: [cited-pages, refresh-audit]142open: [decide noindex or rewrite for the 14 list pages]143```144 145## Failure modes146 147| Problem | Do this |148| --- | --- |149| The reader cites an agency that says a tactic "works" | Judge the tactic, not the claim; a short-term lift is how most of these patterns start |150| A comparison page names competitors | Fine when fair, sourced and disclosed, and the profile's mention policy allows it; check claims with `claim-check` |151| Programmatic pages carry real data per page (pricing by plan, integrations by tool) | Not scaled abuse; a suggestion at most |152| Traffic dropped and the reader wants the cause | Check for a manual action first; then compare the drop date with the tactic's launch and Google's update dates; say plainly that correlation is not proof |153| The reader asks for the hidden text "just for AI crawlers" | Decline; it meets hidden text and cloaking policies whatever the audience |154 155## Influenced by156 157- Google's spam policies for web search, including scaled content abuse, site reputation abuse, cloaking, hidden text and link spam, and its note that attempts to manipulate generative AI responses count: https://developers.google.com/search/docs/essentials/spam-policies158- Google's guide to its generative AI features, which calls inauthentic mentions less helpful than they seem and says no special files, markup or rewriting are needed: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide159- Lily Ray's study of self-promotional "best" lists in B2B AI Overviews, which found most were cited without the publishing brand being recommended, and tracked sites that leaned on them losing visibility: https://lilyraynyc.substack.com/p/why-calling-yourself-the-best-could