Websites that continually add content can maintain XML sitemaps automatically with a CMS plugin, generate them from internal data using custom code, or export them after scanning the site with a crawler. For a time-sensitive events website that adds more than twenty pages a day, the key consideration is not just whether a solution can generate XML, but how the sitemap stays up to date when pages are added, modified, or removed. Below are some more recent plugin and tool options, along with an approach using PHP and cron. The sources used here do not, however, provide a ready-made PHP script that can be directly verified and recommended for download.
For WordPress sites, consider plugins that maintain sitemaps automatically
Yoast’s March 2026 documentation states that Yoast SEO manages sitemaps automatically, keeps them updated as the site grows, and excludes content marked as noindex. If an events website already uses WordPress, this option has more recent documentation to consult and avoids the need to start by compiling URLs manually.
- Posts or pages that should not appear in search results can be marked as noindex through the advanced settings and automatically excluded from the sitemap.
- Developers can use filters to limit the number of URLs in each sitemap or exclude specific content types.
Note that the search visibility option does more than control whether content appears in the sitemap: setting it to “No” also marks the content as noindex, affecting its visibility in search results.
For custom-built dynamic websites, consider generating sitemaps from the database
A discussion on Webmasters Stack Exchange suggests using PHP to list the possible page URLs for dynamically generated pages, then generating the sitemap with a daily cron job. If the site consists of physical HTML files, a script can scan those files instead. This is an implementation approach, not a recommendation for a fully tested script.
Another approach is to have a server-side sitemap script retrieve the latest data from the database each time it receives a request. If content updates are infrequent, the results can be cached and refreshed as needed. Scheduled file generation and on-demand dynamic generation are different options: the former rebuilds the sitemap on a schedule, while the latter reads the data when a request arrives. “Daily” is only an example in the discussion, not a suitable frequency for every time-sensitive website.
Crawlers are another option, but consider the site’s architecture first
A September 2025 Semrush article recommends using crawlers such as Screaming Frog to scan large websites and generate sitemaps. It also recommends establishing an update process for when content is added or removed. When multiple files are needed, a sitemap index can organize them by content type or section.
However, another answer on Webmasters Stack Exchange offers different advice for dynamic websites: obtain URLs directly from internal data rather than using a crawler-based generator. The site’s architecture therefore matters when choosing an approach. Custom-built sites with direct access to their content data can consider a database-based solution; sites using crawlers need to check separately how their sitemaps will be updated. A tool that can export a sitemap does not necessarily keep it updated automatically.
Generating and updating sitemaps: Q&A from across the web
How should the sitemap be handled when event pages expire or are taken down?
When old event pages are removed, remove their URLs from the sitemap too, and regularly clear out broken links. The update process needs to cover more than newly added event pages. If you use an automatic generator, check how it detects URL changes; if you write the sitemap manually, you will need to maintain it yourself. For highly time-sensitive events, also make sure the update method keeps pace with content changes on the site.
Should the sitemap include every event-related URL?
Not every URL needs to be included. Focus on important public pages that you want search engines to index, and exclude login pages, thank-you pages, and duplicate content. When choosing a tool, check whether it lets you control how noindex pages, URL parameters, and duplicate URLs are handled. If the site needs image, video, or news sitemaps, check separately whether the tool supports them.
Besides price, what should you consider when comparing third-party generators?
First, check whether the tool's capacity covers the size of your website and whether it only generates a one-off file or can accommodate ongoing updates. Some tools also offer format checks or checks for URLs returning non-200 status codes, while others focus on monitoring; these functions should not be treated as equivalent. Many free tools cap the number of URLs they can crawl, so check the plan limits before choosing one.
References
- How to create an XML sitemap?www.semrush.com · 2025-09-16T10:10:00Z — Discusses: How should the sitemap be handled when event pages expire or are taken down?; Should the sitemap include every event-related URL?
- easy tool for creating XML sitemaps? (constantly expanding site)webmasters.stackexchange.com — Source used in the article above.
- What is an XML sitemap and why should you have one?yoast.com · 2026-03-11T13:52:01+00:00 — Source used in the article above.
- XML Sitemap: What It Is And How To Generate Onewww.semrush.com · 2015-08-14T15:16:00Z — Discusses: How should the sitemap be handled when event pages expire or are taken down?; Should the sitemap include every event-related URL?
- easy tool for creating XML sitemaps? (constantly expanding site)webmasters.stackexchange.com — Source used in the article above.
- easy tool for creating XML sitemaps? (constantly expanding site)webmasters.stackexchange.com — Source used in the article above.



