Validate, measure, and score any URL or slug against real parsing rules and commonly cited SEO guidance — with every check explained, not just a mystery score. Need a better slug? Generate an SEO-friendly slug and check it again.
Most "URL checker" tools online either just ping the URL to see if it loads, or run a shallow regex and call it a day. This one does neither. It parses your URL with the browser's own native URL API — the same logic real browsers use to interpret links — then runs it through a documented set of length, formatting, and best-practice checks, and shows you exactly which ones passed, which ones didn't, and why.
Whether you're naming a route in your app, generating a slug for a CMS, or double-checking a URL before you ship it, this tool tells you precisely what's wrong (if anything) instead of a vague "looks okay" or "invalid" with no explanation.
I kept running into the same small, dumb bugs: a slug with a trailing hyphen from a bad string-replace, a route name that collided with a reserved path, a "short" URL that was actually 40 bytes longer than it looked because of a few accented characters. None of it was hard to catch — I just wasn't checking for it consistently.
So this tool checks for all of it at once, and shows its work. Every score this tool gives you is the sum of specific, visible checks — not a black box. If you disagree with a deduction, you can see exactly which rule caused it.
my-post-title.Every result starts at 100 points. Each failed or borderline check subtracts a fixed, documented amount — nothing is hidden or arbitrary:
admin or api) — flagged since it can collide with real application routes.These thresholds reflect commonly cited SEO and web-development best practices, not a universal specification — different platforms, CMSs, and search engines can vary. The checklist tells you exactly what triggered each deduction so you can judge for yourself whether it matters for your case.
Example: Naming a new blog post before publishing.
Example: Naming a new route before adding it to the codebase.
Example: Checking a slug that includes accented characters.
Example: Tracking down why a URL behaves unexpectedly.
URL constructor — the same parser that decides whether a link actually works — not a hand-written regular expression trying to approximate it.admin, api, or null) that tend to cause real conflicts in applications.blue-widget reads as two words, blue_widget can read as one./api as your actual API root is completely normal; it's only worth a second look if you didn't intend the collision.Yes — no account, no limits, and nothing is logged or sent to a server.
This tool doesn't try to load or ping the URL at all — it checks the URL's structure, length, formatting, and best-practice adherence. A URL can be perfectly well-formed and still not resolve to anything (or vice versa); those are two different questions, and this tool only answers the structural one.
The checklist flags a slug over roughly 60 characters and a full URL over roughly 100 characters as longer than commonly recommended for SEO, and separately flags anything approaching the 2,048-character range some browsers and servers historically capped URLs at. These are widely cited guidelines, not a single universal rule — check the specific checklist item for the exact number that triggered it.
An empty value can't be analyzed at all. A slug of just one or two characters is flagged as a caution, not an error — it's technically valid, but usually too vague to describe what it points to.
Standard letters and numbers take one byte each in UTF-8, but accented letters, symbols, and non-Latin characters can take two to four bytes. A slug that looks like 20 characters might actually be 30+ bytes — which matters if it's going into a system with a byte-based length limit.
No — it only ever suggests a cleaned-up version for you to review and copy yourself. In Slug Only mode this cleans casing, accents, and invalid characters; in Full URL mode it only cleans the path portion and leaves your protocol and domain untouched.
It flags slugs that match common route names many frameworks and platforms reserve internally (like admin, api, or null). It's a heads-up in case the collision is accidental — if it's intentional, it's safe to ignore.
In Full URL mode, if you leave off the protocol, the tool analyzes it as if https:// were added — and clearly labels that it did so, so you always know exactly what was actually checked.
No — it deliberately doesn't make any network request. It checks structure and formatting only, which is also why it works instantly and never sends what you type anywhere.
Not necessarily — it's a guideline, not a verdict. A short internal admin route, for instance, doesn't need to satisfy public-facing SEO length guidance. Use the checklist to decide which flagged items actually matter for your specific URL.
Paste one in above and see exactly what it's made of — length in characters and bytes, formatting issues, and a score you can actually verify line by line.
If you think a check is missing or a threshold seems off, I'd genuinely like to hear about it.
Go ahead and check your URL — accurate, explained, and entirely private.