Should you really check every version of your site to audit your backlinks?

Why does Google talk about "versions" of a site?

The same domain can exist under four distinct technical variants: http://example.com, https://example.com, http://www.example.com, https://www.example.com. Each of these URLs is considered by Google as a potentially different entity until a clear canonicalization is established.

Backlinks do not always target the canonical version you have chosen. An external site may link to your old HTTP version, another may link to the www version while you have standardized on non-www. If your 301 redirections do not cover all cases, Google may treat these links as pointing to separate URLs, diluting your link juice in the process.

What happens if I only check one version?

Search Console displays backlinks for each property separately. If you have only added https://www.example.com, you won't see links pointing to https://example.com or the old HTTP versions. This partial view skews your analysis: you underestimate your link profile, miss out on disavow opportunities, and overlook potential signals of negative SEO.

Even worse, if some quality backlinks point to an unmonitored version, you won't be able to identify possible redirection issues. A link from an authoritative site that encounters a broken redirection chain loses a significant portion of its value without you knowing it.

How does this fragmentation really impact PageRank?

PageRank flows through links. When a backlink points to http://example.com but your canonical version is https://www.example.com, Google has to follow the redirection. A well-configured 301 typically transfers about 90-99% of the link juice, but it’s never 100%. Multiply this phenomenon by hundreds of misdirected backlinks, and collectively you lose PageRank.

Even more problematic: if you forget a redirection (for example, the HTTP version of the root without www to HTTPS with www), Google may temporarily index multiple versions. In this case, backlinks are divided among distinct URLs, effectively diluting your authority instead of concentrating it on a single canonical version.

• Check all four variants (HTTP/HTTPS × www/non-www) in Search Console for a comprehensive view of your link profile
• Consolidate all versions to a single canonical URL through permanent 301 redirections
• Test each combination under real conditions: a missed redirection can fragment your authority for months
• Monitor "orphaned" backlinks pointing to non-canonical versions: they often reveal weaknesses in your redirection architecture
• Document your canonical choice (www or non-www, HTTPS required) and apply it consistently across all your tracking tools

Is this recommendation still relevant today?

Absolutely, and even more than before. With the widespread migration to HTTPS, many sites now have a fragmented backlink history between HTTP and HTTPS. Webmasters often neglect to claim all properties in Search Console, thinking one is enough. The result: they lose visibility on 30 to 50% of their actual backlinks.

What Mueller doesn't explicitly mention is that Search Console does not automatically aggregate backlink data across versions of the same site. You need to manually add each property and check the reports separately, or use a "Domain" property (which requires DNS verification). This technical aspect escapes many practitioners, who mistakenly believe that Google consolidates data server-side.

What nuances should be added to this statement?

First point: if your 301 redirections are flawless and verified across all four variants, the practical impact of this fragmentation decreases significantly. Google eventually understands your canonicalization and attributes backlinks to the correct version. But "eventually understanding" can take weeks or even months, during which time you lose juice.

Second nuance: third-party tools (Ahrefs, Majestic, Semrush) typically aggregate backlinks from all versions automatically. They detect redirections and consolidate data. This is convenient, but it creates a disconnect between what you see in these tools and what Google shows you in Search Console. [To be verified]: Could Google treat backlinks differently depending on whether they point to the canonical version or a redirected version, even with a clean 301? Field tests suggest yes, with a measurable loss of power on redirected links.

In what cases does this rule become critical?

Three scenarios make this check absolutely essential. First case: you have just migrated from HTTP to HTTPS and notice an unexplained drop in traffic. Checking backlinks on the old HTTP versions can reveal broken links or misconfigured redirections that you would never have detected otherwise.

Second case: you suspect negative SEO. Attackers often target non-canonical versions to inject toxic backlinks, betting that you only monitor the main version. If you don’t check all variants, these bad links slip under the radar until manual action is triggered.

What should I actually do in Search Console?

Open Search Console and manually add the four properties: HTTP www, HTTP non-www, HTTPS www, HTTPS non-www. Yes, it’s tedious. Yes, it’s necessary. For each property, check the "Links" report and export the complete list of referring domains. You’ll likely discover backlinks you were unaware of.

A more elegant alternative: create a "Domain" property in Search Console. This requires DNS verification (adding a TXT record), but it automatically aggregates all versions (HTTP/HTTPS, www/non-www, subdomains). This is the recommended method if you have DNS access. Once configured, you gain a unified view without multiplying properties.

How do I check that my redirections properly consolidate backlinks?

Manually test each variant in an incognito browser. Type http://example.com, http://www.example.com, etc., and check that they all redirect to your canonical version in a single jump (no redirection chains). Use a tool like Screaming Frog or an HTTP status checker to automate this test across the site.

Then, cross-reference Search Console data with a third-party tool like Ahrefs. If Ahrefs shows 500 backlinks but Search Console only shows 300 on your main property, that's an alarming signal. The 200 missing ones likely point to non-canonical versions you are not monitoring. Identify them, check the redirections, and fix the gaps.

What mistakes should be avoided at all costs?

First mistake: assuming Google "automatically understands" your canonicalization. Even with a correct canonical tag and 301 redirections, Google can temporarily index multiple versions, especially after a migration. Manually check with a site: search on each variant to detect any potentially orphaned indexed pages.

Second mistake: ignoring old HTTP versions after a HTTPS migration. Historical backlinks continue to point to HTTP for years. If you remove the HTTP property from Search Console thinking it is obsolete, you lose visibility on those links. Keep all properties active, even the old ones, to maintain a complete history of your link profile.

• Add the four variants (HTTP/HTTPS × www/non-www) in Search Console or create a Domain property
• Export and compare backlink reports from each property to identify discrepancies
• Test all URL combinations in a browser to verify 301 redirections
• Cross-reference Search Console data with a third-party tool (Ahrefs, Majestic) to detect missing backlinks
• Conduct site: searches on each variant to spot any indexed pages on non-canonical versions
• Monitor new backlinks monthly across all versions to detect negative SEO targeting non-canonical variants