Maplain XML Sitemap

Description

Maplain XML Sitemap does exactly one thing: it publishes a clean XML sitemap for your site.

  • Sitemap index at /sitemap.xml, split by type: posts, pages, homepage, and (optionally) categories, 500 URLs per file
  • lastmod dates in your site’s timezone, following your Reading settings for the homepage
  • Image entries for featured and in-content images (up to 20 per post)
  • A plain browser view in the style of the core and major SEO plugins’ sitemaps (title, a short description, and a simple two-column table), generated by XSL; crawlers still receive plain XML
  • Honors noindex: per-post settings and post-type / category-wide settings from Yoast SEO, Rank Math, and All in One SEO are read and excluded
  • Adds the sitemap to the virtual robots.txt, and can disable the WordPress core sitemap (/wp-sitemap.xml) to avoid duplicates
  • Short-lived cache (1 hour) that is cleared automatically when posts, terms, SEO plugin settings, or per-post noindex flags change

What it deliberately does not do:

  • No pinging of search engines, no analytics, no tracking, no external requests
  • No changes to login URLs, /wp-content/, asset paths, the REST API, or anything else outside the sitemap
  • No settings beyond a handful of checkboxes

The collection limit is 20,000 posts and pages; administrators see a warning if a site outgrows it.

Installation

  1. Upload the plugin through Plugins > Add New > Upload Plugin, or unzip it into /wp-content/plugins/.
  2. Activate it.
  3. Visit /sitemap.xml to check the output.
  4. If another SEO plugin also generates a sitemap, disable one of them, and make sure your robots.txt / Search Console point to /sitemap.xml.

Settings live under Settings > Maplain XML Sitemap.

FAQ

Does it conflict with Yoast SEO / Rank Math / AIOSEO sitemaps?

Both would publish a sitemap, so disable the sitemap feature in one of them. This plugin can still read their noindex settings while its own sitemap is the active one.

Does it notify Google or Bing when I publish?

No. Search engines pick the sitemap up from robots.txt and Search Console. There is no pinging and no external communication of any kind.

Why is a post missing from the sitemap?

Common reasons: the post is not published, it is password-protected, it is set to noindex (per-post or post-type-wide) in your SEO plugin, or the site exceeds the 20,000 URL limit (administrators get a warning in that case).

Which noindex settings are detected?

Per-post flags and post-type / category-wide settings of Yoast SEO, Rank Math, and AIOSEO, in the storage formats those plugins use as of late 2026. Unrecognized formats are ignored, so an undetected noindex page may stay in the sitemap; normal pages are never dropped by a misread. See the changelog/readme notes for details.

Can I include custom post types or change the limit?

Not in this version. Keeping the scope small is the point of this plugin — posts, pages, and categories only.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Maplain XML Sitemap” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Maplain XML Sitemap” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.6.0

  • Renamed to “Maplain XML Sitemap” (slug: maplain-xml-sitemap), following the wordpress.org review feedback that the previous name and slug were too generic. “Maplain” is a coined word (map + plain) and is now the plugin’s distinctive name.
  • All prefixes changed from the 3-character spm_ / SPM_ to maplain_ / Maplain_ (class, option, transients, settings group, and the filter hook). Settings stored under the old option key are migrated automatically on first load and the legacy data is removed.
  • Removed the bundled Japanese translation files (plain-xml-sitemap-ja.po / .mo) as requested in review; translations are delivered through wordpress.org language packs instead.
  • No changes to sitemap output or features.

1.5.2

  • Removed the load_plugin_textdomain() call. Since WordPress 4.6 it is discouraged for plugins hosted on wordpress.org: translations are loaded automatically (just-in-time) from language packs, so the manual call is no longer needed.

1.5.1

  • Fix for the wordpress.org automated Plugin Check: removed the “Tested up to” field from the main plugin file header (it is declared only in this readme, as required), and the bundled XSL stylesheet is now served through WP_Filesystem instead of readfile().

1.5.0

  • First public release, prepared for wordpress.org.
  • Renamed to “Plain XML Sitemap” (slug: plain-xml-sitemap) — the plugin has been sitemap-only for a long time, and the previous name was taken/too generic for the directory.
  • All admin strings are now in English and fully translatable (text domain: plain-xml-sitemap); a Japanese translation is bundled. The browser view (XSL) is English as well, simplified to the plain core/Yoast-style layout with no thumbnail images.
  • Official wordpress.org readme format.
  • Upgrading from the earlier private builds (“XML Sitemap” 1.4.x / “Site Privacy Manager”): settings are stored under the same option key and carry over automatically; deactivate and delete the old plugin, then install this one.

1.4.2

  • The over-limit (20,000 URL) admin warning no longer depends on the sitemap cache: it is gated on the published post/page counts and always shown to administrators above the cap.
  • Documented the cross-version caveat for SEO plugin storage formats (unknown formats are ignored — fail-open).

1.4.1

  • Per-post noindex changes now clear the sitemap cache even when they bypass a post save (added/updated/deleted post meta hooks for the three meta keys the plugin reads).
  • Admin warning when the collection limit actually cuts off indexable URLs.

1.4.0

  • Renamed from “Site Privacy Manager” to “XML Sitemap” (internal keys unchanged, settings carry over).
  • Plainer browser view: no blue count badge, white page background, no rounded table corners, no row hover highlight.

1.3.5

  • Homepage lastmod follows the Reading settings (static front page uses that page’s modified time; latest-posts front page considers posts only).
  • Global noindex settings of Yoast SEO, Rank Math, and AIOSEO are now read (post-type and category level), not only per-post flags.

1.3.4

  • Removed the “Generated by” footer from the browser view.
  • On small screens the browser view hides the image-count column as well as thumbnails.
  • The home sitemap now carries a lastmod (latest post/page modification). Categories still have no lastmod, because WordPress has no reliable modified timestamp for terms.

1.3.3

  • Browser view: formatted local dates, newest-first display order, thumbnails, row numbers (display only; XML data unchanged).
  • lastmod is emitted in the site timezone instead of GMT.