Does Google treat uppercase and lowercase URL paths as different?

Definition: A URL path is the part of a web address after the host name and before any query or fragment. As of 17 October 2026, Google Search treats paths that differ only in letter case, such as /APPLE and /apple, as distinct URLs.

Key facts

• Google's URL structure documentation recommends consistent case when a web server treats uppercase and lowercase addresses as the same page.
• RFC 3986, the URI syntax standard, makes the scheme and host case insensitive; other components are case sensitive unless the scheme defines otherwise.
• Google's canonical URL guidance recommends linking internally to the preferred URL for duplicate or very similar pages.

Which parts of the address are case sensitive?

A scheme identifies the protocol, such as http, and a host identifies the server name. Section 6.2.2.1 of RFC 3986 gives this pair of equivalent addresses:

HTTP://www.EXAMPLE.com/
http://www.example.com/

That equivalence concerns the scheme and host. The standard treats the path as case sensitive. Its path definition places the end of the path at a question mark, a number sign or the end of the address. Consequently, lowercasing a host and lowercasing a path apply different comparison rules.

The same section also distinguishes percent encoding: the hexadecimal letters in %3a and %3A are case insensitive. That rule concerns the encoded representation of a character.

How should a website construct its paths?

Google's URL structure documentation uses these paths to illustrate separate URLs:

/APPLE
/apple

The server's treatment of those addresses matters. When both spellings serve the same page, Google recommends converting the text to a consistent case so that it can more easily identify the shared page. The recommendation is conditional on the server treating the spellings alike.

For internal links, Google's canonicalization documentation recommends consistently using the canonical URL, meaning the preferred address for duplicate or very similar content. Applied to case variants, the chosen spelling belongs in those links. The same documentation advises keeping the URL in a sitemap consistent with the canonical declaration for that page.

How can existing duplicate case variants be consolidated?

Google's canonicalization guidance recommends redirects when existing duplicate pages are being removed. A redirect sends traffic from another address to the preferred address.

If duplicate HTML pages remain accessible, a rel="canonical" link can indicate the representative page. The element belongs in the HTML head, and Google recommends an absolute URL. This illustrative element follows its documented syntax:

<link rel="canonical" href="https://example.com/apple" />

Google describes redirects and canonical link annotations as strong canonicalization signals, while sitemap inclusion is a weak signal.

Related terms

• Canonical URL
• HTTP redirects
• Crawlable internal links
• XML sitemap

FAQ

Must I use lowercase paths?

Google's case guidance specifies consistent case when your server treats both forms alike. Its instruction allows a consistent uppercase or lowercase convention.

Should my sitemap and canonical link use the same spelling?

Yes. Google's canonicalization guidance advises against specifying different canonical URLs through different methods, including a sitemap and a canonical link.

Sources

1. Google Search Central, "URL structure best practices for Google Search", updated 10 December 2025
2. IETF, "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax", January 2005
3. Google Search Central, "How to specify a canonical URL with rel="canonical" and other methods", updated 10 July 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer