Why I Built Custom Language Sitemaps for TranslatePress

Multilingual WordPress sites need more than just translated pages. They also need ways for crawlers and tools to clearly distinguish and verify the different language versions.

TranslatePress is pleasantly pragmatic: A page remains a WordPress page, and the language versions are located in directories such as /en/, /fr/ or /it/. For editorial and operational purposes, this is often just right. The technical side issue doesn't come up until later: How do you actually check which URLs for a given language are included in the sitemap?

This is exactly where Language Sitemaps for TranslatePress was created. The plugin is not a new SEO solution and does not replace Rank Math. Its scope is intentionally narrower: TranslatePress sites using Rank Math that require a separate sitemap index for each published language.

The Summary

• A sitemap does not guarantee indexing or rankings.
• However, it helps make important URLs discoverable and verifiable.
• For multilingual WordPress sites, the question isn't just, „Is there a sitemap?“
• A better question would be: „Can I view each language version as its own URL group, check it, and use it for warm-up if needed?“
• Language Sitemaps for TranslatePress adds indexes such as sitemap_index_en.xml and child sitemaps such as sitemap_en_post_1.xml.
• The Standard Rank Math Index sitemap_index.xml remains unchanged.

How to Tell If This Applies to You

You use TranslatePress with language directories and Rank Math for your XML sitemaps. So, for example, your website has German content at /, English content at /en/ and perhaps other languages in their own directories.

Then operational questions quickly arise:

1. Which English URLs are currently actually listed as sitemap paths?
2. Is there a separate entry point for the English version?
3. Can I check robots.txt in a way that makes the language indexes visible?
4. Can a cache warm-up specifically retrieve the English URLs?
5. Does an additional language index still comply with the Rank Math rules?

So the problem isn't that language versions would be invisible without this plugin. That would be too simplistic and incorrect in many setups. TranslatePress SEO Pack and SEO plugins can generate multilingual sitemaps. The point here is more specific: Custom, simple, language-specific indexes for TranslatePress directory URLs that complement, rather than replace, Rank Math.

What the plugin specifically adds

Language Sitemaps for TranslatePress reads the published languages from TranslatePress and generates separate XML sitemap indexes for them. For English, for example, it might look like this:

/sitemap_index_en.xml

This index then points to child sitemaps for each content type or taxonomy:

/sitemap_en_post_1.xml
/sitemap_en_page_1.xml
/sitemap_en_product_1.xml

Rank Math's root index remains in place. This is important because Rank Math continues to serve as the central SEO sitemap layer. The plugin does not add a second layer of SEO logic; instead, it mirrors the relevant Rank Math rules: deactivated post types and taxonomies, global noindex-rules, rank_math_robots on individual pieces of content and items_per_page.

Why robots.txt and Warmup Play a Role Here

Sitemaps aren't just useful for Google. They also serve as an operational signal: Which URLs should tools see, check, or prepare?

The plugin automatically adds language indexes to the robots.txt file. This makes it clear which language sitemaps are available. For setups using NitroPack, there is also a separate warmup index:

/nitro-warmup-sitemap.xml

The WP-CLI command wp localized-sitemaps sync-nitro Set this warm-up index in NitroPack. And with wp localized-sitemaps list-indexes you can quickly check the available endpoints without having to click through XML files in your browser.

What it deliberately does not do

The plugin addresses exactly one specific technical scenario (see above)

• It does not include hreflang annotations in XML sitemaps.
• It is not intended for separate-domain setups for each language.
• It does not reflect every special provider in Rank Math, such as author, news, or video sitemaps.
• It doesn't promise better rankings.

If you already have a setup that provides exactly the sitemap structure you need, you probably don't need this plugin. But if you use TranslatePress directory URLs and want clear, separate indexes for each language, that's exactly what this plugin is designed to do.

Why I Built It

The specific reason was the English rollout of a client’s website. The site uses TranslatePress, Rank Math, and NitroPack. For the operations team, it was important not only to know whether the content had been translated, but also whether the English URLs were visible as a separate technical group and could be warmed up.

In a live setup, it delivers sitemap_index_en.xml Six English child sitemaps: Posts, Pages, Products, Coaches, Skills, and Workshops. The robots.txt file promotes the English-language index. The standard Rank Math index remains unchanged.

This isn't a spectacular list of features, but rather the kind of small-scale infrastructure that makes a multilingual WordPress site easier to test.

Here's how to check your setup

If you're using TranslatePress and Rank Math, I'd check them in this order:

1. Open your regular Rank Math sitemap.
2. Check to see if you can distinguish the language versions clearly enough.
3. Check your robots.txt file: Which sitemaps are listed there?
4. If you're using cache warmup: Check which URL list is being used for the warmup.
5. Check whether noindex-Content in additional sitemaps remains excluded.

After that, you'll have a better idea of whether you even have a problem. If so, Language Sitemaps for TranslatePress is a very small, targeted plugin.

Download

The plugin is free and open source. The product page on isla-stud.io is linked here: Language Sitemaps for TranslatePress. With the 0-euro order, you'll receive a license key for automatic updates via the standard WordPress update mechanism.

If you want to get a better sense of the bigger picture first: In the article Making WordPress More Readable for AI Systems This covers sitemaps, canonical tags, "noindex," internal links, and structured signals as part of clean WordPress readability.

Sources and Verification

Claim	Source
Plugin Name, Version 0.3.1, Requirements, GPL 2.0 or later	Plugin Header and readme.txt
Language-specific indexes and child sitemaps, Rank Math mirroring, robots.txt advertising, NitroPack and WP-CLI features	readme.txt and Core Class
Product is free, EDD Software Licensing enabled, Download ZIP 0.3.1	Language Sitemaps for TranslatePress
TranslatePress SEO Pack can generate multilingual sitemaps	TranslatePress SEO Pack Documentation and Rank Math Compatibility Documentation
Sitemaps do not guarantee indexing	Google Search Central, Sitemaps Documentation