Should I encode spaces as %20 or +?

In query strings both are accepted, but %20 is the safe universal form. The tool uses %20 everywhere.

Can an encoded URL still rank?

Encoding changes nothing about ranking. It only makes a URL valid. Google reads the decoded form for relevance.

Why does my share link break on some platforms?

Usually a raw ampersand or space in a query value. Encode the value and the link survives every parser.

URL encoder / decoder

Paste a string and get the percent-encoded form, or paste an encoded URL and decode it back. Uses the same rules your browser applies to query strings.

result

When encoding matters

URLs only safely carry a small set of characters. Spaces, slashes, ampersands and non-ASCII text must be percent-encoded, or links break, tracking parameters get split, and crawlers read garbage.

The two main uses

Query strings: utm values, search phrases, product names with spaces.
Paths: Unicode titles in slugs, reserved characters like ? and # inside a path segment.

URL encoder / decoder

When encoding matters

The two main uses

Next