claude-code-config

Find keyword cannibalization in Google Search Console data — multiple URLs from the same site competing for the same queries. Use when the user says "find cannibalization", "are my pages competing", "which pages overlap", "keyword cannibalization audit", "why do my rankings keep flip-flopping", or pastes/uploads a GSC query+page export and asks which URLs fight each other. Works standalone from a GSC CSV; no external API required.

Detect content decay — pages that have lost organic traffic versus a past peak. Use when the user says "find decaying pages", "what traffic did I lose", "content decay audit", "why is traffic dropping", "which posts are declining", or pastes two GSC exports (current vs. an earlier/peak period) and asks what slipped. Works standalone from two GSC CSVs.

Audit whether the queries a page ranks for actually match what the page is about. Use when the user says "intent mismatch", "audit search intent", "why is this page not converting", "are my pages matching what people search", "wrong queries ranking", or pastes GSC query+page data plus a page title/URL and asks if they line up. Works standalone from a GSC CSV plus page titles the user provides.

Find internal-linking opportunities to push authority from a strong "donor" page to a weaker "target" page. Use when the user says "internal links to boost a page", "reallocate link equity", "which pages should link to X", "help page B rank by linking from A", "internal link audit for a target page", or names a donor and target page with GSC data. Works standalone from GSC exports the user provides.

Cluster a large GSC query list into topics and search intents, then map each cluster to a page or flag it as a content gap. Use when the user says "cluster my keywords", "group these queries", "topic clusters from GSC", "organize my search queries", "what content gaps do I have", "keyword grouping", or pastes a big query export. Works standalone from a GSC CSV.

Detect sudden ranking or traffic anomalies in GSC time-series data — big position swings or click spikes/drops worth investigating now. Use when the user says "any ranking anomalies", "did anything spike or crash", "alert me to big changes", "what moved suddenly", "ranking volatility check", or pastes GSC data with a date dimension covering 30+ days. Uses DataForSEO to correlate with SERP/algorithm context when available; works standalone from a GSC CSV.

Map a competitor's ranking content for a topic and find the gaps you can exploit. Use when the user says "spy on a competitor", "what content does competitor X rank for", "competitor content gap analysis", "what's competitor.com ranking for in topic Y", "map their SERP coverage", or names a competitor domain plus a topic. Uses DataForSEO when available for live SERP/ranked-keyword data; otherwise works from SERP results the user pastes.

Find "striking distance" keywords — queries ranking on page 2 (positions 11–20) that are one push away from page-1 traffic. Use when the user says "striking distance keywords", "page 2 keywords", "quick SEO wins", "low-hanging fruit", "what's almost ranking", "where's my fastest traffic upside", or pastes a GSC query export and asks what to optimize next. Works standalone from a GSC CSV.

Diagnose and rewrite weak title tags using GSC data — find titles with poor keyword inclusion, low CTR for their position, or intent mismatch, and generate better options. Use when the user says "fix my title tags", "improve my titles", "why is my CTR low", "rewrite page titles", "title tag audit", "low click-through rate", or provides URLs + current titles + their top queries. Works standalone from a GSC CSV plus the titles the user supplies.

Generate a client-ready weekly SEO report from week-over-week GSC data. Use when the user says "write my weekly SEO report", "weekly GSC report", "client SEO update", "WoW performance summary", "what changed this week", or pastes current + prior week Search Console exports. Works standalone from two GSC CSVs.