: Changing pagination, and having more sections per page I'm upgrading an old website, from having 25 results per page (40 pages), to having 50-100 per page (5-10 pages) This will change the pagination,

@Megan663

Pagination is almost never worth it from either a search engine or user experience perspective. Just eliminate that as a feature altogether.

Users

Less than 10% of users usually click to page 2. Less than 1% of users usually click to page 3. I've never measured a situation where enough users rely on pagination to warrant keeping it.

Search engines

Page rank falls off very quickly in a series of pages. Especially when page 1 links to page 2 via "next" and page 2 links to page 3 and so on. By the time you get to page 3, there is so little link juice available that search engines will never rank page 3 content.

Titles and meta descriptions of pagination are usually so similar you also run into duplicate content issues. I have tried writing different titles and descriptions for the first three pages of pagination but I've found that effort has very little payoff.

They also wont push any juice to into the pages you are listing in the pagination beyond page 1. It is far better to have your detail pages link to each other directly (similar products, you might also be interested in, people who looked at x also looked at y).

Get rid of your pagination and redirect everything back to page 1.

Vote Up Vote Down

@Chiappetta492

Instead of recalculating the first item on a page, use a from instead of a page:


example.com/articles/from-40


If you switch to more/less items in a page, you still start at 40.

To prevent "duplicate titles/descriptions" and such, indicate pages using the rel="next/prev :


<link rel="prev" href="/articles/from-20" />
<link rel="next" href="/articles/from-60" />


Do not use noindex/nofollow. Noindex isn't very optimal, just let Google decide about that, and nofollow is terrible, you really do want them to follow the anchors on your pages and index the items.

Vote Up Vote Down

@Sherry384

It is always better to use noindex for sub-pages archive. like /page/2/, /page/3/ & so on. (Search engines don't like it either)

Eventually, your sub-pages will be removed & you won't have to worry about what happens when you change per page items list.

Use Infinite Scroll to load sub pages content. That should also improve UX.

Vote Up Vote Down

@Marchetta884

Here's what I've done in the past with a similar situation without any issues in URLs (404, canonical etc).

So I added a dropdown with a bit of js to take away the submit button like this:

<select onchange="window.location.href = (this.options[this.selectedIndex].value)" name="rows">
<option selected="selected" value="">Please Select</option>
<option value="chapter.php?cid=7&amp;page=1&amp;rows=10">10 Per Page</option>
<option value="chapter.php?cid=7&amp;page=1&amp;rows=25">25 Per Page</option>




So if you have a URL like:

mysite.com/content/8/


that would remain, all your pages would remain as far as search engines are concerned. And only users who have javascript enabled which is most humans/browsers can select and view however many per page. And for those users the URL would look something like this:

mysite.com/content/8/50


and so on. And yes google bot is advanced and is able to view with js enabled so that would new URLS will also get indexed in that case you'd just add, like you say some canonical hints. Have a look here for some tips.

Vote Up Vote Down