What is a Referrer?

A referrer is the web page that sent a visitor to your site. When someone clicks a link on another website and lands on yours, that other website is the referrer.

Your analytics tool captures this information automatically through the HTTP referrer header—a piece of data the browser sends along with the request when a visitor follows a link.

In some cases, the referrer includes the full page URL the visitor clicked from. In practice, many sites and browsers strip the referrer down to just the domain.

How Referrer Data Works

When a visitor clicks a link to your site, here's what happens behind the scenes:

1. The visitor is on a page (e.g., blog.example.com/best-tools)
2. They click a link to your site
3. Their browser sends a request to your server that includes a Referer header containing the URL they came from
4. Your analytics tool reads this header and records the referring URL

This happens automatically—you don't need to set anything up. As long as the browser sends the referrer header, your analytics tool captures it.

(Yes, "Referer" is misspelled in the HTTP specification. The typo dates back to 1996 and has been preserved for compatibility ever since. Analytics tools use the correct spelling "referrer" in their interfaces.)

Referrer vs Referring Domain

Your analytics will show referrer data at two levels:

Referring URL is the full page address that sent the visitor—for example, blog.example.com/best-tools. This tells you exactly which page linked to you. However, many sites set referrer policies that strip the path and only send the domain, so the full URL isn't always available.

Referring domain is just the website—for example, blog.example.com. This groups all referrals from the same site together, which is more useful for understanding which websites drive the most traffic overall.

Since many referrers arrive as domain-only anyway, the domain-level view is often the most reliable and actionable way to look at your referral data.

When Referrer Data Goes Missing

Referrer data isn't always available. Several situations cause the browser to omit or strip the referrer header, making the visit show up as direct traffic instead:

HTTPS to HTTP transitions. If a visitor clicks a link on an HTTPS site that leads to an HTTP site, most browsers won't send the referrer header. This is a security measure to prevent leaking information from secure pages. (This is increasingly rare as most sites now use HTTPS.)

Privacy settings and browser extensions. Privacy-focused browsers and extensions can block referrer headers entirely. Every visit from those users appears as direct traffic in your analytics.

Mobile apps and messaging platforms. When someone opens a link from Slack, WhatsApp, a text message, or many mobile apps, the referrer header is often missing. The click happened, but your analytics can't tell where it came from.

Bookmarks and typed URLs. When a visitor types your URL directly or uses a bookmark, there's no referring page—so there's no referrer header. This is genuine direct traffic.

Meta refresh redirects and some JavaScript redirects. Certain types of redirects strip the referrer header in the process.

This is why UTM parameters are valuable—they encode the source information in the URL itself, so it doesn't depend on the referrer header being present.

How to Use Referrer Data

Referrer data helps you understand where your visitors are coming from and which sources are worth investing in:

Find your best traffic sources. Sort by referring domain to see which sites send you the most visitors. Then look at what those visitors actually do—a site sending 50 highly engaged visitors is more valuable than one sending 500 who bounce immediately.

Discover unexpected mentions. New referring domains appearing in your analytics often mean someone linked to your content. These are opportunities to build relationships with sites that are already promoting your work.

Evaluate partnerships and guest posts. If you're doing content partnerships or guest posting, referrer data shows exactly how much traffic each placement drives. Compare the referring URL data against your conversion rate to see which placements actually produce results.

Identify referral spam. Some referrer data is fake—spam bots send requests with fabricated referrer headers to get their URLs to show up in your analytics. If you see referring domains you don't recognize with suspiciously high traffic and near-100% bounce rates, it's likely referral spam.