Long URL Example: How Long Can a URL Be?
My full address is as long as the Turkish bean I climbed, and rather harder to descend.
The short answer
- What it is
- A long URL is an address with more characters than an audit allows, and a common line is 100 characters for the full URL. This is a style limit, far below what browsers and servers can handle.
- Why it matters
- Long URLs are hard to read, share, and quote. They often point to messy templates or stray tracking parameters, which can also create duplicate pages.
- How a crawler should report it
- Flag any full URL over 100 characters, counting the protocol, host, path, and query. Show the actual length so the reader can see how far over it is, and report it as a warning rather than an error.
- Live examples
How Long a URL Can Be Before It Causes Trouble
A long URL example makes the problem plain. Take a slug that strings together a page title, a category, a date, and three tracking tags. It works, but no one wants to read it. So how long can a URL be? The HTTP standard gives no fixed maximum, though it advises support for at least 8,000 octets. Sitemap files have a firmer rule. Each URL in one must be under 2,048 characters.
Real limits depend on the software. Older versions of Internet Explorer stopped at 2,083 characters, which is why 2,000 became a rule of thumb. Modern browsers accept far more. Servers are often the tighter limit. Apache allows about 8,190 bytes for the request line by default, and nginx has a similar buffer limit. A request that is too long gets a 414 URI Too Long status, or a 400 on some setups.
Search engines can crawl and index long URLs, and length alone is not a penalty. Google has said that a shorter URL may be chosen as the canonical when two URLs show the same page. Long addresses can also be cut off in places where people share links. Some email clients break them across lines. That can leave a reader with half a link.
To detect long URLs, sort your crawl by URL length and read the top of the list. Look for patterns, not just single cases. Session IDs, repeated folders, and stacked filter values are common causes. To fix new pages, write slugs by hand and keep only the words that matter. Remove dates and stop words that add nothing. Move tracking out of the path. If you change a live URL, add a 301 redirect, update internal links, and update the sitemap.