Hi Shaun!
Sorry, I missed your message earlier.
TSF doesn’t support separate sitemaps per post type. However, if you disable the optimized sitemap, WordPress’s built-in sitemap takes over, which does organize entries by post type.
That said, search engines don’t care about sitemap organization—they just look for links. A sitemap with 400 or even thousands of entries won’t cause issues; search engines process these routinely.
TSF sorts entries by last-updated date, so recently changed properties will appear at the top. If older links fall off the sitemap, that’s fine: search engines are already aware of them. For most sites, sitemaps are needed only to discover new and updated content, not as a complete index.
Still, due to popular demand (coming from news networks), I’m working on monthly/yearly sitemaps for archival support (#649); that won’t address per-post-type separation, but it will enable listing all posts of a site.
Hi @cybr thanks for the response.
I didn’t realise WordPress now had a default sitemap! I may explore this option for certain use-cases.
I find separate sitemaps for post-types can help with monitoring larger websites that have regularly changing information. I appreciate the SEO result is potentially no different, but staying organised is always beneficial to me.
