Confirm that HTTP/HTTPS, www/non-www, and trailing-slash variants of URLs all redirect to the site's single preferred version. For example, if the preferred version is https://www.domain.com/page/, then the http, non-www, and no-trailing-slash variants should all redirect there. Redirection is preferred; a canonical tag is a less desirable but acceptable workaround.
Test at least one URL in each variant combination and confirm each redirects to the preferred version.
Note the status code of each redirect: it should be a 301 (permanent), not a 302 (temporary).
Flag redirect chains (e.g. HTTP to non-www HTTP to HTTPS www) that should collapse into a single redirect.
Flag any variant that resolves with a 200 instead of redirecting; these are live duplicate URLs.
Validate preferred-version redirects (written instructions).
Review corresponding Sitebulb Hints.
If variants resolve directly instead of redirecting, the same page exists at multiple URLs, splitting link equity and creating duplication. Consistent 301s to one preferred version consolidate signals cleanly.
HTTPS was added but the HTTP version still resolves with a 200.
Trailing-slash and case variants serve the same page without redirecting.
To Slash or Not to Slash by Google
Sitebulb
Find, fix and communicate technical issues with easy visuals, in-depth insights, & prioritized recommendations across 300+ SEO issues.
Get all the capability of Sitebulb Desktop, accessible via your web browser. Crawl at scale without project, crawl credit, or machine limits.