A URL with raw square brackets cannot simply be treated as identical to its percent-encoded version. According to an October 2026 report by Search Engine Journal, Google’s John Mueller explained that Google crawls the two versions separately; only if the server returns the same content will Google deduplicate them and choose one. For square brackets in locations such as query parameters, he recommends using the encoded form and keeping related links and URL markup consistent. He expects existing sites that have consistently used raw square brackets to continue working, but does not recommend that approach for new sites.
Different encoding is more than a display difference
The examples in the report are ?filter[]=123 and ?filter%5B%5D=123: the first uses raw square brackets, while the second represents the opening and closing brackets as %5B and %5D, respectively. Citing RFC 3986, Mueller explained that reserved characters and their percent-encoded forms are not equivalent. Just because two URLs open the same page does not mean the URLs themselves are identical.
- Raw versus encoded forms: [] and %5B%5D are the two forms discussed here; they cannot simply be treated as equivalent.
- Letter case in encoding: %5B and %5b are equivalent. This is different from the distinction between raw characters and their encoded forms.
- Location matters: Under the standard cited in the report, raw square brackets in query strings are technically invalid. Square brackets enclosing an IPv6 address in the host component of a URL serve a specific purpose, so the same advice does not apply there.
Google can deduplicate URLs, but sites should first make their links consistent
For Google to deduplicate these URLs, both must return the same content. Mueller said that Google crawls both separately and, if the content is the same, deduplicates them and chooses one version. This does not mean the two forms are inherently equivalent, nor does it guarantee that Google will choose the site’s preferred version.
His advice is to first “pick one,” then use it consistently in internal links, canonical tags, sitemaps, and structured data. For example, if you choose ?filter%5B%5D=123, do not use raw brackets in internal links while pointing the canonical to the encoded version. The report notes that a consistent format can make Google more likely to choose the intended version, but cannot guarantee that outcome.
Existing sites need not rewrite every URL solely because of this difference
Vanessa Fox mentioned a site that used invalid square-bracket syntax throughout but appeared to be indexed normally. It was left unchanged because converting it would have been too much trouble. Mueller said he expected no problems with existing sites like this, but would not build a new site that way. His qualified assessment and Fox’s individual example are not an official guarantee that all URLs containing raw square brackets will work properly.
Do not rely solely on the browser’s address bar when checking these URLs: a browser may encode square brackets before sending the URL, while JavaScript or other code may send the raw characters directly. In addition to keeping URL formats consistent in internal links and metadata, Mueller recommends checking how important crawlers and fetching tools handle these URLs. Other tools cannot be assumed to handle them the same way Google does.
URLs containing square brackets: perspectives from across the web
Is it okay to use raw square brackets in internal links but the encoded version in the canonical?
It is best not to mix them deliberately. In query parameters, for example, raw square brackets and their encoded forms produce different URLs. If both return the same content, Google may deduplicate them and choose a version itself; it is not guaranteed to choose the version specified by the canonical. Choose one format and use it consistently in internal links, canonicals, sitemaps, and structured data. For new sites using square brackets, Mueller recommends the encoded form.
Must an existing site that uses raw square brackets extensively convert all of them?
This difference alone does not mean a complete conversion is necessary. Mueller expects existing sites that have consistently used raw square brackets to continue working, but does not recommend designing new sites that way. Vanessa Fox also mentioned a case that appeared to be indexed normally and was left unchanged because converting it would have been too much trouble. These are not universal guarantees. You should still check that links and metadata are consistent and verify how important crawlers and fetching tools actually handle the URLs.
If a URL opens when entered in a browser, does that mean programs and crawlers will receive it in the same form?
No. A browser may encode square brackets before sending the URL entered in the address bar, while JavaScript or other code may send the raw characters directly. If a site relies on URLs containing square brackets, check the actual requests as well as how important crawlers and fetching tools handle them. Mueller cautions that other tools may not handle them the same way Google does.
References
- Google Explains 503s, Robots.txt Limits & Bracket URLs – SEO Pulsewww.searchenginejournal.com · 2026-10-24T12:00:00+00:00 — Discusses: Is it okay to use raw square brackets in internal links but the encoded version in the canonical?
- Google Crawls Raw And Encoded Bracket URLs Separatelywww.searchenginejournal.com · 2026-10-21T12:06:29+00:00 — Discusses: Is it okay to use raw square brackets in internal links but the encoded version in the canonical?; Must an existing site that uses raw square brackets extensively convert all of them?

