SafeShare Help Center
What are the parts of a URL?
A URL is built from fixed blocks: protocol, domain and path – plus an optional subdomain, a query string with parameters and a fragment.
SafeShare Help Center
A URL is built from fixed blocks: protocol, domain and path – plus an optional subdomain, a query string with parameters and a fragment.
Every web address follows the same basic pattern: the protocol comes first, then the address of the server, then the way to the specific page – and optional extras at the end.
https://shop.example.com/products/shoes?color=blue&size=42#details
In this example, https is the protocol, shop.example.com the hostname,
shop the subdomain, example.com the registrable domain, /products/shoes the path,
?color=blue&size=42 the query string with two parameters and #details the fragment.
For link cleaning, the query string is the interesting part: it holds useful settings as well as measuring extras.
https://shop.example.com/products/shoes?color=blue&utm_source=newsletter#details
https://shop.example.com/products/shoes?color=blue#details
color=blue and the fragment #details stay, because they control what the page shows.
https://shop.example.com/products/shoes?color=blue&utm_source=newsletter&fbclid=AbC123#details
https:// – defines how browser and server talk. The s stands for an encrypted connection.
shop. – an optional prefix of the domain, often used for areas like shop, blog or help.
example.com – the registrable part of the hostname. Together with shop, it forms the hostname shop.example.com.
/products/shoes – the way to the specific page within the website.
?color=blue&size=42 – extras as name-value pairs. Settings live here, but so do measuring extras.
#details – jumps to a spot on the page. It is functional and normally stays when cleaning.
Not every parameter is pure tracking. Some keys are functionally necessary, for example for language, search, filters, variants or IDs. That is why it is better to check links instead of simply deleting everything after the question mark.
utm_sourceutm_mediumutm_campaigngclidfbclidcolor, size)#details)SafeShare is not meant to break links. The app helps make recognizable link extras visible and use cleaned links deliberately.
Three ways, depending on your device. The check runs local-first – the link does not have to be uploaded to a SafeShare server for this.
For individual links, SafeShare Free is enough – permanently and free of charge.
If you regularly check, explain or document links before sending – for example in newsletters, editorial content, customer communication or team approvals – SafeShare Link Review is the next step: understand, check, document.
Protocol, an optional subdomain, domain and path – plus an optional query string with parameters and a fragment.
The part after the question mark. It contains parameters as name-value pairs, separated by ampersands.
It marks the fragment and jumps to a spot on the page. It is functional and normally stays when cleaning.
SafeShare reduces recognized tracking extras in the query string. Domain, path and functional parts stay.
No. SafeShare is local-first. The cleanup happens in your browser. Links are not uploaded to SafeShare servers for this.
Check and clean individual links directly in the browser.
Check, understand and document links before sending.
Name-value pairs in the query string – and when they are needed.
The overview of measuring extras in links.