Rel=prev/next and canonical tags on paginated pages?
-
Hi there,
I'm using rel="prev" and rel="next" on paginated category pages. On 1st page I'm also setting a canonical tag, since that page happens to get hits to an URL with parameters.
The site also uses mobile version of pages on a subdomain.
Here's what markup the 1st desktop page has:
Here's what markup the 2nd desktop page has:
Here's what markup the 1st MOBILE page has:
Here's what markup the 2nd MOBILE page has:
Questions:
1. On desktop pages starting from page 2 to page X, if these pages get traffic to their versions with parameters, will I'll have duplicate issues or the canonical tag on 1st page makes me safe?
2. Should I use canonical tags on mobile pages starting from page 2 to page X?
Are there any better solutions of avoiding duplicate content issues?
-
Yes, which is why I thought the first page might be a bit more helpful as a reference point.
-
Yes, but having a "view all" page is not possible. It will be too big to generate it, cache it and display it...
-
Okay, technically you should have a "view all" page and canonical to that which is what that is referring to, as you've got so many pages it is still possible to do that but may suffer from load times etc. So if you were to do it by the book you would ahve the rel=prev/next etc. and a view all button which lists all the content you would then canonical to that.
-
There's another link: http://googlewebmastercentral.blogspot.com/2013/04/5-common-mistakes-with-relcanonical.html
It says:
In cases of paginated content, we recommend either a rel=canonical from component pages to a single-page version of the article, or to use rel=”prev” and rel=”next” pagination markup. If rel=canonical to a view-all page isn’t designated, paginated content can use rel=”prev” and rel=”next” markup.
That's why i'm confused which way to go with...
-
It shouldn't matter how many pages though it might be beneficial to categorize them or similar to help users but you can canonical the first page or you can canonical a page that's the same or very similar.
There are many helpful facts on the link above.
-
Thanks for your answer, but I didn't say that this is for a few pages. What if there are 100k pages like these?
If I put both rel="prev"/rel="next" and canonical tags on them all. Will it be fine? What URLs do I put inside of canonical tags on pages other than the 1st page of the pagination?
-
First off you might find this page handy - http://googlewebmastercentral.blogspot.co.uk/2011/09/pagination-with-relnext-and-relprev.html
Canonical and pagination are the same (sort of) so you don't need both.
Canonical is when you've got a few pages that are the same and you're telling Google these are all the same but here is the original.
Pagination is telling Google these pages are all the same but they are in a sequence here is the first and here is the last page
Now there is no harm having both on a page especially if you've got some parameters, You should be safe plus duplicate content is not the worst thing to face and it's not going to cause that much harm if you've got a couple of pages duplicated.
Hope that helps.
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
-
Rel-canonical vs Href-lang use for an international website.
I have a multi-country website that uses country subfolders to separate countries. When I run a Moz scan, I am getting canonical related alerts (this is probably related to some of our US content being duplicated on the other country websites). Shouldn't I be using href-lang instead since I am telling search engines that a certain article in country B, is just a copy of the same article in country A?
Intermediate & Advanced SEO | | marshdigitalmarketing0 -
Revamping/Re-optimizing State Pages - What to do with old content?
Hello Moz Fam! I work in the insurance industry and we serve all 50 states. We have a state page for each state where the content is thin(ish). We're slowly revamping each page and hitting every talking point for that specific state. I've used multiple tools to come up with a content template and link building template for each page as well. I spent 5 months last year proof reading all these pages. So the content is good, just not SEO good. I didn't have the team or resources to really optimize them all yet, now I do. My question is... what should I do with the old content? I was thinking of publishing it to other platforms that we have a contributor account on and linking back to each state page with it. Of course, I would wait a few days for the search engines to index the new content so it wouldn't be duplicated on these platforms. Good or bad idea?
Intermediate & Advanced SEO | | LindsayE0 -
How does a page with a canonical for another domain impact SEO?
Hi, We have a requirement to host files that contains .html, .css, .js, and .pdf files externally on AWS S3 bucket. We have a landing page on our site that contains a link to those external links (i.e. pdf). On our site's (hosted on Drupal), landing page we already have a canonical link for the current landing page. On the .html file which is hosted externally, we were thinking to add the same canonical link that exists for the landing page so that search engines will go to the externally available .html file and interpret that the externally hosted file is related to our landing page. I was wondering if this is an acceptable solution without any SEO penalty. If there is a penalty, what would be the alternative solution to this so we can host files externally and drive most of the traffic to our landing page? Example Landing page: absolute url = https://www.site-domain.com/page-url ...... Externally available .html file (static) ......
Intermediate & Advanced SEO | | KendallHershey0 -
Best use of Canonical Tag with Mini-Websites
Hello, I was wondering what the best way would be to implement Canonical Tags in kind of a unusual situation. The company I work for creates single property websites for real estate agents. We register a URL such as 123MainSt.com - however through DNS we redirect that to a path. For example: http://www.944milmadadr.com would redirect to: https://www.qwikvid.com/realestate/go/v1/home/?idx=wDg1Gdwt7wnQiR3LMeCx28qPnWTKM0JV If we wanted to rank high in the search engines for our clients: "944 Milmada Dr" - Would it be the best practice to Canonical: http://www.944milmadadr.com ? Thanks in advance for any feedback on this!! Jason
Intermediate & Advanced SEO | | Qwikvid0 -
Canonical tags for duplicate listings
Hi there, We are restructuring a website. The website originally lists jobs that will have duplicate content. We have tried to ask the client not to use duplicates but apparently their industry is not something they can control. The recommendations I had is to have categories (which will have the idea description for a group of jobs), and the job listing pages. The job listing pages will then have canonical tags pointing to the category page as the primary URL to be indexed. Another opinion came from a third party that this can be seen as if we are tricking Google and would get penalised, **Is that even true? **Why would Google penalise for this if thats their recommendations in the first place? This third party suggested using nofollow on the links to these listings, or even not not index them all together. What are your thoughts? Thanks Issa
Intermediate & Advanced SEO | | iQi0 -
Lowercase VS. Uppercase Canonical tags?
Hi MOZ, I was hoping that someone could help shed some light on an issue I'm having with URL structure and the canonical tag. The company I work for is a distributor of electrical products and our E-commerce site is structured so that our URL's (specifically, our product detail page URL's) include a portion (the part #) that is all uppercase (e.g: buy/OEL-Worldwide-Industries/AFW-PG-10-10). The issue is that we have just recently included a canonical tag in all of our product detail pages and the programmer that worked on this project has every canonical tag in lowercase instead of uppercase. Now, in GWT, I'm seeing over 20,000-25,000 "duplicate title tags" or "duplicate descriptions". Is this an issue? Could this issue be resolved by simply changing the canonical tag to reflect the uppercase URL's? I'm not too well versed in canonical tags and would love a little insight. Thanks!
Intermediate & Advanced SEO | | GalcoIndustrial0 -
Is 301 redirect suggested on pagination pages
Hi - Due to pagination the default page of site is coming in 2 url with - ?page=1/ sub-url and /sub-url is 301 a recommended solution due to this pagination urls Also - is it required to create separate title and meta description of every pagination page We are taking specifically in context of our discounts and offer section http://www.mycarhelpline.com/index.php?option=com_offers&view=list&Itemid=9
Intermediate & Advanced SEO | | Modi0 -
Which page to target? Home or /landing-page
I have optimized my home page for the keyword "computer repairs" would I be better of targeting my links at this page or an additional page (which already exists) called /repairs it's possible to rename & 301 this page to /computer-repairs The only advantage I can see from targeting /computer-repairs is that the keywords are in the target URL.
Intermediate & Advanced SEO | | SEOKeith0