NEWWorld's first AI visibility audit tool for Web3 is live.Run free audit →
Free tool · Crypto-aware path detection · Hreflang support

XML sitemap generator for crypto projects. Smart priority weighting in 90 seconds.

Paste your URLs, get a valid sitemap.xml with crypto-aware priority defaults. The generator detects /token, /docs, /audit, /tokenomics, /governance, /staking, /bridge and /whitepaper routes and weights them appropriately so search engines and AI engines know which pages matter most. Hreflang support for multi-language projects. Built to pair with the Web3 Robots.txt Checker.

Free · No signup · 8 crypto route patterns auto-detected

// The generator

Paste URLs. Get sitemap.xml.

Smart defaults for token, docs, audit, governance, staking, bridge, whitepaper paths. Override any URL.

// Step 1: get your URLs Auto-fetch from your live sitemap, or paste manually

We try /sitemap.xml first, then check /robots.txt for a declared sitemap. If your site blocks cross-origin access or has no public sitemap, paste URLs below instead.

or paste manually

// Step 3: sitemap.xml output

Paste URLs and click "Parse and generate" to see your sitemap.xml here.

Upload to: https://yourdomain.com/sitemap.xml

Then add Sitemap: https://yourdomain.com/sitemap.xml to your robots.txt. Submit the URL to Google Search Console for fastest indexing.

Want the full picture?

Run a free Crawlux audit of your live domain

You generated the sitemap. Crawlux is our free audit tool — it scans your full domain and gives you a complete report on whether search engines and AI engines can actually crawl every URL effectively. Covers technical SEO, AI visibility, token schema, content quality and 4 more areas. Takes about 4 minutes. No signup, no credit card.

200+ Web3 brands audited · No credit card · No setup

// How it works

Three steps. About 90 seconds end to end.

No signup. No data leaves your browser. Pure client-side XML generation.

01

Paste your URLs

One URL per line. The generator parses each one and auto-detects crypto-specific paths: /token, /docs, /audit, /tokenomics, /governance, /staking, /bridge, /whitepaper. Each path pattern gets a smart priority and changefreq default.

02

Review and adjust per URL

See each URL with its detected type, priority, and changefreq. Click any value to override. For multi-language projects, add hreflang variants. The output updates live as you edit.

03

Copy or download sitemap.xml

Output is valid sitemap.xml at the schema.org standard with proper namespaces. Copy to clipboard or download as a .xml file. Upload to the root of your domain and submit to Google Search Console for fastest indexing.

// Why crypto-aware matters

Generic sitemap generators treat every URL the same. Crypto sites should not.

Six things this generator does that generic sitemap tools miss.

Token landing page priority 1.0

The token landing page is the highest-conversion page on most crypto sites. Generic generators treat it as 0.5. The Crawlux generator weights it at 1.0, telling search engines and AI engines this is the most important page on your domain.

Audit page priority 0.9

Audit pages are critical trust signals. AI engines specifically look for "audited by" content when answering trust queries about crypto projects. Generic generators leave audit pages at 0.5; this generator weights them at 0.9 so they get prioritized for crawl and re-indexing.

Docs route weighted by depth

Docs landing page at 0.8, docs sub-pages at 0.7. Generic generators apply a flat priority to docs which often means the entry page gets buried below blog posts. This generator surfaces the docs entry to search engines and weights internal docs appropriately.

Whitepaper changefreq monthly

Whitepaper pages do not change often, so generic generators set them to "weekly" or "daily" which wastes crawl budget. This generator sets changefreq to "monthly" or "yearly" for whitepaper paths, freeing crawl budget for pages that actually change.

Hreflang for global crypto audiences

Crypto projects targeting Asian markets benefit massively from hreflang. The generator supports adding language alternates per URL so example.com/en/token, example.com/zh/token and example.com/ja/token are correctly identified as translations of the same page.

Sitemap-index for large projects

Projects with 1000+ pages need sitemap-index files. Generic generators sometimes hit the 50,000 URL limit per file silently. This generator detects when to split into multiple sitemaps (sitemap-blog.xml, sitemap-docs.xml, sitemap-tokens.xml) and outputs a sitemap-index.xml to tie them together.

// Common questions

Common questions about XML sitemaps for crypto

Patterns from crypto SEO audits and TG3 onboarding sessions.

Why does a crypto project need a special XML sitemap?

Generic sitemap generators do not weight token landing pages, audit pages, tokenomics pages or whitepaper pages any differently from a regular blog post. For a crypto project, the token page is the highest-conversion page on the site and should have priority 1.0. The audit page and tokenomics page are critical trust signals and should be priority 0.8 to 0.9. Generic generators treat them all as 0.5. The Crawlux generator applies crypto-aware priority defaults so the most important pages are signalled correctly to search engines and AI engines.

Where do I upload the sitemap.xml file?

Upload to the root of your domain so it is accessible at yourdomain.com/sitemap.xml. Same location pattern as robots.txt. Then add the line Sitemap: https://yourdomain.com/sitemap.xml to your robots.txt file. Submit the sitemap URL in Google Search Console and Bing Webmaster Tools for faster discovery.

What is the difference between sitemap.xml and sitemap-index.xml?

A regular sitemap.xml lists URLs directly (up to 50,000 URLs and 50MB per file). A sitemap-index.xml is a file that lists multiple sitemap.xml files. Use sitemap-index for large crypto projects with separate sitemaps per content type (e.g. sitemap-blog.xml, sitemap-docs.xml, sitemap-tokens.xml). The generator outputs whichever format is needed based on URL count.

How does priority weighting affect crypto SEO?

Priority is a hint to search engines about which pages matter most on your site. It is relative within the sitemap, not absolute. The token landing page at 1.0 tells Google to prioritize crawling and re-indexing that page over the about page at 0.4. For AI engines that read sitemaps (Perplexity, Gemini), priority also helps them surface your most important pages in answers.

Should I add hreflang for crypto projects?

Yes, if you have localized versions of your site. Hreflang tells search engines that example.com/en/token, example.com/zh/token and example.com/ja/token are translations of the same page. Crypto projects targeting global audiences (especially Asia) benefit significantly from hreflang. The generator supports adding language alternates per URL.

How often should I regenerate my sitemap?

On every meaningful content change. New blog posts, new docs pages, new audit reports, new tokenomics page. If you are running a static site, regenerate as part of your build pipeline. For WordPress and CMS sites, plugins handle this automatically. The lastmod date in the sitemap is critical: Google uses it to decide when to recrawl.

Does the sitemap help AI engines cite my project?

Indirectly. AI engines (Perplexity, Gemini especially) crawl your site to build their citation index. A clean sitemap with accurate lastmod dates and proper priorities makes their crawl faster and more accurate. Combined with the llms.txt file and FAQPage schema, the sitemap is part of the AI-readable infrastructure. The Crawlux AI Visibility audit module measures end-to-end whether all of these signals are working together.

What URLs should I exclude from the sitemap?

Login pages, admin pages, internal tools, search result pages, paginated archive pages, parameter URLs (e.g. ?utm_source=). Anything that is not a unique indexable content page. The generator does not automatically exclude these; you control the URL list. For a clean sitemap, paste only the URLs you actually want search engines to index.

// The hard math

Sitemap priority signals matter more for crypto than founders realize

Most crypto SEO conversations skip sitemaps entirely. Founders treat them as a "yeah we have one" checkbox item from 2014. The sitemap.xml file gets generated by a WordPress plugin once, never reviewed, and quietly broken when somebody moves pages around. Then everybody wonders why the audit page is not ranking for "audit yourname".

This is dumb. The sitemap is the single most direct way to tell Google, Bing, Perplexity and Gemini which pages on your site matter most. Skipping that signal because "Google figures it out anyway" leaves citation rate on the table.

What priority actually does

Priority is a relative hint within your own sitemap. Google does not compare your priority 1.0 to another site's priority 1.0. It compares your priority 1.0 to your priority 0.5. The implication: your token landing page at 1.0 tells Google "this is the page on yourcrypto.io that we care about most". Google then allocates more crawl budget to that page and re-indexes it more aggressively.

For crypto sites, the priority math should look approximately like this: token landing 1.0, tokenomics page 0.9, audit page 0.9, docs entry 0.8, about page 0.4, blog posts 0.6, legal pages 0.3. Generic generators apply 0.5 to everything. The crypto-aware generator weights it correctly.

What changefreq does

Changefreq tells search engines how often a page updates. Whitepaper "yearly". Tokenomics "monthly". Docs "weekly". Blog "monthly". Token landing "weekly". Setting changefreq incorrectly wastes crawl budget on pages that never change and starves pages that do.

How lastmod actually drives recrawl

The lastmod date is the most important field in the entire sitemap for crawl prioritization. Google uses it to decide whether to recrawl a page. If lastmod is fresh, Google re-fetches. If lastmod is months old, Google deprioritizes. The generator pulls lastmod from the current date by default; for serious sites this should be updated when content actually changes.

Where this fits in the SEO stack

The sitemap is the routing layer. The robots.txt controls which crawlers get in. The llms.txt tells AI engines what your site is about. The FAQPage schema handles question-answer structured content. The Crypto Schema Generator handles JSON-LD for tokens and organizations. Each tool is narrow. Use them together.

The audit overlay

This tool generates the sitemap. The Crawlux audit checks whether search engines and AI engines can actually crawl every URL effectively once that sitemap is live, plus 7 other Web3-tuned audit areas. Takes about 4 minutes.

What is next

Generated the sitemap. Now audit your live domain with Crawlux.

Sitemap shipped. Crawlux is our free audit tool — it scans your full domain and gives you a complete report on whether crawlers can actually reach every URL effectively, plus 7 other audit areas. Takes about 4 minutes. No signup, no credit card.

200+ Web3 brands audited Free tier forever ~4 minute audit 8 crypto-tuned modules