When you prepare your first website, you will encounter two related but distinct concepts: the domain name and the full URL. Understanding what each one does helps you read addresses correctly, plan your site structure, and communicate links clearly to collaborators.
What Questions Do Domain Names and URLs Each Answer?
Domain names are a key part of the Internet infrastructure. They provide a human-readable address for any web server available on the Internet. Computers reach each other through IP addresses, which are sequences of numbers that people find hard to remember and that might change over time. Domain names solve that problem by giving us a readable label we can type, share, and recall without memorizing numeric strings.1
A URL, or Uniform Resource Locator, goes one step further. It is the address of a unique resource on the internet and serves as one of the key mechanisms browsers use to retrieve published resources such as HTML pages, images, and documents. While a domain name identifies the server, a full URL specifies which particular resource on that server you want to reach. In theory, each valid URL points to a unique resource.2
Think of it this way: the domain name answers the question “which building?” while the full URL answers “which room in that building, and which shelf in that room?” For our exercise we will use a hypothetical address to see how these two levels of specificity work together. The address is https://example.org/notes/first-page?view=compact#intro and it is a made-up example created purely for breaking down the string. It does not represent a real page that exists or is live anywhere.
Identifying Each Part of the Example Address
Let us look at the example address piece by piece. The string begins with https, which is the scheme. The scheme indicates the protocol the browser must use to request the resource. For websites the protocol is usually HTTPS or its unsecured version HTTP. The scheme tells the browser which set of rules to follow when contacting the server.2
After the scheme comes the authority section, separated from the scheme by the character pattern ://. In our example the authority is example.org. This is the domain name, and it indicates which web server is being requested. The domain name itself has internal structure: org is the top-level domain, and example is the label that precedes it. Together they form the host portion that stays constant across every page on that server.21
Following the domain is the path: /notes/first-page. The path represents the location of the resource on the web server. In the early days of the web a path like this represented a physical file location on the server, but nowadays it is mostly an abstraction handled by web servers without any physical reality. The path tells you which resource on the server is being addressed.2
Keeping the Host the Same and Comparing Different Paths and Queries
Now let us keep the host portion of our example unchanged and vary other parts. Consider three strings that all share the same scheme and domain: https://example.org/notes/first-page?view=compact#intro, https://example.org/notes/second-page?view=full, and https://example.org/archive/summary. The domain example.org stays identical in all three. What changes is the path, the query, and whether a fragment is present.
The first and second strings share the same path directory, /notes/, but point to different pages within it: first-page versus second-page. They also carry different query parameters, view=compact versus view=full. The third string uses a completely different path, /archive/summary, and has no query string or fragment at all. These are three distinct strings, and a browser would treat each one as a separate address pointing to a different resource.
It is important to note that we are only observing the structure of these strings here. We are not making claims about what a server would actually return for each address or how it would process the parameters. Different web servers handle paths and parameters according to their own rules, and the only reliable way to know how a specific server handles them is by asking the server owner. Our goal is simply to recognize that changing the path or query produces a different URL string, even when the domain stays the same.
Creating an Address Note Card for a Hypothetical Project
Write down a short note card for any project where you plan to use or share web addresses. For our hypothetical example, the card might include four fields: the purpose of the address, the full URL string, the domain portion, and the path portion. The purpose field helps you remember why this address matters. In our case the purpose could read “demonstration address for learning URL structure.”
Record the full address exactly as it appears, including the scheme, the question mark, and the hash symbol. Even small differences in these characters change what the string means. For the example, the full address is https://example.org/notes/first-page?view=compact#intro. Below it, note that the domain is example.org and the path is /notes/first-page. This separation makes it easier to discuss individual parts with others or to check whether a link was copied correctly.
You might also add a line noting which parts are optional. In our example, the query string and the fragment are both optional components. If you removed ?view=compact#intro entirely, you would still have a valid URL pointing to the same path on the same server. Keeping track of which parts are essential and which are supplementary helps when you later need to share a simplified version of the address or troubleshoot why a link behaves differently than expected.
Verifying the Note Card by Manual Copy and Labeling
Check your note card by copying the full address into a plain text editor and then marking each boundary manually. Place a space or a line break after the scheme, after the domain, after the path, and before the query and fragment. This visual separation makes it much easier to spot a missing slash, a misplaced question mark, or a typo in the domain portion.
Use a consistent labeling system so that every note card you create follows the same format. For instance, you might label the scheme as “protocol,” the domain as “host,” the path as “resource path,” the query as “parameters,” and the fragment as “anchor.” Keeping labels consistent means that when you return to the card weeks later, you will not have to re-learn your own shorthand.
Record the date you created the card and the context in which you plan to use the address. If the address belongs to a hypothetical exercise like ours, note that clearly so you do not later mistake it for a live link. If it belongs to a real project, note the project name. This small habit prevents confusion when you accumulate multiple cards over time and need to distinguish working examples from production addresses.
Keeping Your Record for Future Writing and Communication
Once your note card is verified, store it somewhere you will actually look again. A simple text file in your project folder works well for most people. The format matters less than the habit of keeping the record accessible. When you write documentation, share links with collaborators, or debug an address that is not loading the way you expect, having the broken-down version saved saves you from re-parsing the string from scratch.
You can also reuse the same card format when you encounter unfamiliar addresses in other contexts. If a colleague sends you a long URL and you need to understand what it points to, break it down using the same labels: scheme, host, path, parameters, fragment. Writing those labels next to the unfamiliar string turns a confusing sequence of characters into a structured description you can reason about.
The choices you make about how detailed your cards are depend on your own workflow. Some people only need the domain and path; others want every parameter documented. There is no single correct level of detail. What matters is that your future self can read the card and immediately understand what each part of the address does, without having to look up the rules again. That self-sufficiency is the practical goal of learning URL structure before your site goes live.
Frequently asked questions
Is the domain name the same thing as the URL?
No. The domain name identifies the web server, while the full URL identifies a specific resource on that server. A URL includes the domain name as one of its parts, along with the scheme, path, and optionally a query string and fragment.2
What does the question mark in a URL do?
The question mark signals the start of the query string. Everything after it consists of key/value pairs that provide extra parameters to the web server. In our example, ?view=compact tells the server a parameter named view with the value compact.2
Does the fragment after the hash symbol get sent to the server?
No. The part after the hash symbol, also known as the fragment identifier, is never sent to the server with the request. It is used by the browser to scroll to a bookmarked spot within the resource itself.2