Sitemap Generator

Sitemap XML Generator

Enter a list of URLs, set changefreq, priority and lastmod globally, generate sitemap.org-compliant XML sitemaps in one click.

Input & Parameters

URL list (one per line)3 URLs

Change Frequency

Priority

Last Modified

XML Output

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://geekformat.com/</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://geekformat.com/pricing</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://geekformat.com/blog</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

3 valid URLs, 483 bytes

Generate Sitemap XML website map files online compliant with the sitemap.org 0.9 open protocol standard. Supports complete configuration of 7 changefreq update frequencies, priority 0.0-1.0 relative priority levels, and lastmod date picker. Features automatic XML entity escaping, real-time invalid URL detection, live structured XML preview, and one-click download and copy functions, helping major search engines including Google and Bing quickly discover and efficiently index all important pages on your website.

Robots.txt Generator

HSTS Analyzer

Sitemap Inspector

Hreflang Tag Generator

Meta Tag Generator

Cron Expression Generator

Use Cases

Batch generate Sitemaps for core pages after a new website launch and submit to Google Search Console and Bing Webmaster Tools to accelerate search engine discovery and indexing
Regenerate sitemaps after website section redesigns or URL structure changes to update search engine indexes and prevent broken link remnants from affecting SEO performance
Batch import product list URLs for e-commerce websites, setting different changefreq and priority values based on product categories and listing dates
Split generation of multiple Sitemaps by channel for large portals or news sites exceeding 50,000 URLs and create a Sitemap Index file
Configure appropriate update frequencies and priority parameters for article pages, tag pages, category pages, and archive pages on blog websites
Organize different URL types for corporate websites including product pages, news pages, about pages, and contact pages, setting differentiated lastmod and priority values
Regenerate and submit Sitemaps after website migration (HTTP to HTTPS upgrade, domain name change) to guide crawlers to quickly fetch new addresses
Manually supplement Sitemaps generated by plugins like Yoast SEO, adding special page URLs not covered by the plugin
Regenerate Sitemaps after SEO diagnostics and optimization to ensure important pages have reasonable priority settings, enhancing crawl weight for high-value pages
Validate XML format correctness with this tool before declaring Sitemap location in robots.txt to avoid crawler parsing failures

How to Use

Paste the list of page addresses to be indexed in the URL input area, one complete URL per line (must include http:// or https:// protocol prefix)
Select the page update frequency from the changefreq dropdown: choose daily or hourly for homepage, weekly for article pages, yearly or monthly for static pages
Drag the priority slider or enter a value between 0.0-1.0 to set priority: set core homepage to 1.0, important section pages to 0.8, regular article pages to 0.5, archive pages to 0.3
Click the lastmod date picker to select the last modification date of website content, or leave it blank to exclude the lastmod field
Check the real-time preview area on the right to verify generated XML structure is correct; invalid URLs will be highlighted in red for correction
After confirming correctness, click the "Download sitemap.xml" button to save the file, or click the "Copy" button to copy XML content to clipboard
Upload sitemap.xml to the website root directory, add Sitemap declaration in robots.txt, or submit directly to Google Search Console/Bing Webmaster

Features

Batch URL input support: One URL per line, with automatic filtering of blank lines and duplicate links for fast processing of large page address batches
Automatic XML entity escaping: Special characters in URLs including &, <, >, ", and ' are automatically escaped to &, <, >, ", and ', completely eliminating XML parsing errors
7 changefreq update frequency options: always, hourly, daily, weekly, monthly, yearly, never—covering all page type scenarios
Granular priority settings: Supports any value between 0.0 and 1.0 with one decimal place precision, enabling differentiation of page importance levels
lastmod last-modified date picker: Visual calendar selector that automatically formats to the W3C Datetime standard format (YYYY-MM-DD)
Real-time invalid URL detection: Automatically identifies malformed URLs (missing protocol, illegal characters, etc.) and marks problem line numbers for easy correction
Real-time preview generation: XML content updates instantly when URL lists or configuration parameters are modified—no manual generate button click required
One-click sitemap.xml download: Generated results download directly as a standard XML file, ready for immediate upload to a web server upon saving
URL limit warning: Automatically prompts for Sitemap Index splitting when input URLs reach 50,000 entries
Copy to clipboard: One-click copying of complete XML content to the clipboard for easy pasting into server files or online submission
Byte size statistics: Displays real-time byte count of the generated Sitemap XML file to assess whether file size complies with search engine limits
Standard urlset root element output: Strictly follows the http://www.sitemaps.org/schemas/sitemap/0.9 protocol specification with correct xmlns namespace declaration
UTF-8 encoding declaration: Automatically adds XML encoding declaration to ensure multilingual URLs parse correctly without character corruption

FAQ

Is Sitemap submission mandatory? Will my site not be indexed without submitting?

Websites can be indexed without submitting Sitemaps—search engines can discover your pages through external links from other sites and internal link tracking. However, submitting a Sitemap can greatly accelerate discovery speed, especially for new sites, large sites, and sites with poor internal linking. Google officially recommends that all websites submit Sitemaps as it is low-effort, high-return basic SEO work.

Must URLs in Sitemaps be absolute paths? Can relative paths be used?

Must be complete absolute URLs including protocol prefix (http:// or https://) and complete domain name; relative paths (such as /page1.html) or protocol-omitted formats cannot be used. Search engines need complete URLs to correctly crawl when parsing Sitemaps; relative paths will cause parsing errors.

Are changefreq and priority settings actually useful? Will search engines follow them?

Both fields are "suggestions" rather than "directives," and search engines may not 100% follow them, but accurate settings still have reference value. By comparison, lastmod (last modified time) is the most important of the three fields to search engines because it directly tells crawlers whether pages have new content. Do not dishonestly set all pages to highest priority or always, as this will cause search engines to stop trusting this metadata.

Must Sitemap files be placed in the website root directory?

Not necessarily. Sitemaps can be placed at any path under the website as long as the URL is accessible. However, robots.txt must be placed in the root directory. If you split multiple Sitemaps using Sitemap Index, sub-Sitemap paths have no restrictions. However, conventionally placing them in the root directory is most convenient for management and crawler discovery.

My website has fewer than 50,000 URLs but file size exceeds 50MB. What should I do?

Need to split the Sitemap. 50,000 URLs and 50MB are two parallel limits; exceeding either requires splitting. You can split by content type or streamline the Sitemap (such as removing unnecessary spaces and indentation, using gzip compression), but if it still exceeds 50MB after compression you must split.

Can Sitemaps contain noindex pages or URLs blocked by robots.txt?

Not recommended. Sitemaps should only contain pages you want search engines to crawl and index. Noindex pages, Disallow-blocked pages, pages requiring login to access, and 404 error pages should not appear in Sitemaps, as this reduces search engine trust in the Sitemap and wastes crawl budget.

Do I need to resubmit Sitemap after content updates? How often should Sitemaps be updated?

As long as the Sitemap file URL remains unchanged, search engines will periodically recrawl; there's no need to manually resubmit every time content updates. Update frequency depends on your website's content update frequency: news sites can update Sitemaps daily or even hourly (auto-generated), while corporate websites updating weekly or monthly is sufficient. You can set server-side scripts to automatically update Sitemap files.

What language URLs does Sitemap support? Do Chinese URLs need encoding?

Sitemap supports URLs in any language, but non-ASCII character URLs (such as Chinese) require URL encoding (also called percent-encoding). For example, "中文页面" must be encoded as %E4%B8%AD%E6%96%87%E9%A1%B5%E9%9D%A2. Most browsers and tools handle this automatically, but you need to ensure URLs in generated Sitemaps are correctly encoded.

Can multiple Sitemaps be submitted simultaneously? For example having both article Sitemaps and product Sitemaps?

Yes, in two ways: ①Use a Sitemap Index file to uniformly manage all sub-Sitemaps (recommended approach, only need to submit the index file URL); ②Submit each sub-Sitemap URL individually on webmaster platforms (also works but more cumbersome to manage). Both approaches are effective; search engines will crawl both.

Do Sitemaps need gzip compression after generation? What are the benefits of compression?

Compression is not required but strongly recommended. gzip compression typically reduces Sitemap size by 70%-80%, saving bandwidth and crawler fetch time—especially effective for large websites. Search engines fully support the sitemap.xml.gz compressed format and will automatically decompress. As long as it doesn't exceed 50MB after compression there's no problem.

Do both HTTP and HTTPS versions of a website need Sitemap submission?

You should only submit the preferred version you want indexed. If the entire site is HTTPS with HTTP→HTTPS 301 redirects, only submit the HTTPS version Sitemap. Do not submit both HTTP and HTTPS versions as this causes duplicate content issues. Similarly, determine a preferred domain for www vs non-www and only submit the preferred domain's Sitemap.

WordPress already generates Sitemaps with Yoast SEO. Do I still need this tool?

Yoast SEO can automatically generate Sitemaps for most pages but may miss some pages—such as manually created single pages, improperly configured custom post types, special landing pages, externally imported pages, etc. You can use this tool to supplement URLs not covered by Yoast, generate separate supplementary Sitemaps, or compare and verify that Yoast-generated Sitemaps are complete and correct.

Does URL order in Sitemaps matter? Is putting important pages first useful?

URL order has no official weight in the Sitemap protocol; search engines do not prioritize crawling because URLs appear earlier. However, some SEO practitioners have observed slight order preference effects, so putting important URLs first doesn't hurt, but don't expect significant results—you should still correctly identify priority through the priority field.

Do paginated pages (such as /list?page=2, /page/3) need to be in Sitemaps?

This depends on the value of paginated content. If pagination is "view more" nature duplicate lists (such as article list page 2, page 3), inclusion in Sitemaps is generally not recommended because these pages have duplicate content and low value; focus should be on list first pages and specific article pages. However, if pagination has unique content (such as category browsing with independent value), it can be considered for inclusion with lower priority.

How do I verify that a Sitemap is correct and valid?

Several verification methods: ①After generating with this tool, first preview XML structure locally to verify tag closure, namespaces, and escaped characters are correct; ②Use the sitemap-inspector tool to validate format and URL accessibility online, batch-checking HTTP status codes for all URLs; ③After upload, directly access the Sitemap URL in a browser to verify it displays normally without XML parsing errors; ④After submitting to Google Search Console/Bing Webmaster Tools, check status reports for format errors, inaccessible URLs, limit exceeded, and other error prompts—this is the most authoritative verification method; ⑤You can also use online XML validation tools to check XML syntax correctness.

Troubleshooting

Generated Sitemap XML shows parsing error when opened in browser, indicating incorrect format

URLs contain XML special characters like &, <, > without escaping: the tool automatically escapes when pasted, but if you manually edited the file you may have missed escaping XML declaration or urlset namespace written incorrectly: check that the first-line xmlns value exactly matches http://www.sitemaps.org/schemas/sitemap/0.9 with no extra slashes Tags not properly closed: all opening tags like <url>, <loc> must have corresponding closing tags </url>, </loc>; self-closing tag syntax must be correct File encoding is not UTF-8 without BOM: Windows Notepad may save as UTF-8 BOM or GBK encoding causing parsing errors; save as UTF-8 without BOM URLs contain illegal characters: Chinese URLs require URL encoding (percent-encoding); unencoded special characters will cause XML parsing failure XML version declaration error: first line must be <?xml version="1.0" encoding="UTF-8"?>; do not write 1.1 or other versions Tag nesting order error: child tags must be fully contained within parent tags; cross-nesting such as <url><loc></url></loc> is incorrect ordering

Google Search Console shows "Couldn't fetch Sitemap" or "Format error" after Sitemap submission

Sitemap file URL inaccessible: check if directly accessing the Sitemap URL in a browser returns 200 status code without 403/404/500 errors Server returned incorrect Content-Type: should return application/xml or text/xml; returning text/html will cause recognition failure Sitemap contains URLs blocked by robots.txt: GSC reports errors when it detects Disallow paths in the Sitemap URL redirect issues: Sitemap URLs that 301/302 redirect to other addresses cause errors; ensure URLs are directly accessible without redirects HTTP/HTTPS or www/non-www mismatch: submitted Sitemap domain doesn't match the domain verified in GSC (e.g., verified www.example.com but Sitemap uses example.com) Sitemap file too large exceeding 50MB limit or URLs exceeding 50,000 entries: GSC will directly reject processing over-limit files Used HTML entities instead of XML entities:   for spaces is an HTML entity, not an XML entity, and cannot be used in XML

Long after Sitemap submission, many URLs are still not indexed by Google

Page quality issues: indexing is not guaranteed upon submission; pages with poor originality, duplicate content, or low content value may be chosen not to be indexed by Google New site review period (sandbox effect): new websites may require weeks to months of observation period after Sitemap submission before batch indexing occurs Pages are noindex: pages return noindex meta tags or X-Robots-Tag: noindex response headers; Google will actively exclude them Insufficient website crawl budget: low site authority, slow server response, poor internal link structure result in low crawl frequency allocated by Google crawlers, requiring more time Sitemap contains many low-quality URLs: if many URLs in the Sitemap are 404s, 5xx errors, duplicate content, or low-value pages, Google will reduce trust in the entire Sitemap Domain penalized: website has issues violating Google quality guidelines (such as spam, scraped content, malware) causing indexing blockage Pages are orphan pages: although pages are in the Sitemap, there are no entry points from website internal links; crawlers may consider them unimportant and not index them

Sitemap shows discovered URLs, but actual index count is very low

This is normal: "Discovered" only means Google visited the Sitemap and saw the URLs, not that all will be indexed; indexing rate depends on page quality Duplicate content issues: multiple URLs with highly similar content (such as same page with different parameters, print versions, pagination) will have Google select one canonical version to index Canonical tag pointing to other pages: page has <link rel="canonical" href="other URL"> set; Google will index the address pointed to by canonical Page content too thin: too few words, no substantive value, scraped content—Google considers it not worth indexing Page loading speed too slow: server response timeout, pages loading too slowly; crawlers will reduce crawl priority after multiple failed fetches HTTPS certificate issues: invalid SSL certificates, mixed content errors, HTTP/HTTPS versions coexisting causing canonicalization issues Mobile adaptation issues: poor mobile-friendliness, mobile adaptation errors affect indexing in a mobile-first indexing environment

Bing can crawl Sitemap normally but Google doesn't crawl at all

Google Search Console verification issues: confirm domain ownership verification is valid and verified domain (www/non-www, http/https) matches actual access version Server firewall or CDN blocking Googlebot: check server access logs to see if Googlebot requests (user-agent containing Googlebot) are being blocked or returning 403 DNS resolution issues: Google's DNS resolves to different IP addresses than Bing; ensure all regions can properly resolve to your server robots.txt has special restrictions for Googlebot: check if there are special Disallow rules under User-agent: Googlebot Website has previous cheating history penalized by Google: domains that have received manual actions need to apply for reconsideration first Sitemap URL contains content Google considers unsafe: such as domains flagged for malware or phishing content CDN WAF rules false positives: some security rules may misidentify Googlebot crawler behavior; check CDN security logs

Generated Sitemap tests fine locally, but accessing it after server upload returns 404 error

Incorrect file path: sitemap.xml was not uploaded to the correct directory; confirm it is uploaded to the location corresponding to the URL you declared in robots.txt and submitted to search engines Filename case sensitivity issues: Linux/Unix servers are case-sensitive; Sitemap.xml and sitemap.xml are different files; ensure filename is all lowercase Nginx/Apache configuration blocking xml file access: check server configuration for location rules denying .xml file extension access or incorrect try_files rules File permission issues: incorrect file permissions on server (such as 600 permissions) where web server user lacks read access; typically requires 644 permissions, directories need 755 permissions CDN cached old 404 response: newly uploaded files may have CDN still caching previous 404; need to refresh CDN cache or wait for CDN to automatically refresh origin WordPress or other CMS permalink rule conflicts: CMS rewrite rules intercept sitemap.xml; need to configure exclusion rules so server directly accesses static files Server configured hotlink protection or access control: referer checks, IP whitelists, or other rules in .htaccess or Nginx configuration may be blocking crawler access

Glossary

Sitemap: An XML protocol standard file that informs search engines about all crawlable pages on a website, containing a complete URL list and metadata for each URL. Helps crawlers such as Googlebot and Bingbot more intelligently and efficiently discover, understand, and crawl website content. Maintained by the sitemaps.org organization as a unified open protocol standard (current version 0.9).
urlset: The root element of a standard Sitemap XML file, which must contain the correct xmlns namespace declaration and nest all <url> child element entries inside it. The core identifier of Sitemap validity—Sitemaps missing a correct urlset structure will be directly rejected for parsing by search engines.
Sitemap Index: A sitemap index file that must be used when a website's URL count exceeds 50,000 entries or a single Sitemap file exceeds 50MB. The root element is <sitemapindex>, used to uniformly list and manage multiple sub-Sitemap file addresses, and is the standard solution for splitting Sitemaps on large websites.
changefreq: An optional metadata element in Sitemap used to specify the approximate update frequency of page content. Has seven valid values: always, hourly, daily, weekly, monthly, yearly, and never. Provided as a reference for search engine crawlers to schedule revisit crawl frequency; proper setting can optimize crawl budget allocation.
priority: An optional metadata element in Sitemap used to specify the importance priority of a URL relative to other pages within the website. Takes a decimal value between 0.0 and 1.0 with a default of 0.5. priority only affects relative crawl priority among pages within a site and does not affect search result rankings.
lastmod: An optional metadata element in Sitemap that records the date and time of the last substantive content modification of a page. The format must follow the W3C Datetime specification. It is the most important of the three optional metadata fields for search engines because it directly indicates whether a page has new content requiring recrawling.
loc: A required child element under <url> elements used to specify the complete absolute URL address of a page. Must start with http:// or https:// protocol, include the complete domain name, total URL length cannot exceed 2,048 characters, and relative paths are not allowed.
XML Namespace (xmlns): An XML namespace attribute that must be declared on the urlset root element. The attribute value must exactly match http://www.sitemaps.org/schemas/sitemap/0.9 to identify the protocol version used by the Sitemap. Missing or incorrectly written namespaces will cause Sitemap parsing failure.
W3C Datetime: Date and time representation format specified by W3C (World Wide Web Consortium). The lastmod field in Sitemaps must follow this format. The YYYY-MM-DD simplified date format is commonly used (best compatibility), and the full datetime format including hours, minutes, seconds, and timezone information is also supported.
XML Entity Escaping: In XML syntax, special characters must be escaped to corresponding entity references for correct parsing: & escapes to &, < escapes to <, > escapes to >, " escapes to ", ' escapes to '. URLs containing these characters must be escaped, otherwise XML parsing errors will result.
Google Search Console (GSC): Google's official webmaster platform tool used for submitting Sitemaps, viewing website indexing status, search traffic data analysis, crawl error reports, security issue notifications, manual action penalty notifications, etc. An essential tool for Google search engine optimization (SEO).
Bing Webmaster Tools: Microsoft Bing search engine's official webmaster platform with functionality similar to Google Search Console. Supports Sitemap submission, index coverage statistics, SEO diagnostic analysis, keyword research, backlink queries, etc., covering search traffic from both Bing and Yahoo search engines.
robots.txt: A plain text file placed in a website's root directory that uses directives such as User-agent, Disallow, and Allow to tell search engine crawlers which paths are allowed to be crawled and which paths are forbidden. It can also declare Sitemap file locations in the file for automatic discovery by crawlers.
Crawler (Spider/Bot): Automated programs developed by search engines to fetch web content, such as Googlebot (Google crawler), Bingbot (Bing crawler), and Baiduspider (Baidu crawler). They discover new pages by following page links and reading Sitemap files, downloading page content and storing it in search engine index databases.
Crawl Budget: The total crawl resource amount allocated by search engines to a website within a certain time period, determined by multiple factors including domain authority, server response speed, page content quality, and historical crawl effectiveness. Correct Sitemap configuration can help optimize crawl budget utilization efficiency.
UTF-8 Encoding: The character encoding mandated for Sitemap XML files. UTF-8 supports all Unicode characters including Chinese, specified in the XML declaration through the encoding="UTF-8" attribute. Using other encodings (such as GBK or GB2312) may cause garbled Chinese URLs and parsing failures.
gzip Compression: The Sitemap protocol supports compression transfer using the gzip algorithm (file extension .xml.gz), which can reduce Sitemap file size by 70%-80%, significantly saving server bandwidth and crawler fetch time. Major search engines can automatically decompress and process gzip-compressed Sitemap files; compressed files must still comply with the 50MB size limit.
Yoast SEO: A widely used SEO plugin on CMS platforms such as WordPress and Shopify that can automatically generate Sitemaps, meta tags, breadcrumb navigation, XML sitemaps, RSS optimization, social media metadata, and other SEO-related functions. A commonly used SEO solution for content-focused websites.
Index Coverage: One of the core reports in Google Search Console, showing detailed numbers and reasons for pages indexed, excluded, with errors, and with warnings on a website. Can be used to verify Sitemap submission effectiveness and diagnose page indexing issues.
URL Encoding (Percent-Encoding): Also called percent-encoding, an encoding method used to represent non-ASCII characters (such as Chinese and special symbols) in URLs. Chinese characters are encoded in %XX%XX%XX form (e.g., "中文" encodes to %E4%B8%AD%E6%96%87). Chinese URLs in Sitemaps must be correctly encoded to be parsed.

changefreq Update Frequency Scenario Reference Table

changefreq Value	Update Frequency	Typical Applicable Page Types	Notes
`always`	May change on every visit	Real-time data pages, search entry points, dynamic aggregation pages	Does not mean crawlers visit every time, only indicates extremely high change frequency; do not overuse—regular pages should not be set to always
`hourly`	Updates hourly	News homepages, social media feeds, real-time quote pages	Suitable for pages with hourly new content output; non-high-frequency sites should not set to hourly
`daily`	Updates daily	Website homepage, blog list pages, news channel pages, product category pages	One of the most commonly used values; suitable for most site homepages and section pages
`weekly`	Updates weekly	Regular article detail pages, product detail pages, blog post pages	Appropriate for content pages on most content-focused websites
`monthly`	Updates monthly	Category directory pages, archive pages, FAQ pages, user guide pages	Auxiliary pages with infrequent content updates but occasional adjustments
`yearly`	Updates yearly	Company introduction pages, contact pages, terms of service, privacy policy	Static information pages that almost never change
`never`	Never updates	Historical article archives, expired event pages, archived old content	Set pages confirmed to no longer be modified to never; remember to change back promptly if updates occur

priority Setting Reference Table

priority Value	Priority Tier	Applicable Page Types	Recommended Page Count Ratio
`1.0`	Highest	Website homepage, core landing pages, most important channel entry points	Only 1-3 pages across entire site
`0.8-0.9`	Very High	Main section pages, popular category pages, core product pages, key special topics	Approximately 5-10% of total pages
`0.6-0.7`	High	Secondary section pages, subcategory pages, popular articles, important product details	Approximately 10-20% of total pages
`0.4-0.5`	Normal	Regular article detail pages, general product pages, standard content pages	Approximately 40-60% of total pages (default value)
`0.2-0.3`	Low	Tag pages, archive pagination, old article archives, auxiliary pages	Approximately 15-25% of total pages
`0.0-0.1`	Lowest	Low-value pages, duplicate content pages, pages not prioritized for crawling	Within approximately 5% of total pages; 0 does not mean noindex

Sitemap Protocol Specification Limits Table

Limit Item	Upper Limit	Description	Overage Handling Solution
URLs per single Sitemap	50,000 entries	Hard requirement of sitemap.org 0.9 protocol	Use Sitemap Index to split into multiple sub-Sitemaps
Uncompressed single Sitemap file size	50MB (52,428,800 bytes)	Raw file size including all tags and whitespace	Use gzip compression, split Sitemaps, minimize comments
Sub-Sitemaps per Sitemap Index	50,000 entries	URL entry limit for the index file itself	Theoretically supports 2.5 billion URLs; unnecessary for most sites
Single URL length	2,048 characters	Including protocol, domain, path, and all query parameters	Overly long URLs require parameter simplification or URL rewriting
Sitemap-supported encoding	UTF-8	Mandated by protocol; other encodings may cause parsing failure	Ensure files are saved using UTF-8 encoding
Sitemap-supported protocols	http:// or https://	URLs must include complete protocol prefix	ftp:// and other protocols are not supported
Crawler response time after submission	Hours to days	Depends on site authority and Sitemap complexity	No need to resubmit; wait patiently for processing
gzip compressed file size	50MB	Compressed files also must not exceed the 50MB limit	Compression overage still requires Sitemap splitting