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
-
Redesign Just Starting - Should I Leave The Previous Incomplete Site or Setup A Temporary Holding Page and Redirect Previous URL'S?
Hi All I've picked up a new website project and wanted to ask about the best way to proceed with the current site during the development process. The current site is incomplete although it has been live for a while and has over 80 pages in the sitemap. Link to site https://tinyurl.com/ychwftup The business owner wants to take down the current site and simply add a landing page stating "new website coming soon". From an SEO perspective, am I better to keep the current site live until the new site is ready? Or would it not make any difference if I setup the landing page and add 301 redirects from each page in the sitemap to the landing page. Many Thanks In Advance For Any Assistance
Web Design | | ruislip180 -
Does loading content from an ajax url count as a bounce rate
Hi, Our current website http://www.luxresorts.com has sections that pull content through AJAX which is accessible through a URL. For example, on our homepage, we have a section called "LUX* Magazine THE TASTEMAKER", if you click on "Read More" it would open on the same page while pulling content from this URL: http://www.luxresorts.com/en/posts/lux-magazine. There are two concerns here: a. the above url does not contain any google analytics code, does pulling content from a url through ajax cause a bounce rate? b. since the url is indepenedent, the is no meta tags including title, description or even robot attributes. Should we treat this page as all other pages? Thank you for your help. Tej Luchmun
Web Design | | luxresorts0 -
URL Structure's Effect on SEO
Hello all, I have a client who currently has a very poor URL structure. As it stands, their URLs are formatted in the following manner: http://www.domain.com/category/subcategory/page In all my years of SEO, however, I have always tried to implement the following format: http://www.domain.com/category/page The web designer for this particular project has been very reluctant to change the structure for obvious reasons, but I'm convinced that by modifying the URL structure, SEO will improve. I am correct in thinking this? Likewise, if I am able to get the URL structure changed, what do I need to look out for to make sure we don't lose any traction for our keyword terms? Any and all insight/suggestions is greatly appreciated. Thanks for reading!
Web Design | | maxcarnage0 -
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 -
Is there a way to redirect URLs with a hash-bang (#!) format?
Hi Moz, I'm trying to redirect www.site.com/locations/#!city to www.site.com/locations/city. This seems difficult because anything after the hash character in the URL does not make it to the server thus cannot be parsed for rewriting. Is there an SEO friendly way to implement these redirects? Thanks for reading!
Web Design | | DA20130 -
Existing URL structure and how to handle new pages before migration
Hi there! Currently, our site uses underscores "_" within the url structure. We are moving to Wordpress soon (the site is currently static html) but it will be a couple of months before the migration. Here is an example of the current structure: www.oldsitestructure.com/about_us/success_stories/custom_vinyl_banners When we do change, our url structure will have hyphen's "-" to separate terms, so the preferred new structure will be: www.oldsitestructure.com/about-us/success-stories/custom-vinyl-banners The entire site (with the exception of our Wordpress blog) currently uses the old structure. We have about 10 - 15 pages we will add before our migration, my question is: Should we use the preferred url structure starting NOW or stick with the old one? And set up 301 redirects are part of the migration process? Many thanks!
Web Design | | SEOSponge
Jon0 -
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 -
How will engines deal with duplicate head elements e.g. title or canonicals?
Obviously duplicate content is never a good thing...on separate URL's. Question is, how will the engines deal with duplicate meta tags on the same page. Example Head Tag: <title>Example Title - #1</title> <title>Example Title - #2</title> My assumption is that Google (and others) will take the first instance of the tag, such that "Example Title - #1" and canonical = "http://www.example.com" would be considered for ranking purposes while the others are disregarded. My assumption is based on how SE's deal with duplicate links on a page. Is this a correct assumption? We're building a CMS-like service that will allow our SEO team to change head tag content on the fly. The easiest solution, from a dev perspective, is to simply place new/updated content above the preexisting elements. I'm trying to validate/invalidate the approach. Thanks in advance.
Web Design | | PCampolo0