Canonical url with pagination
-
I would like to find out what is the standard approach for sections of the site with large number of records being displayed using pagination. They don't really contain the same content, but if title tag isn't changed it seem to process it as duplicate content where the parameter in the url indicating the next page is used.
For the time being I've added ' : Page 1' etc. at the end of the title tag for each separate page with the results, but is there a better way of doing it? Should I use the canonical url here pointing to the main page before pagination shows up in the url?
-
Moz crawls paginated pages even if you have added the rel="next" and rel="prev".
-
Does Moz manage crawling through Wordpress paginated posts (with tags rel="next" / "prev") ?
Since I divided long posts in two posts (page 1 and page 2) using "nextpage" feature in Wordpress, Moz shows duplicate title between page 1 and page 2. For example : https://captaincontrat.com/guide/societe-en-cours-de-formation/ and https://captaincontrat.com/guide/societe-en-cours-de-formation/2/
Thanks a lot
-
Thanks.
-
It does, although Google seems to be slightly less fond of it over time. Since I wrote my reply in March, rel=prev/next are actually beginning to be more effective. I've never seen any major issues with NOINDEX'ing pages 2+, though. In many cases, it's just a lot easier to implement.
The big issue this year is that Google sometimes just ignores deindexation signals. So, you really have to try it and see.
I'd also add that I'm talking about search pagination here, not article pagination. Rel=prev/next is a much better choice for article pagination, because the content is unique across pages. Indexing page 11 of search results isn't much of a benefit, in most cases.
-
Anyone use "no-index" and "follow" for page 2 , page 3 etc? Does this work?
-
So, I have to say that I'm actually upset about Google's recent recommendations, because they've presented them as if their simple and definitive, whereas they're actually very complicated to implement and don't always work very well. A couple of problems:
(1) Rel=prev/next is a fairly weak signal. If you're just trying to help the crawlers, it's fine. If you have issues with large-scale duplication (or have been hit with Panda), it's not a good fix, in my experience.
(2) Rel=prev/next isn't honored at all by Bing.
(3) It's actually really tough to code, especially their proposed Rel=prev/next + Rel=canonical solution.
There are a couple of other options:
(a) If you have a "View All" page (or if that's feasible without it being huge), you can rel-canonical to it from all of the paginated pages.
(b) You can META NOINDEX, FOLLOW pages 2+. I find that's a lot easier and usually more effective. Again, it depends on the severity of the problem and scope of the paginated content.
If you're not having problems and can manage the implementation, Rel=prev/next is a decent first step.
I should add that this is assuming you mean internal search results, and not content pagination (like paginated articles). With paginated search, the additional pages usually aren't a good search-user experience (Google visitors don't need to land on Page 11 of 17 of your search results), so I find that proactively managing them is a good thing. It really does depend a lot on the scope and the size of your index, though. This is a very complex issue that tends to get oversimplified.
-
These pages obviously contain different items and each page only shares the same title and meta tags.
Marcin - do you think that if I add the rel attribute that will solve the problem? Will the Moz reports actually pick it and won't mark it as Duplicate Content and Title?
-
Hi Sebastian,
actually, there's a very clean solution which is fully supported by Google - just use rel="next" and rel="prev" in your paginated links to indicate relationships between pages.
Here's a recent discussion of the best practices from Google itself, and here's another comment by Yoast (famous for his Wordpress SEO plugin).
Hope it helps.
-
I think this is going to depend on two things: 1. Your Site Structure and If you want those pages indexed.
Rand Fishkin - recommends for paginated results not to put the canonical tag pointing back to the top page, which I agree.
Site Structure
If the final pages can only be found by going through the paginated structure, you'll definitely want them followed. You'd only want to no-follow to prioritize your crawl rate, but not recommended unless you have multiple formats (see the article above).
Indexed
If the content is unique (usually blog content) and you are getting traffic to those pages from searches then it may be worthwhile to keep them indexed.
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=93710
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
-
Does adding new pages, new slugs, new URLS in a site affects rankings and visibility?
hi reader, i have decided to add new pages to my site. if i add new urls, i feel like i have to submit the sitemap again. my question is, does submitting sitemap again with new slugs or urls affects visibility is serps, if yes, how do i minimize the impact?
Web Design | | SIMON-CULL0 -
Canonical and Sitemap issue
Hi all, I was told that I could change my homepage Canonical tag to match that of my XML sitemap, this sitemap is being generated for me automatically and shows the homepage as e.g. https://www.mysite.com/index.html, yet my Canonical tag has been set to https://www.mysite.com. Google currently shows as https://www.mysite.com/ being indexed, but https://www.mysite.com/index.html is not currently displayed in search results. Can someone please tell me if I should change the Canonical to the index.html version, or if I should do nothing, or remove the Canonical tag altogether? Thank you for looking.
Web Design | | scarebearz0 -
Can the design still be considered adaptive if the URL is different?
I was under the impression our site had a mobile dedicated design, but my developers are telling me we have an adaptive design. The mobile site is set up different and has different content and the url is as follows: www.site.com/MobileView/MobileHome.aspx Can it still be considered adaptive if the URL is not the exact same? Hopefully this make sense and I appreciate anyone's input!
Web Design | | AliMac260 -
Will interlinking using dynamic parameters in url help us in increasing our rankings
Hi, Will interlinking our internal pages using dynamic parameters(like abc.com/property-in-noida?source=footer) help us in increasing our rankings for linked pages OR we should use static urls for interlinking Regards
Web Design | | vivekrathore0 -
URL Re-Mapping Question ?. Do I need to the theme of my business in my url struture even though GWT knows what my site is about
Hi All, I have currently planning to do some url remapping on my Hire Website as alot of most important pages are far to many levels deep from the root domain. This is also making my sitemap not tidy etc. In GWT, Google knows that the theme is my website is Hire as it's the top word. Therefore do I still need to use the word hire in all my new url categories / structures or not ? Examples http://goo.gl/BFmvk2 I was thinking of remapping to www.xxxxxxx.xco.uk/tool-hire-birmingham http://goo.gl/pC9Bdp I was thinking of remapping to www.xxxxxx.co.uk/cleaning-equipment Notice in the later example , I do not have the word rent in the url. Any advice is much appreciated thanks peter
Web Design | | PeteC120 -
URL structure for multiple cities?
Hi, i am in the process of setting up a business directory site that will be used in a number of cities, though i am initially launching with only one city. My question is, what is the best URL structure to use for the site and should i start using this URL structure from day one? At the moment i am using www.mysite.com.au as my primary website where it contains all listings for the the one initial launch city. Though to plan for the future i was considering this URL structure: www.mysite.com.au/cityname so for example, if i launch in the city Sydney initially then all website traffic that goes to www.mysite.com.au would simply be redirected (302 temp redirect?) to www.mysite.com.au/sydney. When i expand to other cities www.mysite.com.au would simply be a "select your city" screen that then redirects to the city of choice (similar to www.groupon.com page). How would doing a 302 redirect from www.mysite.com.au to www.mysite.com.au/city impact on SEO for the initial launch? Or should i just place this on the root domain since no other cities exist at the moment?
Web Design | | adamkirk0 -
Rel Canonical tag usage on ECommerce website
Hello, I have read up on the rel canonical tag and I'm ready to apply it to my site's categorization structure. However, I'm concerned that, because my website does not have a "view all" button for our product pages, the rel canonical tag would not be appropriate. For example, if you come to my site's main category url, you come to mysite.com/main-category At this level - you get the top 12 items in the category. if you want to see the next page, you click a crawlable link that goes to mysite.com/main-category12-24 etc. etc. The site does not offer a view all function. Would applying the rel canonical tag be appropriate in this instance, or do I have to let Google crawl and index each page independantly? Thanks.
Web Design | | Blenny0 -
Crawl Budget vs Canonical
Got a debate raging here and I figured I'd ask for opinions. We have our websites structured as site/category/product This is fine for URL keywords, etc. We also use this for breadcrumbs. The problem is that we have multiple categories into which a category fits. So "product" could also be at site/cat1/product
Web Design | | Highland
site/cat2/product
site/cat3/product Obviously this produces duplicate content. There's no reason why it couldn't live under 1 URL but it would take some time and effort to do so (time we don't necessarily have). As such, we're applying the canonical band-aid and calling it good. My problem is that I think this will still kill our crawl budget (this is not an insignificant number of pages we're talking about). In some cases the duplicate pages are bloating a site by 500%. So what say you all? Do we just simply do canonical and call it good or do we need to take into account the crawl budget and actually remove the duplicate pages. Or am I totally off base and canonical solves the crawl budget issue as well?0