SourceCited / Trends, SERP APIs & GSC
Tooling · Data sources
Autocomplete tells you the questions; Google Trends shows the trajectory; paid SERP APIs reveal who AI actually cites; Search Console is your free ground truth. Here's how to use each.
Complete the demand toolkit: Google Trends (via pytrends — but it was archived in April 2025, so treat it as a one-off check, not a pipeline) shows whether demand is rising; paid SERP APIs (DataForSEO ~$0.60/1K up to SerpApi's premium) return AI Overview text and reference links so you can track citations at scale; and free Search Console is your ground truth. Start free, pay only for scale.
Autocomplete harvesting tells you what people ask. Two other programmatic sources complete the picture: Google Trends tells you whether that demand is rising or fading, and paid SERP APIs let you see, at scale, who actually gets cited — including inside AI Overviews, which no free rank tracker shows. Together with your own Search Console data, these are the inputs that turn a guess into a dataset.
Autocomplete = the questions. Trends = the trajectory. SERP API = the citation reality (who Google/AI actually cite). Search Console = your own ground truth. Pull all four and you can prioritize with evidence instead of instinct.
Google Trends shows relative search interest over time, by region, plus related and rising queries — ideal for catching a topic on the way up (rising demand is where challengers win) and for killing ideas that are fading. For programmatic access people reach for pytrends, the long-standing unofficial Python wrapper — but be clear-eyed about its state in 2026:
| Option | State in 2026 | Use it when |
|---|---|---|
| pytrends (original) | Archived April 2025, read-only, unmaintained; still installs and runs for light use but hits 429 rate limits and breaks unpatched when Google changes endpoints | A quick, personal, low-volume check — never a production dependency |
| pytrends-modern (community fork) | Adds retries and async; still an unofficial wrapper with the same rate-limit ceiling | You want the Python approach and can tolerate breakage |
| Official Google Trends API | In limited alpha | You have access and want the sanctioned path |
| Managed Trends API (via a SERP-API vendor) | Paid, handles proxies/rate limits, returns clean JSON | Production, scheduled, or high-volume trend pulls |
Building a pipeline on archived pytrends. It works until Google shifts an endpoint, then silently returns nothing with no fix coming. Fine for an afternoon of validation; a liability as a cron job. For anything scheduled, budget for a managed API or the alpha official one.
I'm deciding whether to build content on: [topic/keywords]. Using Google Trends thinking: 1. Tell me what to check — interest over time (rising/flat/declining), seasonality, and the related + rising queries that signal where demand is heading. 2. Give me a minimal pytrends snippet to pull interest_over_time and related_queries for my keywords, WITH polite rate-limiting — and note that pytrends is archived/unmaintained so I should treat it as a one-off check, not a production dependency. 3. Tell me how to read the result: what pattern means 'build now', 'skip', or 'seasonal — time it'.
Here is the gap paid SERP APIs fill: free rank trackers show the ten blue links, not what an AI Overview pulled or who it cited. A SERP API returns the parsed search page — organic positions, People Also Ask, featured snippets, and (on the vendors that support it) the AI Overview text and its reference links — as structured JSON you can query on a schedule. That is how you measure, programmatically, whether your money queries trigger an Overview and whether you are among the cited sources.
The market splits on price and on AI-surface support. Verify current pricing yourself — it moves — but the 2026 shape is:
| Vendor | Rough 2026 price / 1K | Notes |
|---|---|---|
| DataForSEO | ~$0.60 (queued) to ~$2.00 (live) | Cheapest at scale, true pay-as-you-go, broadest endpoints (SERP + keywords + backlinks); async queue has a learning curve; AIO can carry a surcharge |
| Serper.dev | ~$0.30–$1.00 | Fast, Google-focused, simple |
| Bright Data | ~$1.50 PAYG, less at volume | Enterprise proxy network, sub-second, often raw HTML you parse yourself; volume commitments |
| SerpApi | ~$15–$25 (subscription tiers) | Polished SDK and docs, wide engine coverage; priciest by far — justified mainly by existing integrations |
| AIO-first vendors | varies | Some newer APIs treat AI Overview parsing and multi-engine (ChatGPT/Perplexity/Gemini) coverage as core, not an add-on — worth it if AI surfaces are the point |
SERP APIs retrieve publicly accessible results; established commercial uses are rank tracking, SEO research, AI grounding, and competitive analysis. The risk is in use — don't resell raw SERP data at scale or breach a platform's terms. This is general information, not legal advice.
I have access to a SERP API that returns organic results plus AI Overview data (text and reference links). Help me design a small rank-and-citation tracker: 1. From my fixed query set (I'll paste it), the schedule and parameters to pull each query (location, device, and the AI-Overview flag) without over-spending. 2. For each result, what to record: my organic position, whether an AI Overview appeared, whether my domain is in the AIO reference links, and which competitors/sources are cited. 3. The output schema (query | date | my_position | aio_present | i_am_cited | cited_sources) and a simple weekly diff so I can see movement and new citation-source targets. Keep it per-platform and cost-aware.
Before paying for anything, mine the data you already own. Google Search Console (and its API) gives you the real queries you rank for, your positions, impressions and clicks — the honest baseline the paid tools only estimate. It is also where the AI Overview battleground lives: filter to queries where you rank 4–15, and those are the ones worth checking for an Overview and answer-shaping first. Bing Webmaster Tools does the same for the Bing-fed engines (Perplexity, Copilot) and is where you submit via IndexNow.
| Budget | Stack |
|---|---|
| Free | Autocomplete harvest + Search Console/Bing Webmaster + manual spot-checks of AI answers. Enough to start and to build your first dataset. |
| Low | Add pay-as-you-go SERP calls (DataForSEO/Serper) for scheduled AI-Overview citation tracking on your priority queries only. |
| Scaling | Add a managed Trends API for trajectory, widen the SERP query set, and pipe it all into the measurement scoreboard from Phase 4. |
The through-line: start with free harvesting and your own Search Console data, and only pay for scale once you know which queries are worth watching. Every one of these feeds the same scoreboard.
Barely, and only for light use. The original pytrends was archived in April 2025 and is unmaintained — it still installs and runs simple queries but hits rate limits (429s) and breaks unpatched when Google changes its internal endpoints. There's a community fork (pytrends-modern) with retries, and Google has an official Trends API in limited alpha, but for scheduled or high-volume work use a managed API. Never build a production pipeline on archived pytrends.
Use a paid SERP API that parses AI Overview data. Vendors like DataForSEO, Serper, Bright Data, and SerpApi return the search page as structured JSON; several expose the AI Overview text and its reference links plus a has-AI-Overview flag. Query your fixed keyword set on a schedule and record whether an Overview appeared and whether your domain is among the cited sources.
In 2026, DataForSEO is generally the lowest cost at roughly $0.60 per 1,000 SERPs on its queued tier (with true pay-as-you-go and no monthly minimum), versus SerpApi at the premium end. Serper and Bright Data sit in between. AI Overview parsing sometimes carries a surcharge, so price your real query mix, not the headline rate. Verify current pricing before committing.
They retrieve publicly accessible search results, and established commercial uses — rank tracking, SEO research, AI grounding, competitive analysis — are well accepted. The risk is in how you use the data: don't resell raw SERP data at scale or violate a platform's terms. This is general information, not legal advice — check the terms of any service you query.
No, not to start. Autocomplete harvesting plus your own Search Console and Bing Webmaster data cover the fundamentals for free and are enough to build your first citable dataset. Add pay-as-you-go SERP calls only once you know which queries are worth watching, then scale from there.