← ClaudeAtlas

apify-search-console-ai-overviewlisted

Build a prioritized page rewrite queue from your Google Search Console data with the Apify AI Overview Rewrite Queue Actor (johnvc/ai-overview-rewrite-queue). It joins your Search Console query positions and CTR against the live Google AI Overview citation state, then returns a tiered queue that puts the highest-leverage rewrites first, the pages where a competitor is cited in the AI Overview while you rank 5 to 20. Use when the user asks about google search console ai overview, search console ai overview, which pages to rewrite for AI Overviews, or wants to turn a Search Console export into an action list. Pass target_domains plus a Search Console CSV, inline rows, or a query list. Pay per scored query, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-search-console-ai-overview · ★ 0 · AI & Automation · score 66
Install: claude install-skill johnisanerd/claude-skill-search-console-ai-overview
# Search Console AI Overview: A Prioritized Rewrite Queue Build a prioritized rewrite queue from your Google Search Console data. This Actor joins each query's Search Console position and CTR against the live AI Overview citation state, then returns a tiered queue so you rewrite the highest-leverage pages first: the ones where a competitor is cited in the AI Overview while you still rank 5 to 20. ## When to use this skill - The user wants to know which pages to rewrite because of Google AI Overviews, starting from their own Search Console data. - They ask about "google search console ai overview" or "search console ai overview" and want an action list, not a dashboard. - They have a Search Console Queries export (CSV) and a domain, and want it turned into a ranked to-do queue. - They want the join that nothing else does: Search Console rank and CTR on one side, live AI Overview citation state on the other. Not for: a plain yes or no citation check across a fixed watchlist (use the google-ai-overview-monitoring skill), organic rank tracking on its own, or content rewriting itself (this tells you which pages to rewrite, not what to write). ## What you get (one row per query) Queue and identity: `result_type` (labels the record), `query`, `query_normalized`, `tier` (A to D, or X), `tier_reason` (why it landed there), `join_status` (whether the query matched a Search Console row). Search Console metrics carried through the join: `clicks`, `impressions`, `ctr`, `position`.