How many posts should the WordPress blog page show?

What the setting controls

Settings → Reading → Blog pages show at most is a single number, stored as posts_per_page, and it governs every standard post listing:

• the blog index, whether that is the homepage or a separate Posts page;
• category, tag, author and date archives;
• internal search results.

When a listing has more posts than the number, WordPress paginates: /page/2/, /page/3/ and so on. Sticky posts are added on top of the first page, so a setting of 10 can show 12.

It does not control the RSS feed, which has its own field directly below ("Syndication feeds show the most recent"), nor custom queries in themes, widgets and blocks. A Query Loop block set not to inherit the main query has its own "items per page".

Themes and plugins can override the number per archive type. If your category pages show 12 while the setting says 10, that is where to look.

The trade-off: depth against weight

Fewer posts per page means deeper pagination. With 600 posts at 10 per page, the oldest post is on page 60. A crawler following "older posts" links needs dozens of steps to reach it, and pages that deep are crawled rarely. At 20 per page it is page 30. Halving the depth helps, but neither figure is good if pagination is the only route to old content.

More posts per page means heavier pages. Each listed post adds markup and usually a thumbnail. Fifty full-size featured images on one page is a real cost in load time, mostly on mobile. WordPress lazy-loads images further down, which softens it, but the HTML still grows.

That is why excerpts matter more than the number. A listing that prints full post content, ten articles in a row, produces a very long page that duplicates each article in full. Ten or twenty excerpts with small thumbnails is light.

For grids, pick a multiple of the column count so the last row is full: 12 for three or four columns, 9 or 15 for three.

Does the number affect rankings?

Not directly. Archive pages rank on their relevance and usefulness like any page, and Google has no stated preference for list length. The setting matters through two side effects:

1. Discovery of older posts. Fewer, larger pages put more posts within a few clicks of the homepage. This is worth having, but internal links from related articles and category pages do the job far better than tuning pagination. If you rely on /page/47/ for Google to find an article, the article needs links, not a different setting.
2. Speed of the archives themselves. The blog index and main categories are often entry points. Keep them quick.

Changing the number also reshuffles which posts are on which paginated page, so /page/3/ shows different posts afterwards. Paginated pages are rarely destinations in search, so this is harmless, but do not flip the number back and forth.

Setting it up well

1. Choose excerpts for listings. In block themes, use the Excerpt block inside the Query Loop on archive templates. In classic themes, look for a "blog display" option.
2. Set the number to suit the layout, typically 10 to 12 for a single column and 12 to 18 for a grid.
3. Check thumbnail sizes. The listing should request a medium-sized image, not the full upload. Inspect one image's src and srcset.
4. Open a category on a phone and scroll. If it feels endless, lower the number or shorten the excerpts.
5. Confirm pagination is crawlable. There should be real links to page 2. If you use "load more" or infinite scroll, the paginated addresses must still exist.
6. Give old posts other routes: category archives, links from newer posts, and an HTML sitemap on larger sites. The orphan pages guide shows how to find posts nothing links to.

Search results use the same number. Since core marks search pages noindex, their length is purely a usability choice.