What Is a URL? A Complete Guide to Web Addresses

A URL (Uniform Resource Locator) is the address you type, click, or paste to reach a specific page, file, or resource on the internet. It's what shows up in your browser's address bar, what you copy to share an article, and what search engines index to rank your pages. Every website, image, PDF, and email link on the web has one.

Understanding how a URL is built helps you write cleaner web addresses, troubleshoot broken links, and make smarter choices about your own site's structure.

In this guide, we'll break down exactly what a URL is, walk through every part of its structure with real examples, clear up the confusion between a URL and a domain name, and answer the questions people ask most about web addresses.

What does URL stand for?

URL stands for Uniform Resource Locator. The "uniform" part means every URL follows the same standardized format, no matter what site or resource it points to. That consistency is what lets browsers, servers, and search engines interpret billions of different addresses using one shared set of rules.

A URL is technically a specific type of URI (Uniform Resource Identifier). A URI is the broader category: it's any string that identifies a resource, whether that resource can be located and retrieved (like a URL) or just named without a way to access it. In everyday use, though, "URL" and "web address" mean the same thing, and that's how we'll use it here.

What is a URL, in plain English?

Think of a URL as a mailing address, but for the internet. A street address tells the postal service which country, city, street, and house number to deliver a letter to. A URL tells your browser which protocol to use, which server to contact, and which exact file or page to retrieve once it gets there.

When you type a URL into your address bar or click a link, here's what happens behind the scenes:

1. Your browser reads the URL and identifies the domain name inside it.

2. Your browser asks a DNS (Domain Name System) server to translate that domain name into an IP address, since computers route traffic by IP address, not by name.

3. Your browser connects to the server at that IP address using the protocol specified in the URL (usually HTTPS).

4. The server locates the exact file or page named in the rest of the URL and sends it back to your browser to display.

That whole exchange typically takes a fraction of a second, but it's the reason a random string of letters after "https://" reliably takes you to the right page every time.

The parts of a URL, explained

A full URL can include up to six distinct parts, though most everyday URLs only use two or three of them. Here's a URL broken into its components:

https://www.example.com:443/blog/what-is-a-url?ref=newsletter#section-2

• Scheme (protocol): https://

• Subdomain: www

• Domain name: example.com

• Port: :443

• Path: /blog/what-is-a-url

• Query string (parameters): ?ref=newsletter

• Fragment (anchor): #section-2

Let's go through each one.

Scheme (protocol)

The scheme is the first part of any URL, and it tells the browser how to communicate with the server. The two you'll see constantly are:

• HTTP (Hypertext Transfer Protocol): the original standard for transferring web pages. Data sent over HTTP isn't encrypted.

• HTTPS (Hypertext Transfer Protocol Secure): the encrypted version of HTTP. It uses an SSL/TLS certificate to scramble data in transit, protecting anything a visitor types in, like passwords or payment details.

Browsers now flag HTTP-only sites as "not secure," so HTTPS is effectively the standard for any public website today. You'll also run into other schemes outside of browsing, like mailto: (which opens a new email addressed to a specific address) and ftp:// (used for transferring files between computers).

Subdomain

The subdomain sits right before the main domain name, separated by a dot. The most common one is www, though it's optional on most modern sites. Businesses also use subdomains to organize different sections of a site, like blog.example.com or shop.example.com. Each subdomain can even point to a completely different part of a site's infrastructure while still living under the same overall domain name.

Domain name

The domain name is the human-readable label that identifies a specific website, like example.com. It's made up of a second-level domain (the unique name, such as "example") and a top-level domain, or TLD (the extension, such as ".com," ".org," or ".net"). You register a domain name through a domain registrar, and once it's yours, no one else can use that exact name for as long as your registration stays active.

This is also the part of a URL people confuse most often with the URL itself, so we'll cover that distinction in detail below.

Port

The port number specifies which "door" on the server a request should go through. It's rarely visible in everyday browsing because browsers use default ports automatically: port 80 for HTTP and port 443 for HTTPS. You'll mostly encounter an explicit port number in development environments or when accessing a service that isn't running on the standard web ports.

Path

The path points to the specific file, page, or folder on the server, similar to a folder structure on your computer. In example.com/blog/what-is-a-url, the path is /blog/what-is-a-url, which tells the server to serve up the "what-is-a-url" page inside the "blog" section of the site. A clean, descriptive path makes a URL easier for both humans and search engines to understand at a glance.

Query string (parameters)

Anything after a question mark in a URL is the query string, made up of one or more parameters in the format key=value, separated by ampersands. Query strings are commonly used to power search results, track marketing campaigns (UTM parameters are a familiar example), or filter and sort content on a page. In ?ref=newsletter, the parameter ref is set to the value newsletter, which might tell an analytics tool that a visitor arrived from an email newsletter link.

Fragment (anchor)

The fragment comes after a hash symbol (#) and points to a specific section within a page, rather than a separate page entirely. Clicking a "jump to section" link on a long article, for instance, often lands you on a URL ending in something like #section-2. Fragments aren't sent to the server as part of the request; your browser handles the scrolling locally once the full page has already loaded.

A brief history of the URL

The URL wasn't always around. In the early days of computer networking, machines identified each other purely by numeric IP addresses, a system that worked fine for a handful of research computers but became unwieldy the moment networks started to grow. The Domain Name System (DNS) arrived in 1983 to solve part of that problem, letting people use memorable names instead of strings of numbers.

The URL format itself came a bit later, developed by Tim Berners-Lee alongside the rest of the World Wide Web in the early 1990s. Berners-Lee needed a consistent way to reference any document, image, or resource across a network of linked pages, and the URL was his answer: a single, standardized syntax that could point to absolutely anything, anywhere on the emerging web. The format was formally standardized in 1994 by the Internet Engineering Task Force (IETF), and aside from incremental refinements, the same basic structure has powered every web address you've ever clicked since.

Common types of URLs you'll encounter

Not every URL points to a web page. The scheme at the start determines what kind of resource is on the other end, and a few schemes show up often enough to be worth recognizing:

• HTTP/HTTPS URLs: the standard for web pages, by far the most common type you'll interact with day to day.

• Mailto URLs: written as mailto:someone@example.com, these open a new message in the visitor's default email application instead of loading a page. You'll often see them behind "Contact us" buttons.

• FTP URLs: written as ftp://example.com/files/, these use the File Transfer Protocol to upload or download files directly, rather than displaying a rendered page.

• Tel URLs: written as tel:+15551234567, these prompt a phone or device to start a call when tapped, common on mobile-friendly contact pages.

• Data URLs: these embed the resource itself, like a small image, directly inside the URL string as encoded data, rather than pointing to a separate file on a server.

For the vast majority of everyday browsing and website management, you'll be working with HTTP and HTTPS URLs, but recognizing the other schemes helps you understand links you might come across elsewhere, like in an email signature or a downloaded document.

URL encoding: why some characters turn into percent signs

URLs can only officially contain a limited set of characters, defined by the ASCII character set: letters, numbers, and a handful of punctuation marks like hyphens, periods, and underscores. Spaces, accented letters, and many symbols aren't part of that allowed set, so when they need to appear in a URL, they get converted into a percent sign followed by a code, a process called percent-encoding or URL encoding.

A space, for example, is commonly encoded as %20 (you'll sometimes see it written as a plus sign, +, instead, depending on the context). An accented character like "é" might turn into something like %C3%A9. This is why a URL copied from a search bar sometimes looks cluttered with unfamiliar percent signs and letters; the browser is simply representing characters that aren't valid in a raw URL.

For your own website, the practical takeaway is simple: stick to lowercase letters, numbers, and hyphens in your URLs whenever possible. It keeps addresses short, readable, and free of the encoding clutter that makes a link harder to share or type from memory.

URLs and phishing: what to watch for

Because a URL is the main thing people rely on to judge whether a site is legitimate, it's also a favorite target for scammers. Phishing attacks often use URLs that are designed to look almost identical to a trusted domain at a glance, swapping in a lookalike character, adding an extra word, or using a completely different top-level domain than the real site.

A few habits make it much harder to fall for a spoofed URL:

• Read the domain name carefully, not just the beginning of the URL. A link like example.com.security-check.net is not the same site as example.com; the real domain is security-check.net, with "example.com" just tacked on as a misleading subdomain.

• Check for HTTPS, but don't treat it as a full guarantee of legitimacy. HTTPS confirms the connection is encrypted, not that the site itself is trustworthy; plenty of scam sites use HTTPS too.

• Hover before you click. Most browsers and email clients show the destination URL in a status bar or tooltip when you hover over a link, letting you verify where it actually leads before committing to a click.

• Be extra cautious with shortened URLs. Link shorteners hide the real destination domain entirely, which is convenient for sharing but makes it impossible to verify a link at a glance without following it.

URL vs. domain name: what's the difference?

This is one of the most common points of confusion for anyone new to building a website, so it's worth spelling out clearly.

A domain name is your website's overall address, the one part of a URL that you actually register and own, like example.com. A URL is the complete, specific address to one exact resource, which includes the domain name plus everything else needed to locate that particular page, image, or file.

Put another way: your domain name gets a visitor to your website. The URL gets them to the exact page they're looking for within it. A single domain name can support thousands of different URLs, one for every page, post, and file on the site, but each of those URLs still shares that same domain name.

	Domain name	URL
What it is	The human-readable name for a website	The complete address to a specific resource
Example	example.com	https://www.example.com/blog/what-is-a-url
Can you own it?	Yes, through registration with a registrar	No, it isn't bought or owned separately
How many per site?	One per registered domain	Potentially thousands, one per page or file
What it controls	Your brand identity and where email/hosting point	Which exact page, image, or file loads

If you're still deciding on a domain name for a new site, running it through a domain name search tool up front will show you what's available and help you avoid picking a name someone else already holds.

Is a URL the same as a link?

Not quite, though they're closely related. A URL is the address itself, the text string. A link (or hyperlink) is the clickable element on a page, usually text or an image, that uses a URL behind the scenes to send a visitor somewhere when they click it. Every link points to a URL, but not every URL you encounter is wrapped in a clickable link; you might just as easily see one typed out in a document or spoken aloud.

How long can a URL be?

Most modern browsers can technically handle URLs of over 2,000 characters, and some support even more, but that doesn't mean you should aim anywhere near that limit. Long, cluttered URLs are harder for visitors to read, harder to share cleanly, and can actually work against you in search results, since search engines tend to favor concise, descriptive paths over long strings packed with parameters. As a practical guideline, keeping a URL path under around 75 to 100 characters, using hyphens instead of underscores between words, and skipping unnecessary parameters where possible will keep your web addresses clean and easy to work with.

Are URLs case-sensitive?

It depends on which part of the URL you're looking at. The domain name is not case-sensitive. Example.com and example.com will take you to the identical website. However, the path, query string, and fragment can be case-sensitive, depending on how the web server is configured. That means example.com/Blog and example.com/blog might load two completely different pages, or one might return a "page not found" error while the other works fine. As a habit, it's safest to always use lowercase letters

throughout your own URLs to avoid duplicate-content issues and broken links.

Do URLs expire?

The URL itself doesn't expire, but the resources behind it can disappear or move, which is exactly what causes broken links (commonly seen as a "404 Not Found" error). A URL will only keep working for as long as three things stay true: the underlying domain name registration remains active, the hosting or server behind it stays online, and the specific file or page at that path hasn't been deleted, renamed, or moved without a redirect in place. If you ever restructure your own site, setting up a redirect from the old URL to the new one preserves any traffic, bookmarks, and search engine rankings that pointed to the original address.

Best practices for structuring your own URLs

If you manage a website, the URLs you choose for each page are one of the small details that quietly add up over time. A few practical guidelines will keep them working in your favor rather than against you:

• Keep it short and descriptive. A path like /blog/what-is-a-url tells both visitors and search engines exactly what the page covers. A path like /blog/post?id=48213 tells them nothing without opening it.

• Use hyphens, not underscores or spaces. Search engines treat hyphens as word separators, so what-is-a-url reads as three distinct words. Underscores and raw spaces don't get parsed the same way, and spaces get encoded into clutter.

• Stick to lowercase. Since paths can be case-sensitive on some servers, using lowercase consistently avoids accidentally creating two different URLs for what's meant to be the same page.

• Avoid unnecessary parameters in permanent links. Query strings are useful for tracking and filtering, but a URL packed with parameters is harder to read, share, and remember than a clean static path. Save parameters for temporary or dynamic uses, like campaign tracking, rather than a page's permanent address.

• Set up redirects when a URL has to change. If you rename a page, restructure your site, or switch domains, a 301 redirect from the old URL to the new one preserves search rankings and keeps old bookmarks and shared links from breaking.

• Match your URL structure to your site's hierarchy. Nesting related pages under a shared path, like /blog/, /products/, or /help/, makes your site easier to navigate and signals a logical structure to search engines.

None of these practices require technical expertise to implement. Most website builders, including Wix, generate clean, editable URLs automatically when you create a new page, so you can apply these habits without touching any code.

Why understanding URL structure matters for your website

If you're building or managing a website, a firm grasp of URL structure pays off in a few concrete ways:

• Search visibility. Search engines read the words in your URL path as a signal of what a page is about, so short, descriptive, keyword-relevant paths tend to perform better than long, auto-generated strings of numbers and symbols.

• User trust. A clean HTTPS URL with a readable path looks more trustworthy to a visitor than a long jumble of parameters, and that trust translates into more clicks and fewer people bouncing off the page.

• Easier troubleshooting. When a link breaks, being able to read a URL and understand which part failed (a mistyped domain, a removed page, a dead fragment) makes it much faster to diagnose and fix.

• Cleaner marketing. Query parameters let you track exactly which email, ad, or social post sent a visitor your way, which only works if you understand how to build and read them correctly.

None of this requires memorizing the technical specification. Just knowing the handful of parts covered above, scheme, domain, path, query string, and fragment, is enough to read almost any URL you'll come across and make informed decisions about your own site's addresses.

Every one of those URLs starts with a domain name you choose and register. If you're still shopping for the right one, you can buy a domain and get your web address secured before you build anything else.

What Is a URL FAQ

What is an example of a URL?

https://www.wix.com/blog/what-is-a-url is a complete URL. It breaks down into the scheme (https://), the subdomain (www), the domain name (wix.com), and the path (/blog/what-is-a-url), which together point a browser to one specific page.

What's the difference between a URL and a website address?

There isn't one. "Web address" and "URL" describe the same thing: the complete string used to locate a specific page or file on the internet. "Web address" is simply the more casual, everyday term.

Can two different URLs point to the same page?

Yes. This commonly happens with www versus non-www versions of a site, or with trailing slashes at the end of a path. Site owners typically set up a redirect so that all variations funnel visitors to one preferred, or "canonical," version of the URL, which also avoids confusing search engines with what looks like duplicate content.

What is a vanity URL?

A vanity URL is a shortened or customized web address chosen for a specific purpose, usually to make a link easier to remember, brand, or track, especially in marketing campaigns or on social media. It typically redirects behind the scenes to a longer, standard URL.

Do I need to buy a URL, or just a domain name?

You register and pay for a domain name, not a URL. Once you own the domain, you (or your website platform) create as many individual URLs as you need under it, for free, simply by publishing new pages.

What happens if I type a URL incorrectly?

If the domain name is wrong, your browser typically returns a "server not found" error, since it can't locate any server at that address. If the domain is correct but the path is wrong, you'll usually see a "404 Not Found" error, meaning the server exists but couldn't find that specific page.

Can a URL contain spaces?

Not directly. A raw space isn't a valid character in a URL, so any space gets automatically converted into %20 (or sometimes a plus sign) through URL encoding before the address is sent to a server. That's why you'll often see hyphens used in place of spaces when naming pages, since a hyphenated path stays clean and readable without needing any encoding at all.

Is www part of the domain name or the URL?

Technically, www is a subdomain, a separate label that sits in front of the main domain name. Many sites configure www and the plain domain (like example.com and www.example.com) to load the exact same content, which makes the distinction feel invisible in everyday use, but under the hood it's still a distinct part of the address, and both versions should redirect to one preferred version to avoid confusing search engines.