In short. The SEO Framework routes several sitemap URL forms to its virtual generator, while language-specific URLs select distinct translated sitemaps.
Definition: The SEO Framework (TSF) generates sitemaps virtually with PHP and does not store them on the website's drive. Its documentation describes dynamic, unlimited sitemap endpoints, including
/sitemap_index.xmlas a compatibility endpoint, so several URL forms can reach the same sitemap output.
Key facts
- TSF says its base sitemap is small and consists of one page. The sitemap documentation says only posts and pages are included.
- The documentation describes TSF's sitemaps as dynamic, with unlimited endpoints available from
/sitemap.xml. - The endpoint accepts additions such as
/sitemap.xmlanything, according to the same documentation. - TSF added
/sitemap_index.xmlfor hosts configured around Yoast SEO. When/sitemap.xmlis accessible, the documentation says the/sitemap_index.xmlendpoint can be ignored. - With the optimized sitemap enabled, TSF can add
/sitemap.xmlto a generatedrobots.txtfile when there is no custom file in the site's root folder.
How does virtual generation make several URLs possible?
TSF's sitemap is generated virtually through PHP, so the response comes from WordPress request handling rather than from a sitemap file stored on disk, as explained in the sitemap documentation. The documentation gives WordPress multisite as a reason for this design: several WordPress sites can use one directory, while a file stored there would prevent unique output for each site.
The same documentation calls the sitemaps dynamic and says that anything can be added to their endpoints. The documented examples are:
/sitemap.xml
/sitemap.xmlanything
These paths can therefore look like separate files while reaching the same TSF sitemap generator. The endpoint text alone does not identify a separately stored XML document.
What is /sitemap_index.xml for?
/sitemap_index.xml is a compatibility endpoint. TSF's sitemap documentation says it added this path to support misconfigured hosts that cater to Yoast SEO. It also states that access to /sitemap.xml indicates that the website is configured correctly in this regard and that the index-named endpoint can be ignored.
The two paths should therefore be read as compatibility names for the same TSF sitemap setup when both respond with the same XML. The documentation does not describe /sitemap_index.xml as a separate index containing a different set of child sitemaps.
Which URLs are genuinely language-specific?
Language variants are a separate case. TSF's translation compatibility documentation says the optimized sitemap outputs a unique sitemap for each language. The advertised URLs appear under SEO Settings, Sitemap Settings, and View translated sitemaps. Their form follows the translation plugin's URL format:
example.com/sitemap.xml (default language)
example.com/es/sitemap.xml (subdirectory)
example.com/sitemap.xml?lang=es (query parameter)
es.example.com/sitemap.xml (subdomain)
The page also says that these sitemaps live at the site root and are not placed under a static front-page slug. A language path or query parameter can select a language-specific sitemap, whereas an arbitrary suffix such as /sitemap.xmlanything is documented as an accepted endpoint form.
How can a site owner check the response?
A check starts with /sitemap.xml, because TSF identifies it as the main optimized-sitemap endpoint. If the site uses WPML, Polylang, or TranslatePress, the language-specific URLs shown in View translated sitemaps should be checked separately. TSF's documentation says WPML and Polylang configurations can cause robots.txt to list the default sitemap and extra language sitemaps, while WordPress Core sitemaps use /wp-sitemap.xml instead.
For a server-level problem, TSF documents a distinct NGINX symptom: /sitemap.xml can redirect to /wp-sitemap.xml or /sitemap_index.xml, or show a 404 error. The documented remedy is to remove sitemap-related NGINX configuration that prevents the request from reaching WordPress.
Related terms
- XML sitemap
- robots.txt Sitemap field
- Where is the built-in WordPress XML sitemap?
- How can The SEO Framework use WordPress core sitemaps instead of its optimized sitemap?
FAQ
Why can /sitemap.xmlanything return a sitemap?
TSF's sitemap documentation documents unlimited sitemap endpoints and says that anything can be added to /sitemap.xml. The path is handled by the virtual sitemap mechanism described in its documentation.
Should you use /sitemap_index.xml or /sitemap.xml?
If /sitemap.xml is accessible, TSF says you can ignore /sitemap_index.xml. The latter exists for compatibility with hosts configured around the Yoast sitemap name.
Why can a translated sitemap have a different URL?
TSF outputs a unique sitemap for each language when its optimized sitemap is enabled. You can find the advertised language URLs in SEO Settings, Sitemap Settings, and View translated sitemaps; the URL form depends on the translation plugin's format.
Sources
- The SEO Framework, "All You Must Know About Sitemaps", 13 October 2026
- The SEO Framework, "Translation Plugin Compatibility", 13 October 2026
Check how a page reads to answer engines. Open the GEO score analyzer