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.
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
-
Penalty for duplicate content on the same website?
Is it possible to get a penalty for duplicate content on the same website? I have a old custom-built site with a large number of filters that are pre-generated for speed. Basically the only difference is the meta title and H1 tag, with a few text differences here and there. Obviously I could no-follow all the filter links but it would take an enormous amount of work. The site is performing well in the search. I'm trying to decide whether if there is a risk of a penalty, if not I'm loath to do anything in case it causes other issues.
Intermediate & Advanced SEO | | seoman100 -
Google overriding meta description - retrospective?
Hi all, we run a furniture store and our results in Google.co.uk almost always use the page's content as the description in the search results, even though we have a correctly implemented meta description tag. The rival's pages that rank above and below us almost always show the ranking page's meta description in Google's results page. Our developer seems to think it's because we added the meta description tags long after the pages were first indexed by Google and he seems to think Google has "fixed" on the page content and is happy with that over our meta description ...but I've never heard of that before. Thank you.
Intermediate & Advanced SEO | | Bee1590 -
Pagination dilemma
We are about to migrate an ecommerce site to a whole different platform and we are facing a pagination dilemma. The new platform has a view all page for each category where all the individual pages point with a rel canonical to the view all page. What would be best to to as for the redirect. should we do the 301 redirect to the view all page ? Considering that the view all page takes quite a time to load, wouldn’t it be good to drop the view all an implement the rel-next, rel-prev and point the 301 redirect to the first page. If we do the view all page, wouldn't be a problem if all the natural backlinks that we'll get will not be for the page view all page, but for the page1, page2 etc?
Intermediate & Advanced SEO | | lvt0 -
Title Tags & Keyword Order
Hi I've read various articles on this - some saying it's still important to have the keyword at the beginning of the title and some saying it's not a big factor anymore? Does anyone have an opinion on this?
Intermediate & Advanced SEO | | BeckyKey0 -
Duplicate content on product pages
Hi, We are considering the impact when you want to deliver content directly on the product pages. If the products were manufactured in a specific way and its the same process across 100 other products you might want to tell your readers about it. If you were to believe the product page was the best place to deliver this information for your readers then you could potentially be creating mass content duplication. Especially as the storytelling of the product could equate to 60% of the page content this could really flag as duplication. Our options would appear to be:1. Instead add the content as a link on each product page to one centralised URL and risk taking users away from the product page (not going to help with conversion rate or designers plans)2. Put the content behind some javascript which requires interaction hopefully deterring the search engine from crawling the content (doesn't fit the designers plans & users have to interact which is a big ask)3. Assign one product as a canonical and risk the other products not appearing in search for relevant searches4. Leave the copy as crawlable and risk being marked down or de-indexed for duplicated contentIts seems the search engines do not offer a way for us to serve this great content to our readers with out being at risk of going against guidelines or the search engines not being able to crawl it.How would you suggest a site should go about this for optimal results?
Intermediate & Advanced SEO | | FashionLux2 -
Duplicate Content and Titles
Hi Mozzers, I saw a considerable amount of duplicate content and page titles on our clients website. We are just implementing a fix in the CMS to make sure that these are all fixed. What changes do you think I could see in terms of rankings?
Intermediate & Advanced SEO | | KarlBantleman0 -
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 -
Blog posts, blog archives and duplication
Just reviewed a blog integrated with my website, and have noticed duplicate content - the blog homepage includes blogpost summaries (not a major issue as now set up so only put in opening paragraphy then anchor text to full blog post). Then that's a full blog blog post if you click for more - then that's carbon copied over in the archive. So one near exact duplicate. Is this something worth taking action on with nocrawl tags, etc., on archive duplicates of blog posts, or shouldn't I be to hung-up on this? I'm a scientist by training, so tend to go further and further once I get going...
Intermediate & Advanced SEO | | McTaggart0