Open the exact public URL and determine whether it is the main posts page, a category archive, a search result or a custom page with its own Query Loop. Record the current count and check whether a theme or page builder controls the listing separately.

Choose a count that suits the card size and expected browsing task. Showing every post at once can create a slow page, while an unnecessarily tiny page size forces readers through excessive navigation.

1. For the general blog-page setting, open Settings > Reading and review Blog pages show at most.
2. Enter the intended number and save the settings.
3. If the target uses a custom Query Loop, select that loop in the editor and review its item-count and query-inheritance settings.
4. Change only the control responsible for the intended listing, then save and inspect the public result.

Check the first, second and final result pages using a collection with enough posts. Confirm that no article disappears or repeats unexpectedly between pages. Review the grid at narrow widths, especially when the new count leaves an incomplete final row.

Clear relevant caches after the settings are correct. A cached archive can continue displaying the previous count even though new uncached requests use the updated setting.

Use a test archive containing exactly twelve eligible published posts, with no additional pinned items or custom query changes. Set its controlling posts-per-page value to five and inspect the public archive.

If the result differs, confirm that this archive uses the setting you changed. Check query inheritance, template overrides and caches before changing unrelated feed settings. Repeat the check after adding new content, because a previously final page can gain more posts.

Inspect the active template, query settings and any plugin modifying the archive. Avoid repeatedly changing unrelated feed settings, which control a different output. A developer can review the actual query if a custom theme overrides the normal behaviour.

If the page becomes slow after increasing the count, reduce it and measure the effect before adding more caching tools. Large featured images, full post content and expensive per-item widgets can make a modest count costly. Keep pagination accessible and provide a clear way for visitors to reach the rest of the collection.

• Paginating a Query Loop without breaking navigation
• Customising category archive templates
• Setting a static homepage and a separate posts page
• Removing sample posts, pages and comments from a new WordPress site

• WordPress: Settings Reading Screen
• WordPress: Query Loop Block