A good URL is understandable, avoids unnecessary duplication and can remain stable. For new pages, use a consistent lowercase and hyphen convention, stable categories and only necessary parameters. Existing URLs are assets connected to traffic, backlinks, bookmarks, ads, forms, APIs and measurement, so do not change them just to make them shorter.
Keep new URLs simple; change published URLs only when the benefit exceeds migration risk
Judge by user understanding, duplicate control, operational stability and ability to verify the migration, not by a vague sense that a URL looks good for SEO or is too long.
| General policy | Create a structure that readers understand, avoids duplicate URLs and can be maintained |
|---|---|
| Separators | Separate English words with hyphens and use a consistent lowercase convention |
| Hierarchy | Use categories users understand rather than an organization chart, and avoid easily changed department names or years |
| Japanese URLs | Supported; check sharing and encoding, input, analytics and integration usability |
| canonical | Indicate a preferred URL among duplicate or similar pages; use redirects to move users or retired URLs |
| Changing existing URLs | Do not change them for appearance alone; require one-to-one mapping and checks before and after launch |
| Review date | July 29, 2026 |
URL structure: rules for a page's location and state
URL structure is more than the path under a domain. It includes how the scheme, hostname, path, query parameters and fragment are used, and which URL is preferred when multiple URLs lead to the same content.
https://Communication scheme, usually standardized on HTTPSexample.comDomain or subdomain/guides/url/Identifies content or page type?sort=priceFiltering, display or tracking#migrationIdentifies a position within the same documentURLs alone do not determine ranking. Simple, consistent URLs can nevertheless help users anticipate link destinations, simplify internal links and sitemaps, and limit unnecessary growth in crawlable URLs.
Seven URL design principles for SEO and operations
Google recommends understandable words, the audience's language, hyphens and necessary parameters, and treats URL path letter case as significant. A lowercase convention is our operational recommendation, not a universal Google requirement. The following principles explain our operational choices.
Use short, descriptive words
Choose words that describe the page rather than a long ID alone. Avoid stuffing the full title or search terms; keep the URL concise while distinguishing it from other pages.
Separate words with hyphens
Separate multiple English words with hyphens, as in "url-structure". Do not change existing underscore URLs in bulk solely to replace the separator.
Use lowercase consistently
Avoid publishing "/Server/" and "/server/" as different pages. If both return the same content, redirect to the preferred form and align internal links and canonical URLs.
Choose hierarchy for user understanding
URLs need not copy internal organizations or server folders. Match expected categories and navigation, with internal links to important pages.
Keep changeable details out of permanent URLs
Years, department names, campaign names and CMS extensions can require future changes. News or legal records where the date itself matters are exceptions.
Choose the audience's language and use a consistent policy
Japanese URLs are supported. Check percent encoding when sharing, input errors, analytics and compatibility with external tools, then choose a site-wide policy for Japanese or romanized paths.
Limit parameters and generated URLs to what is needed
Prevent session IDs, tracking values, sort orders and unlimited filter combinations from proliferating through internal links. Manage URLs with distinct content separately from display states.
Create durable URL patterns for each site type
Inventing a URL for each page increases inconsistencies and exceptions. For each page type, define required identifiers, optional categories, language and region, trailing slash policy and the owner responsible for retirement.
Services
https://example.com/services/web-development/Use service names that remain meaningful as the offering changes, rather than department or pricing plan names.
Articles and guides
https://example.com/guides/url-migration/Use undated paths for continuously updated guides and dated paths for news or records identified by month or year, according to the medium's purpose.
E-commerce products
https://example.com/products/running-shoe-1234/Stable IDs can preserve identity when product names change. Decide in advance whether color and size URLs should be indexed.
Categories
https://example.com/products/shoes/Use stable categories that help users reach listings. Do not create unlimited URLs for every combination of filters.
Multilingual
https://example.com/en/services/Give each language a distinct URL, explicit links to other versions and appropriate hreflang. Avoid pointing a canonical URL to a different language.
Separate the roles of URL parameters, fragments and canonical URLs
First decide whether a URL difference represents independent content or only sorting or tracking of the same content. Avoid blanket rules such as removing every parameter or assuming canonical solves everything.
| Form | Example | Design and SEO decision |
|---|---|---|
| Parameters that change content | /products?category=shoes | If the listing needs its own URL, provide crawlable internal links, a title, headings and canonical. Limit indexing when combinations proliferate. |
| Sorting and display | /products?sort=price | If only the order of the same set changes, avoid duplicating the main listing in the index. Define an indexing policy even when keeping the URL for sharing. |
| Measurement parameters | /guide?utm_source=newsletter | Do not permanently include tracking values that do not change content in internal links or sitemaps. Point the canonical to the untracked URL. |
| Fragment | /guide/#migration | Use fragments for locations within the same document, not to identify independently indexed pages or switch independent content. |
Indicate a preferred URL for duplicate or similar pages
A canonical is a signal to search engines identifying a preferred URL among identical or very similar pages. Use a self-referencing canonical on the preferred page and align internal links and sitemaps with it.
Redirecting users or moving retired URLs
A canonical does not redirect a browser and is not a command that must be followed. Use a server-side 301 or 308 to move a retired URL permanently.
Compare the benefits and migration risks before changing existing URLs
Published URLs connect not only to search indexes but also to external links, bookmarks, email, QR codes, ads, analytics, APIs, form destinations and internal documents. Matching an ideal new URL does not by itself justify breaking those connections.
When the only benefit is appearance
- The URL and content are not seriously inconsistent
- Used by traffic, backlinks, shares, ads or integrations
- The only goal is shorter text, different separators or added keywords
- A URL mapping, redirects and monitoring cannot be prepared
When a clear problem can be solved
- A move to HTTPS, domain change or CMS migration requires a new URL
- Several duplicate pages are being merged into one useful page
- Contains sensitive information, a session ID or serious misclassification
- The old structure continually impedes users or daily operations
Avoid major domain, CMS, design and content changes at the same time
When several major changes occur together, a fall in search traffic or conversions is harder to diagnose. If possible, release hosting, URL, design and content consolidation changes separately and retain a baseline for each stage.
WordPress permalink decisions differ before and after launch
Before launch, decide whether post names, categories and dates are needed. On a published site, changing permalink settings may affect posts, categories, feeds, images and custom post types across a wide area.
Choose a maintainable convention first
For evergreen articles, consider a structure that does not require dates or changeable categories. Use a consistent policy for trailing slashes, lowercase, romanization and Japanese URLs.
Saving a setting is not a migration
You need one-to-one redirects, internal links, canonical URLs, sitemaps, caches, CDN, plugins, Search Console, analytics and recovery procedures for the old and new URLs.
Migrate URLs in seven steps
Google's site move guide recommends mapping URLs, configuring permanent redirects, updating internal links and canonical URLs, and monitoring after launch. For larger moves, estimate testing scope, server capacity, increased crawling and recovery.
https://example.com/old-page/https://example.com/new-page/Record the current state
Record crawled URLs, HTTP status, canonical URLs, indexability, internal links, sitemaps, search traffic, backlinks, key conversions and integrations. Combine CMS data, server logs, analytics and Search Console.
Map old URLs to new URLs one by one
Map to the same or most relevant consolidated content. Do not send many old URLs to an unrelated homepage; consider 404 or 410 when removed content has no replacement.
Complete the new URLs in staging
Check content, images, CSS, JavaScript, forms, login, payments, structured data, breadcrumbs, canonical URLs and hreflang. Assign an owner to remove pre-launch noindex or access restrictions.
Implement permanent redirects
Use server-side 301 or 308 responses to send each old URL directly to the final URL in one hop. Do not make browser JavaScript or delayed meta refresh the first choice.
Update all references to the new URLs
Update internal links, canonical URLs, sitemaps, hreflang, structured data, Open Graph, ads, email, profiles, QR codes, APIs, forms and analytics. Do not leave internal links pointing through old URLs.
Check all URLs immediately after launch
Automatically verify that old URLs return 301 or 308, new URLs return 200, and no chains, loops or incorrect redirects occur. Test important pages in browsers and on mobile, including forms, login and payments.
Monitor long term and retain redirects
Google advises keeping redirects as long as possible, generally at least one year. Longer or permanent retention may be appropriate for users' old links.
Minimal 301 and 308 redirect examples
Implementation varies by server, CDN, CMS and application. These minimal examples illustrate the idea. Test query strings, trailing slashes, URL encoding, caches, loops and POST or API behavior in staging before production.
Redirect 301 /old-page/ https://example.com/new-page/location = /old-page/ {
return 301 https://example.com/new-page/;
}// Normal permanent move
http.Redirect(w, r, "/new-page/", http.StatusMovedPermanently)
// Permanent redirect that preserves the method
http.Redirect(w, r, "/new-page/", http.StatusPermanentRedirect)Verify responses, content, search and business operations before and after launch
A migration is not successful merely because some pages load. Verify that old URLs move correctly, new content and search signals agree, important operations and measurement continue, and post-launch crawling, indexing and traffic remain within acceptable bounds.
HTTP responses and destinations
Check old URLs, HTTP and HTTPS, www variants, letter case, trailing slashes and major parameters. Ensure old URLs reach the final destination directly and new URLs return 200.
HTML and search signals
Align the title, H1, content, images, canonical, robots, hreflang, structured data, Open Graph, breadcrumbs, internal links and sitemap with the new URLs.
Search Console and logs
Inspect representative URLs, page indexing, sitemaps, crawl statistics and server logs for increased 404s, 5xx errors or redirects. Do not audit solely with site: search.
User and business operations
Test navigation, site search, sharing, login, inquiries, purchasing, downloads, ads and external APIs in major browsers and on mobile.
Official sources and review date
We checked the following primary sources on July 29, 2026. Distinguish Google Search recommendations from HTTP semantics, and test site-specific server, CMS, CDN, form and API behavior in staging and production.
- Google Search Central: URL structure best practices
- Google Search Central: How to specify a canonical URL
- Google Search Central: Redirects and Google Search
- Google Search Central: Site moves with URL changes
- Google Search Central: Build and submit a sitemap
- Google Search Central: Multi-regional and multilingual sites
- RFC Editor:RFC 9110 HTTP Semantics
Frequently asked questions about URL structure
Are shorter URLs always better for SEO?
Shortness alone does not determine rankings. Choose a length that identifies the content, avoids unnecessary words and parameters, and is easy to share and maintain. Changing published URLs merely to remove a few characters often does not justify migration risk.
Can URLs contain Japanese characters?
Japanese URLs are supported. Check percent encoding during sharing, input, analytics, integrations and operational usability, then choose a consistent policy for Japanese or romanized URLs.
Do keywords in URLs improve rankings?
Natural descriptive words improve understanding but do not guarantee rankings. Prioritize content, titles, headings, internal links and quality over long URLs that repeat search terms.
Can I change WordPress permalinks after launch?
Because all post URLs may change, prepare an old-to-new inventory, one-to-one redirects, internal links, canonical URLs, sitemaps, cache, measurement and recovery before deciding. Saving a setting is not the same as migrating safely.
Should URLs have a trailing slash?
Either form works, but use one consistently. If both slash variants return 200, redirect to the chosen form and align canonical URLs, internal links and sitemaps.
Should I use 301 or 308?
Both are permanent redirects. For ordinary GET pages, prioritize infrastructure compatibility. For POST and APIs, method preservation matters, so test candidates including 308 with real clients, the CDN and cache.
Should existing URLs be rebuilt for SEO?
Do not rebuild URLs for appearance or keywords alone. Plan a change only when its value exceeds migration risks, such as duplicate consolidation, domain or CMS migration, serious misclassification or sensitive information in a URL.
Summary: good URLs are understandable, controlled and durable
For new URLs, start with audience-friendly words, a consistent lowercase and hyphen convention, stable categories and only necessary parameters. Do not change published URLs for appearance alone; migrate only to solve a clear problem.
If URLs must change, execute the old-to-new mapping, permanent redirects, canonical, internal link and sitemap updates, important form and API actions, and post-launch monitoring as one plan. URLs alone do not guarantee search results; improve content and user experience too.