FICILCOM Inc. LogoFICILCOM Inc.
  • Company
  • Company Overview
  • Mission · Vision · Values
  • Guidelines
  • Services
  • NeX-Ray
  • Xtrategy
  • Trial Job Change
  • Tsurugi
  • Recruit
  • Culture
  • Benefits
  • Process
  • FAQ
  • Open Positions
Contact
  1. Home
  2. Blog
  3. Web Analytics
  4. WordPress Permalinks: Set Up New URLs and Plan Safe Changes

WordPress Permalinks: Set Up New URLs and Plan Safe Changes

パーマリンクの設定方法を画像付きで解説|初期セットアップから運用開始まで

Published: 05/28/2026

Last Updated: 10/11/2026

Category: Web Analytics

Authors: Shusaku Yosa

Ready to put this into practice?

Start NeX-Ray for free→

1-minute signup, free, cancel anytime

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.

  1. Establish whether this is a new or existing site and record current settings.
  2. Choose a candidate structure and inspect an actual resulting URL.
  3. Review the individual slug in the post editor.
  4. Test page links, listing links, and output before launch.
  5. 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.

Related Reading

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.

  • How to Write SEO Titles: Examples and Why Google May Change Them
  • What Are Meta Tags? How They Differ from Titles and Canonical Links
  • Website Analytics Explained: GA4, Search Console and a Practical Improvement Workflow

 

 

 

 

Table of Contents

  1. Permalinks, URL Paths and Slugs Explained
  2. Choose a URL Structure for a New Site
  3. Set the Structure and Post Slug in WordPress
  4. Decide Whether Existing URLs Need to Change
  5. Map Old URLs and Test Permanent Redirects
  6. Monitor Search and Analytics After a Change
  7. Related Reading

 

Company

  • Company
  • Company overview
  • Mission · Vision · Values
  • Guidelines

Services

  • Services

Blog

  • Blog
  • Categories
  • Authors

Estimate

  • Estimate simulator

Careers

  • Careers
  • Culture & Work Style
  • Benefits & Systems
  • Hiring Process
  • FAQ
  • Open Positions

Policies

  • Privacy Policy
  • Anti-Social Policy
  • Information Security Policy

Contact

  • Contact

Social

  • X
  • LinkedIn
  • Facebook
  • Pinterest
© 2026 Ficilcom Inc.

Related Articles

GA4の「探索」の使い方|レポート作成と見方の基本を解説
Web Analytics09/01/2026

How to Use GA4 Explorations|The Basics of Building Reports and Reading Them

A guide to using GA4 Explorations (data exploration), following its difference from standard reports, the main technique...

Shusaku YosaRead more
GA4の権限設定とは?許可レベルの違いと安全な転送・付与手順
Web Analytics08/21/2026

GA4 Permissions: Roles, Sharing and Access Troubleshooting

Compare GA4 roles, add or remove users, understand inherited access, and troubleshoot permission issues when sharing a p...

Shusaku YosaRead more
Googleアナリティクスレポートの見方|主要指標とチェックすべき項目
Web Analytics08/19/2026

How to Read Google Analytics Reports | Key Metrics and What to Check

A screen-by-screen guide to reading GA4 standard reports: the snapshot, realtime, the life-cycle reports (acquisition, e...

Shusaku YosaRead more