SEO Friendly URLs: What They Are and How to Fix Yours

What Makes a URL SEO Friendly?

A web address has several parts, and it helps to name them before judging any of them. Take https://blog.example.com/guides/seo-friendly-urls/?ref=nav#tips. The https at the start is the protocol. The domain name is example.com and blog is a subdomain. The URL path is /guides/seo-friendly-urls/, where guides is a subfolder (or subdirectory) and the URL slug is the last piece, seo-friendly-urls. After the question mark come the URL parameters, and after the hash comes the fragment identifier. Our report cares about the path only.

Clean URLs, also called pretty URLs or human readable URLs, share five traits: readable words, lowercase, hyphens between words, short length and stability over the years. Compare /guides/seo-friendly-urls/ with /index.php?p=4821&cat=7. The first tells a visitor the topic before the page loads.

What Google says about URL structure

The Google URL structure guidelines on Google Search Central are short and worth reading once. They ask for readable words instead of long ID numbers, written in your audience's language and separated with hyphens rather than underscores. They note that URLs are case sensitive, and they advise as few parameters as possible and to avoid session IDs wherever possible. The guide names no maximum length, so any figure you read elsewhere is a convention and not a Google rule.

Folders and hierarchy

A sound SEO friendly URL structure has folders that mirror how the site is really organized, and URL depth should stay as shallow as the content allows. A product buried six folders deep is a navigation problem no slug can repair. The post on flat vs deep site structure covers that trade-off.

Why SEO Friendly URLs Matter

Start with crawling: when capital letters, trailing slash variants and tracking parameters all lead to the same content, Googlebot meets several addresses for one page and has to decide which one counts. Redirects and a rel canonical tag settle that duplicate content problem.

Then people. Your address appears in search results, the browser bar and chat previews. A clear one is easier to read, remember and judge before anyone clicks.

Now the honest part about rankings. Google presents URL structure as a help for crawling and for understanding a site, and it never calls the words in a URL a ranking factor. Treat them as at most a light signal. If you rename a healthy page hoping for a jump in position, expect cleaner data and fewer mistakes, not a jump.

How Our SEO Friendly URL Check Works

The rule: The report reads every link on the rendered page that points to the same site (relative links, and absolute links on the same host) and flags a link when its path has an underscore, three or more digits in a row, more than 80 characters, or any capital letter from A to Z.

What the Report Reads

A headless Chromium browser loads your URL and the report works on the rendered page, so links added by scripts are included and every anchor with an href is collected. A link is tested when it is relative, or absolute and on the same host as the scanned page. Links to another host are skipped, and the www version of a domain counts as a different host from the bare domain.

Anchors such as href="#top" or an empty href count in the total even though they can never be flagged. Whether links work is a separate row, covered in the In-page Links check.

The address of the page you scanned is not graded on its own. The row only judges the links found on that page, so a messy page address shows up only if a link on the page points to it.

The Four Rules and What They Ignore

Only the path is tested. The checks run in the order the callout above lists them, and a link is flagged on the first rule it breaks, so a path with both an underscore and a capital letter is reported as an underscore problem. Query strings and fragments are never examined, and neither are hyphens, keywords, stop words, folder depth, trailing slashes, %20 spaces or HTTPS.

So /Blog/Seo-Tips is flagged for its capital letters and /2024-guide for its four digit run, while /blog/seo-tips and /page-12 pass cleanly. The digit rule surprises people: /page-123 is flagged, /covid19 passes because it has only two digits in a row, and /top-10-tips passes while /top-100-tips is flagged.

• Length limit. A path of exactly 80 characters passes and 81 is flagged.
• File extensions. photo.JPG is flagged but photo.jpg is not, because the capital letter rule reads the whole path.
• Mail and phone links. A link like mailto:john_doe@example.com is flagged because the address is measured as a path, and tel:+15551234567 is flagged for its long digit run.
• Percent encoding. /gem%C3%BCse is flagged because the hex digits are capitals, while /my%20page passes.
• Repeats. A bad link in both the menu and the footer counts twice.

Pass, Warning and Fail in Plain Words

The row has three outcomes. The red How to Fix button appears for both warning and failed with the same sentence, so the difference is only how widespread the problem is.

The wording on a green row can sound broader than this, but the four rules above are all it tests. The count badge next to the row is styled green even when the number is above zero, so read the number, not the color. Signed in users see the flagged addresses, and an account is free.

Run the free report

How to Check if Your URLs Are SEO Friendly

1. Run the report on the page. Open the SEO Friendly URL row and note the count next to SEO unfriendly URL. Sign in, which is free, to see the list of flagged links.
2. Sort the flags into patterns. Group them as capitals, underscores, long numbers and long paths. Most come from a few templates, such as the menu or footer, so one fix clears many links.
3. Judge the untested rules by eye. Treat the report as an SEO friendly URL checker for link spelling only, and look at hyphens, readable words, parameters and folder depth yourself, since the report never examines them.
4. Check scripts when a link seems missing. Links added by scripts exist only in the rendered page, so inspect it in Chrome DevTools.
5. Audit the whole site from a list. Export the URLs from your sitemap or CMS into a spreadsheet and filter for uppercase letters, underscores and long digit runs.
6. Repeat per template. Each report reads one page, so scan one per template: home, article, category and product.

SEO Friendly URL Best Practices

These URL best practices for SEO say where the report flags a problem and where it stays silent.

• Lowercase URLs only. Paths are case sensitive, so /Apple and /apple can be two different addresses. The report catches any capital letter, and uppercase letters in URLs are a common source of duplicates.
• Hyphens between words, never underscores. On hyphens vs underscores in URLs, Google recommends hyphens to separate words, and the report flags underscores too.
• Real words instead of IDs. /blue-running-shoes/ beats /item-98213/. The report flags three or more digits in a row, which also catches long IDs.
• Short and specific. Keep the URL slug to a few meaningful words and drop stop words in URLs such as "the" or "and" when it still reads naturally. SEO friendly URL length has no official cap, since Google's guide names no maximum, and the 80 character cut off in our report is our own practical rule.
• Careful with non English words. Google advises using words in your audience's language, with non ASCII characters in URLs percent encoded in the link href, so a u with an umlaut becomes %C3%BC, as RFC 3986 URI syntax describes. Our report flags those links because the hex digits are capitals, which is a false alarm. The URL Encoder Decoder shows what the encoded form looks like.
• Few parameters, no session IDs. Avoid a session ID in URL parameters wherever possible and consider cookies instead, as Google suggests. Keep parameters out of internal links and use as few as you can. This one is outside the report, which ignores the query string.
• Drop file extensions where you can. Endings such as .php or .html expose the technology behind the page and add nothing for the reader, so use extension free static URLs where your CMS allows. Real files such as photo.jpg keep their extension, in lowercase. The report tests only the capital letters in them.
• Avoid special characters. Stick to letters, digits and hyphens, because spaces and accents get percent encoded and ampersands can break a pasted link. The report ignores this.
• No dates in URLs for evergreen pages. Without a year the page can be refreshed later without needing a new address. A year in a path is flagged by the digit rule.
• One convention for www, HTTPS and trailing slash. Pick one version and redirect the others to it. The report never looks at this.

SEO Friendly URL Examples: Good and Bad

The third column shows what our report does with each example, which is not always the verdict a human editor would give.

How to Fix URLs That Are Not SEO Friendly

Decide first whether a page needs renaming at all. Some flags are false alarms, such as years in archive paths, product codes, upload folders, mailto links and percent encoding of non English words. A page that ranks well with a flagged address is often better left alone.

1. Decide whether to rename at all. If the page already answers on a clean lowercase address, edit the links to use that address and skip the rename. Otherwise follow the steps under Rename a Live URL Safely below.
2. Fix by template, not by page. One change to the menu or footer cleans every page that uses it.
3. Keep a redirect map. List old and new addresses in a spreadsheet and test each line with curl -sIL. You want one 301 followed by a 200, with no redirect chain.
4. Re-run the report and watch. Check the row again, then watch Search Console for crawl errors and spot-check a renamed address with the URL Inspection tool.

Fix the Link Output First

Edit your templates and menus so links use the clean lowercase address. If you have a long list of slugs with stray capitals, the Case Converter lowercases the whole batch in one go before you build the redirect map, and a find and replace in your spreadsheet can then swap any underscores for hyphens.

Rename a Live URL Safely

Pick the new slug, add a single 301 from the old address, then update internal links and the canonical tag. Rebuild the sitemap with the XML Sitemap Generator so search engines see the new URLs. If duplicate versions of an address are part of the problem, the guide to URL canonicalization explains how redirects and canonical tags work together. Never leave the old address returning a 404.

SEO Friendly URLs in WordPress, Shopify and Wix

Each platform has its own place for slugs. In WordPress, open Settings, then Permalinks, and choose the Post name permalink structure. To edit a single slug, use the post editor, and note that WooCommerce adds its product permalink settings to that same screen. Changing the site wide structure touches every post, so take a backup first. WordPress usually redirects a changed post slug; confirm it with curl. The official WordPress permalink settings page documents the screen.

In Shopify, edit the Shopify URL handle in the Search engine listing preview and leave Create a URL redirect selected, which is the default. Prefixes such as /products/ and /collections/ are fixed by the platform. In Wix, open Pages & Menu, choose More Actions, then SEO basics, then URL slug. On a site with a connected domain, Wix normally adds a 301 when you rename a slug, but confirm it with curl -sIL and use the URL Redirect Manager for gaps.

On your own server, a renamed page needs one HTTP 301 line. Here are the Apache HTTP Server and Nginx versions, followed by the curl test. The sample anchors RedirectMatch so that only this one address moves, because Apache's plain Redirect directive also carries everything below the path to the new address.

# Apache, in .htaccess (exact match)
RedirectMatch 301 ^/Blog/SEO_Tips_2024$ /blog/seo-tips

# Nginx, inside the server block
location = /Blog/SEO_Tips_2024 { return 301 /blog/seo-tips; }

# Test from a terminal
curl -sIL https://example.com/Blog/SEO_Tips_2024

The output should show one 301 status line with a Location header pointing to the new address, then a 200. Forcing lowercase on every URL needs a RewriteMap in the Apache server config or a Lua or njs snippet in Nginx, so hand that part to your host or developer.

Common SEO Friendly URL Mistakes

Renaming without a redirect: The old address turns every inbound link and bookmark into a 404 page, while the ranking history stays with an address that no longer exists. If you are already dealing with the fallout, the guide to a custom 404 page shows how to keep those visitors on your site.

• Renaming everything because a tool warned. Changing a healthy URL often risks more than a tidier slug gains: 40 renamed pages mean 40 redirects to maintain and 40 chances of a typo.
• Keyword stuffing in URLs or pasting a whole headline. It reads badly and gains nothing: /best-cheap-seo-tool-free-seo-tool-online looks spammy to a human.
• Fixing the page but not the links. Menus and footers that still point to the old address add a redirect hop to every visit, and the report keeps flagging the same links.
• Mixing conventions. Inconsistent case, trailing slashes or www make one page answer on several addresses, which splits your analytics rows and your link signals.

Reading a pass as proof: A green row means four rules found nothing. It says nothing about parameters, keywords or depth, so don't treat it as a verdict on your whole URL structure.