Skip to content
search-engine-optimizedby Netsolution
  1. Home
  2. Files and configuration
  3. XML Sitemap Generator

XML Sitemap Generator

Produce a valid XML sitemap, putting in it only the pages that deserve to be there.

A real crawl of the site following its links, respecting your robots.txt. The file produced follows the sitemaps.org 0.9 protocol. No usage limit.

What this tool is for

A sitemap is the list of pages you want indexed. It does not replace navigation: Google discovers most of the web by following links. It complements, by flagging what crawling might miss.

Its usefulness is therefore proportional to how hard discovery is. On a ten-page site with good internal links, it serves almost nothing. On a site of several thousand pages, or a new site with no inbound links, it becomes a real discovery channel.

Its second use, often the most valuable, is diagnostic. By submitting it to Search Console you get the report of pages discovered, indexed and set aside — and above all the reasons for exclusion. That is where you find out why half a site does not appear.

What is deliberately not added: the priority and changefreq tags. Google has confirmed it ignores them entirely. Generating them gives the illusion of steering something you do not steer.

How to read the results

The list of URLs kept is the heart of the file. Each has to return a 200 and be indexable. One rule: put in only what you want to see in the results.

The exclusions reported are often more instructive than the list itself. Discovering that forty pages were set aside for a noindex sometimes reveals an unintended configuration, which the meta tags analyzer will confirm.

The lastmod tag is the only one Google takes into account, provided it is sincere. A last-modified date artificially refreshed on every generation makes the signal lose all credibility.

The total number of URLs has to stay under 50,000 per file. Beyond that, split and link with a sitemap index.

The gap with the number of pages you believe you have is the most useful signal. A site announced at 300 pages where the crawl finds only 80 has an internal linking problem.

Common mistakes

Including noindexed pages. You are asking Google to index a page that asks it not to. That contradiction degrades the trust given to the whole file.

Including redirected or erroring URLs. Same problem. A sitemap riddled with 301s and 404s wastes crawl time and discredits the whole thing.

Generating once and forgetting. That is the most widespread failing. A sitemap frozen for years no longer describes the site and signals a lack of maintenance.

Believing a sitemap forces indexing. It proposes, Google disposes. A page with no internal link and no interest will stay unindexed despite being in the file.

Forgetting to declare it. A sitemap placed at the root but absent from robots.txt and never submitted to Search Console will only be found by chance. The robots.txt generator adds the necessary line.

Going further

Frequently asked questions

Does a sitemap improve ranking?

No, it has no effect on positions. It helps discovery: it tells Google which pages exist, which matters mainly for large sites, recent ones, or ones with poorly linked pages. A page listed in a sitemap but with no internal link will stay weak regardless.

What are the priority and changefreq tags worth?

Nothing. Google has confirmed it ignores them entirely, precisely because everybody declared their pages at maximum priority and daily updates. Only the lastmod tag is taken into account, and only if it is honest — a false date gets it ignored too.

What is the maximum size of a sitemap?

50,000 URLs or 50 MB uncompressed, whichever limit is reached first. Beyond that you need several files linked by a sitemap index. Gzip compression is accepted and recommended on large files.

Should every page be included?

No, only the ones you want indexed. Never put in a noindexed page, a redirected page, or a page returning an error: those are contradictory signals that degrade the trust given to the whole file.

Where do I declare the sitemap?

Two places, and do both. A Sitemap line in your robots.txt, which every engine reads. And a submission in Search Console, which additionally gives you a detailed report of pages discovered, indexed and set aside.

How often should I regenerate it?

On every publication or significant change, ideally automatically. A frozen sitemap loses its point: that is the most widespread failing. A file that has not moved for years mostly signals a site nobody maintains.