Welcome to the Q&A Forum

Hi Lynn,

Thank you very much for your answer / analysis! As you said "It is a bit confusing" and I will just read your answer a couple of times...

I will grant your answer "Good answer" for you thorough analysis! I think it is spot on with the double "next/prev" and "rel=can" tags.  I do have one remark. You said:  When I turn off javescript, I get this:

In my opinion this is alright, because it shouldn't have a "prev" as this is the initial page.

We've been getting a ton of critical errors (about 80,000) in SeoMoz' Crawl Diagnostics saying we have duplicate content in our client's E-commerce site. Some of the errors are correct, but a lot of the pages are variations like:

www.example.com/productlist?page=1

www.example.com/productlist?page=2

However, in our source code we have used rel="prev" and rel="next" so in my opinion we should be alright.

Would love to hear from you if we have made a mistake or if it is an error in SeoMoz.

Here's a full paste of the script:

It does and it doesn't (great answer I know!). Let me expand a bit on that

Onpage optimization is definitely scalable. Site architecture really only becomes important as content scales. The more content, the more structure is needed. BUT as we all know onpage is only one part of SEO - and a fairly small one at that if you look at technical onpage optimization. Perhaps 20-25%.

The other 75-80% is content generation and offpage activites (link generation, social engagement etc.) and I think these are much much harder to scale unless you have a wicked unique product that just drives insane amounts of diverse links and mentions to not just a home page but to individual content pages deep within the site structure. I have only seen a handful or so sites ever achieving this.

If you already have a big structure running on a "no-separation" setup don't change it. The upside will not outweigh the potential disruption you cause. Do it for your new pages only.

The difference in interpretation by search engines will not be huge, but it's still worth sticking to the more readable hyphenated version. Also you don't risk the search engines misreading some urls due to new unwanted words forming from other words in a "no separation" scenario.

The PRO Web App is by far the most useful tool we have added to our SEO arsenal ever. It enables us to track and manage our efforts across multiple markets in such an easy and intuitive way.

The difference in interpretation by search engines will not be huge, but it's still worth sticking to the more readable hyphenated version. Also you don't risk the search engines misreading some urls due to new unwanted words forming from other words in a "no separation" scenario.

The PRO Web App is by far the most useful tool we have added to our SEO arsenal ever. It enables us to track and manage our efforts across multiple markets in such an easy and intuitive way.

If you already have a big structure running on a "no-separation" setup don't change it. The upside will not outweigh the potential disruption you cause. Do it for your new pages only.