Lazy Loading Code Generator
Write image and iframe markup that loads at the right time.
Build the sitemap index file that points at all your sitemaps.
Absolute URLs on the same host. Add a date after a pipe to give one sitemap its own lastmod.
Applied to any line without its own date. Leave blank to omit it.
Used for the robots.txt line and to check the sitemaps share its host.
Your generated code appears here.
The Sitemap Index Generator turns a list of sitemap URLs into a valid sitemapindex file, with optional lastmod dates and the robots.txt line that declares it. It exists because splitting sitemaps by content type is what makes Search Console's coverage report per-sitemap — and that is what turns a vague indexing problem into a specific one.
List your sitemap URLs, one per line, and the generator writes the sitemap index file that points at them. Each entry can carry its own lastmod, and the robots.txt line that declares the index is produced alongside it.
A sitemap index is what you need once a single sitemap will not do, and the threshold arrives sooner than most people expect: 50,000 URLs or 50MB uncompressed, whichever comes first. It is also worth splitting well before that, by content type — products, categories, blog posts, static pages each in their own sitemap — because Search Console reports indexing coverage per sitemap. Split that way, "42 of 8,000 product URLs are not indexed" is a sentence you can act on. In one giant sitemap, the same fact is invisible.
The correct namespace and element nesting, which is where hand-written index files usually fail.
Set one date for all of them or a different date per line, written in the W3C format.
Sitemaps on a different host than the index are flagged, since that combination is invalid.
An index listing another index is invalid, and the tool says so rather than generating it.
The Sitemap directive to add is generated alongside the file itself.
One per line, absolute, on the same host — "https://example.com/sitemap-products.xml".
Optional, written after a pipe. Or set one date for all of them at once.
Save it as sitemap.xml at your domain root, or wherever your sitemaps live.
Add the Sitemap line to robots.txt and submit the index in Search Console.
Once you pass 50,000 URLs or 50MB in one sitemap, you must. Well before that, you should: splitting by content type makes Search Console's coverage report per-sitemap, and that is what turns "some pages are not indexed" into a specific, actionable number.
No. The protocol allows exactly one level. An index lists sitemaps; a sitemap lists URLs. Nesting indexes is invalid and Google will reject the file.
At or above the level of the sitemaps it lists, on the same host. A sitemap at the domain root can list sitemaps anywhere on that host; one inside a directory can only list sitemaps in that directory or below.
Just the index. Google follows it to every child sitemap and reports on each one separately. Submitting both the index and its children clutters Search Console without adding anything.
What people who use the Sitemap Index Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Sitemap Index Generator. It takes half a minute and no account.
Write the first reviewWrite image and iframe markup that loads at the right time.
Cross three lists of words into every combination.
Check description length in pixels and spot the ones Google will cut.
Score a page against the on-page checks that actually matter.
Tag campaign URLs so analytics can tell your traffic apart.
Turn a list of old and new URLs into Apache redirect rules.
Turn a topic into dozens of workable title options.
Build the twitter:card tags and preview the result.