Apify AI Overview Rewrite Queue API — Data skill for Claude Code

🔎 AI Overview Rewrite Queue API: ai overview tracking that ranks which pages to rewrite first

Join your Google Search Console export to live AI Overview citation data and get back a scored, tiered rewrite queue: the pages losing clicks to Google's AI, highest-leverage first, each with a plain reason.

**Actor page:** [apify.com/johnvc/ai-overview-rewrite-queue](https://apify.com/johnvc/ai-overview-rewrite-queue?fpr=9n7kx3) **Input schema:** [apify.com/johnvc/ai-overview-rewrite-queue/input-schema](https://apify.com/johnvc/ai-overview-rewrite-queue/input-schema?fpr=9n7kx3)

The AI Overview Rewrite Queue API turns ai overview tracking into a work list. Give it the domains you own and a Search Console Queries export, and it returns one structured JSON row per query. Each row joins your Search Console fields (clicks, impressions, ctr, position) to live AI Overview citation fields (whether an AI Overview appeared, who it cited, whether any of your pages made the reference list), then scores the query into a tier from A to X with a one-sentence reason. It is a practical AI visibility instrument: instead of a raw citation tracking dump, you get a ranked queue that tells you where a rewrite will move the needle.

Video Walkthrough

[](https://www.youtube.com/watch?v=jREWahDGhJM)

Text walkthrough

This repo teaches ai overview tracking with the AI Overview Rewrite Queue API on Apify. The main input is your `target_domains` plus a Google Search Console Queries export, passed either as a published CSV URL (`search_console_csv_url`) or as pasted rows (`search_console_rows`); you can add extra `queries` to check on top of the export. For every query it returns a `tier` (A through X) and a `tier_reason`, next to the joined citation fields: `citation_state`, `ai_overview_present`, `reference_domains`, `cited_urls`, and `join_status`. The highest-value use case is Tier A: queries where y