Special characters in address

url.non_ascii
Priority
Low
Severity
Info

What we look for

The path of these addresses (the part after the domain) holds characters beyond plain unaccented letters, digits and common symbols, such as é, ü or Japanese script.

Why it matters

Copied links turn these characters into long codes, such as %C3%A9 for é, which are hard to read. On sites written in languages that need them, this is normal.

How to fix

Use plain letters, digits and hyphens in new page addresses where your language allows, for example cafe instead of café. Leave addresses that need their own script, such as Greek or Japanese, as they are.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: url.non_ascii
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "url.non_ascii"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=url.non_ascii
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "url.non_ascii"
}