Skip to content
TurboIndex
Sign in

URL Parser and Encoder

Paste a URL to see every part of it. Edit the host, the path or any query parameter and the URL is rebuilt while you type.

99 characters

Parts (edit any field, the URL above updates)

Decoded path: /shop/running shoes

Query parameters (3)

Values are shown decoded and are percent-encoded again when the URL is rebuilt.

Encode and decode

Component encoding escapes every reserved character, including / ? & = and #. Use it for a single parameter value. Full URL encoding keeps those characters so the address stays usable.

The parts of a URL

https://www.yoursite.com:8080/shop/shoes?color=blue&size=42#reviews
\___/   \_____________/ \__/\_________/ \________________/ \_____/
protocol      host       port    path         query          hash
  • Protocol (scheme): https for almost every site today. http and https versions are different URLs.
  • Host: the domain including subdomains. www.yoursite.com and yoursite.com are different hosts and need a redirect between them.
  • Port: only visible when it is not the default (443 for https, 80 for http).
  • Path: case sensitive on most servers. /Shoes and /shoes can be two pages.
  • Query: name and value pairs after the ?, separated by &.
  • Hash: a position inside the page. It is never sent to the server.

Why this matters for SEO

Search engines identify pages by their exact URL. Every variation in protocol, host, letter case, trailing slash, parameter order or tracking parameter creates another address for the same content. Those duplicates split signals and use up crawling that your new pages could have had.

Use the parameter table to find out which parameters change the content (keep them) and which only track visits (drop them from internal links and canonicals). To clean a whole export at once, use the URL list cleaner. To add campaign parameters in a consistent way, use the UTM builder. The canonical checker shows which version a live page declares as the main one.

Percent-encoding in short

URLs may only contain a limited set of ASCII characters. Everything else, such as spaces, umlauts or emoji, is written as % plus the UTF-8 bytes in hex: a space becomes %20, é becomes %C3%A9. Double encoding (%2520) is a common bug when a value gets encoded twice.

Once your URLs are clean and consistent, TurboIndex can submit them to Google and track which ones are indexed.

Questions and answers

What is the difference between encodeURI and encodeURIComponent?

encodeURI is meant for a whole address and leaves characters with a structural meaning alone: / ? & = # and :. encodeURIComponent escapes those too, so it is the right choice for a single value that goes inside a query string, such as a redirect target or a search phrase.

Is a plus sign a space?

Inside a query string, yes: form encoding writes spaces as +, and this parser decodes them that way. In the path, a plus is a literal plus and a space has to be written as %20.

Does Google treat URLs with different parameter order as the same page?

No. /shoes?color=blue&size=42 and /shoes?size=42&color=blue are two URLs for a crawler, even if the server returns the same page. Keep the order consistent in internal links and point canonical tags at one version.

Is the hash sent to the server?

No. Everything after # stays in the browser. Search engines generally ignore it, so content that is only reachable through a fragment is not indexed as a separate page.