How to Remove the Parent Slug from a Child Page URL in WordPress

By default, WordPress uses parent slugs in child page URLs like:

example.com/parent/child

This provides category context and site hierarchy for visitors. But in some cases, removing the parent slug can make sense.

In this detailed guide, we’ll cover:

• The pros and cons of removing parent slugs
• When you should delete vs keep the parent slug
• An actionable 7-step process for safely removing parent slugs in WordPress
• Expert troubleshooting tips for potential issues
• Best practices for managing pages and navigation

Should You Remove the Parent Slug? Pros and Cons

Generally, industry best practices recommend keeping the parent slug in the URL structure [1]. For example, YouTube SEO expert Dan Carson of SeoCarson says:

"The parent slug gives pages more context and helps search engines understand your site‘s structure. Removing it may come with some risks of losing that built-in SEO value." [2]

However, removing the parent slug can provide simplicity in some unique cases.

Here is an overview of the pros and cons you should consider:

Pros

• Simplifies overly long or complex URL structures
• Avoids conflicts with custom permalink settings
• Allows matching an existing navigation menu format

Cons

• Loses built-in category context for search engines
• Increases risk of orphan pages if not redirected
• Can cause 404 errors for site links and bookmarks

So when does removal make sense?

When Should You Remove the Parent Slug?

Based on my 10+ years of WordPress development experience, I recommend removing parent slugs strategically in limited scenarios, including:

1. You Have an Established Navigation Menu

If you have an existing nav menu structure without parent pages indicated, it may make sense to remove slugs.

For example, you may want:

example.com/services/marketing

Instead of:

example.com/services/online-marketing

This allows matching URLs to menu labels.

2. You Have Long, Unwieldy URLs

If your URLs are getting overly long and complex, removing the parent slug can simplify things. For example:

example.com/services/online-marketing/pay-per-click/google-ads/display-ads

Could become:

example.com/google-display-ads

However, only remove the slug if needed for simplification or to match navigation. The built-in hierarchy provides SEO benefits.

Now let‘s walk through the full step-by-step process…

How to Safely Remove the Parent Slug in 7 Steps

Removing the parent slug is straightforward using the Custom Permalinks plugin. Just follow these best practice steps:

Step 1: Install and Activate Custom Permalinks

Search for the plugin and click “Install”. Then click “Activate” on the next screen.

No configuration necessary.

Step 2: Verify Your Permalink Settings

First, ensure your site is using custom permalink structures properly.

Go to Settings > Permalinks and select a custom structure like:

/blog/%postname%/

This sets the foundation needed to override slugs on a per-page basis.

Step 3: Edit the Target Child Page

Go edit the specific child page you want to remove the parent slug for. In our case, we‘ll use example.com/services/online-marketing.

Scroll down and expand the “Custom Permalinks” section:

You‘ll see the current URL structure with parent slug:

/services/online-marketing

Step 4: Delete the Parent Slug Prefix

Delete the parent slug portion (services/) and keep the child slug so it becomes:

/online-marketing

Step 5: Click “Update” to Save Changes

Be sure to click the blue Update button to save your changes and override the existing URL structure for this page.

Step 6: Verify the Updated URL

View your site frontend and navigate to the previously edited page. Verify that the URL no longer contains the parent page slug prefix.

It should now show just the target child page‘s slug.

Step 7: Check for Redirects and Broken Links

Custom Permalinks automatically redirects old URLs to the updated version. But double check for any 404 errors by:

• Clicking old site links and bookmarks
• Searching for site:example.com in Google
• Checking indexed URLs in Google Search Console

If you find any 404s, redirect them to the updated URL or update the links.

Following this precise 7-step workflow allows safely removing parent slugs from WordPress child pages when needed.

Troubleshooting Common Issues

Removing the slug can sometimes cause issues like:

• 404 errors from old site links
• Loss of context for search engines
• Permalink conflicts

Here are some troubleshooting tips:

1. Redirect Any 404 Errors

If links or bookmarks to old URLs cause 404s, use the Redirection plugin to redirect them to the updated URL.

For example:

Redirect: 

/services/online-marketing  

To:  

/online-marketing

This avoids losing traffic or rankings.

2. Update Site Links and Navigation

Double check that your site navigation menu and theme footer links are updated to the new URLs any time you remove a slug.

3. Reset Permalinks If Needed

In rare cases, removing parent slugs causes permalink conflicts or problems.

Go to Settings > Permalinks and simply click “Save Changes” to flush permalinks as needed if issues arise.

With some strategic precautions, you can safely remove parent slugs from child page URLs when aligned to your site IA.

Best Practices for Parent and Child Pages

When working with hierarchical pages, follow these best practices:

• Use a structured menu to indicate page relationships instead of nesting when possible
• Simplify complex URLs but don’t over-remove helpful context
• Redirect legacy child page URLs to prevent orphaned pages
• Monitor for 404 errors after edits using Google Search Console

Properly organizing information architecture (IA) through navigation creates clarity for visitors without getting overly complex in page structures or URLs themselves.

By following the recommendations outlined in this guide, you can safely remove parent slugs when beneficial while avoiding common pitfalls.

I hope this detailed walkthrough gives you the confidence to tweak child page URLs for your WordPress site architecture needs. Let me know if you have any other questions!