A Uniform Resource Locator (URL) is an address used to identify and locate a resource on the web. People commonly call a URL a web address because it tells a browser where a resource is located and how it can be accessed.
https://www.example.com/about
URLs are commonly associated with web pages, but they can identify other types of resources too, such as images, documents, files, or application endpoints.
A URL can contain several parts, including a scheme, host, port, path, query string, and fragment. Not every URL contains every one of these components.
Once you understand what those parts mean, even a long web address becomes much easier to read.
What Is a Uniform Resource Locator?
A Uniform Resource Locator is a structured address that identifies where a resource can be found and provides information about how it can be accessed.
Consider this example:
https://www.example.com/products/shoes
This URL tells a browser several useful things. It identifies the scheme being used, the host involved, and the path associated with the requested resource.
The important point is that a URL is more than a domain name.
In the example above, example.com is only one part of the complete address. The full URL includes other information that helps software understand where the resource is and how the address should be interpreted.
In practical terms, you can think of a URL as the structured address for a resource on the web.
What Does URL Stand For?
URL stands for Uniform Resource Locator.
The term can be broken into three parts.
Uniform reflects the use of a common, standardized syntax for identifying resources.
Resource refers to the thing being identified. It might be a webpage, image, document, file, or another resource available through a network.
Locator reflects the role of the URL in identifying where that resource can be found or accessed.
You do not need to memorize the terminology to use URLs. For everyday purposes, the main idea is simple:
A URL is an address used to reach a particular resource.
Is a URL the Same as a Web Address?
In normal conversation, URL and web address are often used to mean the same thing.
For example, if someone says, “Enter the web address in your browser,” they are usually asking you to enter a URL.
https://www.example.com/contact
This is a URL that identifies a particular resource on that website.
“Web address” is the more familiar everyday term, while “Uniform Resource Locator” is the technical name.
However, URLs are not limited only to the kind of webpage addresses that people manually type into a browser. Different URL schemes and structures can be used for different types of resources and applications.
What Are the Parts of a URL?
One of the easiest ways to understand a URL is to break a complete example into separate components.
Consider:
https://www.example.com/blog/url-guide?source=search#parts
| Component | Example |
|---|---|
| Scheme | https |
| Host | www.example.com |
| Path | /blog/url-guide |
| Query | ?source=search |
| Fragment | #parts |
A URL may also contain a port.
These are possible URL components, not a checklist that every URL must contain.
Scheme
In this URL:
https://www.example.com/blog/url-guide
the scheme is:
https
The scheme appears before the colon.
On ordinary websites, the schemes you will most often see are http and https.
Technically, scheme is the correct name for this URL component. It is common to hear people casually refer to it as the “protocol,” but those terms are not always interchangeable in a strict technical sense.
For beginners, the useful takeaway is that the scheme helps indicate how the rest of the URL should be interpreted and what type of access mechanism is involved.
Host and Domain Name
In:
https://www.example.com/blog/url-guide
the host is:
www.example.com
The host identifies the network location involved in the request.
People often describe this as the domain portion of the URL, although domain and hostname terminology can become more specific in technical discussions.
For example:
example.com
is the domain, while:
www.example.com
can function as the hostname used in the URL.
The domain or host is part of the URL. It is not the complete URL.
Port
A URL can also contain an explicit port.
For example:
https://example.com:8443/account
Here:
8443
is the port.
A port helps identify the network service being addressed on the host.
Most people rarely see ports in everyday website URLs because common schemes can use default ports without displaying them explicitly.
That is why a normal URL such as:
https://example.com
can work without showing a port number.
Path
The path is one of the most useful URL components to understand.
Consider:
https://www.example.com/blog/url-guide
The path is:
/blog/url-guide
The path follows the host and helps identify a resource or location within the website's URL structure.
Now consider:
https://example.com/products/shoes?size=10#reviews
The path is still:
/products/shoes
The section beginning with ? is not part of the path.
The section beginning with # is not part of the path either.
So if someone asks “What is the path in this URL?”, look for the part after the host and before any query string or fragment.
Understanding this distinction helps prevent one of the most common URL misunderstandings: treating everything after the domain as the path.
Query String and Query Parameters
A query begins after a question mark.
For example:
https://example.com/products/shoes?size=10
The query portion is:
size=10
The ? indicates where the query begins.
Queries are commonly used to pass additional information to a website or application. Depending on how a site is built, that information might relate to filtering, search terms, tracking values, sorting, or other application-specific data.
A URL can also contain multiple parameters.
A query string is separate from the path.
The presence of query parameters also does not automatically mean that a URL is bad for SEO. Their effect depends on how the website uses and manages them.
Fragment
A fragment begins with #.
For example:
https://example.com/page#pricing
The fragment is:
pricing
A fragment can identify a particular section or state within the resource represented by the rest of the URL.
On a normal webpage, a fragment may be used to move the browser directly to a particular section of the page.
For HTTP and HTTPS URLs, the fragment is generally handled by the browser and is not sent to the server as part of the HTTP request.
The fragment is therefore separate from both the path and the query.
A Complete Web Address Example
Consider this complete web address:
https://www.example.com/products/shoes?size=10#reviews
You can read it from left to right.
- Scheme:
https - Host:
www.example.com - Path:
/products/shoes - Query:
?size=10 - Fragment:
#reviews
The browser interprets this URL structure, identifies the host, requests the relevant path and query where applicable, and can use the fragment for a location or state within the resource.
Once you learn to separate these components, a long URL becomes much easier to understand.
Absolute vs Relative URLs
An absolute URL includes its own scheme and does not depend on a base URL for interpretation.
For example:
https://example.com/about
A relative reference, by contrast, is interpreted using a base URL.
For example:
/about
If that reference appears on https://example.com, the browser can resolve it relative to that website.
You may encounter relative references in website code, navigation menus, templates, or application routes.
For most readers, the practical difference is straightforward: an absolute URL carries its own scheme, while a relative reference depends on context.
If you want to understand how URLs are used as link destinations inside HTML, RankCrow's HTML SEO article covers crawlable links and href implementation in more detail.
URL vs URI: Are They the Same?
URL and URI are closely related terms, but it is better not to treat them as universally identical.
A URI, or Uniform Resource Identifier, is a broader standards-oriented identifier concept.
RFC 3986 describes a URL as a subset of URIs that, in addition to identifying a resource, provides a means of locating it.
Modern browser standards, particularly the WHATWG URL Standard, generally standardize on the term URL for practical web parsing and APIs.
For most beginners, the useful takeaway is:
URI is the broader standards-oriented identifier concept, while URL is the term you will most commonly encounter when dealing with web addresses, browsers, links, and website resources.
You do not need to understand every historical URI and URN distinction to read normal website URLs correctly.
Why URLs Matter for Websites
URLs are fundamental to how websites work.
A browser uses URLs to request resources. Links use URLs as destinations. People can copy and share URLs to send someone directly to a particular page or resource.
URLs also help distinguish resources from one another.
For example:
https://example.com/products
and:
https://example.com/products/running-shoes
represent different addresses and may correspond to different resources.
A sensible URL structure can also support understandable website organization.
URLs then work together with navigation and internal links so users and crawlers can move between resources.
For a deeper look at how pages should be connected through links, RankCrow's SEO Internal Linking Strategy Guide covers that topic separately.
Do URLs Matter for SEO?
URLs are part of a website's technical and content architecture, but a URL alone does not determine whether a page will rank.
Clear, understandable URLs can make addresses easier for people to interpret.
Google recommends readable, descriptive URLs where practical.
That does not mean putting a keyword in a URL guarantees better rankings, the shortest possible URL automatically ranks higher, every parameter URL is harmful, changing an established URL automatically improves SEO, or a particular URL structure guarantees indexing.
Google Search can also treat URLs that differ by case as distinct, particularly in path-like portions of a URL, so consistent casing is useful.
When URLs change, or when multiple URLs may represent the same or similar content, broader technical considerations such as redirects, canonicalization, internal linking, and indexing can become relevant.
Those topics go beyond the basic definition of a URL.
For practical advice on creating and managing sensible website URLs, see RankCrow's SEO for a New Website article.
For technical issues involving canonicals, redirects, indexability, and similar concerns, the Technical SEO Issues Guide provides the more appropriate deeper explanation.
Common URL Mistakes and Misunderstandings
Several URL concepts are commonly confused.
A domain name is not the complete URL. In:
https://example.com/blog/article
example.com is only part of the address.
Likewise, /blog/article is only the path.
In:
https://example.com/products?color=black
the path is /products, while the query starts after ?.
A URL also does not need to include www.
And URLs are not limited to ordinary HTML webpages. They can identify different types of resources.
Another common misunderstanding is assuming that the URL visible in a browser must always be the site's preferred canonical URL.
Canonicalization is a separate technical concept concerned with selecting a representative URL when multiple URLs contain duplicate or very similar content.
If you need to understand how search engines discover and process URLs more broadly, RankCrow's Search Engine Indexing Guide explains crawling and indexing separately.
How to Read a URL Step by Step
Consider this example:
https://shop.example.com:8443/guides/shoe-care?source=email#cleaning
Start from the left.
- Scheme:
https - Host:
shop.example.com - Port:
8443 - Path:
/guides/shoe-care - Query:
?source=email - Fragment:
#cleaning
This gives you a repeatable way to read unfamiliar URLs.
Instead of treating the entire address as one long technical string, identify each component separately.
Once this becomes familiar, other website concepts such as internal links, redirects, canonical URLs, and crawlability become easier to understand.
Frequently Asked Questions
What does URL stand for?
URL stands for Uniform Resource Locator. It is an address used to identify and locate a resource, commonly on the web.
What is a URL example?
A simple URL example is https://example.com/about. In this address, https is the scheme, example.com is the host, and /about is the path.
Is a URL the same as a domain name?
No. A domain name can be one part of a URL, but a complete URL may also include a scheme, path, port, query, and fragment.
What is the path in a URL?
The path is the portion that normally follows the host and comes before the query or fragment. For example, in https://example.com/blog/seo?source=email, the path is /blog/seo.
Is a URL the same as a web address?
In everyday language, people commonly use “web address” to mean a URL. URL is the more technical term.
What is the difference between a URL and a URI?
URI is the broader standards-oriented identifier concept. URL is the term most commonly used for web addresses and resource locations in browsers and everyday web development.
Final Thoughts
A Uniform Resource Locator becomes much easier to understand once you stop treating it as one unexplained string.
A URL may contain a scheme, host, port, path, query, and fragment, and each component has a different role.
Not every URL contains every component.
For most people, the most useful skill is simply being able to look at a URL and identify its major parts.
Once you can do that, related concepts such as internal links, redirects, canonical URLs, crawlability, and website structure become easier to understand.
If you are reviewing an individual webpage, RankCrow's free page-level SEO analyzer can help inspect supported signals such as titles, meta descriptions, headings, links, HTTPS, canonical and indexability signals, and other page-level SEO checks. It does not crawl or audit the complete URL architecture of an entire website.