Element Code: UR-001
TL;DR: Your URL isn't going to hit a browser's hard limit, that ceiling sits around 2,000 to 2,083 characters depending on the browser and server. The real problem is anything north of about 100 to 115 characters looks bad in the SERP, gets truncated, confuses users who try to share it, and often signals a deeper information architecture problem (bloated categories, duplicate parameters, session IDs baked into the path).
What actually counts as "too long"
There are two completely different thresholds people mix up, and untangling them matters.
The first is the technical limit: the point where a browser or server will actually choke on a URL. Internet Explorer topped out at 2,083 characters. Modern browsers like Chrome, Firefox, and Safari can handle URLs tens of thousands of characters long without blinking, but servers, proxies, and CDNs often impose their own caps well below that, commonly somewhere around 2,000 to 8,000 characters depending on configuration. If you're anywhere near this range, you don't have an SEO problem, you have an architecture problem, because something is jamming session data, tracking parameters, or serialized state directly into the path or query string.
The second threshold is the practical SEO one, and it's the one this check is actually about. Screaming Frog's SEO Spider flags any URL over 115 characters by default under its "Over 115 Characters" issue in the URL tab. That's not an arbitrary number, it's roughly where Google started truncating URLs in SERP snippets on mobile, and it lines up with what most crawl audits use as a working ceiling. Google's own John Mueller has said URL length itself "doesn't matter" for rankings because Google treats URLs as identifiers, not ranking inputs, but he's also said keeping URLs under roughly 1,000 characters makes life easier for monitoring and debugging. Practically, if you're writing new URLs, you want to land in the 60 to 80 character range for anything that needs to look clean in search results and get shared without wrapping across three lines in a Slack message.
Why this actually matters
Google has stated URL length is not a direct ranking signal. Don't let anyone sell you on "shorter URLs rank better" as a blanket claim, that's not what's happening. But length correlates with several things that do matter:
Truncation in search results. Google displays a green breadcrumb-style URL path above the title in both desktop and mobile results, and long paths get cut with an ellipsis. A truncated URL looks less trustworthy and gives the user less context before they click, which affects CTR even though it's not touching your ranking position.
Crawl and rendering overhead. Excessively long URLs are frequently a symptom, not the disease. Faceted navigation exploding into thousands of parameter combinations, session IDs appended to every link, infinite calendar or filter permutations, these all generate long URLs and they also generate crawl budget waste. Screaming Frog and Sitebulb will show you the URL length issue sitting right next to duplicate content and near-duplicate parameter issues on the same set of pages, because they're usually the same root cause.
Canonicalization signals. Google has acknowledged that in choosing which URL variant to treat as canonical among near-duplicates, URL length and structure can be one of many secondary signals it weighs, alongside internal linking patterns and sitemaps. A shorter, cleaner URL among several variants of the same content has a slight edge in that specific decision, separate from any general ranking effect.
Sharing and UX. Long URLs break in emails, get mangled when pasted into chat tools, and look untrustworthy in a browser address bar. Users copy-paste URLs more than SEOs like to admit, and a URL that wraps or gets truncated by a messaging app's link preview is a real conversion friction point.
How to detect it
You don't need anything exotic here, standard crawl tooling covers this well.
- Screaming Frog: Crawl the site, open the URL tab, filter by "Over 115 Characters." Export the list and sort by length descending to find your worst offenders first.
- Sitebulb: Flags long URLs under its URL hints section and will cluster them with related issues like excessive parameters, which helps you spot the pattern instead of fixing symptoms one page at a time.
- Google Search Console: Won't give you a dedicated URL length report, but the Page Indexing report and the URL Inspection tool let you check individual long URLs for indexing status, and you can cross-reference against your Coverage or Pages report to see if long-URL pages are underperforming on impressions.
- Server log analysis: Pull your access logs and look at which long URLs are actually getting crawled by Googlebot versus which ones are being ignored. If Googlebot is spending crawl budget hammering a wall of 200-character faceted URLs that never get indexed, that's your priority fix, not the marketing blog post with a 130-character slug.
- Spreadsheet sanity check: If you don't have crawler access, export your XML sitemap and run a simple character count formula (LEN() in Excel or Google Sheets) against the URL column. Quick and dirty, but it works.
How to fix it, step by step
Fixing URL length is really an exercise in fixing information architecture, and it needs to be done carefully because you're touching indexed URLs.
- Audit before you touch anything. Crawl the site, export every URL over 100 characters, and sort by organic traffic or impressions from Search Console so you know what's actually earning rankings before you redirect it.
- Simplify slug structure. Drop stop words, dates that don't matter for evergreen content, and category paths nested more than two or three levels deep. "/blog/2019/03/12/category/subcategory/how-to-fix-broken-links-on-your-website" becomes "/blog/how-to-fix-broken-links".
- Kill duplicate and unnecessary parameters. Session IDs, tracking parameters like extra UTM strings baked permanently into canonical URLs, and redundant filter combinations should be handled through canonical tags or moved to POST requests where possible, not left stacking up in every crawlable link.
- Redirect properly, don't just rename. Every shortened URL needs a 301 redirect from the old path to the new one. Skipping this step or chaining multiple redirects (old to newer to newest) burns crawl budget and can dilute link equity. One hop, done.
- Update internal links to point directly at the new URL. Don't rely on the redirect to do this for you across your whole site, that just means every internal link now costs an extra hop. Find and replace internal links pointing to the old path.
- Resubmit and monitor. Push the updated URLs through Search Console's URL Inspection tool or submit an updated XML sitemap, then watch the Coverage and Performance reports for a few weeks to confirm the new URLs get indexed and retain rankings.
- Set a slug convention going forward. Whatever CMS you're on, lock in a rule: lowercase, hyphens not underscores, no stop words, no dates unless the content is genuinely time-bound, target under 80 characters including the domain.
What good looks like
A clean, well-structured URL reads like a short sentence a human could say out loud. Compare "seoprocheck.com/seo-checks/urls/url-too-long" (46 characters after the domain, and even the domain-inclusive version stays well under 60) to something like "seoprocheck.com/index.php?page=checks&category=urls&subcat=length&item=too-long&session=8f2b1a9c3d". The first tells you exactly what the page is about at a glance. The second is a database query wearing a URL costume.
| Length Range | Status | Typical Cause | Action |
|---|---|---|---|
| Under 60 chars | Ideal | Clean slug, shallow path | None needed |
| 60 to 100 chars | Acceptable | Descriptive category plus slug | Monitor, no urgency |
| 100 to 115 chars | Watch list | Deep nesting, extra taxonomy levels | Review for simplification |
| 115 to 2,000 chars | Flagged | Parameters, session IDs, faceted nav | Fix per steps above |
| 2,000+ chars | Critical | Broken parameter handling, infinite facets | Fix immediately, check crawl logs |
DO
- Keep new URLs under 80 characters including the domain where you can
- Use hyphens to separate words, never underscores or spaces
- Redirect old long URLs with a single 301, not a chain
- Cross-check Screaming Frog's URL length report against Search Console impressions before cutting anything
- Set a slug convention in your CMS so this doesn't recur
DON'T
- Mass-redirect high-traffic URLs without checking rankings and backlinks first
- Bake session IDs or unnecessary tracking parameters into canonical paths
- Chain multiple redirects when shortening a URL
- Assume shortening a URL will move rankings on its own, it won't
- Nest category paths five or six levels deep just to mirror your site's internal folder structure
FAQ
Does URL length directly affect Google rankings?
What's the actual character limit before a URL breaks?
Why does Screaming Frog flag URLs over 115 characters specifically?
Should I redirect every long URL on my site right now?
Do dates and category names in a URL count against length in a meaningful way?
Want a full crawl-level audit instead of fixing this one check in isolation? URL length issues rarely travel alone, they usually show up next to parameter bloat, duplicate content, and crawl budget waste. Our Advanced SEO Audit digs into the whole architecture, not just the symptom.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
