1

I'm rewriting URLs for a website, I know it could affect SEO, but I've no choice but to rewrite them, and 301 redirect the old ones to their new URLs. I want to try to keep the new URLs short and to the point.

When I'm counting the total number of characters in a URL, I shouldn't include the protocol https:// in my character count, right? Should include every character including dots, hyphens, slashes etc, after the initial https:// or something else? I'm assuming I count characters like I'll show in an example below, but want to check, please.

example.com/product/shoes

Would count as a total of 25 characters, right?

  • Oh, and should I could a trailing slash too like example.com/product/shoes/ would be a count of 26? – Matt Oct 13 at 18:27
  • 3
    Why are you counting the characters in your URLs? The specific count doesn't matter. It is all about usability. How descriptive are your URLs? How easy are they to type? How easy are they to remember? Sure, shorter URLs are better as long as they are descriptive enough, but what are you planning to do if your URLs are a bit "too long" for some metric or SEO tool? – Stephen Ostermiller Oct 13 at 18:52
1

Maybe there is more to your backstory that you have omitted?

You count the number of characters in the URL by literally counting every single character in the URL. No more; no less.

I shouldn't include the protocol https:// in my character count, right?

Why not? It is part of the URL. It is also shown in the Google SERPs.

Oh, and should I could a trailing slash too like example.com/product/shoes/ would be a count of 26?

Yes, include the trailing slash too.

Also include the query string and fragment identifier - it is all part of the URL.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.