URLs are a small ranking factor and a bigger usability one. People see them in search results, in shared links, in WhatsApp messages. A clear URL tells them what they'll get before they click, and it's easier to link to and remember.

The bigger lesson, though, is about permanence. Once a URL has rankings and links, changing it carries real risk. So it pays to get them right from the start.

Key takeaways from this guide

What a good URL looks like

The rules

Use words that describe the page

Two to five meaningful words is usually enough. Include the main topic; it's a small relevance hint and makes the link self-explanatory when shared.

Hyphens, not underscores or spaces

Google treats hyphens as word separators. Underscores join words together (root_canal may be read as one token). Spaces become %20 and look broken.

Lowercase only

URLs are case-sensitive on most servers: /About and /about can be two different pages, which creates duplicates. Stick to lowercase, and redirect uppercase variants if they exist.

Leave out filler words when it reads fine

"a", "the", "and", "of" can usually go: /how-to-choose-a-water-purifier becomes /choose-water-purifier. Keep them if removing them makes the URL confusing. Our text to slug converter turns any title into a clean slug.

Folders should mean something

/services/, /blog/, /shoes/mens/ help people and Google understand sections. But avoid deep nesting (/category/sub/sub-sub/product) and avoid putting things in folders you might reorganise later, such as blog categories.

No dates in evergreen URLs

/2024/03/seo-tips looks stale the moment the year changes, and you can't update the content without the URL looking outdated. News sites are the exception.

Be careful with parameters

Filters and sorting often create URLs like /shoes?color=blue&sort=price. That's fine for users, but thousands of parameter combinations can waste crawling and create duplicates. Use canonical tags pointing to the main category, and keep only valuable filter pages indexable. See our canonical tags guide.

Should the URL match the title exactly?

No. The title can change ("10 tips" becomes "12 tips"), but the URL should stay the same forever. Make the slug a stable description of the topic: /meta-title-tips survives any rewrite of the headline.

Non-English URLs

You can use Hindi or other scripts in URLs; browsers display them properly. But when copied, they often turn into long percent-encoded strings that look broken in emails and chats. For sites mainly in English, transliterated or English slugs are more practical. If you do use non-Latin domains, our IDN converter shows the punycode version.

When is it worth changing a URL?

Rarely. Changing a URL means Google has to find the redirect, transfer signals and re-evaluate the page, which can cause a temporary dip even when done perfectly. Change URLs when:

• they're genuinely broken or unusable (session IDs, random strings),
• you're merging duplicate pages,
• you're moving to a new site structure or platform anyway,
• the URL is actively misleading (the page's topic completely changed).

Don't change a working, ranking URL just to add a keyword. The gain is small and the risk is real.

How to change a URL safely

1. Set up a permanent 301 redirect from the old URL to the new one. Our .htaccess redirect generator writes the rules for Apache servers.
2. Update every internal link to point directly to the new URL.
3. Update the canonical tag and the sitemap.
4. Test the old URL with the redirect checker: one hop, 301, ends on a 200 page.
5. Keep the redirect in place permanently; links from other sites may point to the old address for years.

Getting URLs right at the start is one of those decisions that saves a lot of work later. If you're building a new site, plan them alongside the page list in our new website checklist.