URL budget
SitemapHost-specific term — the per-domain URL cap a customer allocates from their plan's total URL pool. Lets multi-domain accounts split URLs flexibly between domains.
Also known as: per-domain budget
URL budget is a SitemapHost-specific concept: the maximum number of URLs you've allocated to a single domain, drawn from your plan's total URL pool.
Why it exists
Most hosted-sitemap services apply a single per-account URL cap. SitemapHost's plans expose two layers:
- URL pool — total URLs across all your domains. E.g., Pro = 500,000 URLs.
- URL budget — how many of those URLs are allocated to each individual domain.
This matters because real teams rarely have evenly-distributed needs. A Pro customer might have:
sitemap.shop.example.com— 350,000 URLs (large e-commerce catalog)sitemap.blog.example.com— 50,000 URLs (editorial)sitemap.docs.example.com— 100,000 URLs (programmatic SEO landing pages)
A single per-account cap of 500K is meaningless if a hard per-domain cap of 100K would be applied to the e-commerce domain. URL budgets let you allocate the pool flexibly.
How it works
When you add a domain, SitemapHost asks for the URL budget (or assigns a default — typically the minimum domain budget for your plan). When you push URLs via the API, we check the budget on the specific domain, not the global account total.
Budgets can be adjusted from the dashboard at any time. The sum of all your domain budgets must not exceed your plan's URL pool.
Example
A Pro plan (500K URL pool, 5 domains max):
| Domain | Allocated budget | URLs used |
|---|---|---|
| sitemap.shop.example.com | 350,000 | 312,000 |
| sitemap.blog.example.com | 50,000 | 8,400 |
| sitemap.docs.example.com | 100,000 | 78,000 |
| Total | 500,000 | 398,400 |
If shop.example.com grows past 350K, you can rebalance: take 50K from docs (which is using 78K of 100K and has headroom) and give it to shop.
What this isn't
URL budget is not a Google or sitemap-spec concept. Google has its own concept of "crawl budget" (how many requests Googlebot is willing to make to your site per day), which is unrelated. URL budget is purely how SitemapHost partitions your plan's URL pool.
When you'd reduce a budget
- A domain is no longer in use — set its budget to 0 (or delete the domain).
- You're approaching the plan pool limit and want to free up capacity elsewhere.
- You're testing a new domain and don't want it consuming pool you might need later.
You can't reduce a budget below the URLs currently used; first delete or regenerate the sitemap to free URLs, then lower the budget.
See also
For the technical concept of how Google decides how much of your site to crawl, see the SitemapHost blog post on programmatic SEO sitemaps.
Related terms
Need help managing your sitemaps?
SitemapHost hosts your XML sitemap at your own domain with auto-SSL, IndexNow, and GSC integration.
Get Started Free