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://moz.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://moz.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
-
Google Not Pulling The Right Title Tag & Meta Description
Hi guys. We've found Google is pulling the wrong information for our title tag and meta description. Instead of pulling the actual title tag, Google is pulling the menu name you click on to get to the page: "Bike Barcelona" instead of "Barcelona Bike Tours | ...." Also, we've found that, instead of pulling the meta description we wrote, Google is using text from the pages copy. Any tips?
Intermediate & Advanced SEO | | BarcelonaExperience0 -
How would you handle this duplicate content - noindex or canonical?
Hello Just trying look at how best to deal with this duplicated content. On our Canada holidays page we have a number of holidays listed (PAGE A)
Intermediate & Advanced SEO | | KateWaite
http://www.naturalworldsafaris.com/destinations/north-america/canada/suggested-holidays.aspx We also have a more specific Arctic Canada holidays page with different listings (PAGE B)
http://www.naturalworldsafaris.com/destinations/arctic-and-antarctica/arctic-canada/suggested-holidays.aspx Of the two, the Arctic Canada page (PAGE B) receives a far higher number of visitors from organic search. From a user perspective, people expect to see all holidays in Canada (PAGE A), including the Arctic based ones. We can tag these to appear on both, however it will mean that the PAGE B content will be duplicated on PAGE A. Would it be the best idea to set up a canonical link tag to stop this duplicate content causing an issue. Alternatively would it be best to no index PAGE A? Interested to see others thoughts. I've used this (Jan 2011 so quite old) article for reference in case anyone else enters this topic in search of information on a similar thing: Duplicate Content: Block, Redirect or Canonical - SEO Tips0 -
Pagination duplicate title and meta description
Hello, Getting a lot of duplicate title and meta description errors via google webmaster tools. For best SEO practices, do i no-index the page/2's, page/3's...? More importantly, i see how MOZ did it by adding "page 3" to their titles such as http://moz.com/blog?page=3. Is that a better way of doing it? If so, how do i do that on Yoast SEO? Thank you so much!
Intermediate & Advanced SEO | | Shawn1240 -
Duplicated privacy policy pages
I work for a small web agency and I noticed that many of the sites that we build have been using the same privacy policy. Obviously it can be a bit of a nightmare to write a unique privacy policy for each client so is Google likely to class this as duplicate content and result in a penalty? They must realise that privacy policies are likely to be the same or very similar as most legal writing tends to be! I can block the content in robots.txt or meta no-index it if necesarry but I just wanted to get some feedback to see if this is necessary!
Intermediate & Advanced SEO | | Jamie.Stevens1 -
Site been plagiarised - duplicate content
Hi, I look after two websites, one sells commercial mortgages the other sells residential mortgages. We recently redesigned both sites, and one was moved to a new domain name as we rebranded it from being a trading style of the other brand to being a brand in its own right. I have recently discovered that one of my most important pages on the residential mortgages site is not in Google's index. I did a bit of poking around with Copyscape and found another broker has copied our page almost word-for-word. I then used copyscape to find all the other instances of plagiarism on the other broker's site and there are a few! It now looks like they have copied pages from our commercial mortgages site as well. I think the reason our page has been removed from the index is that we relaunced both these sites with new navigation and consequently new urls. Can anyone back me up on this theory? I am 100% sure that our page is the original version because we write everything in-house and I check it with copyscape before it gets published, Also the fact that this other broker has copied from several different sites corroborates this view. Our legal team has written two letters (not sent yet) - one to the broker and the other to the broker's web designer. These letters ask the recipient to remove the copied content within 14 days. If they do remove our content from our site, how do I get Google to reindex our pages, given that Google thinks OUR pages are the copied ones and not the other way around? Does anyone have any experience with this? Or, will it just happen automatically? I have no experience of this scenario! In the past, where I've found duplicate content like this, I've just rewritten the page, and chalked it up to experience but I don't really want to in this case because, frankly, the copy on these pages is really good! And, I don't think it's fair that someone else could potentially be getting customers that were persuaded by OUR copy. Any advice would be greatly appreciated. Thanks, Amelia
Intermediate & Advanced SEO | | CommT0 -
Help with Effective Meta Description
Can someone give me a sample of an effective meta description tag? All of the best practice stuff I read doesn't talk about how to raise CTR. It seems to me that this is a neglected area of SEO, and we want to do this right. Obviously, we will need to test. For example, my main home page keyword is "IT Support" Things I might want to put in the tag: Free Network Assessments 100% Risk Free Trials "Relentless IT Support" (Major Theme) 30 Years of Experience (since 1984) Eliminate your IT Support Headaches Forever (Too long) Call to action? BTW, Thanks to everyone for your help. This is a great community. Solid advice from experts. Here's an example of what I would create Relentless IT Support Since 1984. Trust and Accountability. 100% Risk Free Trials. Contact us today for Free IT Assessment.
Intermediate & Advanced SEO | | CsmBill0 -
Simple Pagination and Rel Canonical
Hello, I am trying to find a solid solution to this. I think it is simple, but trying to think of a good setup for SEO. If you have a paginated result set, page 1, page 2, page 3, page 4. What i am wondering is, should I point my REL CANONICAL page to Page 1 always, so i'm not loosing power from the first page? Domain structure: www.domain.com/search/[term]/page1/
Intermediate & Advanced SEO | | aactive
www.domain.com/search/[term]/page2/ Should I point all pages to page 1, so I don't get watered down as we go farther into the site? Thoughts?0 -
Capitals in url creates duplicate content?
Hey Guys, I had a quick look around however I couldn't find a specific answer to this. Currently, the SEOmoz tools come back and show a heap of duplicate content on my site. And there's a fair bit of it. However, a heap of those errors are relating to random capitals in the urls. for example. "www.website.com.au/Home/information/Stuff" is being treated as duplicate content of "www.website.com.au/home/information/stuff" (Note the difference in capitals). Anyone have any recommendations as to how to fix this server side(keeping in mind it's not practical or possible to fix all of these links) or to tell Google to ignore the capitalisation? Any help is greatly appreciated. LM.
Intermediate & Advanced SEO | | CarlS0