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
-
Paginated Pages Page Depth
Hi Everyone, I was wondering how Google counts the page depth on paginated pages. DeepCrawl is showing our primary pages as being 6+ levels deep, but without the blog or with an infinite scroll on the /blog/ page, I believe it would be only 2 or 3 levels deep. Using Moz's blog as an example, is https://mza.seotoolninja.com/blog?page=2 treated to be on the same level in terms of page depth as https://mza.seotoolninja.com/blog? If so is it the https://site.comcom/blog" /> and https://site.com/blog?page=3" /> code that helps Google recognize this? Or does Google treat the page depth the same way that DeepCrawl is showing it with the blog posts on page 2 being +1 in page depth compared to the ones on page 1, for example? Thanks, Andy
Intermediate & Advanced SEO | | AndyRSB0 -
Domain Change Of Address & Sale
Hi Moz community Let's say I have two domains www.domain1.com www.domain2.com domain1 is my main website. Domain 2 was a peripheral side project I was working on. I recently decided to shut it down. So I hooked up the proper 301s and filed a change of address request with Google Webmaster tools. I have had an offer for someone to purchase domain2 - I have absolutely no use for it and would like to sell it. I just want first to figure out that: I can do this without losing any ranking to my main site. I can disassociate this domain from myself and my Company completely. I don't want any of the work we put into it to transfer to the new owner. How can I do this? thanks!
Intermediate & Advanced SEO | | Shop-Sq0 -
Duplicate meta descriptions
Hi All Does having quite a few Duplicate meta descriptions hurt SEO. I am worried that I have too many and thinking this could be the reason for my recent drop in search visibility. Thanks in Advance. Andy
Intermediate & Advanced SEO | | Andy-Halliday0 -
Pagination, Canonical Tag & Best Practices
I have an eCommerce site that dynamically creates category pages, which produce canonical tags in the header. For multiple page categories, it adds the page number to the URL. For example, this category has 3 pages.... Because most categories have too many products, I can't follow Googles suggestion of creating a "view all" page. Furthermore since all these pages use the same template, I'm unable to insert a NOINDEX tag in all the pages after the first page. Also, in this scenario, I'm unable to insert the discreet code for Next/Previous, which is also suggested by Google. My only option for maintaining these dynamically generated category pages would be to hardcode the first conical tag in the template, which would then be produced on all subsequent paginated pages. Consequently, every paginated page in this category would have the same canonical tag pointing to the first page. Would this incur the wrath of Google and would I'd be better off leaving the pagination they way it is?
Intermediate & Advanced SEO | | alrockn0 -
Meta tags - are they case sensitive?
I just ran the wordtracker tool and noticed something interesting. The tool didn't pick up our meta description. It's strange as our meta descriptions appear in organic search results and Moz never reported missing meta descriptions.After reviewing other pages, I noticed our meta description tag is written as the following: name="Description" content=" I never thought about this, but are meta tags case sensitive? Should it be written as: name="description" content=" Thoughts?
Intermediate & Advanced SEO | | Bio-RadAbs0 -
Duplicate title tags in a pagination case (not search results)
Hello fellows I working on a site that have duplicate pages' titles tags, the case is the following: there is a category page that is split in couple pages via pagination (1,2,3 ....) all these pages have the same title tag for example: looking at this page for example, it has a pagination at the bottom, all the pages in the pagination (let's say page 5 for example) have the same title tag for the rest (including the first page). How should I deal with this case? should I simply add to the title tag its corresponding page number? e.g, full interviews - page 1? or I should I use canonical tag? I'm really confused. Your help is really appreciated.
Intermediate & Advanced SEO | | MHD0 -
How are they avoiding duplicate content?
One of the largest stores in USA for soccer runs a number of whitelabel sites for major partners such as Fox and ESPN. However, the effect of this is that they are creating duplicate content for their products (and even the overall site structure is very similar). Take a look at: http://www.worldsoccershop.com/23147.html http://www.foxsoccershop.com/23147.html http://www.soccernetstore.com/23147.html You can see that practically everything is the same including: product URL product title product description My question is, why is Google not classing this as duplicate content? Have they coded for it in a certain way or is there something I'm missing which is helping them achieve rankings for all sites?
Intermediate & Advanced SEO | | ukss19840 -
Nuanced duplicate content problem.
Hi guys, I am working on a recently rebuilt website, which has some duplicate content issues that are more nuanced than usual. I have a plan of action (which I will describe further), so please let me know if it's a valid plan or if I am missing something. Situation: The client is targeting two types of users: business leads (Type A) and potential employees (Type B), so for each of their 22 locations, they have 2 pages - one speaking to Type A and another to Type B. Type A location page contains a description of the location. In terms of importance, Type A location pages are secondary because to the Type A user, locations are not of primary importance. Type B location page contains the same description of the location plus additional lifestyle description. These pages carry more importance, since they are attempting to attract applicants to work in specific places. So I am planning to rank these pages eventually for a combination of Location Name + Keyword. Plan: New content is not an option at this point, so I am planning to set up canonical tags on both location Types and make Type B, the canonical URL, since it carries more importance and more SEO potential. The main nuance is that while Type A and Type B location pages contain some of the same content (about 75%-80%), they are not exactly the same. That is why I am not 100% sure that I should canonicalize them, but still most of the wording on the page is identical, so... Any professional opinion would be greatly appreciated. Thanks!
Intermediate & Advanced SEO | | naymark.biz0