#545 · Developer Tool

Sitemap Split Planner

Plan how a URL inventory should be divided across sitemap files before XML generation. Paste one absolute URL per line and set conservative limits for URL count and uncompressed file size. The planner estimates each encoded url entry in UTF-8, groups records without crossing either limit, and prints file ranges plus estimated sizes. The default ceilings match the widely used sitemap limits of 50,000 URLs and 50 MB, but smaller deployment limits are supported.

Developer Input

Web metadata input
Ad space

How to use this developer tool

  1. Paste the requested source text or load a local file.
  2. Set any comparison values or processing options shown below the input.
  3. Select the primary action or press Ctrl/Cmd + Enter.
  4. Review the diagnostics, then copy or download the output.

What this developer tool does

Each output row proposes a sitemap filename, its URL range, item count, and estimated uncompressed XML size.

A fixed XML wrapper and an encoded value are counted for every URL. A new file starts before the next record would exceed either selected limit.

The estimate includes loc elements only; lastmod, image, video, or news metadata will increase the real file size.

Example

Input

https://example.com/page-1/
https://example.com/page-2/
https://example.com/page-3/
https://example.com/page-4/

Run the sample to see the exact report and metrics produced by the current implementation.

Use cases

  • Pre-deployment review of generated site files
  • Debugging crawler or link-preview configuration
  • Auditing metadata during a migration
  • Creating repeatable QA evidence for a release

Tips for reliable output

  • Paste the complete source when grouping or document context matters.
  • Use absolute public URLs unless the field explicitly accepts a path.
  • Retest after redirects, route rules, or locale mappings change.
  • Keep a deliberately invalid sample for regression checks.
  • Confirm the deployed result with the relevant external platform.

Processing details

A fixed XML wrapper and an encoded value are counted for every URL. A new file starts before the next record would exceed either selected limit. The parser runs entirely in the current browser tab and returns copy-ready text plus structured exports when useful.

The estimate includes loc elements only; lastmod, image, video, or news metadata will increase the real file size.

Frequently asked questions

Can I use this tool without uploading data?

Yes. Processing happens in your browser, and the page makes no request with the supplied input.

What happens when the input is malformed?

The Sitemap Split Planner stops, displays an actionable error, and does not produce a misleading successful result.

Does the result guarantee search engine behavior?

No. The result checks the supplied markup or rules; crawlers and social platforms may apply additional policies and cached data.

Can I download the result?

Yes. Use Download for the primary output, or the CSV and JSON buttons when structured exports are available.

How should I test the result before deployment?

Run a representative valid sample and a deliberately invalid case, then verify the deployed public URL with the relevant crawler or platform tool.

Checks and output

AreaBehavior
InputProcessed locally
ErrorsReported without silent correction
ExportCopy, download, and structured data when available

Web Meta & Server Files

Inspect crawler directives, sitemap files, canonical URLs, localized alternates, and social metadata.

View category hub