Off-topic, but I'm having a terrible experience with Cloudflare and would love to know if someone could offer some help. All of a sudden, about 1/3 of all traffic to our website is being routed via EWR (New York) - me included -, even tough all our users and our origin servers are in Brazil. We pay for the Pro plan but support has been of no help: after 20 days of 'debugging' and asking for MTRs and traceroutes, they…
Do you think cloudflare is responsible for all of the network traffic routing in the entire world and can simply fix any problem even if it's on somebody else's network?
Cloudflare crawl endpoint
141–150 of 194 posts
Re: Cloudflare crawl endpoint
#142Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.
Re: Cloudflare crawl endpoint
#143Could they collaborate with the website's creators that have websites behind cloudfare to allow their content to be accessed via an API in exchange of a compensation?. This could be a way to compensate creators and AI companies be able to access content that's unreachable as it's protected by cloudfare
Sort of though. Still private beta since July 2025.
Re: Cloudflare crawl endpoint
#144The idea of exposing a structured crawl endpoint feels like a natural evolution of robots.txt and sitemaps. If more sites provided explicit machine-readable entry points for crawlers, indexing could become a lot less wasteful. Right now crawlers spend a lot of effort rediscovering the same structure over and over. It also raises interesting questions about whether sites will eventually provide different views for hum…
Re: Cloudflare crawl endpoint
#145Re: Cloudflare crawl endpoint
#146Re: Cloudflare crawl endpoint
#147Is cloudflare becoming a mob outfit? Because they are selling scraping countermeasures but are now selling scraping too. And they can pull it off because of their reach over the internet with the free DNS.
I think the simple explanation is that they weren't selling scraping countermeasures, they were selling web-based denial of service protection (which may be caused by scrapers).
Re: Cloudflare crawl endpoint
#148Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.
Re: Cloudflare crawl endpoint
#149Earlier quoted context omitted.
So what’s the user agent for their bot? They don’t seem to specify the default in the docs and it looks like it’s user configurable. So yet another opt out bot which you need your web server to match on special behaviour to block
>So yet another opt out bot which you need your web server to match on special behaviour to block Given that malicious bots are allegedly spoofing real user agents, "another user agent you have to add to your list" seems like the least of your problems.
If I need to treat cloudflare bots the same as malicious bots, that undermines their claim.
Re: Cloudflare crawl endpoint
#150Doesn't work for pages protected by cloudflare in my experience. What a shame, they could've produced the problem and sold the solution.
Came here to write this. I am getting much better results from Firecrawl (not affiliated with them, just a happy customer).