A sitemap should help search engines find your content.
It should be current, complete, and easy to access.
WordPress includes a built-in sitemap, which is useful. But the default approach creates runtime work when crawlers request sitemap data. WordPress loads, collects the URLs, and generates the XML response.
For one request, that is not dramatic.
But crawlers come back. They check again. On larger or performance-focused sites, that runtime work is not the smartest way to serve a URL list.
A sitemap does not need to be rebuilt just because someone asked for it.
It needs to be updated when content changes.
When a post is published, updated, deleted, or unpublished, the sitemap should be refreshed. When a crawler requests /sitemap.xml, the sitemap should already be ready.
That is the smarter workflow.
That is what atec Sitemap is built for.
It replaces the default WordPress sitemap with a controlled sitemap that is generated from published content, kept updated when posts change, and served through /sitemap.xml.
It also makes the sitemap quasi-static: the XML file is served without loading WordPress. Instead of doing sitemap work again and again on crawler requests, the sitemap is kept ready for crawlers.
Instead of doing sitemap work again and again on crawler requests, the sitemap is kept ready for crawlers.
The result is simple:
Your sitemap stays current.
Crawler access stays fast.
WordPress avoids unnecessary runtime work.
For performance-focused WordPress sites, that is the better workflow.
atec Sitemap is available from atec Plugins:
Top comments (0)