A URL (Uniform Resource Locator), often called a web address, is a reference to a unique resource on the internet. It specifies both the digital location of a resource and the mechanism used to retrieve it. For SEO practitioners, a clean URL structure ensures that search engines can crawl, index, and understand a website's content hierarchy efficiently.
Entity Tracking
- URL: A reference to a unique resource on the internet specifying its location and the mechanism for retrieving it.
- Scheme: The part of a URL indicating which protocol (like HTTPS or mailto) the browser must use to request a resource.
- Domain Name: The unique identifier for a web server, composed of labels separated by dots like "example.com."
- Path: The component of a URL following the domain and port that specifies the location of a specific resource or file.
- Query String: A series of parameters following a question mark used to pass non-hierarchical data to a web server.
- Fragment: An optional identifier preceded by a hash symbol that points to a specific location or anchor within a resource.
- Top-Level Domain (TLD): The highest level of the domain name system hierarchy, appearing after the final dot in a URL (e.g., .com).
- Second-Level Domain (SLD): The part of a domain name that directly precedes the top-level domain, typically representing the brand or organization name.
- Effective Top-Level Domain (eTLD): An entry in the Public Suffix List under which domains can be registered, such as "com.au" or "github.io."
- Authority: The component of a URL containing the domain name and port, separated from the scheme by "://".
What is URL Structure?
URL structure is the hierarchical organization of components that make up a web address. Modern URLs follow a generic syntax established when the [Uniform Resource Locator was first defined in 1994 via RFC 1738] (Wikipedia). This structure combines a domain name system with a file path syntax, using slashes to separate directories and files.
The syntax for an absolute URL typically includes a scheme, an authority, a path, a query string, and a fragment. While some parts are mandatory for the browser to locate a resource, others are optional and used to provide extra data to the server or browser.
Why URL Structure Matters
- Crawl Efficiency: Simple structures help search engines like Google discover content without consuming excessive bandwidth.
- User Experience: Human-readable or "semantic" URLs clarify where a user is and what they are viewing.
- SEO Classification: Search engines use the words in a URL to help classify and rank associated pages.
- Security: Using the HTTPS scheme ensures data is encrypted, which is a recognized ranking factor.
- Analytics: URL parameters allow marketers to track the success of specific promotional campaigns.
How URL Structure Works
The URL acts as a set of directions for the browser. It follows a specific order of significance from left to right.
- Scheme: The protocol used to exchange data. While HTTPS is the standard for web pages, other schemes like mailto: or ftp: perform different functions.
- Authority: This includes the domain name (the "city" in a postal address) and the port. [Standard ports are 80 for HTTP and 443 for HTTPS] (MDN), though these are usually omitted if they follow the default.
- Path: This specifies the location of the resource on the web server. It often mimics a physical file system, though it is usually an abstraction today.
- Query String: Introduced by a question mark, this contains key-value pairs (e.g., ?id=123) that provide extra instructions to the server.
- Fragment: Marked by a hash (#), this points to a specific anchor within the resource itself. [Fragment identifiers are never sent to the server with the request] (MDN).
Best Practices
- Use Descriptive Words: Replace long ID numbers with readable words that describe the page content.
- Separate Words with Hyphens: Use hyphens (-) instead of underscores (_) to separate words. Search engines and users identify concepts better when hyphens are used.
- Maintain Case Consistency: URLs are case-sensitive. Treat /apple and /APPLE as distinct addresses and use lowercase for all URLs to avoid indexing issues.
- Match Audience Language: If your primary audience speaks German, use German words in the URL slug rather than English.
- Keep it Simple: [Google Search recommends following IETF STD 66] (Google Search Central) and percent-encoding reserved characters to ensure the structure is crawlable.
- Limit Parameters: Trim unnecessary query parameters that do not change page content to avoid creating duplicate URL versions.
Common Mistakes
Mistake: Using underscores to separate words.
Fix: Use hyphens, as underscores are often used in programming to keep concepts together, which can confuse search engine identification.
Mistake: Relying on URL fragments for content changes.
Fix: Use the History API. Google Search generally does not support fragments for changing a page’s content.
Mistake: Creating "Infinite" URL spaces with dynamic calendars.
Fix: Add a nofollow attribute to links pointing to future dates or use robots.txt to block access to these pages.
Mistake: Broken relative links.
Fix: Use root-relative URLs (starting with /) in links to prevent the creation of "bogus" URLs if a parent-relative link is placed on the wrong page.
URL vs Origin
Understanding the difference between an origin and a site is critical for managing cookies and security.
| Feature | URL | Origin | Site (eTLD+1) |
|---|---|---|---|
| Includes Scheme | Yes | Yes | Yes |
| Includes Port | Yes | Yes (if non-default) | No |
| Includes Path | Yes | No | No |
| Includes Domain | Yes | Yes | Yes (Registrable only) |
FAQ
What is the difference between an absolute and a relative URL?
An absolute URL contains the complete address, including the scheme and domain name. A relative URL is used within a document and relies on the context of that document's URL to fill in missing parts. For example, a link starting with / is a root-relative URL that tells the browser to look from the top root of the server.
Are URLs and URIs the same thing?
A URL is a specific type of URI (Uniform Resource Identifier). While people use the terms interchangeably, a URL specifically implies the location and the mechanism to access the resource, which is not true of every URI.
What is an eTLD+1?
An eTLD+1, also known as a registrable domain, consists of the Effective Top-Level Domain (like .com or .co.uk) plus one label before it (like example.com). This is the part typically under the control of the domain registrant.
How does Google handle case sensitivity in URLs?
Google treats URLs as case-sensitive. If your server treats /APPLE and /apple as the same page, Google may still view them as two distinct URLs. This can lead to inefficient crawling or duplicate content issues if you do not standardize on lowercase.
Why should I avoid using underscores in my URL structure?
For historical reasons, underscores are used in programming to denote that concepts should be kept together. Search engines may not recognize underscores as word separators, making it harder for them to identify specific keywords in your URL.
What is Punycode?
Punycode is a system used to convert Internationalized Resource Identifiers (IRIs) that contain non-ASCII characters (like Chinese or Japanese characters) into a format the Domain Name System can understand. For example, a Chinese domain name will be converted into a string starting with "xn--" to identify it as an internationalized domain.
