---
language: en
title: "Crawl-to-referral ratio"
description: "The ratio of crawler requests to referral requests for a platform, calculated using the same data set, period and log criteria."
canonical: "https://tropk.ai/en/resources/glossary/crawl-to-referral-ratio"
last_modified: "2026-10-12T16:12:03.628Z"
---

# Crawl-to-referral ratio

Reviewed on 2026-10-06.

## What it means

The crawl-to-referral ratio compares [crawler](/en/resources/glossary/crawler) requests with access requests originating from a platform over the same period. In the methodology published by Cloudflare Radar, it divides [HTML](/en/resources/glossary/html-the-web-s-markup-language) content requests from agents associated with the platform by HTML requests with the platform’s hostname in the Referer header. The unit is crawler requests per identified referral request.

## Why it matters for marketing

For content publishers, the ratio helps examine the relationship between automated access to their content and traffic returning to their site. It can [prompt](/en/resources/glossary/prompt) a discussion about access policies, with support from the technical team. Looking only at the final number is not enough: a higher ratio may result from more [crawling](/en/resources/glossary/crawling), fewer referrals or changes in how requests are identified.

## Example in practice

Suppose a magazine’s CDN logs record, over seven days, 6,000 HTML requests from a platform’s agents and 30 HTML requests with that platform’s Referer. The local ratio is 200 to 1. The team includes both totals in its report and investigates the most-requested paths before discussing changes to access permissions.

## How to apply or verify

Define the host, time window, log source, agents and included hostnames. Check the content type, filters and coverage before dividing the totals. Compare periods using the same protocol and report the numerator and denominator alongside the ratio. If no referrals are identified, report a zero denominator; do not turn an undefined division into zero or an arbitrary number.

## Important distinctions

Requests are not unique visitors or sessions. Applications that omit Referer may leave referrals out of the count and increase the observed ratio. A bot request does not prove a [citation](/en/resources/glossary/ai-citation), actual training or a lost sale. The ratio also does not link each automated access to a later click. The Radar result describes its observed data set and does not automatically represent any Brazilian website.

## Sources and references

- [The crawl before the fall… of referrals: understanding AI’s impact on content providers](<https://blog.cloudflare.com/ai-search-crawl-refer-ratio-on-radar/>) — Cloudflare

## Continue a leitura

- [Crawling](</en/resources/glossary/crawling>)
- [Referrer](</en/resources/glossary/referrer>)
- [AI referral traffic](</en/resources/glossary/ai-referral-traffic>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)