Refbacks
Identify referring websites through information attached to incoming HTTP requests.
Guide · Backlinks
A refback allows a website to discover that another site has linked to its content by examining where incoming visitors came from. It's an older method of tracking incoming links, but the technology behind it still plays a role in how websites understand referral traffic.
A refback is a linkback a website records when a visitor arrives by clicking a link on another site. The visitor's browser may send the referring address in the HTTP Referer header; the receiving site logs it and, ideally, checks that the source page really links to it.
Refbacks only see links that people click, and modern browsers often share just the referring domain rather than the exact page.
Unlike systems that notify a website when someone publishes a link, a refback generally depends on someone actually following that link. The receiving website examines information attached to the visitor's request and may use it to identify the referring page.
Refbacks were particularly useful during the early development of blogging, when authors wanted to know who was referencing their posts. Today, browser privacy protections and more sophisticated analytics tools have changed how that information is collected.
Understanding refbacks helps explain both the history of linkbacks and an important limitation of modern website referrals: a website can send visitors to your content without revealing exactly which page those visitors came from.
A refback is a type of linkback that uses HTTP referrer information to help a website identify external pages directing visitors to it.
A linkback, more broadly, is a mechanism for identifying or communicating references between websites. In blogging systems, linkbacks could also appear alongside articles, allowing readers to discover related discussions published elsewhere.
Refbacks belong to a group of four commonly identified linkback mechanisms, set out below. This four-part classification is supported by the W3C Webmention specification, which explicitly identifies Refback, Trackback, and Pingback as related linkback mechanisms. However, the terminology developed over time. Earlier literature commonly discussed three principal mechanisms because Webmention had not yet been standardized.
The distinction matters because these systems identify references in different ways. A refback can reveal a referring website through a visitor's activity, whereas the other mechanisms use direct notifications between websites.
Linkback types
Identify referring websites through information attached to incoming HTTP requests.
Send notifications from one publishing system to another, traditionally including information about the referring post.
Use automated notifications to inform a receiving website that another page links to it.
Use a standardized notification protocol through which websites can report references and verify their existence.
Refbacks rely on a feature of HTTP known as the Referer header. Despite its unusual spelling, Referer is the official name of the header used to communicate where a request originated.
When you follow a hyperlink, your browser requests the destination page from its web server. Depending on the browser's settings and the referring website's policies, that request may include information about the page you were previously visiting.
How a refback is recorded
The process works as follows.
Website A publishes an article containing a hyperlink to Website B.
A visitor follows that hyperlink.
The visitor's browser requests the linked page on Website B, potentially including a Referer header.
Website B examines the request and records the available referring URL.
If Website B uses a refback implementation, it may investigate the referring page and register the reference.
How do refbacks work?
Consider a visitor following a link from https://site-a.com/article to https://site-b.com/guide.
If the browser transmits the full referring URL, Website B might receive:
Website B now has a potential source URL that it can investigate.
The important limitation is that the link must generally be followed before a refback can discover it. Website A could publish a link that remains unnoticed indefinitely if nobody clicks it.
Referrer information also does not establish that a genuine hyperlink exists. A more careful refback implementation can retrieve the reported source page and check whether it links to the destination.
The HTTP behavior underlying this process is documented in RFC 9110, Section 10.1.3, which describes referrer information as useful for logging, analytics, and generating links back to referring resources.
How do refbacks work?
Even when a browser sends referrer information, the receiving website may only learn the referring domain.
Under the common strict-origin-when-cross-origin policy, a browser navigating between different HTTPS websites normally sends the origin, such as https://site-a.com/, rather than the full article URL.
Website B can therefore recognize that traffic came from Website A without knowing which article contained the link.
Mozilla's Referrer-Policy documentation explains how these restrictions work and why the amount of information available depends on the applicable policy.
Side by side
Although all four mechanisms help connect references across websites, they differ in how notifications are produced and whether a link is checked.
How it works: uses referrer information from incoming requests.
Verification: optional source-page inspection.
How it works: sends an HTTP notification to a designated endpoint.
Verification: not required by the original protocol.
How it works: sends an XML-RPC notification.
Verification: the receiving server checks the source for a link.
How it works: sends source and target URLs to a receiving endpoint.
Verification: source verification is required before use.
Refbacks vs. other linkbacks
Trackbacks emerged alongside blogging platforms such as Movable Type. The system allowed authors to send a notification to another blog when publishing a related post, without requiring someone to visit through the link first.
The original TrackBack specification describes how receiving endpoints accept these notifications.
Pingbacks automated more of the process. Rather than requiring authors to manage trackback notifications, compatible publishing systems could discover the receiving endpoint and send an XML-RPC request.
The Pingback 1.0 specification, edited by Stuart Langridge and Ian Hickson, also includes a mechanism for checking whether the claimed referring page contains a link to the target.
Refbacks vs. other linkbacks
Webmention offers a newer, standardized approach to linkback notifications.
A sending website identifies the receiving website's Webmention endpoint and submits the source and target URLs. When the receiving system intends to use the notification, the specification requires it to retrieve the source and verify the reference.
Unlike a conventional refback, the notification does not depend on a visitor following the link. Webmention also supports interactions beyond ordinary article references.
The W3C Webmention Recommendation establishes these requirements and provides the clearest formal distinction between Webmention and earlier linkback methods.
Refbacks can help website owners identify external references, making them useful for understanding how content circulates online. They also overlap with several activities associated with search engine optimization (SEO), particularly backlink monitoring and referral traffic analysis.
A backlink is a hyperlink from another website pointing to yours. Refbacks may reveal some of these links when visitors follow them, but they cannot provide a complete backlink inventory.
A page might link to your content without sending any visitors. Search engine crawlers may still discover that link, while a refback system remains unaware of it.
For more systematic backlink monitoring, tools such as Google Search Console's Links report identify external linking websites and pages. Google notes that its report provides a sample rather than an exhaustive record.
Refbacks can also help explain where website referrals originate. A referring article may introduce your content to an audience you would otherwise struggle to reach, even if the link produces relatively little traffic.
However, refbacks themselves do not directly improve search rankings. They collect information about references rather than creating ranking signals. Google's search documentation distinguishes legitimate links from artificial linking practices intended to manipulate rankings.
Refbacks and SEO
Modern analytics platforms perform some of the same observation that made refbacks useful, although their purposes are different.
Google Analytics, for example, categorizes visits using traffic-source information, including referring websites and acquisition channels. Its Traffic acquisition report helps website owners understand where visitors originate.
Traditional refback implementations were concerned with identifying incoming references and sometimes displaying them alongside published content. Modern referral analytics generally focuses on visits and user activity.
Both can use referrer information, but a referral reported in analytics does not automatically confirm that a publicly accessible backlink exists.
Limitations
Refbacks are constrained by the information browsers provide and the trustworthiness of incoming requests.
Browsers may omit referrer information entirely. This can happen when a website applies a restrictive referrer policy, when navigation moves from HTTPS to HTTP, or when privacy tools interfere with referral tracking.
A missing referrer therefore does not necessarily mean someone entered your URL directly.
Modern browsers limit the information shared between websites to reduce unnecessary disclosure of browsing activity.
With the default strict-origin-when-cross-origin policy, the receiving website usually learns the referring domain rather than the exact source page. That significantly reduces the usefulness of traditional refbacks for discovering individual articles.
Referrer headers are not proof of genuine user activity. Automated clients can generate requests containing misleading or fabricated referring URLs.
Referrer spam exploits this weakness to introduce unwanted domains into logs, analytics reports, or publicly displayed linkback records. A refback implementation that publishes unverified references risks promoting pages that never linked to its content. Verifying the source URL can reduce this problem, although it cannot eliminate automated traffic or other forms of manipulation.
Refbacks belong to the history of blogging systems that attempted to connect conversations published across independent websites.
Trackbacks were introduced with Movable Type in August 2002, and related mechanisms subsequently provided different ways for authors to discover references to their work. Refbacks offered a comparatively passive approach because they could operate using information already present in HTTP requests.
They have not disappeared completely. In December 2020, developer David Shanske documented an updated WordPress refback plugin that checked referring pages for actual links before creating refback comments.
Nevertheless, modern referrer policies make complete source-page identification increasingly unreliable.
For most website owners, referral analytics and backlink monitoring provide more practical ways to understand incoming traffic and external links. Webmentions remain an option for websites that want explicit, verifiable notifications between publishing systems.
Refbacks still illustrate an important principle: the links pointing to a website and the visitors arriving through those links are related, but they are different things to measure. Knowing that distinction makes incoming-link data much easier to interpret.
The points to remember from this guide.
A refback is a way for a website to learn that another site linked to it. When someone clicks the link, their browser may tell the receiving site which page they came from, in the HTTP Referer header. The site records that address and may check that the page really contains the link.
A refback is passive: it only appears when a visitor follows the link. A pingback is sent by the linking site's publishing system as an XML-RPC notification when the post is published, and the receiving server checks that the source page contains a link to it. No visitor is needed.
No. Refbacks collect information about references; they do not create ranking signals. The links themselves are what search engines may take into account, and Google's spam policies separate legitimate links from artificial linking intended to manipulate rankings. A refback is useful for seeing who sends you visitors, not for moving a ranking.
Most browsers use the strict-origin-when-cross-origin referrer policy by default. Between two HTTPS websites, that sends only the origin, such as https://site-a.com/, not the full article address. You can see which website sent the visit, but not which page held the link.
Referrer spam is automated traffic carrying fake referring addresses, sent to put unwanted domains into your logs, analytics reports or public linkback lists. Referrer headers are not proof of a real visit, so a refback system should fetch the source page and confirm the link before recording or showing it.
Google Search Console's Links report lists external websites and pages that link to you, though Google notes it is a sample. Google Analytics' Traffic acquisition report shows where visits come from. Webmentions suit websites that want verified notifications between publishing systems.
Yes. Link building is part of our SEO services in Edinburgh: we earn links from relevant, respected websites through useful content, local partnerships and directories, and watch new links and referral visits in Google Search Console and analytics. Tell us about your website and we will say where we would start.
The following sources support the definitions, specifications and browser behaviour described in this guide.
Send us your website and tell us what you sell. We will tell you what is holding it back in Google and what to fix first.