How to convert a json url list to an xml sitemap
- Step 1Format the JSON as a URL array — Each element needs a loc key (absolute HTTPS URL). Optional keys: lastmod (ISO date), changefreq (always/hourly/daily/weekly/monthly/yearly/never), priority (0.0–1.0).
- Step 2Paste or upload the JSON — Drop the file or paste the array. The tool validates URL format and flags any relative paths or malformed entries with a line reference before generating the XML output.
- Step 3Download the sitemap.xml — Click Download to save sitemap.xml. The tool warns if the URL count exceeds 50,000 — Google's per-sitemap limit — so you can split into a sitemap index before submitting.
- Step 4Upload and submit to Search Console — Place sitemap.xml at your site root (https://example.com/sitemap.xml). Then go to Google Search Console →’ Sitemaps and submit the full URL so Google starts crawling the listed pages.
Frequently asked questions
Does Google use the changefreq and priority fields?+
Google officially ignores both changefreq and priority and uses its own crawl scheduling based on PageRank and content freshness signals. Including them does no harm and Bing still reads changefreq, but do not expect them to influence Google's crawl rate.
My site has 80,000 URLs. How do I handle the 50,000 URL limit?+
Split the JSON array into multiple files of 50,000 URLs or fewer, convert each to a separate sitemap.xml, then create a sitemap index file that references all the individual sitemaps. The tool shows a snippet of the index XML in the warning when the count exceeds the limit.
Are the URLs sent to JAD Apps servers?+
No. The entire conversion runs locally in your browser. The URL list — including any private staging or pre-launch URLs — never leaves your machine until you choose to upload the generated sitemap.xml to your server.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.