The Complete Guide to URL Parsing, UTM Building, and UTM Link Checking
Every link you click carries hidden machinery. Behind the visible page address sits a query string — a chain of key-value pairs that tells websites who you are, where you came from, and what you clicked. Marketers call these UTM parameters, and developers call the whole thing a query string. Whether you are a marketer tagging campaign links, a developer debugging an integration, or an analyst cleaning up tracking data, a reliable URL parser is one of the most useful tools in your kit. QueryKit was built to be exactly that: a free, in-browser control room where every query parameter becomes a valve you can open, close, inspect, and rebuild.
What is a URL parser?
A URL has several parts: the protocol (https://), the host (example.com), the path (/sale), and then — after the question mark — the query string. A URL parser splits that query string at every ampersand and equals sign and shows you each parameter as a separate, editable row. Instead of squinting at a 300-character link, you see a clean list: utm_source = newsletter, utm_medium = email, utm_campaign = black-friday, and so on.
QueryKit takes this one step further with its valve pipeline. Each parsed parameter is rendered as a valve in a pipe. Twist a valve open and the parameter stays in the rebuilt URL; twist it closed and the parameter is dropped — instantly, with a live preview of the resulting link. This is enormously practical: strip gclid, fbclid, and msclkid click IDs before sharing a link, remove a stale ref parameter before re-running a campaign, or temporarily disable a parameter to test how a page behaves without it. You can also edit values inline or add new valves entirely, and the rebuilt URL updates on every keystroke.
What are UTM parameters and why do they matter?
UTM stands for Urchin Tracking Module, named after the Urchin Software company that Google acquired in 2005. UTM parameters are five standardized query parameters that marketers append to URLs so analytics platforms — Google Analytics, Mixpanel, Amplitude, and others — can attribute traffic to the right source. They are the reason a marketing team knows that 4,200 visitors came from the October newsletter and not from organic search.
The five parameters are: utm_source (where the traffic came from: google, newsletter, instagram), utm_medium (the marketing channel: cpc, email, social), utm_campaign (the specific promotion: black-friday-2026), utm_term (the paid-search keyword, optional), and utm_content (which tells apart two links in the same campaign, e.g. hero-banner vs footer-link). Of these, source, medium, and campaign are effectively required — without all three, your reports lose the ability to answer "which campaign on which channel drove this traffic?"
Why you need a UTM link checker
Tagging links by hand is error-prone, and the errors are expensive because they corrupt your analytics silently. The most common mistakes QueryKit's auditor catches are: missing parameters (a link with utm_source and utm_medium but no utm_campaign cannot be tied to a promotion), spaces in values (a value like Summer Sale gets URL-encoded into Summer%20Sale, and some tools report the encoded and unencoded versions as different campaigns), uppercase letters (Email and email are treated as two different mediums by every major analytics platform, splitting one channel into two rows), and non-standard medium values (using banner_ad instead of display fragments your channel grouping).
A good UTM link checker does not just say "wrong" — it explains the problem in plain English and tells you exactly how to fix it. That is the design philosophy of QueryKit's auditor. Paste any campaign URL and you get a 0–100 UTM health score plus a list of issues, each with a title, a plain-English explanation of why it matters, and a concrete fix (often with the corrected value pre-computed). The auditor also spots duplicate UTM keys, mixed casing across your three required parameters, and leftover click IDs like gclid that ad platforms append automatically and that are safe to strip before you share a link publicly.
UTM naming conventions that keep reports clean
Conventions are the difference between analytics you can trust and a spreadsheet full of near-duplicates. The industry-standard rules are simple: always lowercase (pick lowercase once and never deviate), never use spaces (use hyphens or underscores — hyphens are more readable in reports), be consistent with medium values (agree on one spelling per channel across your whole team: email, not a mix of email, e-mail, and newsletter as a medium), and keep campaigns descriptive but compact (black-friday-2026 beats bf and also beats a forty-character sentence).
For utm_medium specifically, there is a widely used standard vocabulary: organic for unpaid search, cpc or paid for paid search and ads, referral for links on other sites, email for email marketing, social for organic social, display for banner ads, affiliate for partner links, and video for video placements. QueryKit's preset builder has these guardrails built in: the moment you type a non-standard medium or an uppercase value, it warns you before the link ever ships.
How the UTM preset builder saves you from yourself
Teams that tag dozens of links a week should never type UTM values from scratch each time. A UTM builder with presets solves this: define a named preset once — say "Google Search Ads" with source google, medium cpc, and a campaign template — and then apply it to any URL in one click. QueryKit ships with three starter presets (Google Search Ads, Email Newsletter, Social Organic) and lets you save unlimited custom presets in your browser.
The key word is guardrails. Presets are only as good as the values inside them, so QueryKit validates every preset the moment you edit it: required fields are enforced, spaces trigger errors, uppercase triggers warnings, and non-standard mediums get flagged with a suggestion. You can apply a preset to the valves you already parsed (it cleanly replaces any existing utm_* parameters) or build a brand-new tagged link by pasting a landing page and hitting "Build tagged link". The result is a correctly encoded, convention-compliant campaign URL every time.
Parsing URLs as a developer or analyst
Marketers are not the only audience. Developers debugging OAuth callbacks, webhook payloads, or deep links constantly need to read query strings. Analysts auditing a site's tracking implementation need to extract every parameter from dozens of URLs. QueryKit's export station serves both: one click copies or downloads the parsed parameters as JSON (structured, ready for scripts and APIs) or CSV (opens directly in Excel or Google Sheets). You can choose to export only the open valves, so parameters you closed during cleanup are excluded automatically.
Because everything runs locally in your browser, there is a privacy benefit worth stating plainly: your URLs are never sent to a server. Campaign links often contain sensitive information — internal campaign names, partner identifiers, test parameters — and pasting them into a random online tool means handing that data to a stranger's server logs. QueryKit parses, audits, builds, and exports entirely on your device. Nothing leaves the page.
A practical workflow: audit, fix, rebuild
Here is how the four stations work together in a real session. First, paste a campaign link into the parser and hit Parse URL — the link breaks into valves. Second, run the same link through the UTM auditor and read the health score; suppose it flags utm_medium=Email as uppercase and utm_campaign=Summer Sale as containing spaces. Third, fix them: either edit the valve values directly in the pipeline or apply a clean preset, which replaces the broken UTM values in one click. Fourth, watch the live rebuilt URL update, copy it, and export the final parameter set as CSV for your campaign tracker. What used to be a careful manual rewrite in a text editor — with a real risk of breaking the URL's encoding — becomes a two-minute guided process.
Common questions about query strings, answered
Does the order of query parameters matter? For UTM tracking, no — analytics reads them by name. For some APIs and signed URLs, yes, so QueryKit preserves the original order and keeps your valves in the sequence they arrived. Do special characters need encoding? Yes: spaces, ampersands, question marks, and non-ASCII characters inside a value must be percent-encoded, and QueryKit's rebuilt URLs are always properly encoded. Can a URL have the same parameter twice? Technically yes, and the auditor will warn you about duplicate UTM keys since analytics tools typically read only the first occurrence. What about the fragment (the part after #)? QueryKit parses it separately and reattaches it at the end of the rebuilt URL, so deep links and single-page-app routes survive the round trip.
Whether you came here searching for a URL parser, a UTM builder, or a UTM link checker, the goal is the same: links you can trust. Clean parameters mean clean attribution, clean attribution means honest reports, and honest reports mean better marketing decisions. QueryKit puts the whole pipeline — parse, audit, build, export — behind one free page with no account and no tracking of its own. Open a valve, close a valve, and ship links with confidence.
Frequently Asked Questions
What does the QueryKit URL parser do?
Paste any URL and QueryKit splits its query string into individual parameters, each shown as a toggleable valve. You can edit values, add or remove parameters, close valves to drop them from the link, and copy the live-rebuilt URL — with proper percent-encoding handled automatically.
What are UTM parameters and why do they matter?
UTM parameters (utm_source, utm_medium, utm_campaign, plus optional utm_term and utm_content) are standardized tags appended to URLs so analytics platforms can attribute traffic to the right source, channel, and campaign. Without them, you cannot tell whether visitors came from your newsletter, your ads, or organic social.
What is a good utm_medium value?
Use the standard vocabulary: organic, cpc, paid, referral, email, social, display, affiliate, video, or newsletter. Standard values keep your channel reports grouped correctly. QueryKit's auditor and preset guardrails flag non-standard mediums and suggest the closest standard alternative.
Should UTM values be lowercase?
Yes — always. UTM values are case-sensitive, so "Email" and "email" appear as two separate mediums in your reports. Use lowercase everywhere and replace spaces with hyphens (e.g. black-friday-2026). QueryKit warns you whenever a value breaks these conventions.
Does QueryKit send my URLs to a server?
No. Everything — parsing, auditing, preset building, and exporting — runs entirely in your browser using JavaScript. Your URLs never leave your device, which makes QueryKit safe for internal campaign links and sensitive tracking URLs.
Can I export the parsed parameters?
Yes. The export station lets you copy or download the parameters as JSON (for scripts and APIs) or CSV (for Excel and Google Sheets). You can export all parameters or only the open valves, so anything you closed during cleanup is excluded automatically.