Can long URLs hurt you?

At SEO Liverpool we’ve been having a discussion about long URLs, in the past they have been spammy. I’m sure I’ve read a thread that actually commented on some URLs being a bit too long for comfort (SEO SEM agencies take note!)

Look at my example URL:

www.thisoldsite.co.uk/some-item-like-this-and-another-keyword-like-this-and-sometimes-even-more.42html

I’m all for having descriptive URLs, but …. but on occasion this seems to be taking it a bit too far and most of the time you’ll have trouble identifying anything that matches in the content of the page. Too far? Does that mean a search engine will penalise really long URLs? Or in this case, it does it just looks spammy to a manual review?

Sometimes if you dig deeper, you’ll noticed that you can find the same page as long as you include 42 at the end of the URL. Now, this is a common CMS issue with many sites. We’d deal with this with a 301 redirect from the broken URL to the true URL.

In this illustration, the CMS identifies the page by having the ID (i.e. 42) in the URL and then returns the dynamic content. The CMS should contain a real URL and then 301 redirect any other URLs that have id 42 in them to the real URL.

So, when building a CMS or SEO training staff, you might want to do a couple things in terms of URLs:

(1) Restrict the length of the URL to something normal

(2) 301 Redirect any duplicate URLs to the real URL

404 or 301 Your Old Pages? Which is Best For SEO?

We’ve had a bit of a discussion at SEO Liverpool about getting did of multiple subpages & not get penalised. The discussion is around the topics of using different techniques when removing or redirecting pages.

Which is better to do for SEO? Do you want to 301, redirect a page, or 404, return a not found status, a page?

I can tell you that the best SEO companies think about this fairly frequently. At Summit we take different approaches for different sites. I try, try hard, to not think only about SEO and think what would also benefit the user.

Here is my guide:

301 redirect everything you possibly can, when it makes sense. If you have a page about big blue pineapple chairs on the old site and you are moving it to the new site, 100% use a 301 redirect from the old URL to the new one. However, sometimes it is not that easy.

Sometimes you have a site with hundreds, if not thousands of pages, if not more. Manually redirecting each page is a huge chore. When we can, we set up logic based 301 redirects, to redirect the old URL to the new URL dynamically. That can result in thousands of redirects, but Google should handle those fine over time.

For all the pages that do not match that pattern or logic AND for sites where there is no logic (large, old, non-database driven sites), you want to manually redirect the most important pages. So make sure you have analytics installed on the previous site, way before launching the new site – this way you have the 301 redirects in place, on the most important pages, when you launch.

Then, all other pages, I typically set up a 404 page, returning a valid 404 status code, plus it is set up as a custom 404, so users who land on it, have an avenue to find the right page.

Some people have suggested that sometimes you should think about setting up what is called a “soft” 404 page. Basically, a soft 404 page, is a page that looks like a page not found page, but returns a server status of 200, meaning, the page is valid and active and should not be deleted. The only issue I see with that, is that the URL of the page will be different but the content of the page will be very similar, if not exact, to the other soft 404 pages you set up. Of course, if you are a smart coder, you can look at the Google referrer or the old page’s data and serve up contextual relevant product or content on that page, which would make the page’s content more unique.

So, like I said, it totally depends on the situation and your search engine marketing experience.