--- title: "How to Add Infinite Scroll to Blog Posts in WordPress?" url: https://nexterwp.com/docs/add-infinite-scroll-to-blog-posts-in-wordpress/ date: 2023-05-06 modified: 2026-09-27 lang: en author: "Aditya Sharma" description: "Numbered pages ask the reader to make a decision and click. On a browsing page, where nobody is looking for anything specific, that is friction. Infinite scroll loads the next..." image: https://nexterwp.com/wp-content/uploads/2024/05/add-infinite-scroll-to-blog-posts-in-wordpress-1024x519.jpg word_count: 499 --- # How to Add Infinite Scroll to Blog Posts in WordPress? ## Key Takeaways - Nexter Blocks uses the free Post Listing block to enable infinite scroll, and the block is switched on under Nexter > Blocks in the WordPress dashboard. - The block writes its paging data into a data-dypost attribute on the published page, including page, total_page, load_more, load_class, loaded_posts, and loadingtxt. - Infinite scroll has clear limits: the footer becomes unreachable, returning to a previous position lands at the top again, and search engines do not reliably discover posts that appear only after several loads. Numbered pages ask the reader to make a decision and click. On a browsing page, where nobody is looking for anything specific, that is friction. Infinite scroll loads the next set of posts as the reader reaches the bottom, so the list just keeps going. [LIVE BLOCK LINK](https://nexterwp.com/nexter-blocks/listing/wordpress-post-listing/) ## Before You Start - **Edition:** Free — works in Nexter Blocks (free) and with Nexter Blocks Pro.- **Block to enable:** Post Listing, switched on under **Nexter > Blocks** in your WordPress dashboard.- **Noticeably more posts than one page shows**, or there is nothing to load. ## Steps - Select your **Post Listing** block. ![The Post Listing block](https://nexterwp.com/wp-content/uploads/2026/09/pl-type-post.webp) - Set how many posts load at a time. ![Setting the batch size](https://nexterwp.com/wp-content/uploads/2026/09/pl-query-display.webp) - Set the pagination option to the **infinite scroll** style. ![Choosing infinite scroll](https://nexterwp.com/wp-content/uploads/2026/09/pl-steps-lazy-2.webp) - Publish and scroll the real page to the bottom of the listing. ![Loading more posts by scrolling](https://nexterwp.com/wp-content/uploads/2026/09/pl-steps-lazy-3.webp) ## How It Behaves The block carries the paging information the loader needs, and fetches the next batch as the reader arrives. - **Measured on a published page:** the `data-dypost` attribute carried `page`, `total_page`, `load_more` and a `load_class` that identifies this listing, which is what the loader uses to fetch the next batch.- **It also carries the finished message.** Measured: `loaded_posts` holds the text shown once every post has loaded, and `loadingtxt` the text shown while fetching.- **Each batch is a request.** The posts are not all in the page at the start, which is the difference from simply showing more posts.- **Everything ends up in one attribute.** The block writes its whole query configuration into a `data-dypost` attribute on the published page, so if a setting is not doing what you expect, that is where to look.- Measured with Nexter Blocks Pro deactivated: the listing still renders its posts. The block itself is free. ## Limitations - **The footer becomes unreachable** while posts keep loading, which frustrates anyone looking for contact details or links down there.- **It is hard to return to a position.** A reader who follows a post and comes back lands at the top again.- **Search engines do not scroll.** Posts that only appear after several loads are not reliably discovered, so do not rely on it for indexing.- **Every batch is another request**, so a long scroll is a lot of round trips on a slow connection.- **A load more button is often kinder**, because it keeps the reader in control. ## Troubleshooting ### Nothing loads when I reach the bottom There may be nothing left to load. Check the listing is limited to fewer posts than you have, and that you are on the published page rather than the editor. ### I cannot reach my footer That is the known trade-off with infinite scroll. Switch to a load more button or numbered pages if the footer matters. ### It loads the same posts again Two listings on the page are sharing paging state. Keep one infinite listing per page. ### Will Google see all the posts? Not reliably. Anything that only appears after several loads may not be discovered. Keep a paginated archive as well. ## Related Docs - [Add pagination to blog posts](https://nexterwp.com/docs/add-pagination-in-blog-posts-in-wordpress/)- [Add a read more button to blog posts](https://nexterwp.com/docs/add-read-more-button-in-blog-posts-in-wordpress/)- [Add post listing in WordPress](https://nexterwp.com/docs/add-post-listing-in-wordpress/)- [Advanced tab settings](https://nexterwp.com/docs/use-advanced-tab-in-nexter-blocks/) ## Frequently Asked Questions **Q: What do I need before adding infinite scroll to WordPress blog posts?** A: Infinite scroll in Nexter Blocks works on the free edition, and it needs the Post Listing block turned on under Nexter > Blocks in your WordPress dashboard. It also only makes sense when there are more posts than one page shows, because otherwise there is nothing for the loader to fetch. That setup matters because the block is loading the next batch as the reader reaches the bottom, not replacing a single static page. **Q: How do I add infinite scroll to blog posts in WordPress?** A: The core setup is simple: select your Post Listing block, set how many posts load at a time, switch pagination to the infinite scroll style, then publish and test the real page by scrolling to the bottom of the listing. Nexter Blocks writes the paging data into the published page so the loader knows what to fetch next. Testing on the published page matters because the editor is not the same as live output. **Q: Why does infinite scroll stop at my footer?** A: That is normal behavior for this setup. Infinite scroll keeps loading more posts as you reach the bottom, which means the footer becomes unreachable while loading continues. If contact links or footer navigation matter, a load more button or numbered pages is a better fit because they keep control with the reader instead of trapping them in an endless feed. **Q: Why are my infinite scroll posts loading twice?** A: Two listings on the same page can share paging state, which makes them pull the same batches again. The practical fix is to keep one infinite listing per page. That limitation comes from how the loader tracks paging information in the published page, so duplicate listings can confuse which batch has already been fetched. **Q: Will Google index all posts loaded by infinite scroll?** A: Not reliably. Search engines do not scroll, so posts that only appear after several loads may not be discovered consistently. That is why a paginated archive should still exist alongside infinite scroll if indexing matters. Nexter Blocks can load batches for readers, but search visibility should not depend on content that only appears after repeated scrolling. **Q: Is infinite scroll better than pagination for blog archives?** A: It depends on what matters more: browsing flow or reachability. Infinite scroll removes the friction of clicking through numbered pages, but it also makes it hard to return to a spot and can hide the footer during loading. For archives where indexing and footer access matter, pagination or a load more button is usually safer. Related options include [Add pagination to blog posts](https://nexterwp.com/docs/add-pagination-in-blog-posts-in-wordpress/) and [Add a read more button to blog posts](https://nexterwp.com/docs/add-read-more-button-in-blog-posts-in-wordpress/).