From the blog

The Same Page, Four Different URLs

Quick answer: try loading http://example.com, https://example.com, https://www.example.com, and https://www.example.com/ for your own site. If more than one of those returns a normal 200 response…

Dhruv PrajapatiSecurity research20 Nov 20268 min read

Quick answer: try loading http://example.com, https://example.com, https://www.example.com, and https://www.example.com/ for your own site. If more than one of those returns a normal 200 response instead of redirecting to a single version, search engines can end up treating them as separate pages that happen to contain the same content, rather than one page with several ways to reach it. That splits whatever ranking signals those pages earn instead of combining them on one URL, and it wastes crawl time on copies of a page that's already been seen. The fix is picking one canonical form, redirecting every other variant to it, and confirming the page itself agrees with a rel="canonical" tag.

This usually isn't a deliberate decision anyone made. It's what happens by default when nobody specifically configured a server, CMS, or CDN to enforce one version, each layer just responds to whatever URL it's asked for, and most of them are perfectly happy to return your homepage for several different-looking requests.

In short: a canonical tag and a redirect do different jobs. A redirect stops the duplicate URL from ever fully loading. A canonical tag is a hint telling search engines which version to treat as authoritative if a duplicate does get requested. Sites with this problem usually need both, not just one.

How One Page Ends Up With Several URLs

Each of these is an independent setting, and by default none of them point at each other:

  • Protocol. http:// and https:// are different URLs unless something forces one to redirect to the other.
  • Host. www.example.com and example.com are different hosts as far as a browser or crawler is concerned, even though they're clearly "the same site" to a person.
  • Trailing slash. example.com/pricing and example.com/pricing/ can be treated as two different URLs depending on how the server is configured.
  • Case. example.com/Pricing and example.com/pricing are technically different URLs on most server setups, even though they look nearly identical.
  • Tracking parameters. example.com/pricing?utm_source=newsletter is, strictly, a different URL from example.com/pricing, even though it's the exact same page with the exact same content.

None of these need to overlap for a problem to exist. Even just protocol and host combined already produce four reachable versions of a homepage, and it's common for a site to have never deliberately picked which one is "real."

Why This Actually Costs You Something

Duplicate content from URL variants isn't treated as some kind of penalty, search engines aren't punishing you for it. The cost is more indirect: links, shares, and authority that should all be consolidating on one URL end up spread across several instead, which can mean a page ranks less well than it would if every signal pointed at the same address. On top of that, a crawler spending time re-fetching a page it's effectively already seen, just at a slightly different URL, is crawl budget that isn't going toward finding or re-checking pages that actually need it.

There's also a practical, ongoing cost: backlinks accumulate over years, and if some of them point to the www version and others to the non-www version, you're permanently splitting credit for the same page unless the variants properly resolve to one another.

What the Canonical Tag Actually Does (and Doesn't Do)

A rel="canonical" link in a page's <head> tells search engines, "if you've found this content at more than one URL, treat this specific one as the real version." It's a signal, not a directive, search engines generally respect it, but they can override it if other signals (like which version actually gets linked to and crawled most) point somewhere else.

That's the main reason a canonical tag alone isn't a complete fix. If https://example.com and https://www.example.com both fully load and both have a canonical tag pointing at the www version, you've reduced the ambiguity, but you still have two live, fully-loading URLs for the same content. A redirect is what actually prevents the non-canonical version from loading at all, the canonical tag is what you set in addition, as a hint for any variant that does still get requested, including parameterized URLs you may not have redirect rules for.

Checking Your Own Site

Variant to checkHow to check itWhat to look for
http:// vs https://curl -IL http://yoursite.comDoes it redirect to https, or return content directly over http?
www vs non-wwwcurl -IL https://www.yoursite.com and curl -IL https://yoursite.comDo both return a 200, or does one redirect to the other?
Trailing slashcurl -IL https://yoursite.com/some-page and .../some-page/Does one version redirect to the other, or do both load independently?
Canonical tagView source on a live page, search for rel="canonical"Is it present, and does it point to the exact URL you've chosen as the real one?
URL parametersLoad a page with a tracking parameter appended, e.g. ?utm_source=testDoes the canonical tag still point to the clean URL without the parameter?

If more than one row shows a direct 200 instead of a redirect, that's a live duplicate right now, not a theoretical risk.

Fixing It

Pick one canonical form for your site: a protocol (almost always HTTPS at this point), a host (with or without www, either is fine as long as it's consistent), and a trailing-slash convention. Then:

  • Redirect every other variant to that one form, with a 301, at whichever layer handles it for you, your CDN, DNS provider, or server configuration. This should happen before the request ever reaches your application code.
  • Add a self-referencing canonical tag to every page, pointing to that same page's URL in the canonical form you picked. This covers cases a redirect rule might miss, like arbitrary tracking parameters.
  • Check your sitemap only lists URLs in the canonical form. A sitemap that mixes www and non-www URLs, or includes both with and without trailing slashes, is sending a mixed signal in the one place that's supposed to be unambiguous.
  • Update internal links to consistently point at the canonical form, rather than relying on redirects to clean up links that were never quite right to begin with.

None of this requires touching your actual content. It's entirely a configuration and templating fix, and once the redirects and canonical tags are in place, it tends to stay fixed without ongoing attention. A technical SEO check can confirm your site resolves to one consistent URL form across these variants, which is a faster first pass than checking each combination by hand.

Frequently asked questions

No, there's no penalty in the sense of a site being punished. The cost is indirect, split ranking signals and wasted crawl time, rather than any kind of flag or demotion applied to the site.

Final Thoughts

This is one of those problems that's invisible from normal browsing, because browsers quietly follow whatever redirects exist and show you the end result either way. Whether your site has one clean canonical URL or four live duplicates looks identical if you're just clicking around it yourself.

The check is a handful of curl commands and a look at your page source for the canonical tag. The fix, once you know which variants are live, is almost always a redirect rule and a template change, not a content rewrite.

If you've never specifically checked whether your own homepage resolves to exactly one URL, it's worth running those checks today, especially if your site has carried links and backlinks across more than a few years.

How FlawPilot helps

FlawPilot finds security and quality issues in your AI-built app and shows you how to fix them. It checks your deployed site across security, performance, infrastructure, and SEO, and scans your source code for vulnerabilities, hardcoded secrets, and vulnerable dependencies.

Every finding is prioritized and explained in plain English, with the actual fix: the configuration change, DNS record, security header, or code change needed. For supported findings, AI-powered guidance adds step-by-step instructions and suggested code fixes.

Connect your Git provider to scan your repository alongside your live site, so application findings, code vulnerabilities, secrets, and dependency issues all land in one place.

It fits your existing workflow too: a REST API for scores and findings, an embeddable security badge, and an MCP server so tools like Claude, Cursor, or ChatGPT can read your findings and help you work through them.

The boundaries are clear: the public website scan reads only publicly accessible signals, with no agent or credentials required, and source-code scanning is opt-in and read-only. Fixes are never applied or merged without your review.

Canonical TagsDuplicate ContentURL VariantsTechnical SEOSite StructureCrawl Efficiency

Verify your AI-generated app is production-ready.

117 security checks in 60 seconds - free, no account needed.

Scan one page

Enter a URL - no account, no install.

Run a Site Health check

Requires a free account

Crawls every page we can reach and scores each one, so a slow template deep in the site stops hiding behind a healthy homepage.

Scan your source code

Requires a free account

Connect a Git provider to check for vulnerabilities, secrets, and risky dependencies.