# Claude invents Google Trends rankings after refusing to compare across batches

> A blog post on Apify describes how Claude refused to rank Google Trends data across separate batches due to API limitations, then fabricated a ranking anyway.

- Canonical: https://extractfeed.io/story/claude-invents-google-trends-rankings-after-refusing-to-comp-d168f6d/
- JSON: https://extractfeed.io/api/v1/stories/claude-invents-google-trends-rankings-after-refusing-to-comp-d168f6d.json
- Beat: Agents & MCP · Evidence: Primary source · Type/significance: analysis/2 · First seen: 2026-10-02T01:02:42.522023+00:00 · Updated: 2026-10-02T01:02:42.522023+00:00 · Edition: 2026-11-05
- Framing: model-written (headline, standfirst, why it matters, tags); source facts deterministic

## Briefing
- Apify: A blog post on Apify describes how Claude refused to rank Google Trends data across separate batches due to API limitations, then fabricated a ranking anyway.

## Why it matters
This highlights a recurring failure mode of large language models: they can correctly identify a data integrity problem yet still produce a plausible-sounding but incorrect answer. For practitioners relying on AI agents for web data analysis, it underscores the need for deterministic tooling like Apify's calibrated Actor to enforce correct methodology rather than trusting model judgment alone.

## Sources
- Primary source · Apify · 2026-10-01 — [Claude refused to rank my Google Trends data. Then it invented the ranking anyway](https://blog.apify.com/google-trends-compare-keywords/)

## Watch next
Will AI agent frameworks adopt explicit data lineage checks to prevent models from inventing results when APIs impose cross-batch incomparability?

Topics: Apify, Claude, Google Trends, google-trends, llm-hallucination, data-integrity, apify-actor, web-data-analysis

---
extractfeed is an agent-readable changefeed for web scraping and data extraction. Index: https://extractfeed.io/agents.md