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 -
Shortened URL is breaking when URL is in Upper Case
Hi there, Currently I'm having some troubling mitigating an odd occurrence with some redirected shortened URLs being in upper case. Here is how they should be behaving - www.rhinosec.com/webapp -> https://rhinosecuritylabs.com/landing/sample-report-webapp-pentest/
Web Design | | BCaudill
www.rhinosec.com/network -> https://rhinosecuritylabs.com/landing/sample-report-network-pentest/
www.rhinosec.com/se -> https://rhinosecuritylabs.com/landing/social-engineering-example-report/ but when the /______ is capitalized - for example - WEBAPP, NETWORK, SE; WordPress either gives me a 404 or guesses the pages and lands on: NETWORK = https://rhinosecuritylabs.com/assessment-services/network-penetration-testing/
SE = https://rhinosecuritylabs.com/assessment-services/secure-code-review/
WEBAPP = 404 I was wondering if this discrepancy should be taken care of in the Htaccess file, Cloudflare, or WordPress redirect plug-in?0 -
301 Redirect Issue for URL with # and !
Hi All, We had a WIX website and now moved to Wordpress. I m having issue while doing redirecting from old URL to new URL. Example: Old Url: http://www.firsttraffic.com.au/#!traffic-management/ccfn New Url: http://www.firsttraffic.com.au/our-services/traffic-management/ I tried different wordpress plugin but nothing works. I m thinking its due to the # . But How can I to redirection for URL like this . Thanks
Web Design | | emarketexperts0 -
Help with error: Not Found The requested URL /java/backlinker.php was not found on this server.
Hi all, We got this error for almost a month now. Until now we were outsourcing the webdesign and optimization, and now we are doing it in house, and the previous company did not gave us all the information we should know. And we've been trying to find this error and fix it with no result. Have you encounter this issue before? Did anyone found or knows a solution? Also would this affect our website in terms of SEO and in general. Would be very grateful to hear from you. Many thanks. Here is what appears on the bottom of the site( www.manvanlondon.co.uk) Not Found The requested URL /java/backlinker.php was not found on this server. <address>Apache/2.4.7 (Ubuntu) Server at 01adserver.com Port 80</address> <address> </address> <address> </address>
Web Design | | monicapopa0 -
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 -
Is it necessary to Remove 301 redirects from Wordpress after removing the 404 url from Google Webmaster?
There were many 404 urls in my site found by Google Webmaster. I've redirected these urls to the relevant urls with 301 redirect in wordpress. After that I removed these 404 urls from Google Index through Webmaster. "Should I cleanup these 301 redirects from Wordpress or not? ". Help Needed.
Web Design | | SangeetaC0 -
Multi-page articles, pagination, best practice...
A couple months ago we mitigated a 12-year-old site -- about 2,000 pages -- to WordPress.
Web Design | | jmueller0823
The transition was smooth (301 redirects), we haven't lost much search juice. We have about 75 multi-page articles (posts); we're using a plugin (Organize Series) to manage the pagination. On the old site, all of the pages in the series had the same title. I've since heard this is not a good SEO practice (duplicate titles). The url's were the same too, with a 'number' (designating the page number) appended to the title text. Here's my question: 1. Is there a best practice for titles & url's of multi-page articles? Let's say we have an article named: 'This is an Article' ... What if I name the pages like this:
-- This is an Article, Page 1
-- This is an Article, Page 2
-- This is an Article, Page 3 Is that a good idea? Or, should each page have a completely different title? Does it matter?
** I think for usability, the examples above are best; they give the reader context. What about url's ? Are these a good idea? /this-is-an-article-01, /this-is-an-article-02, and so on...
Does it matter? 2. I've read that maybe multi-page articles are not such a good idea -- from usability and SEO standpoints. We tend to limit our articles to about 800 words per page. So, is it better to publish 'long' articles instead of multi-page? Does it matter? I think I'm seeing a trend on content sites toward long, one-page articles. 3. Any other gotchas we should be aware of, related to SEO/ multi-page? Long post... we've gone back-and-forth on this a couple times and need to get this settled.
Thanks much! Jim0 -
Weird url backslashing action...
Hi guys this is more of a technical question. Has anyone seen this before in a url www.domain.com/\page\ i'm referring to the forward slash / followed by a backslash \ resulting in /\ Any idea why this happens?
Web Design | | Immanuel0