Skip to content
Tool4SaaS
HomeAboutContactBlog
Tool4SaaS

185 fast, local utilities for developers and creators. No sign-ups — most tools run in your browser (see /privacy).

hello@tool4saas.com

Categories

  • Text & Documents

  • Business & Writing

  • Developer Tools

  • Converters

  • Generators

  • Images & Design

  • PDF Tools

  • Calculators

  • Finance & Money

  • Health & Fitness

  • SEO & Marketing

  • Time & Date

Popular Tools

  • Invoice Generator

  • QR Code Generator

  • Word Counter

  • Password Generator

  • JSON Formatter

  • Mortgage Calculator

  • EMI Calculator

  • SIP Calculator

  • View all tools →

Company

  • All Tools

  • About Us

  • Author

  • Methodology

  • Blog

  • Contact Us

Guides

  • Invoice Generator Guide

  • QR Code Generator Guide

  • Resume Builder Guide

  • Mortgage Calculator Guide

  • Password Generator Guide

  • Word Counter Guide

  • llms.txt (for AI)

© 2026 Tool4SaaS. All rights reserved.

  • Privacy Policy

  • ·
  • Terms of Service

  • ·
  • ·
  1. Home
  2. /
  3. Blog
  4. /
  5. SEO Guide
  6. /
  7. Split Large Sitemaps Search Console Accepts

Split Large Sitemaps Search Console Accepts

Split 120K catalogs into 50K/50MB sitemap files: index structure, honest changefreq/priority tiers + rejection fixes. Free generator.

By Tool4SaaS Editorial Team · Published 2026-10-07 · Updated 2026-10-07 · 3 min read

Try it now — Sitemap Generator, free in your browser

XML sitemap builder · No signup · No watermark · Free forever.

Open Sitemap Generator →
On this page
  • Split math
  • Tiers
  • Rejection fixes

Catalog: 120,000 URLs. Search Console: “Sitemap exceeds limits.” One file cannot hold it — the sitemap protocol caps files at 50,000 URLs or 50MB uncompressed, and a single relative-path entry can poison the whole submission. Splitting catalogs into indexed sitemap files is a thirty-minute job that unblocks crawling for months. This guide covers the split math, changefreq honesty, priority tiers and the relative-path rejection that fails most first attempts.

Part of the SEO publishing guide. Generate maps in the sitemap generator; gate crawling with the robots.txt generator.

Split math: 50K URLs / 50MB per file + index

120,000 URLs → three files (50K + 50K + 20K), each under 50MB uncompressed, listed in a sitemap index that Search Console accepts as one submission. Name them by segment (sitemap-products-1.xml, not part1.xml) so coverage reports stay readable. Regenerate on catalog change — stale sitemaps listing dead URLs waste crawl budget exactly when launches need it most. Paste up to 1,200 URLs per run into the generator for clean XML output.

changefreq honesty + priority tiers

Page typechangefreqpriorityWhy
Bestsellers / pillarsweekly0.8Crawl often, rank-bearing
Product / cluster pagesmonthly0.5–0.6Steady value
Archives, tagsyearly0.3De-prioritize crawl spend

Priorities are hints, not orders — but honest tiers focus crawler attention where revenue lives. Marking everything 1.0/daily trains crawlers to ignore your signals; underclaiming archives is a feature. Revisit tiers quarterly as catalog mix shifts.

Rejections: relative paths, bad dates, wrong content-type

  • Relative URLs rejected: every <loc> must be absolute HTTPS (https://…, never /page). One relative entry can fail the file.
  • Malformed lastmod: W3C datetimes only (2026-10-07, not “yesterday”). Future dates confuse schedulers.
  • Wrong encoding: UTF-8, ampersands escaped (&amp;). Hand-edited XML breaks here most.
  • Blocked by robots: URLs disallowed in robots.txt get “submitted but blocked” status — allow what you submit.

After acceptance, watch Search Console's indexed-vs-submitted delta: a growing gap means quality or duplication filters, not sitemap syntax — fix content, not XML. Pair sitemap work with crawler gates in robots vs noindex.

General guidance only. Sitemap hygiene amplifies crawling; it cannot rescue uncrawlable architecture or thin content.

Related free tools

Robots.txt Generator →SEO Analyzer →

Frequently asked questions

Each sitemap file caps at 50,000 URLs or 50MB uncompressed, so catalogs must split into files listed in a sitemap index. A 120,000 catalog becomes 50K plus 50K plus 20K files submitted as one Search Console entry. Name segments like sitemap-products-1.xml, regenerate on catalog change, and paste up to 1,200 URLs per run.

Use weekly with 0.8 priority for bestsellers, monthly with 0.5 to 0.6 for cluster pages, and yearly with 0.3 for archives and tags. Honest tiers focus crawler attention where revenue lives because priorities are hints, not orders. Marking everything 1.0 daily trains crawlers to ignore signals, so revisit tiers quarterly.

Search Console usually rejects for relative URLs, since every loc must be absolute HTTPS and one relative entry can fail the file. Other causes are malformed lastmod dates needing W3C format like 2026-10-07, wrong encoding without UTF-8 and escaped ampersands, or submitted URLs blocked by robots. Allow what you submit and validate encoding before resubmitting.

No, priorities are crawl hints, not orders, so marking everything 1.0 daily trains crawlers to ignore your signals. Honest tiers focus attention where revenue lives, with bestsellers at 0.8 and archives at 0.3 to de-prioritize spend. If indexed versus submitted gaps grow, fix content quality or duplication, not XML, and revisit tiers quarterly.

Usually content quality or duplication filters cause the gap, not XML, because the sitemap did its delivery job once accepted. Watch Search Console indexed versus submitted delta, since a growing gap signals filters rather than syntax. Fix thin or duplicate content instead of XML, regenerate sitemaps on catalog change, and pair mapping with crawler gates.

Done reading — open the Sitemap Generator

XML sitemap builder — free in your browser, no signup.

Open Sitemap Generator →

Keep reading in this guide

Pillar guide

Score 80+ On-Page SEO Without a Plugin: 11 Checks

In this silo

Fix SEO Score From 60 to 80: Worked Example

In this silo

Robots.txt vs Noindex: When to Use Each

In this silo

Name UTM Campaigns Without Splitting Reports