Fixes a fatal error on post save and on every sitemap request. Update immediately.<\/p>","1.0.3":"
Improves Plugin Check compatibility without changing sitemap output.<\/p>","1.0.2":"
Clarifies that sitemap output is generated XML, not HTML.<\/p>","1.0.1":"
Sanitizes conditional request headers and uses WordPress.org translation loading.<\/p>","1.0.0":"
First release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.4"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The settings screen: choose what goes into the sitemap.","2":"The sitemap index, rendered with the bundled stylesheet."}},"plugin_section":[],"plugin_tags":[4865,186,1557,23216,6358],"plugin_category":[55],"plugin_contributors":[277384],"plugin_business_model":[],"class_list":["post-381102","plugin","type-plugin","status-publish","hentry","plugin_tags-image-sitemap","plugin_tags-seo","plugin_tags-sitemap","plugin_tags-video-sitemap","plugin_tags-xml-sitemap","plugin_category-seo-and-marketing","plugin_contributors-gmcfuerte","plugin_committers-gmcfuerte"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/gmcfuerte-xml-sitemap.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
WordPress has generated a sitemap since version 5.5, and for many sites that is\ngenuinely enough. This plugin is for the sites where it is not.<\/p>\n\n
Core's This plugin serves If none of the above matters to your site, core's sitemap is fine and you do\nnot need this plugin. That is a genuine recommendation, not modesty.<\/p>\n\n This plugin makes no external network requests whatsoever<\/strong>. It contacts no\nAPI, sends no telemetry, pings no search engine, checks no remote server for\nupdates, and loads no font, script or image from a third-party domain. It reads\nyour database and writes XML. Nothing leaves your server.<\/p>\n\n It also writes no file anywhere outside its own plugin directory, and deletes\nno file at all \u2014 not on uninstall, not ever. Your site root is left exactly as\nit was found.<\/p>\n\n Publishing two sitemaps for one site is not useful, so by default this plugin\nswitches core's Your sitemap is linked from For image, video, news or hreflang entries, which core does not produce at all.\nIf you only need a list of your posts, pages and terms, core already does that\nand you should keep using it.<\/p><\/dd>\n By default yes \u2014 it turns off Technically yes, but you should not run two sitemap generators at once. Turn\nthe other plugin's sitemap off, or this one.<\/p><\/dd>\n Go to Settings \u2192 Permalinks<\/strong> and click Save Changes. That regenerates the\nrewrite rules. If your permalinks are set to \"Plain\", pretty sitemap URLs are\nnot available at all \u2014 the settings screen shows the query-string URL that\nworks instead.<\/p><\/dd>\n No. The plugin makes no external requests of any kind. See \"Privacy and network\nuse\" above.<\/p><\/dd>\n No. This plugin never deletes a file, and never writes one outside its own\ndirectory. If a static 50,000, the limit in the sitemap protocol. The content, image and video\nsitemaps split at that point into numbered files ( Because the index lists only the sitemaps that have something in them. Switch\nthe video sitemap on with no videos published and no \/wp-sitemap.xml<\/code> lists posts, pages, public custom post types,\ncategories, tags and author archives, and gives each entry a <loc><\/code> and a\n . That is the whole of it. Core implements none of the sitemap\nextensions, so if you need search engines to see your images, your videos or\nyour news content as such, core cannot express it.<\/p>\n\n\/sitemap.xml<\/code> and adds exactly the parts core leaves out:<\/p>\n\nWhat this adds that WordPress core does not<\/h4>\n\n
\n
<image:image><\/code> entries for the images in your content, so\nGoogle Images has a URL list instead of having to discover them by crawling.\nCore has no image sitemap at all.<\/li>\n<video:video><\/code> entries with thumbnail, title, description\nand player URL for embedded and self-hosted video. The post's featured image\nis the thumbnail, and Google rejects a video entry that has none, so posts\nwithout a featured image are left out. Core has no video sitemap.<\/li>\n<news:news><\/code> sitemap of the last 48 hours, up to\n1,000 posts, in the shape Google News expects. Core has no news sitemap.<\/li>\n<xhtml:link rel=\"alternate\" hreflang=\"...\"><\/code> inside\neach URL entry, for sites translated with Polylang<\/strong> or WPML<\/strong> (those two\nare what the plugin reads translations from). Core emits no alternates.<\/li>\n<changefreq><\/code> and <priority><\/code><\/strong> \u2014 core deliberately emits neither. They\nare hints, and the major engines mostly ignore them, but some crawlers and\ninternal tools still read them.<\/li>\n\/sitemap.xml<\/code><\/strong> \u2014 the conventional path, rather than core's\n \/wp-sitemap.xml.<\/li>\nPrivacy and network use<\/h4>\n\n
Working alongside core<\/h4>\n\n
\/wp-sitemap.xml<\/code> off. If you would rather keep both, untick\n\"Disable the WordPress core sitemap\" in the settings.<\/p>\n\n\n\n
\/wp-content\/plugins\/<\/code>.<\/li>\nhttps:\/\/your-site.tld\/sitemap.xml<\/code> in Google Search Console or Bing\nWebmaster Tools.<\/li>\n<\/ol>\n\nrobots.txt<\/code> automatically.<\/p>\n\n\n\n
WordPress already makes a sitemap. Why would I install this?<\/h3><\/dt>\n
Does it replace the core sitemap?<\/h3><\/dt>\n
\/wp-sitemap.xml<\/code> so your site publishes one\nsitemap instead of two. You can turn that behaviour off in the settings and run\nboth.<\/p><\/dd>\nDoes it work with another SEO plugin that also makes a sitemap?<\/h3><\/dt>\n
My sitemap returns a 404.<\/h3><\/dt>\n
Does it send my data anywhere?<\/h3><\/dt>\n
Will it delete my existing sitemap.xml file?<\/h3><\/dt>\n
sitemap.xml<\/code> file already exists in your site root, your\nweb server will serve that file instead of this plugin's output \u2014 delete or\nrename it yourself if you want the plugin's sitemap to take over.<\/p><\/dd>\nWhat is the maximum number of URLs per sitemap?<\/h3><\/dt>\n
sitemap-content-2.xml<\/code> and\nso on) listed in the index. The category, tag and author sitemaps are single\nfiles and stop at the same 50,000; the news sitemap stops at 1,000, which is\nGoogle's own limit for it.<\/p><\/dd>\nWhy does the index list fewer sitemaps than I switched on?<\/h3><\/dt>\n
sitemap-videos.xml<\/code>\nappears in the index \u2014 an index entry pointing at an empty file is what makes\nSearch Console report \"Sitemap is empty\". Publish a video and it appears by\nitself, at the latest when the cache expires.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n