URL & Encoding · Free tool
URL Encoder / Decoder
URLs can only contain a limited character set. Spaces, special characters, and non-ASCII text must be percent-encoded (%20, %26, etc.) to be valid in a URL. This tool encodes plain text to URL-safe format and decodes percent-encoded strings back to readable text.
SEO, GEO & AEO: why this checklist matters
Who should use this
Developers building URLs dynamically, SEOs analyzing query parameters, and marketers troubleshooting tracking links.
Rankings, AI answers, and citations
URL encoding doesn't directly affect rankings. Correctly encoded URLs ensure links work and can be crawled. Query parameter URLs should generally be excluded from sitemaps and potentially blocked with canonical tags to prevent indexing URL variations that serve the same content.
What to verify before you ship
- Encode all user-supplied data before including it in a URL
- Decode URLs before reading analytics or log data to see the actual parameters
- Verify tracking URLs by decoding them before deploying campaigns
- Test encoded URLs in all target browsers — some older systems handle encoding differently
What you can expect next
Use this workflow on drafts and live URLs. For continuous monitoring across Google and AI surfaces, pair results with Linkstonic SEO audit, AI tracking, and TrueTrace.
Frequently asked questions
Written for search snippets, People Also Ask-style surfaces, and answer engines that quote short Q&A units.
What characters need to be encoded in URLs?
Spaces, &, =, ?, #, /, \, <, >, and non-ASCII characters all need encoding. The specific characters that must be encoded vary by the part of the URL (path, query, fragment). When in doubt, encode it.
What is the difference between URL encoding and HTML encoding?
URL encoding converts characters to percent-encoded form (%20) for use in URLs. HTML encoding converts characters to HTML entities (&, <) for safe display in HTML. They're different and used in different contexts.
Why do spaces become + in some URLs but %20 in others?
In query strings (after ?), spaces are often encoded as + (form encoding). In URL paths, spaces should be %20. Both are valid in their respective contexts. %20 is unambiguous and works everywhere.
Does encoding affect SEO?
URLs with unencoded special characters may be treated inconsistently by crawlers and browsers. Consistently using encoded URLs in your links prevents duplicate URL issues where the same page is accessible via encoded and unencoded versions.