Pagination & duplicate meta
-
Hi
I have a few pages flagged for duplicate meta e.g.:
http://www.key.co.uk/en/key/workbenches?page=2
http://www.key.co.uk/en/key/workbenchesI can;t see anything wrong with the pagination & other pages have the same code, but aren't flagged for duplicate:
http://www.key.co.uk/en/key/coshh-cabinets
http://www.key.co.uk/en/key/coshh-cabinets?page=2
I can't see to find the issue - any ideas?
Becky
-
Regarding the links which point to pages, but include the hash. If Google is only seeing this page http://www.key.co.uk/en/key/workbenches
Will it be seeing these as pages which have duplicate content?
-
No problem thank you
-
I could write out how to implements rel next prev but it would be better to look at these articles
https://webmasters.googleblog.com/2011/09/pagination-with-relnext-and-relprev.html
https://mza.seotoolninja.com/ugc/seo-guide-to-google-webmaster-recommendations-for-pagination
-
Hi,
Yes there is javascript to sort the results on those pages.
Is the solution to have these URLs page=2 etc, correctly linked from the page number?
Then ensure rel/prev are used correctly?
I'm also concerned about the content we have at the bottom of the products being shown as duplicate.
-
Hi
Thank you for this. One thing I am confused about is, if Google doesn't crawl those paginated pages, why will it pick up the meta as duplicate?
Thank you for highlighting the links - I hadn't noticed this before.
Where should the rel next prev be coded?
Thanks for your feedback
-
I get how hashes work.
Crawlers do see the page=2, page=3, etc. URLs because the right/left navigation buttons to the side of the numbers link to them. I just proved this by crawling the site in Screaming Frog and doing a search for page=, they're all found.
Becky, there's something larger at play here, potentially with your CMS configuration. It looks like the navigation for paginated sections is messed up. Mouse-over the links and look at the URL in the lower left of your browser, and then click the link and look at your URL bar. The results are very different from what you see on mouse-over. I'd recommend your first step is to talk to your developers and see if they can fix this issue. As VivaCa mentioned, you could be getting false alarms on duplicates here from Moz, so you might be clear with the canonical and prev/next fix - Screaming Frog finds all of those tags properly.
-
I think you guys are missing the point. Anything after the hashtag is ignored. As far as the crawler is concerned, all the links to page 2,3,4,5 are all the same URL - that is why the crawler does not see the other pages.
There is no issue with canonical or how it interacts with the rel next prev. My point on the canonical was simply for illustrative purposes and looks to be implemented correctly.
Separate from the canonical the rel next prevs are setup incorrectly and that needs to be fixed once the issue with how the paginated pages are linked to using the URL with the hashtag parameters.
-
We have the exact same issue, and I found this reply from Dr. Pete helpful regarding this (assuming that what he says is still true): https://mza.seotoolninja.com/community/q/pagination-issues-on-e-commerce-site-duplicate-page-title-and-content-on-moz-crawl
His reply:
Unfortunately, Moz Analytics/PRO don't process rel=prev/next properly at this time, so we may give false alarms on those pages, even if the tags are properly implemented.
It can be tricky, but Google recommends a combination of rel=canonical and rel=prev/next. Use the canonical tag to keep sorts from getting indexed, and then use rel=prev/next for the pagination itself. Your 3rd example (page=2...) should rel=prev/next to the URLs before and after it but then canonical to the page=2 variation with no sort parameter. It can get complicated fast, unfortunately, but typically rel=canonical can be implemented in the template. So, once you've got it figured out, it'll work for the entire site.
-
As far as I am aware, there is nothing wrong with using both canonicals and pagination on the same page. Google says this as well here: https://support.google.com/webmasters/answer/1663744?hl=en
We have pagination and canonicals set up as suggested in the Google article and also have some issues with Moz saying we have duplicate content, which the pagination should "fix" as far as I understand it.
From the article:
rel="next"
andrel="prev"
are orthogonal concepts torel="canonical"
. You can include both declarations. For example, http://www.example.com/article?story=abc&page=2&sessionid=123 may contain: -
View source on both pages.
http://www.computerhope.com/issues/ch000746.htm
Or use the handy Moz bar to view the descriptions
Both your title and meta are exactly the same - aka they are duplicates
view-source:http://www.key.co.uk/en/key/workbenches
<title>Workbenches & Work Stations from Key</title>view-source:http://www.key.co.uk/en/key/workbenches?page=2
<title>Workbenches & Work Stations from Key</title>You can remedy this by simply adding "- Page #" at the end of your title and description, where # is whatever page in the pagination you are at.
The reason why the other pages in your pagination are not showing up with the duplicate issue is that you are hiding them from Google.
When I am on Page 2 and I click on the buttons for page 3,4,5 etc - here are the links that are shown
Page 3 http://www.key.co.uk/en/key/workbenches?page=2#productBeginIndex:60&orderBy:5&pageView:list&
Page 4 http://www.key.co.uk/en/key/workbenches?page=2#productBeginIndex:90&orderBy:5&pageView:list&
Page 5 http://www.key.co.uk/en/key/workbenches?page=2#productBeginIndex:120&orderBy:5&pageView:list&
These are the links that people can click on to navigate at the bottom of the page. Everything behind the hash is ignored by Google. It is a clever way to hide parameters, but when Google looks at this it is just seeing links to the exact same page. Likewise, on that page you have a canonical link to page 2, so even if Google could see the parameters you are giving it a directive that tells Google that Page 2 is the only page that exists.
I can see that you are using rel next prev to designate Page 3 as Page 3 http://www.key.co.uk/en/key/workbenches?page=3 etc, but you are not coding the rel next prev properly by putting it up in the header with the meta tags.
In summary
- You have duplicate title and meta tags for all your paginated pages
- You are not linking to your paginated pages properly within the user navigation
- You are incorrectly using rel next prev
-
Hi,
I can't explain why Moz throws a duplicate for one and not the other, that's odd. I did look at the source code for both of the paginated URLs you posted, and it looks like rel=prev/next is mostly right, but a couple suggestions:
- Remove the self-referring canonical tags - On this URL (http://www.key.co.uk/en/key/coshh-cabinets?page=2) you've got a canonical that points to itself, that's in conflict with the rel=prev/next tags. Rel=prev/next should be used in place of canonical tags, not in conjunction with.
- The one exception to my point about canonicals above: on page=1 of your pagination, canonicalize that to the root. Example, http://www.key.co.uk/en/key/coshh-cabinets?page=1 should canonicalize to http://www.key.co.uk/en/key/coshh-cabinets, since those are identical in actual displayed content.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
WhoIs, SEO & Privacy
Is WHOIS data used by Google as a ranking signal? We had a website that had some bad SEO work done a while ago hence took a knock, If I use the same WHOIS data on a new site is that likely to cause an issue? Also I don't like the idea of providing too much information for privacy reasons, so have tended to stick to general email addresses and department names rather than actual personal information. Is that a bad approach?
Intermediate & Advanced SEO | | seoman100 -
Rel=Alternate on Paginated Pages
I've a question about setting up the rel=alternate & rel=canonical tags between desktop and a dedicated mobile site in specific regards to paginated pages. On the desktop and mobile site, all paginated pages have the rel=canonical set towards a single URL as per usual. On the desktop site though, should the rel=alternate be to the relevant paginated page on the mobile site (ie a different rel=alternate on every paginated page) or to a single URL just as it is vice versa. Cheers chaps.
Intermediate & Advanced SEO | | eventurerob1 -
E-commerce duplicate URLS
Hi I just realized that my e-commerce products do not have any difference except the SKUS, PRICE and THE PRODUCT name. Apart from each page has the same sidebar and a piece of content ( same ) under each product pages. And this is the reason why i am getting too many duplicate urls warning through Moz analytics. I do not have any other contents to add for each product because of the nature of the product. Only the price, product name and the SKUs will be different and rest will all be same for each products. How can i fix this ? Thanks
Intermediate & Advanced SEO | | MindlessWizard0 -
Yoast & rel canonical for paginated Wordpress URLs
Hello, our Wordpress blog at http://www.jobs.ca/career-resources has a rel canonical issue since we added pagination to the front page and category-pages. We're using Yoast and it's incorrectly applying a rel-canonical meta tag referencing page 1 on page 2, 3, etc. This is a known misuse of the rel-canonical tag (per Google's Webmaster Blog - http://googlewebmastercentral.blogspot.ca/2013/04/5-common-mistakes-with-relcanonical.html, which says rel-canonical should be replaced with rel-prev and rel-next for page 2, 3, etc.). We don't see a way to specify anywhere in Yoast's options to correct this behaviour for page 2, 3, etc. Yoast allows you to override a page's canonical URL, otherwise it automatically uses the Wordpress permalink. My question is, does anyone know how to configure Yoast to properly replace rel-canonical tags with rel-prev and rel-next for paginated URLs, or do I need to look at another plugin or customize the behavior directly in my child theme code? This issue was brought up here as well: http://moz.com/community/q/canonical-help, but the only response did not relate to Yoast. (We're using Wordpress 3.6.1 and Yoast "Wordpress SEO" 1.4.18)
Intermediate & Advanced SEO | | aactive0 -
2 Ecommerce sites & SEO
Hi, i am managing 2 ecommerce sites that sell a lot of identical products. snowsupermarket.co.uk - public webshop shop.snowbusiness.com - trade webshop Should i optimise the 2 sites to target different keywords for all products or, should i keep the keywords the same but, vary the meta data/ description etc. to avoid duplication. Is there a clear argument to have to ecommerce websites ranking high for our products & dominating page 1, even though they will be technically competing against each other? Thanks, Ben
Intermediate & Advanced SEO | | SnowFX0 -
Duplicate Content/ Indexing Question
I have a real estate Wordpress site that uses an IDX provider to add real estate listings to my site. A new page is created as a new property comes to market and then the page is deleted when the property is sold. I like the functionality of the service but it creates a significant amount of 404's and I'm also concerned about duplicate content because anyone else using the same service here in Las Vegas will have 1000's of the exact same property pages that I do. Any thoughts on this and is there a way that I can have the search engines only index the core 20 pages of my site and ignore future property pages? Your advice is greatly appreciated. See link for example http://www.mylvcondosales.com/mandarin-las-vegas/
Intermediate & Advanced SEO | | AnthonyLasVegas0 -
Canonical Meta Tag
Can someone explain how this works and how necessary is it? For example, I have a new client, who is ranking WITHOUT the www in their domain, but they have a good deal of backlinks already that have www in it. When I set up google webmaster tools I made 2, one for WWW and one for WITHOUT and there are diffenet numbers of backlinks for each. I have no idea what do about this or if I should even do anything. Thanks
Intermediate & Advanced SEO | | TheGrid0 -
Is this will post Duplicated Content
I have domain let say abcshoesonlinestore.com and inside pages of this abcshoesonlinestore.com is ranking very well such as affiliate page, knowledgebase page and other pages, HOWEVER i would like to change my home page and product page to shorter url which abcshoes.com and keep those inside page like www.abashoesonlinestore.com/affiliate or www.abcshoesonlinestore.com/knowledgebase as it is - will this pose duplicate content? This is my plan to do it: the home page and product page will be www.abcshoes.com and when people click www.abcshoes.com/affiliate it will redirect 301 to abcshoesonlinestore.com/affiliate HOWEVER if someone type abcshoesonlinestore.com or abcshoesonlinestore.com/product it will redirect to abcshoes.com or its product page itself (i want to use 302 instead 301 (ASSUMING if the homapage or product page have manual penalization or anything bad we want to leave it behind and start fresh JUST assume because i read some post that 301 will carry any bad thing to new site too) The reason i do not want to 301 from abcshoesonlinestore.com to abcshoes.com is because those many pages is ranking top 3 in GOOGLE ( i worry will lose this ranking since this bringing traffic for us) Is this good idea or bad idea or any better idea or should i try to see the outcome 🙂 - the only concern is from abcshoesonlinestore.com to abcshoes.com will pose as duplicate content if i do not use 301 - or can i use google webmaster tools to remove the home page and product page for abcshoesonlinestore.com can we tell google that? PS: (home page and product page will have new revise content and minor design change) but inside page will stay the same design Please give me some advise
Intermediate & Advanced SEO | | owen20110