Try to save a blog as a PDF and you stop at ten posts. That is the normal limit of an RSS feed. A feed is a window onto recent content, not a full archive; the publisher decides how many items it contains. That is why a request for older posts usually ends at the latest handful of entries. You can page back through the feed or use narrower feeds to reach further into the site's history. Here is why the limit exists and how to get older posts from an RSS feed, even when the main feed offers only ten items.
Why Feeds Only Show Recent Items
An RSS feed delivers what is new, not what is old. Open a typical feed and you see the most recent posts, often ten. The number varies with the publisher's settings. The feed is not a copy of the website; it is a summary of recent activity. The publisher chooses how many items to expose, and that number stays small to keep the feed fast and to encourage readers to visit the site for the full archive.
A WordPress site shows the ten most recent posts by default. That number is set in the WordPress admin under Settings > Reading, in the field labeled "Syndication feeds show the most recent." A publisher can raise it, but most do not. When you want older posts, you are asking the feed to reach further back than its default window. That is possible, but you need the right URL tricks.
The Paged Parameter for WordPress Feeds
WordPress, which powers a large share of blogs, has a built-in way to page through feed items. The main feed URL, such as https://example.com/feed/, shows the first ten posts. To get the next ten, add a query parameter: https://example.com/feed/?paged=2. This works for the main feed and also for comment feeds, though the latter is less common.
The paged parameter is not limited to page two. Use ?paged=3, ?paged=4, and so on, as long as the site has enough posts to fill those pages. Each page returns ten items. If a blog has fifty posts, fetch pages one through five. This is the most direct way to get older posts from a WordPress feed.
Building a PDF Archive from Paged Feeds
Collect several paged feed URLs and convert them into a single PDF. Here is the procedure:
- Identify the base feed URL of the blog, such as https://example.com/feed/.
- Create a list of paged URLs: ?paged=2, ?paged=3, and so on, until you reach the last page or the number of posts you need.
- Open each URL in a browser to confirm it returns content and not an empty feed.
- Use a feed-to-PDF converter or a browser's print-to-PDF feature for each page.
- Combine the resulting PDFs into one file using any PDF merger tool.
This method works best when you know the total number of posts. You can also keep adding pages until you get a page with fewer than ten items, which signals the end.
Using Topic and Tag Feeds to Reach Older Posts
Sometimes the main feed drops older posts quickly, but you can still find them through topic or tag feeds. WordPress generates a separate feed for each. For example, https://example.com/category/name/feed/ gives you the ten most recent posts in that topic, and https://example.com/tag/name/feed/ does the same for a tag. These feeds also accept the paged parameter, so https://example.com/category/name/feed/?paged=2 gets the next ten posts in that topic.
This is useful when you want to archive a specific subject rather than the whole blog. If a blog has a topic for "tutorials," page through that feed to get older tutorials the main feed has already forgotten. The same logic applies to tag feeds. This approach does not give you the entire blog history in one go, but it lets you target the older posts you care about.
When Topic Feeds Beat the Main Feed
The main feed shows ten items. You need twenty posts on a single subject. The topic feed is your answer. The main feed might have dropped the older tutorial after a week, but the topic feed still holds it. Page through that feed and you can retrieve posts several months old, as long as the site has not deleted them. This is especially handy for building a topical PDF archive.
What About Other Platforms?
WordPress is not the only platform, but many other systems have similar limits. A YouTube channel feed returns only the most recent fifteen videos. That is a hard limit set by YouTube, and there is no paged parameter for the standard channel feed. To get older videos, use YouTube's search or playlist feeds.
For other platforms, the rules vary. Some blog platforms allow a query parameter like ?page=2 or ?paged=2, but many do not. The safest approach is to check the feed's XML output for a link to the next page, often indicated by a rel="next" link. If that link is present, follow it. If not, you are out of luck with that feed.
For sites that do not support paging, your only option is to use the site's own archive pages, which are not feeds. You can still convert those HTML pages to PDF, but that is not an RSS feed operation.
Practical Steps to Build a Longer PDF Archive
Once you have identified the feed URLs you need, the process is straightforward. Here is a checklist:
- Determine the base feed URL (usually /feed/ for WordPress).
- Test the paged parameter by adding ?paged=2 and checking the output.
- If the main feed does not page, try topic or tag feeds.
- Collect all the URLs you want to include.
- Convert each feed to PDF using a browser or a dedicated converter.
- Merge the PDFs into one file.
Remember that each feed page returns ten items by default, but the number can differ if the publisher changed the setting. Check the number of items in the feed by looking at the XML and counting the <item> tags. Fewer than ten on a page means you have likely reached the last page.
Limits and Workarounds for Full Blog Archiving
Even with paged feeds, you cannot always get the entire history of a blog. The publisher might have set the feed to show only the most recent posts, and paging might stop after a certain number of pages. Some WordPress sites disable paging for feeds, or they use a plugin that changes the feed structure. In those cases, the paged parameter fails.
Another limitation: feeds often include only a summary, not the full content. If you need the full text for your PDF, visit each post individually. That is time-consuming but doable with a browser's print-to-PDF feature.
To archive an entire blog, the most reliable method is to use the site's sitemap or archive pages, which list all posts. Those are not RSS feeds, but you can convert them to PDF. For most purposes, paging through the feed with ?paged=2 and topic feeds is enough to get a few months of older posts.
Turning Paged Feeds Into a Single PDF
After you have collected several paged feed URLs, turn them into one PDF. The simplest way: open each feed in a browser and use the print function, selecting "Save as PDF." Then merge the PDFs. A more automated approach uses a feed reader that exports to PDF, but that adds extra steps.
For a cleaner result, use a dedicated RSS-to-PDF service. One option is rss2pdf.com, which converts a feed URL directly to a PDF. Feed it each paged URL separately and then combine the outputs. The service requires no account.
Fetching a few pages is fine. Do not hammer a site with hundreds of requests. Be respectful and limit your paging to what you actually need.