b2KIT

URL Structure Analyzer

Analyze URL structure for SEO best practices. Check length, depth, parameters, hyphens, keywords, and HTTPS. Score with recommendations.

Tested tool guide Tested browser tools Checked August 16, 2026

What URL Structure Analyzer does, with a checked example

Paste a URL and this tool judges its structure the way SEO guidance does: length, path depth, query parameters, word separators, keyword presence, and HTTPS. Each check passes or flags, the flags produce recommendations, and the results roll up into one score. The surprise for most users: the score is structure-only. A short URL still fails on underscores or tracking parameters, and the fixes apply to URLs you are about to publish - rewriting a live URL without a 301 redirect from the old path destroys rankings instead of improving them.

Worked example

A concrete input and expected output from the current implementation.

Input

https://example.com/blog/post_title_2024?id=123&ref=partner

Expected output

HTTPS: pass - secure scheme
Length: 59 characters - short
Depth: 2 path segments - flat
Parameters: 2 (id, ref) - flag: query string dilutes the keyword slug
Separators: underscore in post_title_2024 - flag: replace with hyphens
Keywords: "post title 2024" readable in the slug - pass

Overall: 4 of 6 checks pass. Suggested rewrite: https://example.com/blog/post-title-2024 with the parameters removed.

Four checks pass on inspection of the string itself: the scheme is https, the URL is 59 characters, the path is two segments deep, and the slug reads as words. The two flags are equally visible: the underscore joins "post" and "title" into one token where Google's guidance calls for hyphens, and the id and ref parameters add tracking clutter. The suggested rewrite is exactly those two fixes applied.

How the result is produced

1

How the URL is taken apart

The tool separates the URL into scheme, host, path segments, and query string before judging anything. It counts total characters for the length check, counts path segments for depth, enumerates every parameter, and inspects the slug for separators: hyphens split words cleanly, while underscores merge them. It then looks for readable keyword terms in the slug and confirms the scheme is https://.

2

How flags become recommendations

Each check ends as pass or flag. Flags feed the recommendation list with a concrete rewrite, such as swapping underscores for hyphens or stripping parameters, and all checks aggregate into the single score. The score is guidance, not a prediction: it reflects the URL's shape at the moment of analysis, so treat a high score as a clean bill of health for structure only.

Good uses

  • Before hitting publish on a blog post, paste the permalink draft to catch underscores, tracking parameters, or an overgrown slug - fixes are free when the URL has never gone live.
  • Audit a site's URL templates: paste one example from each pattern (article, category, product, filter) and fix the structural problem once at the template level instead of page by page.
  • Compare candidate URL schemes for a restructure, such as /2024/05/example against /blog/example, to see which is shorter and shallower before committing the whole site to one hierarchy.

Limits and checks

  • The score measures structure, not ranking power. Content quality, backlinks, internal linking, and site authority outweigh URL shape, so a perfect score never guarantees visibility and a flagged URL can still outrank a clean one.
  • Applying the recommendations to a live URL without a 301 redirect breaks the page: the old path stops resolving, and its link equity and rankings strand with it. The tool judges the URL as a string and cannot know what already points at it.
  • Some flags are not fixable. Platforms that generate query strings, forced parameter names, or framework slug formats can make the ideal URL impossible; treat flags as suggestions to simplify, since Google publishes guidance rather than hard length or depth limits.

Common questions

If my URL scores well, will the page rank?

No, and the tool does not claim otherwise. Structure is one factor among many - content relevance, backlinks, page speed, and site authority all weigh more. What a good score buys you is one less thing to fix later: the URL never becomes a liability. Use the recommendations as a pre-publication checklist and keep expectations at that level.

Why does an underscore in the slug get flagged?

In a URL, an underscore glues words together - search engines treat post_title as a single token, so the words stop reading as separate terms. A hyphen keeps them distinct and human-readable. Google's own URL structure guidance recommends hyphens over underscores, so the flag is standard practice rather than this tool's opinion.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools