How to Set Clean URLs for a New Website (and Change Them Safely)

URL structure is one of those settings that causes the most trouble when left on default. An out-of-the-box URL on many platforms looks like yoursite.com/?p=123 — a numeric query string that tells visitors and search engines nothing about the page they’re about to visit.

Most site owners don’t notice this until they’ve already published content. At that point, changing the structure gets more complicated because every existing URL changes, which means setting up redirects to avoid broken links and lost rankings. Getting it right before you publish — or changing it safely if you haven’t — is worth doing early.

Quick Answer

On most platforms, look for a URL or permalink setting and choose the option that produces a clean slug from the page title — something like yoursite.com/your-post-title/ — rather than a numeric ID or a full date. Save the change. If you’re changing an existing site’s URL structure, set up redirects first and verify all old URLs are covered after the switch.

Why URL Structure Matters

The URL is one of the first signals a search engine reads about a page. A clean, descriptive URL reinforces what the page is about and makes it easier for both crawlers and readers to understand the content before clicking. Readable URLs also perform better when shared — a link that includes the post topic is more trustworthy and clickable than one containing a numeric ID.

On most sites I build, I set a clean, name-based URL structure immediately during setup, whatever the platform. It’s the clearest option for both SEO and usability, and it avoids the extra work of migrating URLs later.

How to Set a Clean URL Structure

The exact setting lives in a different place depending on your platform, but the underlying choice is the same everywhere: pick the option that uses the page’s own title or slug, not a number, a date, or a category path baked permanently into the address.

If You’re on WordPress

Go to Settings > Permalinks in your WordPress dashboard. WordPress offers six options:

• Plain — yoursite.com/?p=123. The default, and the worst choice for SEO.
• Day and name — yoursite.com/2024/06/08/post-name/. Includes the full date, which visually dates your content.
• Month and name — yoursite.com/2024/06/post-name/. Same problem, slightly shorter.
• Numeric — yoursite.com/archives/123. Still numeric, still not useful.
• Post name — yoursite.com/post-name/. Clean, readable, and recommended.
• Custom structure — Lets you build a pattern from available tags.

Select Post name and click Save Changes. WordPress updates the rewrite rules automatically — on most hosting setups this takes effect immediately, no server restart needed. The WordPress permalink documentation covers all available structure tags if you decide to build a custom format.

On Other Platforms

Hosted builders and other CMS platforms handle this under names like “URL settings,” “permalink settings,” or “SEO settings,” usually inside the page or post editor itself rather than a separate global screen. Some hosted builders generate a clean, editable slug from the title automatically and don’t expose the underlying setting at all — if that’s the case for your platform, there’s nothing further to configure here.

How to Change URLs Safely on an Existing Site

Changing your URL structure on a site with published content is more involved than setting it up initially. Every existing URL changes, which means incoming links from other sites will break, bookmarks will stop working, and search engines will see the old URLs as 404 errors until redirects are in place.

To handle this correctly you need a 301 redirect from every old URL to its new equivalent. On WordPress, the Redirection plugin handles this well — it can detect URL changes automatically when activated before you switch the permalink structure. The full process is covered in the guide to setting up 301 redirects in WordPress. On other platforms, check whether your CMS or hosting dashboard offers a built-in redirect manager before reaching for a third-party tool.

Steps for Changing Safely

1. Set up a way to catch redirects (a plugin like Redirection on WordPress, or your platform’s built-in equivalent) before making any changes.
2. Run a scan to log your existing URLs, if your tool supports it.
3. Switch to the clean, name-based URL structure.
4. Save changes and let your redirect tool create the 301s automatically where it can.
5. Test a sample of old URLs to confirm they redirect correctly to the new structure.
6. Check Google Search Console over the following weeks for any 404 errors that need additional redirects.

Practical Tips

Set the URL structure before you publish anything. This is the cleanest approach — it avoids the redirect problem entirely. If you’re in the setup phase, sort this out on day one before creating any content.

Avoid including dates in URLs. Date-based structures make content look outdated as it ages. A post from 2022 looks stale in the URL even if the content is completely current. A clean, name-based URL keeps content evergreen.

Edit individual page slugs when needed. Most platforms generate the slug from the page title by default. If your title is long, trim the slug in the editor to keep the URL clean and focused on the main keyword.

Don’t change individual page slugs after publishing without setting up a redirect. Each slug change is a new URL — without a redirect the old URL becomes a 404.

Common Mistakes

Skipping redirects when changing structure. Without 301 redirects, every existing page becomes a 404 until search engines recrawl the new URLs. Any rankings, links, or traffic attached to the old URLs will be affected until the new URLs accumulate the same signals.

Changing structure multiple times. Each change creates a new layer of redirects. Redirect chains slow down crawling and can create coverage issues in Search Console. Choose a structure and stick with it.

Leaving the default numeric structure in place. Some sites never change this and end up with numeric URLs on all published content permanently. It’s fixable but requires more work the longer it’s left — every URL needs a redirect.

Name-Based vs Custom Structure

For most sites, a clean, name-based URL is the right choice. It’s simple, readable, and produces URLs with no extra clutter.

A custom structure can be useful if you’re running a large publication where category-based URLs help organise content — for example, yoursite.com/category/post-name/. The trade-off is that category changes affect URLs: if you ever reorganise your categories, you’re dealing with another round of redirects. For most sites the simplicity of a name-based URL outweighs the categorisation benefit. You can handle content organisation through internal linking and category archive pages without baking it into the URL.

Clean URLs are closely related to how search engines handle duplicate URL signals — for a deeper look at that topic, the guide to canonical URLs explains how search engines choose between competing versions of the same page.

Conclusion

Set a clean, name-based URL structure before publishing content. If you’re changing it on an existing site, set up a redirect plan first and verify that all old URLs are covered after the switch. Clean URLs are one of the foundational settings covered in the step-by-step guide to making a website — getting them right early saves significant rework later.