Mobile app version of vmapp.org
Login or Join
Gretchen104

: How to avoid duplicate Title, H1 tags on keyword pages? As my question states i want to avoid duplicate Title and H1 tags on my website. My pages are like this example.com/rock-music-list-1/

@Gretchen104

Posted in: #DuplicateContent #Pagination #Title

As my question states i want to avoid duplicate Title and H1 tags on my website.

My pages are like this

example.com/rock-music-list-1/
...
example.com/rock-music-list-9/


On each page there is a pagination system that allow users to go back and forth.

[<] [1] [2] ... [8] [9] [>]


So on each of these 9 pages they all have the exact title and h1 tag.

10.03% popularity Vote Up Vote Down


Login to follow query

More posts by @Gretchen104

3 Comments

Sorted by latest first Latest Oldest Best

 

@Courtney195

For paginated page or other variations, you can put canonical tag to parent page.

This will solve problem.

For example:

example.com/rock-music-list-1/
example.com/rock-music-list-2/
example.com/rock-music-list-3/
example.com/rock-music-list-4/


all with canonical example.com/rock-music-list

10% popularity Vote Up Vote Down


 

@Hamaas447

I disagree with dhaupin, it is an issue that is every common with blog pagination and few SEO plugins, themes, templates make it right.

The first page should contain

<link rel="next" href="url-to-page-2">


The second page and following pages should contain:

<link rel="previous" href="url-to-page-1">
<link rel="next" href="url-to-page-3">


The last page should contain:

<link rel="previous" href="url-to-page-x">


None of the inner pages should have a canonical tag to the first page but they should always point to their own url

Reference: support.google.com/webmasters/answer/1663744?hl=en googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html http://googlewebmastercentral.blogspot.fr/2013/04/5-common-mistakes-with-relcanonical.html

10% popularity Vote Up Vote Down


 

@Debbie626

Duplicates like these are a thing of the past if you have set up proper schemas/relations/canonicals in regards to pagination: support.google.com/webmasters/answer/1663744?hl=en
Note this too from the bottom of that article:


rel="next" and rel="prev" are orthogonal concepts to rel="canonical".


This means that each page is it's own canonical, which is contrary to the popular practice of making only the first page the canonical. In the snippet on the Google KB page we see this example of this:

<link rel="canonical" href="http://www.example.com/article?story=abc&page=2"/>
<link rel="prev" href="http://www.example.com/article?story=abc&page=1&sessionid=123" />
<link rel="next" href="http://www.example.com/article?story=abc&page=3&sessionid=123" />


Notice how page 2 is a canonical. When you goto page 3, that would be a canonical. All pages are a canonical in relation to others before and/or after them.

Some other things you can do is to dynamically add - Page 3 to the ends of page titles beyond page 1. Or you can also indicate via SERP that youre about to land into page 3 (for example) by putting the pagination current location info in a syntax that looks specifically like this:

Showing 30-40 of 100 or Products 30-40 of 100

Which will show in SERPS like this:

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme