Scraping API Prices
MenuClose

Search the site

82 providers, their alternatives and head-to-heads, targets, guides and answers

Home / Tools / URL parser and normaliser

URL parser and normaliser

Paste a web address to see its host, path and every query parameter decoded, and a normalised form with the parameters sorted and tracking tags removed, so two links to the same page compare equal before you pay to crawl both.

Normalised: https://shop.example.com/products?color=blue&page=2

The address's parts, and each query parameter decoded, in order
PartValue
Schemehttps
Hostshop.example.com
Path/products
Query: utm_sourcenewsletter
Query: colorblue
Query: page2
Query: gclidabc123
Fragmentreviews

Worked out in your browser. Nothing you paste is stored, sent or added to the page address, so tokens and cookies stay on your machine.

What it is for when you scrape

Crawls collect the same page under several addresses: tracking tags (utm_source, gclid, fbclid), parameters in a different order, a #fragment the server never sees. Each copy is a separate paid request. Normalising addresses before you queue them removes those duplicates; on a large crawl they can be a real share of the bill.

The normalised form sorts parameters by name and drops the tracking tags listed above, and the fragment. Keep any parameter that changes the page (page, sort, color, id); the parser shows them all decoded so you can decide. The crawl budget prices a crawl once you know how many distinct pages it holds.