A useful URL is stable, understandable and consistent with the page it identifies. When creating new URLs, use descriptive words in the audience's language and hyphens between words where appropriate. Do not rename established pages solely to fit a character count or an imagined limit on the number of slashes.
Choose a name that will still describe the page later
Google's URL-structure guidance recommends simple, descriptive URLs and a logical organization. The purpose is understandable navigation and efficient crawling, not a guaranteed percentage increase in clicks.
| New page | Possible URL | Why it fits |
|---|---|---|
| A stable product model | /products/model-a-pump/ | Identifies the product without embedding a temporary promotion |
| A maintenance tutorial | /guides/pump-seal-replacement/ | Describes the task and its content group |
| A German-language category | /de/produkte/pumpen/ | Uses the intended language and a consistent locale path |
| A dated event | /events/2026-industry-meeting/ | The year is part of the event's identity |
These are naming examples, not migration instructions. A numeric product identifier can still be useful, and an existing URL is not unindexable merely because it contains one. Include information that distinguishes the page; avoid repeating several keyword variants in its path.
Hyphens, capitalization and non-English characters
Google recommends hyphens rather than underscores to help identify concepts. That recommendation is not evidence of an underscore penalty, a millisecond processing limit or a reason to replace every historical URL.
Paths are case sensitive in Google's URL handling. If your server treats upper- and lower-case forms as the same content, choose a consistent form for generated links and the canonical URL. Do not lowercase all existing paths without checking their actual routing.
Words in Chinese, Japanese and other audience languages are valid choices. Encode non-ASCII characters appropriately when producing links, using the CMS or a proper URL library. A percent-encoded address is not automatically an error, and indiscriminately decoding and re-encoding a stored path can create a different URL.
Directory depth is not the same as navigation depth
The number of slashes in a path does not tell you how many links a reader must follow to reach the page. A deeper-looking address can be directly linked from a relevant category; a short address can have no useful internal path at all.
Organize URLs according to the site's content and maintenance needs. Then separately inspect navigation and contextual internal links. Google does not publish a rule that each extra directory loses 15% of a page's value.
Handle parameters according to what they change
Parameters are not inherently bad. Decide whether each one changes meaningful content, changes its presentation, or only tracks a visit. The difficult cases are systems that generate very large numbers of near-identical combinations.
- Tracking and session values: avoid distributing unnecessary URL variations through normal internal links.
- Sorting: determine whether the view needs to be independently discoverable or should share a canonical destination.
- Filters: identify useful landing pages separately from redundant combinations and invalid states.
- Pagination: preserve usable paths to the items; do not assume every page is a duplicate of page one.
Use standard parameter syntax such as ?color=blue&size=large. Read Google's faceted-navigation guidance before applying broad crawl controls. A robots block prevents crawling; it does not by itself remove an already known URL from search or let Google read a new canonical on that blocked page.
When a URL genuinely needs to change
URL changes may be necessary for a migration or a major structural correction. Plan the old-to-new mapping before publication, using the site-move guidance. Preserve meaningful counterparts rather than sending every retired page to the homepage.
- Inventory existing URLs and their intended replacements.
- Implement appropriate permanent redirects to the final destinations.
- Update internal links, canonical declarations, sitemaps and applicable language references.
- Test valid pages, redirect chains and genuinely missing URLs.
- Monitor responses and Search Console after launch, allowing for reprocessing.
There is no need to promise that a fixed percentage of ranking value will transfer in a particular number of days. For new pages, choose sensible names at creation. For established pages, stability and correct routing usually matter more than cosmetic shortening.