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
-
Infinite Scroll and URL Changing
Hi, So my website is having an issue indexing. Much like other sports sites like ESPN or MLB or a variety of others my site changes the URL as you go down the page. So if you go on a news article and continue scrolling you'll go to another news article. I believe that this is creating errors in Search Console with the article being given an error of being "too long". I don't know how to keep this infinite scroll and url changing which increases my pageviews and eliminate the errors. Can someone help?
Web Design | | mattdinbrooklyn0 -
Pushstate and Infinite Scrolling Article Pages: Is it detrimental to not change URLs as the page is being scrolled?
I've noticed a recent trend of news sites using infinite scrolling on article pages to garner more pageviews and I can assume serve up more ads. Here is an overview. Here is an article from NBC news that uses this technique: http://www.nbcnews.com/pop-culture/music/grammys-2016-here-s-why-adele-s-performance-was-out-n519186 Studies have shown that this technique has decreased bounce rates by +15% for some sites. My question is: If a site is using the technique without changing URLs as the user scrolls down what overall negative effects does this have? Obviously you wouldn't be getting credit for the extra pageviews but I was wondering if there were any indexation implications with this. Here is an example of article infinite scrolling without changing the URL: http://www.wftv.com/news/national-content/deputies-wife-attacks-husband-because-he-didnt-get-her-a-valentines-day-gift/87691927
Web Design | | Cox-Media-Group1 -
URL Structure
Hello, Within the last few months, my company launched a brand new website for our clients. Unfortunately, the web developers we went through aren't very knowledgeable on SEO practices and as a result, our URL structure is a total mess. I'm looking for some advice on the best way to go about a possible restructure of the URL's or what you suggest I should do from here. Any advice helps. Thanks! Lauren McLaughlin
Web Design | | LMcLaughlin0 -
Interlinking using Dynamic URLs Versus Static URLs
Hi Guys, Could you kindly help us in choosing best approach out of mentioned below 2 cases. Case. 1 -We are using: We interlink our static pages(www.abc.com/jobs-in-chennai) through footer, navigation & by showing related searches. Self referential Canonical tags have been implemented. Case. 2 -We plan to use: We interlink our Dynamic pages(www.abc.com/jobs-in-chennai?source=footer) through footer, navigation & by showing related searches. Canonical tags have been implemented on dynamic urls pointing to corresponding static urls Query 1. Which one is better & expected to improve rankings. Query 2. Will shifting to Case 2 negatively affect our existing rankings or traffic. Regards
Web Design | | vivekrathore0 -
Magento URL Structure
I'm about to migrate to Magento and wanted to ask about the optimal URL structure for the following page: Knowledge Centre |-Videos |-Customer Testimonials |-Customer X Would it be better to use: Domain/knowledge-centre/videos/customer-testimonials/customer-x or Domain/customer-x Thanks in advance for any replies.
Web Design | | ssoneil0 -
Yes or No for Ampersand "&" in SEO URLs
Hi Mozzers I would like to know how crawlers see the ampersand (& or &) in your URLs and if Google frown upon this or not? As far as I know they purely recognise this as "and" is this correct and is there any best practice for implementing this, as I know a lot of people complained before about & in links and that it is better to use it as &, but this is not on links, this is on URLs. Reason for this is that we looking to move onto an ASP.Net MVC framework (any suggestions for a different framework are welcome, we still just planning out future development) and in order to make use of the filter options we have on our site we need a parameter to indicate the difference on a routing level (routing sends to controller, controller sends to model, model sends to controller and controller sends to view < this is pattern of a request that comes in on the framework we will be using). I already have -'s and /'s in the URLs (which is for my SEO structuring) so these syntax can't be used for identifying filters the user clicks or uses to define their search as it will create a complete mess in the system. Now we looking at & to say; OK, when a user lands on /accommodation and they selects De Kelders (which is a destination in our area) the page will be /accommodation/de-kelders on this page they can define their search further to say they are looking for 5 star accommodation and it should be close to the beach, this is where the routing needs some guidance and we looking to have it as follow: /accommodation/de-kelders/5-star&close-to-the-beach. Now, does the "&" get identified by search engines on a URL level as "and" and does this cause any issues with crawling or indexation or would it be best to look at another solution? Thanks, Chris Captivate
Web Design | | DROIDSTERS0 -
URL parameters causing duplicate content errors
My ISP implemented product reviews. In doing so, each page has a possible parameter string of ?wr=1. I am not receiving duplicate page content and duplicate page title errors for all my product URLs. The report shows the base URL and the base URL?wr=1. My ISP says that the search engines won't have a problem with the parameters and a check of Google Webmaster Tools for my site says I don't have any errors and recommends against configuring URL parameters. How can I get SEOmoz to stop reporting these errors?
Web Design | | NiftySon1 -
Ajax pagination and filters for ecommerce site
Hi There, Is it ok to use ajax for product filters and pagination? In this case url doesn't change when you navigate to 2nd or 3rd page also when you filter by colours, etc. If not what's your advise?
Web Design | | Jvalops0