What is Cloudflare Custom Hostname Verification?
Cloudflare Custom Hostname Verification is an SEO crawler. You can set up Agent Analytics to see when Cloudflare Custom Hostname Verification visits your website.
Category
| Example User Agent | Cloudflare Custom Hostname Verification |
| Triggered By | Customer-configured crawl |
| Used for AI Model Training | Not expected |
| Affects AI Chat & Search Visibility | Not directly |
| Expected To Follow Robots.txt | Yes |
Why Is Cloudflare Custom Hostname Verification Visiting My Website?
Your domain appears in the ranking, backlink, or competitor data maintained by Cloudflare Custom Hostname Verification's operator. A customer may be tracking your site, one of your competitors, or a backlink that connects another site to yours.
Should I Block Cloudflare Custom Hostname Verification?
Consider blocking Cloudflare Custom Hostname Verification only if you do not want your pages included in SEO databases. It does not influence how search engines rank you, and blocking it will not hide backlinks to your site because those are discovered on the linking sites. For context, 7% of the top websites we track currently have robots.txt rules for Cloudflare Custom Hostname Verification.
How Do I Block Cloudflare Custom Hostname Verification Using Robots.txt?
Add this rule to your robots.txt file to block Cloudflare Custom Hostname Verification from accessing your website, or use Automatic Robots.txt to block all SEO crawlers at once. You can customize which pages are blocked by swapping out / for a different path.
User-agent: Cloudflare Custom Hostname Verification # https://knownagents.com/agents/cloudflare-custom-hostname-verification
Disallow: /
Insights for Cloudflare Custom Hostname Verification
As of October 31, 2026, this data reflects agent visits measured across thousands of websites using Agent Analytics, combined with daily scans of the top 1000 websites and their robots.txt files.
Robots.txt Compliance
Country of Origin
Robots.txt Blocked Percentage
Robots.txt Blocking Trend
7% of top websites block Cloudflare Custom Hostname Verification in their robots.txts.
Cloudflare Custom Hostname Verification Traffic
0.0038% of all website traffic is coming from Cloudflare Custom Hostname Verification.
Frequently Asked Questions
What Traffic Patterns Should I Expect From Cloudflare Custom Hostname Verification?
Cloudflare Custom Hostname Verification usually performs comprehensive, link-following crawls rather than spot checks. Visit frequency may rise while a customer actively monitors your site or a related market.
Does Cloudflare Custom Hostname Verification Follow Robots.txt Rules?
Cloudflare Custom Hostname Verification is expected to follow robots.txt rules, so a disallow rule is the appropriate first step if you want to block it. Automatic Robots.txt can add and maintain that rule, while Agent Analytics lets you verify whether Cloudflare Custom Hostname Verification respects it.
Is Cloudflare Custom Hostname Verification Used for AI Model Training?
Not ordinarily. Cloudflare Custom Hostname Verification is not categorized as an AI training scraper or data provider, so AI model training is not its expected purpose.
Does Blocking Cloudflare Custom Hostname Verification Affect AI Search or Citations?
Not directly. Cloudflare Custom Hostname Verification's expected purpose is not to supply an AI search index or retrieve pages for AI-generated answers.
Does Cloudflare Custom Hostname Verification Access Private Content?
No. Cloudflare Custom Hostname Verification can reach only public pages, and authentication prevents it from accessing private content.
How Can I Verify a Request From Cloudflare Custom Hostname Verification?
Agent Analytics tracks Cloudflare Custom Hostname Verification visits in real time. You can also check your server logs for requests whose user-agent string contains "Cloudflare Custom Hostname Verification". Look for comprehensive site crawls that follow internal links. Because Cloudflare Custom Hostname Verification does not publish a verification method, any client can claim its identity and a log match is only a clue.