CloudFlare AMP Fetcher
CloudFlare AMP Fetcher is a single-page fetcher operated by Cloudflare. It fetches one page (or a small set) when triggered by a user action, typically a link being shared on social media, a messaging app, or an RSS reader.
Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but CloudFlare AMP Fetcher will not crawl the rest of your site.
Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.
See CloudFlare AMP Fetcher on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Per user action
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Cloudflare runs 35 bots in total. Each one is a separate user-agent so you can allow or block them independently.
DevOps & Monitoring
10SEO Crawler
6CDN Infrastructure
5Training Crawler
4Security Scanner
3AI Search Index
2Link Unfurler
2- Collapsify
- CloudFlare AMP FetcherYou are here
Generic Crawler
2Task Automation
1Should I let CloudFlare AMP Fetcher through?
In most cases, yes. Fetchers power link previews and feed readers. Blocking breaks the user experience on social and messaging platforms. If volume gets noisy, rate-limit it before you block it outright.
Does blocking CloudFlare AMP Fetcher affect my Google rankings?
No. CloudFlare AMP Fetcher is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from CloudFlare AMP Fetcher?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be CloudFlare AMP Fetcher", not "the traffic is genuinely CloudFlare AMP Fetcher". If you need stronger guarantees, look for a reverse-DNS check or wait for Cloudflare to publish IP ranges.
What breaks if I block CloudFlare AMP Fetcher?
Link previews, embeds, and unfurls on whatever surface CloudFlare AMP Fetcher feeds will stop rendering. Users sharing your URLs into Cloudflare will see a bare link instead of a rich card. Usually that's the first thing people regret blocking.
How is CloudFlare AMP Fetcher different from Cloudflare's other bots?
Cloudflare splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Cloudflare family above to see which ones actually matter for your site.
What's the cleanest way to control CloudFlare AMP Fetcher?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.