WordPress Permalinks: Set Up New URLs and Plan Safe Changes

May 28, 2026

Author: Shusaku Yosa

A WordPress permalink is a URL intended to keep pointing to a post or page. Choose a structure before launching a new site. For an established site, first decide whether a change is necessary: a cosmetic preference alone may not justify migrating many URLs. This guide separates initial setup from a planned URL change.

Permalinks, URL Paths and Slugs Explained

Calling every part of a URL a permalink makes a change request ambiguous. Following the WordPress permalink explanation, break an example into its components.

Term	Example	Meaning
Complete URL	scheme + :// + hostname + path	The page’s permalink
Scheme	https	The connection scheme
Host	example.com	The destination host
Path	/blog/permalink-guide/	The location within the host
Post slug	permalink-guide	The identifying text for this example post

A common structure and an individual post slug are also different settings. Either may affect a published address, so record the existing URL before editing.

Choose a URL Structure for a New Site

For a new site, consider both readability and what future edits could change the URL. A structure less dependent on categories or dates may simplify maintenance where those values change frequently. Do not automatically apply a new-site preference to an existing site.

Structure	Reason to choose it	Change dependency	Existing-site decision
Post name /sample-post/	A readable content identifier	Changing the slug changes the URL	Keep a working structure if migration is unnecessary
ID ?p=123 or /archives/123	Stable identification by ID	The subject is less obvious from the address	The format alone does not prevent search inclusion
Date /2026/10/11/sample-post/	Publication date forms part of the organization	Check effects of date edits	Weigh a real need against migration work
Category /topic/sample-post/	Classification appears in the path	Category edits may affect the URL	Identify affected addresses before reorganizing

Google’s URL structure guidance supports readable words and the audience’s language. Non-ASCII text is not inherently an SEO failure. Select a naming policy around the audience, sharing behaviour, and maintainability instead of automatically replacing existing Japanese or other localized URLs.

Set the Structure and Post Slug in WordPress

With appropriate permissions, WordPress exposes common structures under Settings and Permalinks. Select the structure and save it. Exact labels and behaviour can vary with the version, permissions, and hosting environment; refer to the official settings documentation.

Establish whether this is a new or existing site and record current settings.
Choose a candidate structure and inspect an actual resulting URL.
Review the individual slug in the post editor.
Test page links, listing links, and output before launch.
If saving reports a server-side requirement, consult the implementation owner.

A new slug should summarize the content and follow a consistent team policy. Hyphens can separate words. This is not an instruction to rewrite every published localized or ID-based address.

Decide Whether Existing URLs Need to Change

Existing URLs may appear in external references, bookmarks, email campaigns, and internal navigation. Identify the reason and impact before changing a common setting.

Situation	Starting decision	Next step
A cosmetic preference	Consider keeping existing URLs	Check whether copy or title improvements are enough
Necessary restructuring or business migration	Define the affected scope	Build a URL map and migration plan
Redirects cannot be implemented or tested	Reconsider timing	Secure an owner and test environment
Only the article body needs updating	Keep that separate from migration	Do not treat a rewrite as a URL-change requirement

Old links do not inevitably become 404s: inspect the actual responses and redirects. Equally, correct redirects do not promise that search visibility will remain unchanged throughout a migration.

Map Old URLs and Test Permanent Redirects

Map old URLs to relevant new destinations. The Google guide to URL-changing moves covers permanent server-side redirects and coordinated updates to links, canonicals, and sitemaps. Avoid sending unrelated old pages to the homepage.

Check	Fictional example or evidence
Old to new	/old-guide/ → /blog/guide/
Old response	301 or 308 directly to the intended destination
Final destination	Intended content and a final 200 response
Redirect steps	No unnecessary intermediate chain
Canonical	Intended new reference and actual output
Internal links	Update menus, listings, and related links
Sitemap	Verify the current new URL is included
Query parameters	Test retention of required UTM values separately
Handover	Owner, date, results, important referral paths

Google generally recommends retaining redirects for at least a year. A URL migration does not guarantee a fixed percentage of ranking retention or a recovery date. Also consider how long customers may continue to use old links.

Monitor Search and Analytics After a Change

After launch, separate technical success from search and analytics observations. A correct redirect does not mean that every report immediately moves to the new address.

Test old URLs through to their intended final destinations.
Check retrieval, indexing, and canonical information for new URLs.
Track old and new search impressions and clicks under consistent conditions.
In GA4, match host, language, period, and channel while retaining separate old/new path rows.
Evaluate outcomes only with tested success and duplicate-counting definitions.

A path is useful for classifying content, but it does not identify the visitor’s channel. A /blog/ page can receive advertising visits, and a /campaign/ page can receive organic visits. Keep URL organization separate from source analysis and causal claims about marketing performance.

Record the current URL structure and decide whether you are setting up a new site or planning an existing URL migration. The following guides cover page titles, meta information, and measurement after a change.