URL Compare

Compare protocol, hostname, port, pathname, query, and fragment and show exactly which components differ.

URL A

URL B

Sort query

Ignore fragment

Ignore non-root trailing slash

ReadyEquivalent here means equal after only the normalization rules selected above; servers may apply different routing semantics.

Before editing a URL

Inspect structure first, then normalize or edit only the part you mean to change. Browser-local tools avoid sending pasted links to a remote parser.

ParseSeparate scheme, authority, path, query and fragment.

Normalize deliberatelyChoose cleanup rules instead of assuming one universal canonical URL.

Edit / expandWork with query rows, relative references or URI templates structurally.

Compare / batchAudit repeated params or many URLs without fetching them.

Verify destination contextSyntax tools cannot prove a URL exists, redirects safely or is authorized.

Parse Normalize Build Edit query Diff query Batch parse Remove tracking Resolve relative URI template OAuth URL

URL tools are string-processing utilities. They do not crawl destinations, follow redirects, resolve DNS, check TLS, or verify OAuth provider registration.

URL Compare: Canonical, Query & Tracking Diff

Compare normalized URLs by scheme, host, path, query keys and tracking parameters with a canonicalized diff.

Quick-win audit

Before editing a URL

Parse before editing, normalize only with explicit rules, preserve repeated query keys when they matter, and use batch tools when you need to audit many links consistently.

Syntax is not reachability

These browser-local tools do not resolve DNS, follow redirects, inspect remote HTTP status, verify TLS, or decide search-engine canonicalization.

Practical guide and verification

Use the tool first, then use these checks to interpret, verify and hand off the result without displacing the primary workflow.

Define what “equivalent” means for the task

Two URLs can differ textually yet lead to similar resources, while two almost identical URLs can behave differently because of case, query order, fragments, encoding, or server routing. Decide whether you are comparing literal strings, normalized URL components, cache keys, analytics URLs, or expected navigation before interpreting a difference.

Review normalization options one at a time

Sorting query parameters, ignoring fragments, or normalizing a trailing slash can be useful, but each option changes the comparison rule. Toggle one rule at a time and keep the original URLs visible. This makes it clear which transformation caused the URLs to appear equal or different.

Do not treat syntax comparison as a redirect check

The page compares URL structure locally. It does not fetch the destinations, follow redirects, resolve DNS, inspect canonical tags, or prove that a server treats two paths the same way. Use network or site-specific checks separately when live behavior matters.

Check repeated and encoded parameters carefully

Repeated keys, empty values, plus signs, percent-encoding, Unicode hostnames, and encoded slashes can be meaningful. Preserve the original form when debugging an application or signature scheme, because reserializing a URL can change the byte sequence even when a browser displays something similar.