Can URLs have spaces or special characters?
Rubric check: space or special character in a URL (check id url_non_ascii)
They can, but they shouldn't. Spaces, curly quotes and long dashes have to be encoded (a space becomes %20), and those links often break when people copy or share them. Letters in your own language, such as é or ü, are fine.
Why it matters for SEO
Google supports UTF-8 in URLs, so a page in French or Japanese can use its own letters. What causes trouble is punctuation and spaces, which turn into long % codes in the address bar and in shared links.
Google's URL guidance suggests hyphens between words. Changing an old URL just for this is rarely worth it.
Does this matter for ChatGPT and AI Overviews?
There's no evidence that ChatGPT or AI Overviews treat these URLs differently. They read the page, not the address.
A clean address does survive being pasted into chats and AI answers better. Rubric shows this as a minor note, inside a capped allowance shared with its other URL checks.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Spaces and symbols in addresses get encoded and can break when people share the link.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This is one of 7 URL checks. Together they can take off at most 12 points, so a site isn't marked down many times for one kind of problem.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 0 of 300 sites where Rubric could judge it (0%). That is 0 of 287 judged sites in Rubric's 313-site test set and 0 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 6 of its findings by hand and 4 were wrong (67%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- WordPress builds the slug from the title and removes most special characters. If one slipped through, edit the Permalink in the post's settings panel.
- Uploaded file names with spaces become URLs too. Rename files before you upload them (for example
blue-boots.jpg). - If you change a live URL, add a 301 redirect from the old one.
Shopify
- Shopify builds handles from titles and replaces spaces with hyphens. To change one, edit the URL handle under Search engine listing > Edit.
- Keep Create a URL redirect ticked when you change a live handle.
- Rename image and file names before uploading them in Content > Files.
Webflow
- Edit the page's Slug in Page settings, or the CMS item's Slug field. Webflow only allows letters, numbers and hyphens in slugs.
- Special characters usually come from asset file names. Rename the file before you upload it.
- Add a 301 redirect for any live URL you change. Publish.
Custom code
Build slugs from lowercase words and hyphens:
const slug = title.toLowerCase().replace(/[^\p{L}\p{N}]+/gu, "-").replace(/^-|-$/g, "");This keeps letters in any language and swaps spaces and punctuation for hyphens.