URL Tools

UTM Builder

Create campaign URLs locally, inspect the complete query structure and repeated keys, and review tracking tags before sharing the final URL.

Quick presets

Campaign URL

ReadyExisting non-UTM query parameters are preserved; empty UTM fields are removed.

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.

Bulk campaign workspace & UTM audit

Reuse the single-link campaign fields above across a destination list, normalize naming deliberately, flag rows that already carry UTM tags, and export a reviewable CSV.

Destination URLsNaming policyApplied to source, medium, campaign, term and content only.

—Input rows

—Valid URLs

—Domains

—Review flags

Ready.

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.

Use this result with confidence

Keep campaign naming rules consistent before bulk generation

UTM values are most useful when the same channel and campaign are named the same way across every link. Decide whether your team preserves case, uses lowercase, or normalizes spaces to underscores or hyphens before creating a batch. Consistent source, medium, campaign, term, and content values make analytics grouping easier and reduce the need to repair fragmented reports later.

Audit existing query parameters instead of silently stacking tags

A destination URL can already contain UTM parameters or unrelated query values. Replacing an old utm_campaign may be intentional, while preserving an affiliate ID, locale, product filter, or experiment parameter may also be necessary. Review flagged rows before publishing so a new tracking link does not accidentally carry stale attribution or remove a parameter the destination actually needs.

Bulk output should be reviewable outside the builder

A CSV handoff makes it easier to compare source URLs, generated URLs, and audit status row by row before links are inserted into ads, newsletters, QR codes, or social posts. Keep the original destination beside the tagged result. That makes later troubleshooting easier when a redirect, encoded character, or campaign naming mistake appears only after links are distributed.

Tracking syntax does not prove analytics collection

A well-formed UTM URL only proves that the parameters were attached correctly. It does not confirm that redirects preserve them, consent settings allow measurement, analytics is installed on the destination, or the reporting platform interprets the values as expected. Test representative links through the real publishing path and verify incoming campaign data in the actual analytics system.