Enter a domain name
Enter a domain name
An XML sitemap is a machine-readable file that lists the preferred URLs of a website. It gives search engines a clear source from which they can discover important pages, especially when a site is large, recently launched, frequently updated, or not perfectly connected through internal links.
This free XML Sitemap Generator crawls the address you enter and prepares a sitemap from the URLs it can find. You can review the generated list and save it as an XML file. No registration is required. A sitemap supports discovery, but it does not guarantee that every submitted URL will be crawled, indexed, or ranked.
The generator can normally find pages that are publicly accessible and connected through crawlable links. Pages hidden behind a login, blocked from crawling, loaded only after complex scripts run, or not linked from other pages may be missed. Always inspect the output instead of assuming that it represents every page on the site.
An XML sitemap is usually stored at a public address such as https://example.com/sitemap.xml. Each entry contains a page URL inside a <loc> element. An entry may also include <lastmod> to show when that page was last significantly updated.
A standard sitemap uses the sitemap protocol namespace and full, absolute URLs. The URLs should use the same preferred protocol and hostname as the website's canonical pages. For example, if the canonical site uses HTTPS and WWW, the sitemap should not mix those URLs with HTTP or non-WWW versions.
The optional fields do not give a page extra authority. A clean list of accurate canonical URLs is more useful than a file filled with artificial dates, maximum priority values, or unrealistic change frequencies.
Include URLs that you want search engines to consider for indexing. In most cases, each URL should return a successful 200 response, contain useful public content, allow indexing, and identify itself as the canonical version.
Good candidates include important service pages, tool pages, articles, category pages, product pages, and other original content that users can reach. Use the final preferred URL after HTTPS, hostname, and path rules have been settled.
A sitemap is public and is not a security feature. Do not place confidential addresses in it. Removing a URL from a sitemap also does not automatically remove that page from search results; indexing controls and the page's HTTP response must be handled correctly.
Search engines can discover pages through normal links, but a sitemap provides another reliable discovery path. This is useful for websites with many pages, new sites with few external links, archives with isolated content, or sites where some important pages sit several clicks away from the homepage.
A sitemap can also make website maintenance easier. The submitted sitemap report in Search Console shows whether Google could read the file and how many URLs were discovered. That information helps with diagnosis, but a successful sitemap status does not mean that all listed pages have been indexed.
Every sitemap URL should match the version you want indexed. Keep the sitemap, canonical tag, internal links, redirects, and HTTPS/WWW preference consistent. Conflicting signals make it harder for a search engine to determine the preferred version.
Update lastmod when the main content changes in a meaningful way. A correction, substantial rewrite, product update, or important new section may justify a new date. Changes to advertisements, copyright years, navigation, or other minor sitewide elements usually do not. Avoid setting every URL to today's date each time the sitemap is generated.
Regenerate the sitemap after adding, permanently removing, or changing important URLs. Check that deleted pages disappear, redirected URLs are replaced by their final destinations, and new pages have useful internal links in addition to being listed in the sitemap.
A single sitemap can contain up to 50,000 URLs and must not exceed 50 MB when uncompressed. If a website exceeds either limit, divide the URLs into multiple sitemap files and list those files in a sitemap index. This generator offers a crawl limit of up to 5,000 pages per run, so larger websites may need a platform-based or server-side sitemap system.
Save the document with UTF-8 encoding and use complete URLs. Special characters in XML must be escaped correctly. After uploading the file, open its public URL in a browser and confirm that it returns HTTP 200 without redirecting to a login page or displaying a server error.
You may also add a line such as Sitemap: https://example.com/sitemap.xml to the site's robots.txt file. Use the final public sitemap URL. You do not need to resubmit the same sitemap every day; search engines can revisit a stable sitemap address when the file changes.
Check that important pages are linked with standard HTML links and are accessible without signing in. Confirm that robots rules, firewall settings, rate limits, and server errors are not preventing the crawler from loading pages. Orphan pages may need to be added to the website's navigation or relevant content, not merely placed in the sitemap.
Open the exact sitemap URL in an incognito browser window. It should load publicly, use valid XML, return HTTP 200, and not be blocked by authentication. Also verify that the sitemap belongs to the same property and that the file does not contain HTML from an error page.
This is not necessarily a sitemap error. Check each page's content quality, canonical tag, indexing directive, response status, internal links, duplication, and rendered mobile content. A sitemap can help Google find a URL, but Google still decides whether and when to crawl and index it.
Replace each redirecting URL with its final canonical destination. Standardize HTTPS, WWW preference, capitalization, and trailing-slash rules. Regenerate the file after the corrections and confirm that only one preferred version of each page remains.
No. It helps search engines discover URLs, but it does not guarantee crawling, indexing, or higher rankings.
A small, well-linked website may be discovered without one, but a clean sitemap is still useful for monitoring, future growth, and confirming preferred URLs.
No. Google ignores the priority field. Selecting 1.0 for every page provides no ranking advantage.
It is optional. Google ignores changefreq, so you may leave it as None. Accurate content and modification dates matter more.
No. Important pages should still be connected through useful navigation and contextual internal links. A sitemap is an additional discovery method, not a replacement for website structure.
Update it when important URLs are added, removed, or changed. The right schedule depends on how often the site changes; there is no benefit in publishing false daily changes for static pages.
A root-level address such as https://example.com/sitemap.xml is simple and widely used. If it is placed elsewhere, remember that a sitemap normally affects URLs within its directory scope unless submitted and configured appropriately.
Use the generated file as a reviewed technical map of your preferred public URLs. Keep it consistent with the real website, submit it through Search Console, and treat indexing issues as page-level quality or technical problems rather than assuming that the sitemap alone can solve them.
