URL slug checkeraudit any URL in seconds
Paste a URL or slug and get an instant SEO audit: more than 15 checks covering length, case, separators, stop words, special characters, dates, nesting and query parameters — each with a plain-English explanation and a one-click fixed slug.
Paste a URL above — the audit runs instantly in your browser. Nothing is fetched or uploaded.
How to check a URL slug
- 1Paste a full URL (https://…), a path (/blog/post) or a bare slug into the first box.
- 2Optionally add the keyword the page should rank for — the checker confirms it appears in the slug.
- 3Read the results: problems first, then warnings, notes and passes. Each links to a guide explaining the rule.
- 4Copy the suggested slug, update the page, and add a 301 redirect from the old URL.
What the checker looks at
- HTTPS, lowercase and spaces — the issues that create broken or duplicate URLs.
- Hyphens vs underscores, doubled or dangling separators, and special characters.
- Slug length in words and characters, against the 3–5 word / ~60 character guideline.
- Stop words, repeated keywords and an optional target-keyword match.
- Dates in the path, file extensions, nesting depth, and dynamic or tracking parameters.
- Native-script awareness: Arabic, Cyrillic and CJK slugs are treated as valid, not as errors.
Frequently asked questions
What makes a URL slug SEO-friendly?
An SEO-friendly slug is short (3–5 words), lowercase, uses hyphens between words, contains the page’s main keyword, and has no special characters, dates, session IDs or file extensions. The checker tests all of these.
Does the checker fetch or crawl my page?
No. It analyzes the URL text only, entirely in your browser. That means it works on staging URLs, unpublished drafts and internal links — and nothing you paste is sent anywhere.
How is the slug score calculated?
Every URL starts at 100. Each problem subtracts 20 points and each warning subtracts 8. Notes are informational and cost nothing. A score of 90+ means the slug follows best practice.
Should I change existing URLs that score badly?
Only if the gain is worth it. Changing a URL resets some signals and requires a 301 redirect. Fix new pages first; change old ones when they have serious issues like uppercase duplicates, session IDs or misleading words.
Are Arabic or other non-Latin slugs penalized?
No. Native-script slugs are valid and indexable, and Google displays them readably. The checker flags them as an informational note, not a problem.