Welcome to Vortx Community Forum, where you can ask questions and receive answers from the staff at Vortx and other members of the community.

If you had a user account on our previous forums website, you will need to register a new account here.

Learn more about...

AspDotNetStorefront
DotFeed

Does anyone know how to fix duplicate content issues due to pages being produced with the ?pagenum=

So I am working on a ecommerce site & the main category pages (c-) are creating duplciates of themselves & Google WMT is reporting this as duplicate content & it is killing my rankings! For instance, if the category pages primary URL is: 

http://www.mysite.com/c-40-category-name.aspx?pagenum=3

 

Google is now reporting a ton of duiplicate page URLS such a as:

http://www.mysite.com/c-40-category-name.aspx?pagenum=3

http://www.mysite.com/c-40-category-name.aspx?pagenum=4

http://www.mysite.com/c-40-category-name.aspx?pagenum=5

http://www.mysite.com/c-40-category-name.aspx?pagenum=6

http://www.mysite.com/c-40-category-name.aspx?pagenum=7

And the list goes on & on & keeps growing. Does anyone out there have a solution for this? My current developer has no idea how to fix this & suggested using URL parameters in WMT but that does not seem to be working either.  Any help is greatly appreciated!

 

 

asked Oct 7, 2013 in MultiStore by spectrumSEO (110 points)

4 Answers

0 votes

A few easy ways to handle this...

  1. Output a rel canonical tag which points them all back at the c-40-category-name.aspx page (i.e. without the querystring).
  2. Modify your xmlpackage so that the description isn't output for any page other than the first.
  3. Don't worry about it.

 

TTFN

BFG

answered Oct 7, 2013 by BFG 9000 (1,050 points)
I just omit any url with pagenum from our sitemap
0 votes

You could try some of the solutions from this thread in the old forum.

http://forumarchive.vortx.com/threads/20241-Canonical-tag-amp-default-aspx-and-root-duplicate-content.html

 

 

answered Oct 29, 2013 by Chris (3,685 points)
0 votes
My understanding is that the rel="canonical" is intended only for pages with 100% duplicate content. In the scenario you describe you've actually got different content on each of those pages, and the URL querystring ?pagenum=n controls which set of content is being displayed.

I don't think that the canonical tag is appropriate for this, but rel="next" and rel="prev" probably are.

You should do a View All page if you can without taking too big a performance hit on that page load. Then put a canonical pointing to the View All on each of the paginated entities. If a View All just isn't possible, then just leave off the canonical altogether.

Those paginated entities should also have rel="next" and rel="prev" tags in their heads, pointing to the next and previous pages in the series. The first page in the series will not have a rel="prev" and the last page won't have a rel="next".
answered Jan 3, 2014 by Chris (3,685 points)
edited Feb 5, 2014 by Chris
0 votes

I know I keep commenting on this, but I've been working on the same issue.

Here's my solution for the paginated content.

https://forums.vortx.com/?qa=835/how-to-identify-last-of-paginated-pages

answered Feb 11, 2014 by Chris (3,685 points)
...