Page architecture

[dexm10]

We have some good content on our site, particularly relating to UK employment law.

One section on unfair dismissal is split into 9 pages - there is a fair amount of legal detail.

The question is whether we should combine it all into one "mother of all unfair dismissal" page just to satisfy the Google monster or keep in as it is.

Some of the individual pages rank on page 1 already.

If we change the architecture are 301 redirects the best way to handle the changing urls?

The other more important issue is whether it is easier to read it all on one page or split it.

Keeping G happy may not actually keep our users happy. As the content is quite dense we want to ensure we don't overload people.

Any thoughts appreciated.

[SebastianCowie]

Google has come on a long way from the days where pagination was a major issue. If the pages are currently ranking, then I'd be adverse to 301'ing them all to one page.

Looking at your existing site structure, I think from a user perspective your current system is very user friendly and 1 super page wouldn't really add to the user experience.

Your best bet would be to introduce the rel=next / prev tags on pages that are sequential - more info is available here -> http://googlewebmastercentral.blogspot.co.uk/2012/03/video-about-pagination-with-relnext-and.html

[dexm10]

Hi Sebastian

Thanks for the response.

We were also concerned about cannibalisation as some of the links/page titles are:

qualifying for unfair dismissal, unfair dismissal exceptions, unfair dismissal & retirement, unfair dismissal test.