A sitemap is the shortest message you can send a search engine: here are the pages on my site that matter. The PageForge free XML sitemap generator builds that message from a real crawl of your website. Enter a domain, and the tool reads your robots.txt, checks any sitemap you already have, follows internal links, and returns a clean sitemap.xml that lists only indexable, canonical pages that return a 200 status.

That last part is where most free sitemap generators fall short. They collect every URL they can find, including redirects, 404s, filtered URLs and pages you deliberately marked noindex, then hand you a file that sends mixed signals to Google. This tool checks each page before it goes in, shows you exactly what it left out and why, and scores the health of your sitemap setup so you know what to fix next.

No signup. No email gate. Download the XML, a gzip version, a plain URL list or a full CSV audit in one click.

What Is an XML Sitemap?

An XML sitemap is a structured file, usually found at yourdomain.com/sitemap.xml, that lists the URLs you want search engines to crawl and index. Each entry contains the page address and can include extra details such as the date the page last changed. The format follows the Sitemaps protocol, an open standard supported by Google, Bing, Yandex and other search engines.

Here is what a small, valid sitemap looks like:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-09-10</lastmod>
  </url>
  <url>
    <loc>https://example.com/services/seo-audit/</loc>
    <lastmod>2026-08-28</lastmod>
  </url>
</urlset>

Every sitemap opens with an XML declaration, wraps its entries in a urlset element that declares the protocol namespace, and places each page inside its own url element. The only required child is loc, which must hold the full, absolute URL including the protocol.

Think of a sitemap as a map, not a set of instructions. It tells search engines which pages exist and which ones you consider important. It does not force Google to index anything, and it does not override robots.txt rules, noindex tags or canonical signals. That is exactly why the URLs inside it need to agree with every other signal on your site.

Why XML Sitemaps Still Matter in 2026

Search engines discover most pages by following links. If a page is well linked from your navigation and content, Googlebot will usually find it without help. So why bother with a sitemap at all?

Because real websites are rarely that tidy. New pages go live before anyone links to them. Old posts get buried five clicks deep in pagination. Product variations, location pages and programmatic landing pages multiply faster than your internal linking can keep up. A sitemap closes those gaps.

Google’s own sitemap documentation says a sitemap is most useful when a site is large, when it is new and has few external links pointing to it, or when it has lots of rich media or news content. Google also notes that a small site of roughly 500 pages or fewer, with thorough internal linking, may not strictly need one. In practice, almost every business site benefits, because the cost of creating a sitemap is close to zero and the downside of pages going undiscovered is lost traffic.

Sitemaps also do quieter work:

• Faster discovery of new and updated pages. A sitemap with accurate lastmod dates helps crawlers prioritise what changed instead of recrawling everything.
• A canonical hint. Google treats URLs listed in a sitemap as a weak signal about which version of a page you prefer, which helps when duplicate or near-duplicate URLs exist.
• Indexing diagnostics. Once you submit a sitemap in Search Console, you can filter the Page indexing report by that sitemap and see exactly which of your chosen pages are indexed and which are not.
• Better coverage for AI-driven search. Answer engines and AI crawlers still depend on well-structured, crawlable sites. A clean sitemap supports the same discoverability that powers traditional rankings. If AI visibility is a priority, pair it with a proper llms.txt file and check your site with the AI Search Readiness Checker.

What Makes This Sitemap Generator Different

Plenty of tools will spit out a list of URLs. This one is built to give you a sitemap you can submit with confidence, plus the context to improve it.

It checks your existing setup first

Before crawling anything, the generator fetches your robots.txt file. It reads your crawl rules and any Sitemap lines, then opens every sitemap you have declared, including sitemap index files and gzipped sitemaps. If you have not declared one, it checks the common locations used by WordPress core, Yoast SEO, Rank Math and most other platforms.

It verifies every URL before including it

Each candidate page is requested and inspected. A URL only makes it into your sitemap when it:

• returns an HTTP 200 status code without redirecting
• serves an HTML page (or a PDF, if you enable PDFs)
• is not blocked by robots.txt
• does not carry a noindex directive in a meta robots tag or X-Robots-Tag header
• points to itself as the canonical URL
• passes your include and exclude keyword rules

It explains every exclusion

Leaving URLs out is only useful if you can see why. The Excluded tab groups every rejected URL by reason, such as redirect, HTTP error, noindex, non-canonical or blocked by robots.txt, and flags which of them are sitting in your current sitemap right now. Those flagged URLs are often the fastest technical SEO wins on a site.

It compares your live site with your current sitemap

In Smart mode, the tool knows which URLs came from your existing sitemap and which it found by following links. That lets it surface two problems that are otherwise hard to spot: indexable pages linked on your site but missing from your sitemap, and sitemap URLs that no internal link reaches, which are likely orphan pages.

It gives you more than one file

You can copy the XML, download sitemap.xml, download a compressed sitemap.xml.gz, export a plain-text URL list, or grab a CSV audit with every included and excluded URL, its depth, discovery source, last-modified date, page title and exclusion reason.

How to Use the Free XML Sitemap Generator

Creating a sitemap takes less than a minute for most sites. Larger sites take a little longer because every page is checked.

Step 1: Enter your website URL

Type your homepage address, such as https://example.com. You can skip the https:// and the tool will add it. If your site redirects from HTTP to HTTPS or from non-www to www, the generator follows that redirect and uses the final version as the canonical origin for every URL.

Step 2: Choose a discovery method

• Smart (recommended): reads existing sitemaps and crawls internal links. Best for finding gaps between what your sitemap says and what your site actually links to.
• Live crawl only: ignores any existing sitemap and discovers pages purely through links, the same way a search engine would on a site with no sitemap.
• Verify existing sitemaps only: checks every URL in your current sitemap without crawling further. Use this to clean up a bloated plugin-generated sitemap.

Step 3: Set limits and output format

Pick the maximum number of URLs (up to 1,000 per run on the free tool). Choose how lastmod dates should appear, and decide whether to add changefreq or priority tags. Our recommendation is to keep lastmod and skip the other two, for reasons explained in the tag reference below.

Step 4: Add include or exclude rules

Exclude rules stop the crawler from visiting matching URLs at all. The defaults already skip cart, checkout, account, login, tag and author archives, and internal search results. Include rules work differently: the crawler still follows every page to discover links, but only URLs containing your keywords end up in the final file. That is handy when you want a sitemap for one section, such as blog or locations.

Step 5: Pick your crawl options

Leave robots.txt, noindex, canonical and query-parameter filtering switched on unless you have a specific reason not to. Turn on image sitemap tags if image search matters to you, and enable PDFs if you publish documents you want indexed. The folder scope option keeps the crawl inside the path you entered, so https://example.com/blog/ only returns blog URLs.

Step 6: Generate and review

Press Generate sitemap. A progress panel shows each stage live, and you can stop at any time to use the pages checked so far. When the crawl finishes, review the health score, insights, XML preview, included URLs and exclusions before you download anything.

Step 7: Download, upload and submit

Download sitemap.xml, upload it to the root folder of your site, add the Sitemap line from the robots.txt tab to your robots.txt file, and submit the sitemap URL in Google Search Console and Bing Webmaster Tools.

How to Read Your Sitemap Results

The results panel is designed to answer three questions quickly: is the file ready, what is wrong with my current setup, and what should I fix first?

The four headline numbers

• URLs in your sitemap: pages that passed every check and appear in the XML.
• Pages checked: how many URLs the crawler actually requested. This is usually higher than the sitemap count because redirects, errors and noindex pages are checked too.
• URLs excluded: everything discovered but deliberately left out.
• Existing sitemaps read: the number of sitemap and sitemap index files found on your site.

The sitemap health score

The score starts at 100 and loses points for issues that weaken how search engines use your sitemap. The biggest deductions come from URLs in your current sitemap that redirect, return errors, carry noindex or point to a different canonical. Smaller deductions apply when no sitemap exists, when robots.txt does not reference one, when few pages expose a last-modified date, and when linked pages are missing from the sitemap. A score of 85 or higher is healthy. Between 65 and 84 needs attention. Below 65 usually means your sitemap is sending conflicting signals.

Exclusion reasons explained

Reason	What it means	What to do
Redirect	The URL returns a 301, 302, 307 or 308 and sends visitors elsewhere.	List the final destination instead. Update internal links that still point to the old address.
HTTP error	The URL returns a 4xx or 5xx status, such as 404 or 500.	Restore the page, redirect it to a relevant replacement, or remove links to it.
noindex	A meta robots tag or X-Robots-Tag header tells search engines not to index the page.	If you want the page in search, remove the noindex. If not, keep it out of the sitemap.
Non-canonical	The page’s canonical tag points to a different URL.	Keep the canonical version in the sitemap. Check the tag is intentional.
Blocked by robots.txt	A Disallow rule prevents crawling.	Remove the rule if the page should rank. A blocked URL in a sitemap is a common Search Console warning.
Query parameters	The URL contains a query string, often from filters, sorting or tracking.	Usually correct to exclude. Switch the option off if parameter URLs are real, unique pages.
Exclude or include rule	The URL matched your exclude keywords or did not match your include keywords.	Adjust your rules if something important was filtered.
Not an HTML page	The response was a feed, image, JSON file or other non-page content.	No action needed in most cases.
Fetch failed	The request timed out or the connection was refused.	Check server performance, firewall rules and bot protection.

XML Sitemap Tags Explained

The Sitemaps protocol defines four tags inside each url entry. Only one is required, and search engines treat the others very differently than many older SEO guides suggest.

Tag	Required	How search engines use it	Our recommendation
loc	Yes	The full canonical URL of the page. It must be absolute and properly escaped.	Always included.
lastmod	No	When the page content meaningfully changed. Google uses it when it is consistently and verifiably accurate.	Include it, but only with honest dates.
changefreq	No	A hint about how often a page changes. Google ignores it.	Leave it out unless another search engine you target relies on it.
priority	No	Relative importance from 0.0 to 1.0. Google ignores it.	Leave it out. Use internal linking to signal importance instead.

Google confirmed its position on these tags in a 2023 Search Central blog post, which also announced the retirement of the old sitemap ping endpoint. The key takeaway is that lastmod is valuable only when you do not fake it. Setting every page to today’s date every time the sitemap regenerates teaches Google to ignore the field entirely.

The generator pulls lastmod from the most reliable source available for each page: the article:modified_time or og:updated_time meta tags, a dateModified value in structured data, the lastmod listed in your existing sitemap, or the Last-Modified HTTP header. It ignores headers that simply report the current time, which many dynamic sites send on every request.

Image sitemap extensions

If you enable image tags, each page entry can include image:image elements holding the address of images found on that page. Google still supports the image:loc tag, while the older caption, title, geo location and license tags were deprecated. The image sitemap documentation covers the current format. Image entries are most useful when images load through JavaScript or lazy loading that crawlers might miss.

XML Sitemap Rules and Limits

A sitemap that breaks the protocol rules can be partially or completely ignored. Keep these requirements in mind, especially if you edit the file by hand.

• Size limits: a single sitemap can hold up to 50,000 URLs and must be no larger than 50MB uncompressed. Larger sites split URLs across multiple files and list them in a sitemap index.
• Sitemap index files: an index can reference up to 50,000 child sitemaps. You submit the index once and search engines discover the rest.
• UTF-8 encoding: the file must use UTF-8, and special characters such as ampersands inside URLs must be escaped as entities.
• Absolute URLs: every loc value needs the full address with protocol and host. Relative paths are invalid.
• Consistent host and protocol: URLs should match the version of your site you want indexed. Mixing http and https, or www and non-www, creates avoidable duplication.
• Location matters: a sitemap generally covers URLs in its own directory and below. A file at example.com/blog/sitemap.xml should not list pages outside /blog/ unless you declare it in robots.txt or submit it through a verified Search Console property.
• Compression is allowed: you can serve a gzip-compressed sitemap.xml.gz to save bandwidth. Size limits apply to the uncompressed file.

For the full technical rules, read Google’s guide to building and submitting a sitemap.

What to Include in an XML Sitemap and What to Leave Out

The golden rule is simple: a sitemap should list the URLs you want to appear in search results, and nothing else.

Include

• Your homepage and core commercial pages, such as services, products, pricing and features
• Blog posts, guides and resources that you want to rank
• Category pages that carry unique, useful content
• Location and service area pages, including programmatically generated pages that meet your quality bar
• Important landing pages, even if they are not in your main navigation
• PDFs and other documents that you intend to be indexed

Leave out

• Redirected URLs and pages returning 404, 410 or server errors
• Pages tagged noindex, including thank-you pages, internal search results and gated content
• Duplicate URLs that canonicalise to another page
• Faceted navigation, sorting and filter URLs with query parameters
• Cart, checkout, login and account pages
• Thin tag and author archives that you do not want competing with real content
• Staging, test or development URLs

When a sitemap contains only clean, canonical, indexable pages, it becomes a trustworthy signal. When it is full of junk, search engines learn to rely on it less. If you need to double-check page-level issues after generating your file, run a free SEO audit on the URLs that matter most.

How to Add an XML Sitemap to WordPress

WordPress sites have more options than most, which also means more ways to end up with duplicate or conflicting sitemaps.

Option 1: Use the WordPress core sitemap

Since version 5.5, WordPress generates a basic sitemap automatically at /wp-sitemap.xml. It covers posts, pages, public custom post types, taxonomies and author archives, and splits them into files of up to 2,000 URLs each. The feature was introduced in the WordPress 5.5 core announcement. It works, but it offers little control and does not add lastmod dates for every content type.

Option 2: Use your SEO plugin

Yoast SEO and Rank Math both replace the core sitemap with their own, typically at /sitemap_index.xml. These sitemaps respect the noindex settings you choose inside the plugin, add lastmod dates, and update automatically when you publish. For most WordPress sites this is the best long-term setup. PageForge works alongside both plugins, so generated pages are picked up in the same sitemap as the rest of your content.

Option 3: Upload a static sitemap file

Upload the sitemap.xml file from this tool to your site root through your hosting file manager, SFTP or a file manager plugin. A static file is ideal for non-WordPress sites, landing page builders and one-off audits. The trade-off is that it does not update itself, so you need to regenerate and re-upload it when you publish or remove pages.

Avoid sitemap conflicts

A physical sitemap.xml file in your root folder will usually be served instead of a dynamic one at the same address. If you use an SEO plugin, do not upload a static file with the same name. Pick one source of truth, make sure only that sitemap is referenced in robots.txt, and submit only that one in Search Console.

Use the generator as an audit tool even when a plugin manages your sitemap. Run it in Verify mode against /sitemap_index.xml, and you will instantly see whether your plugin is listing redirects, noindexed pages or non-canonical URLs that need attention.

How to Reference Your Sitemap in robots.txt

Adding your sitemap to robots.txt lets every crawler that reads the file find it, including search engines where you do not have a webmaster account. Open the robots.txt file in your site root and add a line like this anywhere in the file:

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://example.com/sitemap.xml

The Sitemap directive must use a full, absolute URL. You can add more than one Sitemap line, and the directive is independent of user-agent groups, so its position in the file does not matter. On WordPress, Yoast SEO and Rank Math let you edit robots.txt from the dashboard, and WordPress core adds its own sitemap line to the virtual robots.txt when no physical file exists.

Be careful not to block the pages you list. A URL that is both in your sitemap and disallowed in robots.txt is a contradiction search engines will flag. Google’s robots.txt introduction is a good refresher on how crawl rules work, and it explains why robots.txt is not a tool for keeping pages out of search results.

How to Submit Your Sitemap to Google and Bing

Submit to Google Search Console

1. Open your sitemap URL in a browser and confirm it loads without errors.
2. Sign in to Google Search Console and select the property for your domain.
3. Go to Indexing, then Sitemaps.
4. Enter the sitemap path, for example sitemap.xml, and select Submit.
5. Check the status column. Success means Google fetched and parsed the file.

You only need to submit once. Google recrawls known sitemaps on its own schedule. The old practice of pinging Google with a URL every time your sitemap changed no longer works, because that endpoint was retired. Google’s Sitemaps report help article explains each status and error message you might see.

After submission, open the Page indexing report and filter by your sitemap. That view shows how many of your chosen URLs are indexed and lists the reasons others are not, such as Crawled but currently not indexed or Duplicate without user-selected canonical.

Submit to Bing Webmaster Tools

Bing also accepts sitemaps through the Sitemaps section of Bing Webmaster Tools, and you can import verified sites directly from Google Search Console to save time. Bing supports the IndexNow protocol as well, which lets your site notify participating search engines the moment a URL is added, updated or deleted. IndexNow complements a sitemap rather than replacing it.

Common XML Sitemap Errors and How to Fix Them

Error or warning	Likely cause	Fix
Couldn’t fetch	The sitemap URL returns an error, is blocked, or the server timed out.	Open the URL in a browser, check robots.txt and firewall rules, and resubmit.
Sitemap could not be read	Invalid XML, wrong encoding, or HTML served instead of XML.	Validate the file, ensure UTF-8 encoding and escape special characters.
Submitted URL has noindex	A page in the sitemap carries a noindex directive.	Remove the noindex or remove the URL from the sitemap.
Submitted URL blocked by robots.txt	A Disallow rule matches a sitemap URL.	Update robots.txt or drop the URL from the sitemap.
Page with redirect	The sitemap lists an old URL that redirects.	Replace it with the final destination URL.
Not found (404)	Deleted or moved pages are still listed.	Regenerate the sitemap after removing or redirecting pages.
Duplicate without user-selected canonical	Multiple versions of the same content are being crawled.	Set a self-referencing canonical and list only that version.
Too many URLs	More than 50,000 URLs or over 50MB in one file.	Split into multiple sitemaps and use a sitemap index.

Every one of these issues except parsing errors shows up in the Excluded tab of this generator before Google ever sees them. That is the main reason to run a verification pass whenever you make large changes to a site.

XML Sitemap vs HTML Sitemap vs robots.txt vs llms.txt

These four files get confused constantly, yet each solves a different problem.

File	Main audience	Purpose	Location
XML sitemap	Search engine crawlers	Lists indexable URLs and change dates for discovery and indexing.	/sitemap.xml
HTML sitemap	Human visitors and crawlers	A navigational page linking to key sections, useful on large or complex sites.	Any page, often /sitemap/
robots.txt	All crawlers	Controls which paths crawlers may request and points to sitemaps.	/robots.txt
llms.txt	AI models and agents	A Markdown summary of your site’s most useful content for language models.	/llms.txt

A strong technical foundation uses all of them together. Your robots.txt allows crawling and points to your XML sitemap. Your sitemap lists your best pages. Your internal links and HTML navigation connect those pages for people. Your llms.txt file summarises them for AI systems. You can create one in seconds with the free llms.txt generator.

XML Sitemaps for Programmatic SEO and Large Websites

Programmatic SEO changes the sitemap conversation. When you publish hundreds or thousands of location, service, comparison or directory pages from structured data, discovery becomes the bottleneck. Google can only rank pages it has crawled, and it only crawls a portion of a large site on any given day.

If you are building pages at scale with a WordPress bulk page generator, a few sitemap habits make a measurable difference.

Split sitemaps by page type

Instead of one massive file, group URLs into separate sitemaps for blog posts, service pages, location pages and products, then list them in a sitemap index. In Search Console, you can then compare indexing rates per page type. If your location pages are indexed at 40 percent while your service pages sit at 95 percent, you know exactly where to invest in content quality and internal links.

Publish in controlled batches

Pushing 10,000 pages live on the same day gives crawlers a huge backlog and gives you no way to learn from early results. Releasing pages in batches with a programmatic SEO scheduler spreads crawl demand over time, keeps lastmod dates meaningful, and lets you check indexing before you scale further.

Make lastmod dates honest

Programmatic pages are often regenerated when data changes. Only update the modified date when the content visitors see actually changes, such as new prices, availability or local details. Touching every page on every import wipes out the value of the lastmod field.

Pair sitemaps with internal links

A sitemap helps crawlers find pages, but internal links tell them which pages matter and pass authority between them. Pages that exist only in a sitemap are orphans, and orphans rarely perform well. Build hub pages, related-page modules and breadcrumb trails with an internal linking workflow for programmatic SEO, then run this generator in Smart mode to spot sitemap URLs that no link reaches.

Watch crawl budget on very large sites

For sites with tens of thousands of URLs or more, Google publishes guidance on managing crawl budget. The short version: keep low-value URLs out of your sitemap, fix redirect chains and errors, keep servers fast, and make sure your most valuable pages are easy to reach. A lean, accurate sitemap is one of the simplest ways to steer crawlers toward the right pages.

If you are new to the approach, the programmatic SEO for WordPress guide walks through planning, templates, data and publishing, and the programmatic SEO ROI calculator helps you estimate whether a page set is worth building before you start.

Sitemap Tips for Different Types of Websites

Local businesses and service providers

List every city, suburb and service area page you want to rank, but only if each page offers genuinely local information. Thin pages that swap a city name into identical text tend to be crawled and then ignored. A local SEO location page generator that pulls in unique data per location, such as service details, reviews, landmarks and FAQs, produces pages worth listing.

Ecommerce stores

Include category pages and canonical product pages. Exclude filter combinations, sort orders, internal search results, cart and checkout URLs. If products go out of stock permanently, remove or redirect them and regenerate your sitemap so it does not fill up with dead ends. Image tags are worth enabling for stores where product images drive discovery.

Blogs and publishers

Keep posts, pillar guides and useful category archives. Consider excluding thin tag archives and date archives. If you publish news, Google supports a separate news sitemap format for articles published in the last two days.

SaaS and software companies

Prioritise product, feature, integration, pricing, comparison and documentation pages. Keep app login screens, dashboards and account areas out. Documentation sites often benefit from their own sitemap because they update on a different cadence from marketing pages.

Multilingual websites

Each language version should appear in the sitemap under its own URL. You can also declare alternate language versions inside the sitemap using xhtml:link elements, as described in Google’s guide to localized versions of your pages. Make sure the hreflang annotations are reciprocal, meaning every version points to every other version.

Static Sitemap File or Dynamic Sitemap?

A static sitemap generated by a tool like this is a snapshot of your site at one moment. A dynamic sitemap created by your CMS or SEO plugin updates every time content changes.

Choose a static sitemap when your site is built with plain HTML, a site builder without sitemap support, or a headless setup where adding a sitemap route is not practical. It is also the right choice for audits, migrations and one-off checks before launch.

Choose a dynamic sitemap when you publish or update content regularly, especially on WordPress. It removes the risk of forgetting to regenerate the file.

Most growing sites end up using both: a dynamic sitemap for day-to-day indexing and a crawl-based generator to audit it. Because this tool verifies each URL against live status codes, noindex tags and canonicals, it catches mistakes a plugin will happily repeat forever.

One technical note: the crawler reads the HTML your server returns and does not execute JavaScript. If your navigation links only appear after JavaScript runs, some pages may not be discovered through crawling. Smart mode reduces that risk by also reading your existing sitemaps, and it is a useful test of how crawl-friendly your site really is.

XML Sitemap Best Practices Checklist

• Use a single source of truth for your sitemap and submit only that one.
• List only canonical, indexable URLs that return a 200 status.
• Use absolute URLs that match your preferred protocol and host.
• Keep lastmod dates accurate and skip changefreq and priority.
• Split large sites into multiple sitemaps grouped by page type and reference them in a sitemap index.
• Stay within 50,000 URLs and 50MB uncompressed per file.
• Add a Sitemap line to robots.txt and make sure no listed URL is disallowed.
• Submit your sitemap in Google Search Console and Bing Webmaster Tools.
• Review the Page indexing report filtered by sitemap every month.
• Regenerate or audit your sitemap after migrations, redesigns and large content launches.
• Support every sitemap URL with internal links so no important page is an orphan.
• Improve page-level signals as well. Bulk AI meta optimization and schema markup automation help indexed pages earn clicks once they appear in results.

More Free SEO Tools from PageForge

A sitemap is one piece of technical SEO. These free tools help with the rest:

• Free SEO Audit: check on-page SEO, metadata, headings and technical issues for any URL.
• Domain Authority Checker: measure the strength of a domain before you compete for keywords.
• AI Search Readiness Checker: see how well your site is prepared for AI answers and citations.
• Free llms.txt Generator: create an AI-ready Markdown summary of your website.
• Programmatic SEO Template Generator: find scalable keyword patterns and page templates.
• Programmatic SEO ROI Calculator: estimate traffic and revenue potential before you build.

Frequently Asked Questions

Is this XML sitemap generator really free?

Yes. You can generate, copy and download sitemaps without creating an account or entering an email address. The free tool includes up to 1,000 URLs per run, the gzip download, the URL list and the full CSV audit.

How many URLs can the free sitemap generator handle?

Each run can include up to 1,000 verified URLs. For larger sites, use include rules or the folder scope option to generate section-specific sitemaps, such as one for blog posts and one for services, then combine them in a sitemap index.

Does submitting a sitemap guarantee my pages get indexed?

No. A sitemap helps search engines discover and prioritise your pages, but indexing still depends on content quality, duplication, internal links, crawlability and site authority. Use the Page indexing report in Search Console to see which submitted pages were indexed and why others were not.

Where should I upload my sitemap.xml file?

Upload it to the root directory of your website so it is available at yourdomain.com/sitemap.xml. Then add a Sitemap line to robots.txt and submit the URL in Google Search Console.

Should I include changefreq and priority tags?

Generally, no. Google has stated it ignores both values. Accurate lastmod dates are far more useful. The generator leaves changefreq and priority out by default, but you can add them if another platform you use requires them.

Why were some of my pages excluded from the sitemap?

Pages are excluded when they redirect, return an error, carry a noindex directive, point to a different canonical URL, are blocked by robots.txt, contain query parameters, or match your keyword rules. The Excluded tab shows the exact reason for every URL so you can decide whether it needs fixing.

Do I need a sitemap if I already use Yoast SEO or Rank Math?

Those plugins already generate a dynamic sitemap, so you do not need to upload a second one. Instead, use this tool in Verify mode to audit the plugin sitemap for redirects, noindexed pages and non-canonical URLs, and in Smart mode to find linked pages the plugin is not listing.

How often should I update my XML sitemap?

Dynamic sitemaps update automatically. If you use a static file, regenerate it whenever you add, remove or significantly update pages. For active sites, a monthly audit is a sensible minimum, plus a check after any migration or redesign.

Can I create a sitemap for a website I do not own?

The tool works with any public website, which makes it useful for competitor research, client pitches and pre-migration audits. You can only submit a sitemap in Search Console for properties you have verified.

Why did the crawler find fewer pages than my site has?

Common causes include links that only appear after JavaScript runs, pages without any internal links, firewall or bot protection blocking the crawler, strict robots.txt rules, or the URL limit being reached. Switch to Smart mode so existing sitemaps are read too, and check the insights panel for warnings.

What is the difference between a sitemap and a sitemap index?

A sitemap lists page URLs. A sitemap index lists other sitemap files. Large sites use an index to organise many smaller sitemaps, and you only need to submit the index to search engines.

Does a sitemap help with AI search visibility?

Indirectly, yes. AI-powered search features still rely on pages that can be crawled, indexed and understood. A clean sitemap improves discovery, while structured content, schema and an llms.txt file make your pages easier for AI systems to interpret and cite.

Turn a Clean Sitemap into Real Growth

A sitemap can only list the pages you have. If your competitors rank for hundreds of location, service and comparison keywords while your sitemap holds twenty URLs, the gap is not technical. It is coverage.

PageForge is an AI programmatic SEO plugin for WordPress that turns a spreadsheet into SEO-ready pages. Import rows from CSV to WordPress pages or connect Google Sheets to WordPress, write unique copy with the AI content generator, and publish every page with metadata, schema and internal links built in. Your SEO plugin adds each new page to your sitemap automatically, and this generator lets you verify the result.

Download PageForge free from WordPress.org or compare PageForge plans to scale beyond the basics.