Hello webmasters, thanks for your great questions!
@anthonydnelson, @kees-van-dieren: @poooook is correct that for Google
indexing of paginated content, rel="next" and rel="prev" declarations
belong in the <head> section, not in the <body> as anchor
links. As an example, the second page of a series may show this:
rel="next" and rel="prev" values specified in the <body> section will be ignored with regard to pagination.
Because we consider rel="next" and rel="prev" as an independent concept
from rel="canonical", you can still include a rel="canonical" value on
your pages (or you can also choose to omit it). For example, for the
We recommend no more than one value for rel="next" and no more than one
value for rel="prev". The meaning of next/prev is “the *immediately*
following/preceding page.” Therefore, page 2 should not mark all pages
3, 4, 5, etc., as "next" pages, but only page 3.
@Stecki: rel="canonical" and rel="next"/"prev" aren't mutually exclusive, they're independent concepts.
our rel="next" and rel="prev" pagination announcement, paginated
component URLs (pages that are part of a series) can either: 1. Include rel="next" and rel="prev" values in the <head> of their page 2. Not include rel="next" and rel="prev" values in the <head> of their page
Separate from this announcement, each of these component URLs can still: 1. Not specify a canonical value 2. Specify the canonical value as the view-all page 3. Specify the canonical value as a similar URL, but say, one without extraneous parameters such as session ID
It's fine if your paginated content works like Google Image Search
results where pagination doesn't create a new URL (so there's no way you
can add rel="next"/"prev"), but instead dynamically loads content.
However, you may want to make sure that Googlebot and users without
Fico: Yes, you can specify rel="next" and rel="prev" values on
individual components/URLs of a brand or category on an e-commerce site.
When you implement rel="next" and rel="prev" on component pages of a
series, we'll then consolidate the indexing properties from the
component pages and attempt to direct users to the most relevant
page/URL. This is typically the first page. There's no need to mark page
2 to n of the series as noindex unless you're sure that you don't want
those pages to appear in search results.
@jerenel: If you've marked page 2 to n of your paginated series as
"noindex, follow" to keep low quality content from affecting users
and/or your site's rankings, that's fine, you can additionally include
rel="next" and rel="prev." Noindex and rel="next"/"prev" are entirely
means that if you add rel="next" and rel="prev" to noindex'd pages, it
still signals to Google that the noindex'd pages are components of the
series (though the noindex'd pages will not be returned in search
results). This configuration is totally possible (and we'll honor it),
but the benefit is mostly theoretical.
you believe the user experience on page 2 to n provides little value --
so much so that you've already marked these pages as noindex -- then to
ensure that these low-quality pages aren't returned to users and/or
considered in ranking updates such as Panda, even if you choose to add
rel="next" and rel="prev," you may want to consider keeping the noindex
(or "noindex, follow").
@TiggerFish: Is your site’s existing use of rel="next" and rel="prev"
located within the <body> section of the page? For the feature
described in our blog post, Google indexing looks at rel="next" and
rel="prev" within the <head> section. So you don't need to remove
your existing rel="next" and rel="prev" tags if they’re found in the
<body> -- those will continue to be treated the same way as prior
to our rel="next" and rel="prev" pagination announcement on September
15, 2011, and we will not consolidate their indexing properties.
rel=”next” and rel=”prev” markup that isn’t intended to work with
Google indexing, we’ll develop more heuristics over time to understand
which attributions to trust.
@thericker: Ah yes, SMX Advanced... Thanks for following our updates!
It's always best to have a unique title and meta description for each
page. Ideally, the title and description are descriptive of the page's
content. For example: