Slug and URL SEO Basics for Real Production Pages
Reproduce Unicode slug suggestions, preserve URL context, and check changes before migrating a published page.
A tidy-looking URL is not proof of a correct canonical or a reason to rename an existing page. Use concrete examples to separate naming choices from routing and indexing decisions.
Tools in this guide
1. Compare an accented title in two character styles
In URL Slug Checker, load English title and accents. The default result is café-notes-for-developers. ASCII mode produces cafe-notes-for-developers after you generate again. Both are naming choices; no search-ranking score is assigned.
Load Chinese URL and parameters. Keeping Unicode letters preserves 中文-说明. ASCII mode cannot translate those words and reports that no usable letters or digits remain. Choose language-appropriate wording rather than erasing it to satisfy a generic score.
2. Check the full URL context
The Chinese sample retains /zh/guides/, ?edition=2, #part, and the original trailing slash while replacing the final segment. Compare both the readable slug and its percent-encoded representation. The suggestion does not confirm that this route exists.
The host is normalized by the browser URL parser. The path is not universally case-insensitive: lowercasing an existing segment can identify a different route. Review the original and suggested text before using it.
3. Inspect query semantics before cleanup
Use URL Parser to compare raw fields with decoded values. q=a+b contains a space after form-style decoding, while q=a%2Bb contains a literal plus. Repeated keys, their order and empty values may be meaningful to the application.
Decide which parameters affect content, filtering or pagination before excluding them from a canonical. A formatter or tracking-field list cannot make that content decision for the site.
4. Validate a necessary URL change
For an existing page, keep its URL when a title edit does not require a route change. If a move is necessary, record the old and new URLs and check the redirect map for chains, loops and self-redirects. Then test actual HTTP responses.
Verify that internal links, sitemap, canonical and language alternates match the chosen page policy. Toolskit uses no-slash page URLs; another site may use a different convention. Neither a slug suggestion nor a fixed character count overrides the site’s routing and content requirements.