What is Cloudflare Custom Hostname Verification?

Cloudflare Custom Hostname Verification is an SEO crawler. Agent Analytics can track when it visits your website.

Category

SEO Crawler
Analyzes website structure and content to identify SEO improvement opportunities

Expected Behavior

Cloudflare Custom Hostname Verification maps sites the way its customers' SEO tools need, following internal links to build a full picture of structure, content, and ranking signals. Expect thorough crawls rather than spot checks, with frequency rising when your site or your competitors are actively monitored in its tools.

Overview

Expected To Follow Robots.txt Yes
Insights Last Updated July 6, 2026

Robots.txt Blocked Percentage

0%
0% of top websites are blocking Cloudflare Custom Hostname Verification
Learn How →

Country of Origin

United States
Cloudflare Custom Hostname Verification normally visits From the United States

Robots.txt Blocking Trend

As of July 6, 2026, 0% of top websites block Cloudflare Custom Hostname Verification in their robots.txt files.

Overall SEO Crawler Traffic

As of July 6, 2026, 2.4% of all web traffic came from SEO crawlers.

Track SEO Crawlers Visiting Your Website
Use Agent Analytics to get realtime visibility into visits from every crawler, scraper, and AI agent.

This data reflects agent visits measured across thousands of websites using Agent Analytics, combined with daily scans of the world's top 1000 websites and their robots.txt files.

Cloudflare Custom Hostname Verification's User Agent

User Agent Cloudflare Custom Hostname Verification

Access other known user agents and IP addresses using the Enterprise API.

How To Block Cloudflare Custom Hostname Verification

Add this rule to your robots.txt file to block Cloudflare Custom Hostname Verification from accessing your entire website. 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: /
Block Every SEO Crawler
⚠️ Manually adding individual robots.txt rules is not scalable. Instead, use Automatic Robots.txt.

Frequently Asked Questions

Should I Block Cloudflare Custom Hostname Verification?

Only if you want your own pages and outbound links out of those tools. Cloudflare Custom Hostname Verification collects the ranking and backlink data behind SEO tools, likely including ones you or your agency use, and it does not change how search engines rank you. Blocking it will not hide your backlink profile either, because backlinks are discovered on the sites that link to you. Almost none of the top websites we track have robots.txt rules for Cloudflare Custom Hostname Verification right now.

Does Cloudflare Custom Hostname Verification Respect Robots.txt?

Yes. Cloudflare Custom Hostname Verification is expected to honor robots.txt rules, so a disallow rule is the right first move. Automatic Robots.txt adds and maintains that rule for you, and Agent Analytics confirms Cloudflare Custom Hostname Verification actually honors it.

Does Cloudflare Custom Hostname Verification Access Private Content?

Login walls stop it. Cloudflare Custom Hostname Verification analyzes public pages for rankings, links, and site structure.

Why Is Cloudflare Custom Hostname Verification Visiting My Website?

Your domain shows up in the ranking, backlink, and competitor data Cloudflare Custom Hostname Verification's operator sells. If anyone tracks your site or your competitors in an SEO tool, Cloudflare Custom Hostname Verification visits you.

How Can I Tell if Cloudflare Custom Hostname Verification Is Visiting My Website?

Agent Analytics tracks Cloudflare Custom Hostname Verification visits in real time alongside every other known AI agent, crawler, and scraper. You can also check your server logs for requests whose user agent string contains "Cloudflare Custom Hostname Verification". Look for full site crawls that follow your internal links. Keep in mind that Cloudflare Custom Hostname Verification doesn't publish a verification method, so any client can claim its user agent string and a log match is a hint rather than proof.