---
title: "SEO friendly URL structure: what to keep and what to change"
description: "SEO friendly URL structure: keep stable page addresses, use hyphens and few parameters, and redirect any old URL you change with a permanent 301."
url: "https://webleveling.com/blog/what-your-page-urls-should-look-like/"
lang: "en"
published: "2026-10-21"
modified: "2026-10-21"
author: "Cal Hewitt"
tags: ["seo","website-maintenance","small-business"]
image: "https://webleveling.com/og/blog-what-your-page-urls-should-look-like.jpg"
alternates:
  es: "https://webleveling.com/es/blog/estructura-de-urls-amigables-para-seo.md"
---

# SEO friendly URL structure: what to keep and what to change

SEO friendly URL structure: keep stable page addresses, use hyphens and few parameters, and redirect any old URL you change with a permanent 301.

![A small wooden signpost with two blank arrow boards standing on a smooth gray stone beside a closed brass compass.](https://webleveling.com/blog/what-your-page-urls-should-look-like/url-featured.jpg)

You looked at your page addresses and saw numbers, underscores, a string like \`?id=42\`, or a date from 2021. Now you wonder whether that is hurting you in search, and whether someone should rewrite all of it. The worry behind an SEO friendly URL structure question is rarely about syntax. It is about losing rankings, breaking links customers already use, or paying for a big change nobody explained.

The short answer is that a clear naming rule for new pages is cheap, and changing old addresses is optional unless a specific problem calls for it. A stable page that loads, ranks and gets links can usually stay put.

When a change is worth making, there is a safe way to do it. It comes down to a direct permanent redirect from every old address to its new one, plus a short list of things to update. You can check your five most important addresses yourself in about five minutes.

**Key Takeaways**

**Name new pages with readable words and hyphens**

Google recommends readable words instead of long ID numbers and hyphens to separate words, with as few parameters as practical.

**Keep one consistent case**

Google treats URLs as case-sensitive, so pick lowercase and stay with it.

**A number, date or underscore alone is not a reason to rename**

Change a URL when it misleads, exposes session or tracking parameters, has a serious naming error, or no longer describes its page.

**Every change needs a direct permanent redirect**

Use a 301 or 308 from the old address to the final one, keep it for at least a year, and update internal links and the sitemap.

**Check five addresses first**

Your homepage, main service page, busiest article, best-converting landing page and one older page tell you whether anything needs fixing.

## What does an SEO friendly URL structure look like?

Google Search Central's [URL structure guidance](https://developers.google.com/search/docs/crawling-indexing/url-structure) is short and practical. It recommends readable words instead of long ID numbers, words in the language your audience uses, hyphens instead of underscores, and as few parameters as practical. It also says URLs are case-sensitive, so a consistent case is the safer habit.

On Google's wording about separators: "We recommend separating words in your URLs, when possible." Hyphens are the recommended choice because they help people and search engines see where one word ends and the next begins.

Put together, a good address for a service page reads like a plain description of the page. Something like \`yoursite.com/services/web-design/\` tells a customer, and a search engine, what they will find before they click. Compare that with \`yoursite.com/Page\_ID\_4471.php\`, which tells nobody anything.

Parameters are the part after a question mark. Google says to use the standard \`=\` and \`&\` characters and to remove parameters you do not need. If you write a page address in a language with accented or non-Latin characters, Google supports it and recommends percent encoding when you link to it.

These are best practices. They describe a tidy, predictable address, not a guarantee that renaming a page will lift its rankings.

![A neat row of identical blank index cards standing upright in a wooden box on a desk.](https://webleveling.com/blog/what-your-page-urls-should-look-like/url-index-cards.jpg)

One simple, repeatable rule for naming new pages keeps every address easy to read.

## Should I change my URLs if they have numbers, underscores or dates?

Not by default. A number, a date or an older format in a page address is not, on its own, a reason to change a stable URL. If the page loads the right content, people link to it and it already appears in search, the address is doing its job.

Google's guidance is a recommendation for how to name pages, and it applies most naturally to new ones. An existing underscore address keeps working. A dated blog address keeps working. A numeric ID that is part of how your platform identifies a page keeps working too.

That matters because every rename carries risk. Each change creates a new address that has to be found, indexed and linked to, while the old one has to be redirected perfectly. If a page is healthy, the safest edit is often no edit.

So, what should you do first? Spend your effort where an address is actually causing trouble, and leave the rest alone. Content quality, working links, crawlable pages and a sensible site layout matter more than cosmetic cleanup. Do not spend a week replacing underscores on pages that are indexed, linked and bringing in customers.

If your messy addresses are mostly on old pages that bring in no traffic and have no links, the question may be whether those pages should exist at all. That is a content decision, covered in [what to do with old pages: update, merge or delete](https://webleveling.com/blog/update-merge-or-delete-old-pages/).

## When is a URL worth changing?

A change makes sense when the address itself is the problem. Google's [site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) and URL guidance point to a short list of reasons:

- **The address misleads**: It names a topic the page no longer covers, or a product you stopped selling.
- **It exposes session or tracking parameters**: These can create many crawlable copies of one page.
- **It has a serious naming error**: A typo in a service name, or the wrong town or brand.
- **The site structure changed**: Pages moved into new sections, so the path no longer fits.
- **It no longer describes its page**: The content was rewritten and the address now points at something else.

Outside that list, hold off. A tidier slug that makes you feel better is not enough reason by itself to take on the risk of a redirect project.

One more case deserves a flag. Mixed upper and lowercase versions of the same address, or a trailing slash that works both with and without, can create duplicate copies of a page. That is a real problem, and it is usually fixed with redirects and one chosen version, not with a rename of every page.

## How do I change a URL without losing rankings?

Use a direct permanent redirect. Google's [guidance on redirects](https://developers.google.com/search/docs/crawling-indexing/301-redirects) says to use a permanent server-side redirect, usually a 301 or 308, when a page has moved for good. Google also says permanent redirects are a strong signal for which address should be treated as the main one, and that a 301 redirect does not cause PageRank loss.

Redirects need to stay in place long enough for search engines and visitors to catch up. Google's site move guidance says to keep them as long as you can, generally at least one year, and preferably longer for the sake of people who still have the old link. On a small or medium site, most addresses commonly move over search within several weeks, and temporary ranking swings are possible during that time.

This order keeps a change safe:

1.  **Write an old-to-new map**: One row per page, with the current address, the new address, and what the page does for your business.
2.  **Redirect each old address to its final new address**: One step, no chains where A goes to B and B goes to C.
3.  **Update everything you control**: Internal links, menus, the sitemap, ads, email signatures and printed QR codes.
4.  **Test every old address**: Open it and confirm it lands on the right page with a permanent redirect.
5.  **Watch Search Console**: Check Page indexing and URL Inspection for the new addresses over the following weeks.

A canonical tag is not a replacement for a redirect when the old address should disappear, and a sitemap does not redirect anything. A sitemap helps search engines find the addresses you prefer, and a redirect is what moves a visitor.

![A brass mail slot set into a plain painted door, with a few blank envelopes resting on the floor below it.](https://webleveling.com/blog/what-your-page-urls-should-look-like/url-mail-slot.jpg)

A redirect forwards everyone who uses the old address to the new one, so nobody arrives at a dead end.

## How do WordPress, Wix and Squarespace handle a changed URL?

Each platform sets page addresses from the page name, and each handles a change differently. Check the exact behavior in your own account before editing anything, because it can vary by plan, page type and setup.

What each platform does when you change a page address

| Platform | Where the address is set | Old address after a change |
| --- | --- | --- |
| WordPress | Settings, then Permalinks for the site-wide pattern; the slug is edited in each post or page sidebar | The old address is not kept automatically; a redirect plugin or equivalent setup is needed |
| Wix | Page URL comes from the page name; the URL Redirect Manager handles redirects | Wix generally adds an automatic 301 on supported page types; Wix Blog slug changes need a manual redirect |
| Squarespace | URL slug field in the page settings; slugs are forced to lowercase | Changed slugs are not redirected automatically; add redirects under Developer Tools, then URL mappings |

WordPress offers Plain, Day and name, Month and name, Numeric, Post name and Custom structure options under Permalinks. The [WordPress.com help page on changing permalinks](https://wordpress.com/support/change-the-permalink-structure/) warns that changing a slug does not preserve the old address by itself. Its page on [permalinks and slugs](https://wordpress.com/support/permalinks-and-slugs/) covers how to edit them.

Wix explains the redirect tool in its guide to [setting up a 301 redirect](https://support.wix.com/en/article/setting-up-a-301-redirect-for-a-page-on-your-site). Squarespace documents [URL slugs](https://support.squarespace.com/hc/en-us/articles/205814578-URL-slugs) and, separately, [URL mappings](https://support.squarespace.com/hc/en-us/articles/205815308-URL-mappings) for creating redirects.

The point to carry away is simple: renaming a page in the editor is the easy half. The redirect is the half that protects your visitors and your search presence.

![Two small brass keys hanging on neighboring hooks of a bare wooden rack, one old and tarnished and one new.](https://webleveling.com/blog/what-your-page-urls-should-look-like/url-old-and-new-keys.jpg)

An old address and a new one both need to open the same door.

## How can I check my five key URLs in five minutes?

Open a plain note and list the five addresses that matter most to your business. They are your homepage, your main service page, your highest-traffic article, your highest-converting landing page and one older page from before your current site structure.

Next to each address, mark any of these that apply:

- **Long numeric IDs or page IDs**
- **Underscores or capital letters**
- **A date in the path**
- **Session or tracking parameters**
- **A redirect, a redirect chain or a 404 response**

Then open each address in a browser and see where it lands. After that, use Search Console. The Page indexing report shows reasons such as "Duplicate without user-selected canonical," "Duplicate, Google chose a different canonical," "Page with redirect" and 404 errors. URL Inspection shows the Google-selected canonical, the declared canonical and the fetch result for any address you paste in. Google explains both in its Search Console help on the [Page indexing report](https://support.google.com/webmasters/answer/7440203) and [URL Inspection](https://support.google.com/webmasters/answer/12482179).

Also check the Sitemaps report. It should list the addresses you prefer, not parameter versions or ones that redirect.

Do not change an address just because it carries one mark. First look at its traffic, links, conversions and internal references. A marked address that is indexed, linked and converting is usually one to keep. A marked address that creates duplicates or lands on a 404 is one to fix.

![A single sheet of blank paper with a pencil resting across it beside five small, evenly spaced wooden blocks.](https://webleveling.com/blog/what-your-page-urls-should-look-like/url-five-blocks.jpg)

Five addresses, checked one at a time, tell you whether anything needs to change.

## What URL mistakes cause real problems?

The costly problems are rarely an ugly slug. They are unmanaged changes and duplicate copies of the same page. In rough order of how often small sites run into them:

- **A slug changed with no redirect**: Visitors and links land on an error page.
- **Old addresses still used in links, menus, ads or QR codes**: Traffic keeps going to a dead end.
- **Backlinks pointing at a deleted or moved page**: The links keep arriving and find a 404.
- **Duplicate versions of one page**: Parameters, capital letters, trailing slashes or an alternate domain each create a separate address.
- **A whole permalink pattern changed with no URL map**: Some pages get missed.

Redirect chains belong on this list too, where one old address passes through several others before it lands. Send each old address straight to its final home. Google's [canonicalization troubleshooting guide](https://developers.google.com/search/docs/crawling-indexing/canonicalization-troubleshooting) and its guide to [consolidating duplicate URLs](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) explain how to spot and resolve duplicates.

If broken pages are your main issue, the fix is covered in [how to fix broken links and 404 errors](https://webleveling.com/blog/fix-broken-links-and-404-errors/). If you are moving to a new platform, [moving your website without losing Google rankings](https://webleveling.com/blog/moving-your-website-without-losing-google-rankings/) walks through that bigger project.

## When is it worth paying someone to help with URLs?

You can inspect five addresses and set a sensible naming rule yourself. Paid help makes sense when the job gets bigger than that.

That is usually the case when you have no reliable list of your current addresses, you are changing platforms, you already have broken links or redirect chains, Search Console shows duplicate or canonical problems, or you need a large permalink change across many indexed pages. It also applies when you cannot safely test server or platform behavior yourself.

What you should receive is concrete: an old-to-new URL map, redirect rules, updated internal links, testing, and monitoring after launch. It should not be a promise that prettier slugs will produce rankings, because naming alone does not guarantee that.

A careful specialist may tell you to keep most of your current addresses. That restraint is part of the work: change only what has a clear reason, and make each change traceable and reversible. If someone proposes changing every address on the site, ask which problem each change fixes and what the redirect plan is.

**Quiz: Should this URL change?**

1. A blog post at /2021/08/our-spring-checklist/ ranks well and gets steady links. What is the safest default?
   - Remove the date and the year folders right away
   - Keep it, since a date alone is not a reason to change a stable URL **(correct answer)**
   - Delete the page and start again
   - Change it to use underscores
2. You rename a service page's slug in the editor. What must you also do?
   - Nothing, the platform always handles it
   - Add a direct permanent redirect (301 or 308) from the old address to the new one **(correct answer)**
   - Add a canonical tag only
   - Submit the sitemap and wait
3. Which separator does Google recommend between words in a URL?
   - Underscores
   - Spaces
   - Hyphens **(correct answer)**
   - Capital letters

## Frequently Asked Questions About SEO Friendly URL Structure

**Should URLs use hyphens or underscores?**

Use hyphens where possible. Google recommends them because they help people and search engines see where words begin and end. An existing underscore address can keep working, so only change it when there is another reason to.

**Should URLs be lowercase?**

Use one consistent case. Google says URLs are case-sensitive, so mixed-case versions of one page can become separate addresses. Squarespace forces lowercase slugs automatically.

**Are numbers in URLs bad?**

Not by themselves. Google recommends readable words instead of long ID numbers, but a number that identifies content or belongs to your platform's structure does not need to change on a stable page.

**Should blog URLs include dates?**

Dates are optional. Keep them when they are stable and useful. Remove them only as part of a planned change with redirects from every old address.

**Can I change a URL without losing rankings?**

Change it only when there is a clear reason, and add a direct permanent redirect from the old address to the new one. Google says a 301 redirect does not cause PageRank loss. Update internal links and the sitemap, and monitor Search Console afterward.

**Does a sitemap redirect an old URL?**

No. A sitemap helps search engines find the addresses you prefer. A redirect is what sends a visitor from the old address to the new one.

## The Bottom Line

Write new addresses with readable words, hyphens, one consistent case and as few parameters as practical. Leave stable pages alone when the only objection is a number, a date or an underscore. Change an address when it misleads, exposes tracking or session parameters, has a serious naming error, or no longer matches its page or your site structure.

Whenever you do change one, use a direct 301 or 308 redirect, keep it for at least a year, update every link you control, and check the result in Search Console. Write the old-to-new map before you touch anything.

With that plan, your pages keep their customers and their links through any cleanup, and you avoid paying for changes that do nothing. If your platform, your Search Console reports or the size of the job make you unsure, [Web Leveling](https://webleveling.com/) can build the URL map, redirect rules and testing with you as part of our [search engine optimization](https://webleveling.com/services/search-engine-optimization/) work. We work with small and medium businesses across the country and overseas, and if your addresses are fine as they are, we will say so. [Send us your five key addresses](https://webleveling.com/contact/) and we will tell you which to keep.

## Terms

URL words in this post

Tap a term to see what it means.

**URL.** The full web address of a page, such as the one you type into a browser.

**Slug.** The readable part of an address that names one page, usually at the end.

**Parameter.** Extra text after a question mark in a URL, often used for tracking or sorting.

**301 redirect.** A permanent instruction that sends visitors and search engines from an old address to a new one.

**Canonical URL.** The address Google treats as the main version when several addresses show the same page.

**Redirect chain.** An old address that passes through one or more other addresses before reaching the final page.

- [Keep a page out of Google search: noindex or a password](https://webleveling.com/blog/block-indexing-of-link-shared-content/): Shared quote or price sheet showing in Google? Check it with a site search, then use noindex if people need the link, or a password if it is confidential.
- [Search Console indexing report not updating: check pages first](https://webleveling.com/blog/search-console-page-indexing-report-stuck/): Google has given no cause or fix date for the Page indexing report. Check your key pages with URL Inspection and the Performance report while it catches up.
- [Soft 404 in Search Console: What It Means and How to Fix It](https://webleveling.com/blog/soft-404-in-search-console/): A soft 404 means a page returns 200 OK while looking missing or empty. Return a 404 or 410 if it is gone, a 301 if it moved, or repair it if it should stay.