What Is a Website URL? A Complete Guide to Every Part

Think of a street address. The city and street get the mail carrier to the right neighborhood, and the house number gets them to the exact door. A website URL works the same way, telling your browser precisely where to go.

That full address has a name: the Uniform Resource Locator (URL). Every page you visit has its own, including the ones on your future site.

We’ll cover what each part does, how it differs from a domain and a web address, and how to read and choose one for your site.

What a Website URL Actually Is

Every page you publish has one, and it’s what visitors type to find you. Here’s how the term works and where people mix it up.

The address of any internet resource

A URL (short for Uniform Resource Locator) is the address of an internet resource, like a page, image, or file. Most people simply call it a web address.

A browser uses it to retrieve content, so a URL has two parts: a location (where the resource lives) and a retrieval mechanism (how the browser asks for it). The location answers where; the mechanism answers how.

What a URL can point to

Not every URL leads to a web page. A URL can point to:

• Web pages, images, and videos
• Documents and downloadable files, like a printable price list
• Email and database access
• Broken or moved resources

A broken or moved resource still has a URL, but that address may now lead to an error or nothing at all. A candle maker who printed her catalog link on business cards learned this the hard way when she reorganized her site.

She can’t reprint every card, so from now on she links only to pages she expects to keep.

How URLs and URIs relate

You’ll also meet URI (Uniform Resource Identifier), the broader category. A URL is one type of URI, and the difference is access: a URL implies how to reach the resource, not just what it’s called.

People use the two terms interchangeably all the time, and for a first website, that’s fine.

Real examples in the address bar

Type either of these into your browser’s address bar and the page loads:

• https://www.example.com
• https://www.facebook.com

The https:// at the front is the retrieval mechanism, telling the browser which set of rules to use when it asks for the page. Typing just example.com is a partial address, and your browser usually fills in the missing https:// on its own.

For your own site, share the full version so nobody has to guess.

When someone asks for your URL, it usually means they want the exact address they can type or tap to reach your site or one page of it.

When a wedding planner asks a photographer for her URL, the full address, not just the business name, lets her open the portfolio on her phone.

The Parts That Make up a URL

A URL (short for uniform resource locator) packs several instructions into one line of text. Each part answers a different question, so we’ll go through them from left to right.

Which protocol the browser uses first

Every URL starts with a protocol, the set of rules the browser follows to talk to the server. It’s usually http or https (short for HyperText Transfer Protocol, where the s means secure), followed by a colon and two slashes, like https://.

The protocol tells the browser how to connect, not where it’s going.

The domain, port and optional userinfo

Next comes the domain, the readable name people type, like yoursite.com. Sometimes an internet protocol (IP) address appears in its place: a string of numbers that identifies the server. An optional port can follow the domain after a colon, such as :8080.

Port 80 and port 443 are the defaults, which is why most addresses don’t show one. Before the domain, an optional userinfo (a username, sometimes with a password, followed by an @ sign) can appear, though you’ll rarely see it on a public site.

Where the resource sits on the server

After the domain comes the path, which points to a specific resource on the server, such as a page, image or file. At first, a path pointed straight to a physical file. Today it’s often an abstraction rather than a file you could open.

Segments are separated by slashes, like /shop/spring-bouquets, and some servers also accept extra information after the file name, called pathinfo. Clean URLs drop technical file endings so the address reads like a plain title.

A florist who keeps her spring arrangements at /spring-bouquets can send customers straight to that collection with one short link.

Extra settings added after the question mark

A query string starts with a question mark and holds key/value pairs, such as ?color=blue&size=large. Each key is a setting name, its value follows an equals sign, and the pairs are separated by ampersands (&).

Query strings control page display, like sorting a product list, or track where a click came from. The server decides how to read them, so the same settings can behave differently on different servers.

Jumping to a spot on the page

A fragment starts with a hash symbol (#) and points to a spot within the resource, such as a heading further down the page. The browser scrolls to that element once the page loads.

The fragment tells the browser where to scroll, not what to fetch, and it’s never sent to the server.

A wedding photographer can link a client to yoursite.com/services#pricing, and the client lands right on the prices instead of scrolling past the portfolio.

Mail address analogy and required parts

Think of a URL like a postal address. The protocol is the mail service, the domain is the street and city, and the path is the apartment number.

Formally, this structure follows a generic URI (uniform resource identifier) syntax, one set of rules meant for many kinds of addresses, not just websites. Only two parts are mandatory:

• Protocol: how the browser connects
• Domain: where it connects, by name or IP address

Everything else is optional: userinfo, port, path, query string and fragment. Two required parts, five optional extras.

Protocols and Schemes URLs Rely On

Every URL starts with a scheme, or protocol, that tells your browser how to connect.

Why HTTPS matters more than HTTP

HTTP (HyperText Transfer Protocol) is unencrypted, so anyone on the connection can read what it sends. HTTPS (HTTP Secure) uses SSL/TLS (Secure Sockets Layer and Transport Layer Security) to encrypt that traffic.

The one-letter difference matters a lot: data is encrypted instead of readable.

• An HTTPS connection protects passwords and card details typed into your login or checkout pages.
• Don’t launch a site that takes logins, payments or contact forms without HTTPS.

Other schemes like email and file links

Each one does a different job:

• mailto opens the visitor’s email app with a new message addressed to you.
• ftp (File Transfer Protocol) moves files to and from a server.
• data embeds small content, like an image, in the link.
• file points to a file stored on a computer.
• irc opens a chat channel on an IRC (Internet Relay Chat) network.

IANA (Internet Assigned Numbers Authority) maintains a registry of schemes. The URL Standard says new ones should be registered there, and mailto and ftp both appear on it.

How FTP and mailto links work

An FTP link follows the pattern ftp://server-address/folder. You’d use one to upload site files or download them back.

A mailto link can also prefill the subject and body. Add subject= and body= after a question mark, like mailto:address?subject=Cake%20order.

Picture a bakery with an “Order a cake” link in its footer. One click opens an email with the subject already filled in. Less typing for the customer. Reuse that link in your email signature.

Domains, Subdomains and How DNS Works

Here’s how the pieces fit together. A URL (uniform resource locator) is the full address people type, the domain name is the readable name inside it, and hosting is the rented space where your files live.

Finding a site’s domain and IP address

Your domain name identifies the web server, the computer that stores your site and sends it to visitors. The numeric alternative is an IP address (Internet Protocol address), a label made of numbers that points to that server.

Two formats exist:

• IPv4 (Internet Protocol version 4) uses four groups of numbers separated by dots.
• IPv6 (Internet Protocol version 6) uses longer groups of letters and numbers separated by colons.

If you’re curious, type the domain into an online IP lookup tool.

Using subdomains to organize site sections

A subdomain is a prefix placed before your main domain. In blog.yourbakery.com, the word blog is the subdomain.

Picture a local bakery with an online shop and a recipe blog. Using shop.yourbakery.com and blog.yourbakery.com keeps everything under one name, and customers always know where they are.

Many free builders give you a subdomain on their own domain, which is fine for a practice run. A custom domain like yourbakery.com is yours to take with you if you switch platforms.

A free subdomain is borrowed space, while a custom domain is your own address.

How DNS turns names into numbers

Names are for people. Numbers are for machines. The DNS (Domain Name System) bridges the two: when a visitor types yourbakery.com, it finds the matching IP address so the browser reaches the right server. You never have to memorize a single number.

Full Links Versus Relative Links

Every link on your site is a URL (uniform resource locator), but you’ll notice they aren’t all written the same way.

Full URLs that work from anywhere

A full URL holds everything a browser needs: the scheme (the https:// part), the domain and the page path, so it works anywhere. A bakery owner can print https://yourdomain.com/order on every takeout bag, and a customer at home taps straight through.

The address bar expects the full version, since a bare path like /order doesn’t have a page to start from.

The shorthand forms of relative links

A relative link skips part of the address and borrows the rest from the current page. Full links send people somewhere; relative links move them around. Less to type, same destination.

• Scheme-relative links start with //, like //yourdomain.com/order, and borrow the scheme from the current page.
• Domain-relative links start with /, like /order, and stay on your domain.
• Sub-resource paths load files such as images/logo.png. Visitors won’t click them.
• Going up with ../ moves up one folder, so from /blog/recipes/soup, ../contact lands on /blog/contact.
• Anchor-only links start with # and jump to a spot on the same page.

Linking inside your site and deep pages

Within your own site, relative links are the easier pick, since /services keeps working if your domain changes.

Deep links point past your homepage to a specific page. A wedding photographer can email couples a link straight to package prices, so they see the numbers in one tap.

Your anchor text (the clickable words) should show where the link goes, like ‘see our wedding packages,’ not a vague ‘click here.’

Practical Things to Do with URLs

Knowing what a URL is only helps once you can use one. Here’s how to grab one and what your browser does next.

Find and copy a URL quickly

The address bar is the long field across the top of your browser, and it shows the URL of the page you’re on. Take a wedding photographer emailing her portfolio to a couple.

Copying the link beats retyping it, since one missed letter sends them somewhere blank. So copy the address rather than retype it. Three quick ways:

• Select, copy and paste. Click the address bar, select the address, copy it, and paste it wherever you need it.
• Copy link address. Right-click any link and choose the copy link address option.
• Find it in your builder dashboard. Your site’s URL is shown there, so you can copy it instead of guessing.

What happens after you type a URL

Once you press enter, your browser works in two steps:

• Hostname lookup. The browser reads the hostname, the name part of the address, and checks an online directory for the server that holds your site. Think of it as looking up a name in a phone book to get a number.
• Page request. The browser navigates to the site, asks that server for your page, and displays what comes back.

Consider a florist whose shop just launched. If one letter in the hostname is off, the directory finds no server and no page appears.

A lost client is a lost order, so she checks every link before it goes on her business cards. One wrong letter, and nothing loads.

Readable, Meaningful and Global URLs

A good URL sends people to a page and tells them what’s there. It can also handle the letters your visitors actually use.

Clean URLs with meaningful words

Picture a potter selling mugs. A link like yourshop.com/mugs/blue-ceramic-mug tells shoppers what’s behind it, while random numbers tell them nothing. The words are there for people, not just for computers.

A guide from Search Engine Land notes that meaningful words in URLs may benefit a page’s search engine visibility.

A clean URL is easy to read and easy to edit. You can fix a typo or rename a page without decoding a jumble of codes.

A slug is the readable ending that names one page, like blue-ceramic-mug above. Keep slugs short and hyphenated.

URLs with characters from any language

Not every visitor reads English. Several standards handle other alphabets.

• Internationalized Resource Identifiers (IRIs) let addresses include Unicode characters, the system that gives letters from most writing systems their own codes.
• Punycode handles domain names, which follow stricter rules. It converts accented or non-Latin letters into plain characters.
• Percent-encoding handles the path after your domain by swapping special characters for a percent sign and a code. A Montréal bakery’s pâtisseries page becomes /p%C3%A2tisseries. Browsers usually handle this, so you’ll rarely type it yourself.
• UTF-8, a common way of turning characters into computer codes, is the first step. That’s why a copied link can look messier than the word you typed. Messy on the surface, same page underneath.

Where URLs Appear Across the Web

Your URL isn’t only the address up top. It also drives photos, buttons and scripts.

How links, images and scripts use URLs

A URL tells the browser where a file lives, not what it looks like. That one idea explains most of what happens on a page:

• Links send visitors to another page when they click.
• Images, video and audio load from the URL of their file.
• Scripts, stylesheets and iframes pull in code, styling or other pages from their own URLs.

Each file your page loads starts its URL with a protocol, such as HTTP (HyperText Transfer Protocol) or its secure version, HTTPS. Use HTTPS wherever you can.

A data URL packs a small file’s contents straight into the URL, so there’s no separate file to fetch. A bakery owner’s tiny logo suits this well, but a full product photo belongs in a normal image link. Small files only, please.

Forwarding visitors and shortening links

Addresses don’t always stay put, so a few tools keep old links working.

A redirect forwards anyone who opens an old address to the new one. A florist ending her spring sale can point that old page at her main shop, so last month’s flyer still leads somewhere.

A preferred domain is the version of your site you choose as the main one, with or without the www at the front. Redirects send visitors from the other version to it, so everyone lands on one address.

A URL shortener turns a long address into a short one that forwards to the original, which helps when space is tight. A wedding photographer printing a gallery link on a card needs one guests can type without mistakes.

Old links are still out there, so keep them pointing somewhere useful.

Putting Logins Directly in URLs

Some web addresses carry a login right in the text. Here’s how that works and why you should think twice before using it.

Adding a username and password to URLs

A URL can hold a username and password placed before the host, the domain name the address points to. The pattern has three parts:

• Username and password, joined by a colon
• An @ sign, which marks where the login ends
• The host, such as example.com

It looks like https://username:password@example.com. The method is used for HTTP authentication, the process where a server checks who’s asking before it shows a page. Normally, the browser pops up a small login box for those details.

Putting them in the URL bypasses that login dialog, so the page opens straight away.

Think of a freelance photographer who wants a client to see a private proof gallery without any fuss. Baking the details into the link gets the client straight in. It’s a handy shortcut, but it trades convenience for safety.

Why this practice is discouraged now

This practice is deprecated, meaning it’s no longer recommended, and the reason is security. A password written in clear text is readable by anyone who sees it, with no decoding needed.

Consider a bakery owner who texts the login link to a part-time employee. The password is now sitting in that message in plain view, readable by anyone who gets hold of the phone.

So when you set up your own site, log in through the page your platform provides, not through a link that carries your password. Keep the password out of the link.

How URLs Started and Got Standardized

Why does every web address look the way it does? The answer goes back to the early web, and the rules have been refined since.

Where the idea came from in 1994

Tim Berners-Lee defined the Uniform Resource Locator (URL) in 1994. The Internet Engineering Task Force (IETF) formalized it in RFC 1738, a Request for Comments document produced by one of its working groups.

A URL combines a domain name, the site’s address, with a file path, the route to one page inside it. Picture a florist who wants wedding clients to land on her wedding page.

The domain gets them to her shop, and the path /weddings takes them straight to the right room, so she can paste one link into an email.

The name says uniform rather than universal, because the goal is one consistent format for every resource. Not one giant place that holds them all.

The rules URLs follow today

RFC 3986 sets the generic syntax for Uniform Resource Identifiers (URIs), the broader family that URLs belong to. It leaves the details of each scheme (the https:// at the front of an address, for example) to other specifications.

The Web Hypertext Application Technology Working Group (WHATWG) publishes the URL Standard, a living standard that’s updated over time rather than frozen in one version.

The double slashes after the scheme? Sir Tim Berners-Lee has confessed they were “unnecessary.” You’ll still see them in every address, so treat them as a quirk of the format, not a detail to memorize.

A URL is more than a string of letters and slashes. Each part has a job, from the protocol at the front to the path at the end, and knowing those jobs makes any link easier to read and choose.

A domain is just one piece of the address, and it’s the part visitors will see and remember most.

Your URL is the address people type, share and remember, so give it the same care you’d give your own front door.

References

1. URI Generic Syntax — Summary: URI Resource Pages - IFLA CDNL Alliance for Digital Standards (ICABS) (Standards — loc.gov
2. RFC1738: Uniform Resource Locators (URL) — dl.acm.org (1994)
3. URL Standard Review Draft February 2026 — url.spec.whatwg.org (2026)
4. How to create SEO-friendly URLs — searchengineland.com (2026)
5. BBC NEWS | Technology | Berners-Lee ‘sorry’ for slashes — news.bbc.co.uk
6. URL Standard — url.spec.whatwg.org
7. Uniform Resource Locators (URL) — doi.org (1994)