How does an online sitemap.xml generator work?
A sitemap helps search engines find relevant URLs and understand the structure of crawlable pages. This file is especially useful for online stores, catalogs, new projects, and websites with large amounts of content and complex internal structures. Having a sitemap address does not guarantee indexing – the decision to crawl and index a page is made by the search engine.
The generator crawls the website's available internal links and collects page addresses. The result depends on the project structure, internal links, response codes, indexing rules, and other technical settings. If a page exists but is not accessible through a normal crawl, the automatic website sitemap generator may not detect it.
Before uploading the finished file, it's worth reviewing the resulting list. The sitemap should contain the actual pages that the website owner actually wants to submit to search engines. This approach helps avoid discrepancies between the sitemap, canonical, meta robots, and the actual URL.
What do you need to specify to create a Sitemap?
To launch, simply enter the full website address along with the protocol, for example, https://example.com/. If additional scanning parameters are available in the interface, select them based on the project structure and the task. Don't change the settings unless necessary if you only need to generate a standard sitemap.
Requests for "free sitemap generator", "generate sitemap online", and "xml sitemap creator" typically involve the same task: quickly obtain a ready-made XML sitemap for a website address. Once launched, the service begins crawling and collecting URLs accessible through internal links. For a small project, this process is usually simpler than manually compiling a file.
What happens during a website crawl?
The robot starts from the specified address, follows the links found, and generates a list of pages. During the crawl, it may consider URL availability, server response codes, internal links, and any limitations imposed by the service itself. The more complex the site, the more carefully the results should be checked.
If a project contains cyclic parameters, filters, technical sections, or a large number of automatically generated URLs, the list may require cleaning. The sitemap should reflect the indexable structure of the site, not the full set of URLs the engine can generate.
What does the user get after generation?
Once the crawl is complete, the user receives a completed sitemap.xml file or a list of URLs from which XML can be generated. Depending on the service's capabilities, the interface may also display the number of pages found, crawl errors, and the processing status of individual URLs.
A ready-made sitemap.xml generator saves time on manually preparing the file, but it's still a good idea to check the results. Pay particular attention to redirects, 404 errors, URL parameters, non-canonical pages, and sections blocked from indexing.
Do I need to install a program or plugin?
The online service requires no installation. Simply open the tool in your browser, enter your domain, and wait for the scan to complete. This option is suitable for one-time generation, structure verification, and for sites without a suitable CMS module.
For a constantly changing online store or portal, it's best to set up automatic sitemap updates using the CMS or server-side. In this case, an online XML sitemap generator is convenient for monitoring the results and independently verifying the URL list.
Common mistakes when creating an XML sitemap
Most problems stem not from the XML format itself, but from the quality of the URL list. A URL generator can collect URLs, but the decision about which ones actually need to be included in the sitemap rests with the website owner or SEO specialist.
Verification is especially necessary after redesign, migration, changes to the directory structure, and the mass creation of new pages.
Adding all site URLs without verification
A large sitemap by itself doesn't provide any advantage. If the file contains parameters, duplicates, and technical pages, the search engine receives a less clean set of URLs.
First, define the structure to be indexed, then transfer it to XML. The number of URLs should be a consequence of the site structure, not a generation goal.
URLs with redirects and 404 errors
A URL after a 301 is no longer the final page, so it's best to include the destination URL in the sitemap right away. Pages with 404s are removed from the sitemap after their removal is confirmed.
Regular checking helps you find such addresses after moving a site, changing a slug, or deleting old products.
Sitemap and canonical mismatch
If a sitemap contains one URL and the canonical page points to another, the search engine receives different signals. For a regularly indexed page, it's preferable for the sitemap to contain its canonical URL.
Such discrepancies often appear after changing the protocol, domain, directory structure, or parameter settings.
Adding pages closed from indexing
Pages with noindex should generally not be included in the XML sitemap of indexed content. If they are included automatically, it's worth checking your CMS settings and sitemap generation rules.
Robots.txt needs to be analyzed separately, because the crawl blocker works differently and does not replace meta robots.
Lastmod is no longer relevant.
The lastmod file should reflect a real, significant change to the page. Automatically updating all URLs to today's date each time the file is recreated is undesirable.
For static pages, the date may remain the same for a long time. For products and articles, it changes after significant content changes.
The sitemap is created once and is no longer updated.
A static file quickly becomes outdated on a project where pages are regularly added or removed. As a result, new URLs are missing, and deleted ones continue to be passed to the search engine.
If your site changes frequently, set up automatic updates or include the Sitemap in your regular technical monitoring.
I view sitemap.xml as a technical list of canonical pages that we actually want to submit to search engines. Before submitting, I check to make sure there are no redirects, 404s, duplicates, or URLs blocked from indexing. For large sites, I separate sitemaps by page type. This makes it easier to check the data in Google Search Console and quickly identify problematic sections. I don't use priority and change frequency as SEO factors, as Google ignores these values.
How to create a sitemap.xml using an online generator?
An XML sitemap generator is suitable for quickly preparing a file for an existing website. The process consists of a few straightforward steps: specify the domain, start the crawl, check the found pages, and save the XML.
Before starting, it's a good idea to ensure the site is accessible without authorization, important sections are linked internally, and the server isn't blocking the service's crawler. Otherwise, the results may be incomplete.
Enter the website address
Enter the full address of the homepage, for example, https://example.com/. Check the protocol, domain, and working mirror. An error at this stage may result in the sitemap being generated for the wrong version of the site.
If your project has recently moved to HTTPS or a different domain, first check your redirects and canonicals. There's no point in creating a new XML file based on the old mirror if it's no longer expected to be indexed.
Run the scan
Once launched, the robot begins following internal links and collecting URLs. Speed depends on the site's size, server response, structure depth, and the limitations of the service itself.
Don't block important sections from crawling during generation. If a page is only accessible to the user through a form, JavaScript, or a complex filter without a regular link, the automated crawl may miss it.
Check the found pages
Before downloading the file, review the URL list if the service displays one. Find unnecessary parameters, old URLs, 301 redirects, 404 errors, duplicates, and noindex pages.
This check is useful in itself. If the generator detects hundreds of technical URLs, the problem may lie in the internal linking or site architecture, not just the future sitemap.
Download the sitemap.xml
After checking, save the finished XML file. Its name is usually left as sitemap.xml, although for multiple maps, you can use more descriptive names like sitemap-products.xml or sitemap-posts.xml.
Before uploading, it's recommended to validate the file. Errors in XML markup, encoding, or URLs can prevent search engines from processing the map properly.
Upload the file to the website
For a single shared sitemap, it's convenient to use the address https://example.com/sitemap.xml. The file should open via a direct link and return the correct server response.
After uploading, check the URL from a browser or with a technical tool. If the server returns a 404 or 403 error, or redirects the file to an unexpected address, first fix accessibility issues and then submit the sitemap to the search engine.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history on a website builder. We built the semantic core for both cities, reworked the landing pages and built the link profile from zero. Four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and closed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
Answers to your questions
Is it possible to create a sitemap.xml for free online?
Yes, this uses an XML sitemap generator, which scans the site and collects accessible pages. This method is suitable for small or medium-sized structures, one-time checks, and projects without a suitable CMS module.
After generating the file, you need to review it. Even a good service doesn't understand the site's business logic and may find URLs that are technically accessible but shouldn't be in search results.
Where to upload the sitemap.xml file?
Typically, the file is placed at a URL like https://example.com/sitemap.xml. It should open directly and return a valid server response without authorization.
Once uploaded, the address can be added to robots.txt and submitted through Google Search Console. If a sitemap index is used, the address of the index file should be specified in these places.
Should I add a sitemap to robots.txt?
Yes, this is a convenient way to tell search engines where to find your sitemap. A line containing the absolute URL of the XML file is added to robots.txt.
If you have multiple sitemaps, you can specify multiple directives or a single sitemap index. After making changes, be sure to check the accessibility of both files.
How many URLs can be in one sitemap.xml?
A single file can contain up to 50,000 URLs and occupy up to 50 MB uncompressed. If the limit is exceeded, multiple sitemaps are created.
Individual files are combined through a sitemap index. On large projects, they are also often divided by page type for easier control.
Does a Sitemap guarantee that pages will be indexed?
No. Adding a URL to a sitemap helps Google discover a page, but it doesn't guarantee its crawling, indexing, or ranking.
Page accessibility, content, canonical, internal links and other technical signals are also important for indexing.
Should I add noindex pages to my Sitemap?
Usually not. If the site owner deliberately prevents the URL from being indexed, it's illogical to include it in the sitemap as a landing page.
If such addresses appear automatically, you need to check the CMS rules and the way XML is generated.
Do I need to specify priority and changefreq?
For Google, these values don't provide the benefit claimed in the old guidelines. The search engine reports that it ignores priority and changefreq.
If they are already present in the automatically generated XML, there's no need to remove them immediately. Don't expect these fields to have any impact on SEO.
How often should I update my sitemap.xml?
Update the map after adding, removing, or changing indexed URLs. For a dynamic site, it's more convenient to set up automatic generation.
A static corporate website can be checked less frequently, but after a migration, redesign, or change to the XML structure, it is worth recreating it.
A correct sitemap.xml contains up-to-date indexable URLs, complies with canonical and meta robots, doesn't include deleted pages, and is regularly updated along with the site. For a large project, it's convenient to split the sitemap into multiple files, and after uploading, monitor processing through Google Search Console.
Enter your website address into the Seo-Gen generator, create an XML sitemap, check the resulting URLs, and upload the completed file to your website. Then, add the sitemap to robots.txt and submit it to Google Search Console.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: Sitemap.xml generator
What is a sitemap.xml and why does a website need it?
Sitemap.xml is an XML file containing a list of URLs that the website owner submits to search engines for discovery and crawling. It can specify canonical URLs and the date of the last significant page change. The file is placed on the website and, if necessary, submitted through Google Search Console.
A sitemap is especially useful where simple internal linking isn't enough to quickly find all the necessary pages. However, a sitemap doesn't replace navigation, proper links, canonical URLs, or index management. A page with technical issues doesn't become high-quality just because its URL is specified in XML.
How does an XML sitemap help search engines?
Search engines use sitemaps as an additional URL source. This is useful for new projects, large catalogs, online stores, publication archives, and pages located deep within the structure. Sitemaps also help quickly discover new URLs after website expansion.
A sitemap is especially useful where some content appears dynamically or internal links are unevenly distributed. However, the primary traversal path of the site should still be accessible through regular links. Hiding important pages from navigation and relying solely on an XML sitemap is not recommended.
How is an XML Sitemap different from an HTML Sitemap?
An XML sitemap is created primarily for search engines and has a machine-readable structure. An HTML sitemap is a regular page with links that a user can navigate. These formats serve different purposes and are used differently.
The XML file can be submitted to Google Search Console and added to robots.txt. The HTML sitemap aids navigation and internal linking if visitors actually need it. Both options can be used simultaneously on a single site.
Do all websites need a sitemap.xml?
A small website with a few well-linked pages can be crawled without a sitemap. However, a sitemap simplifies URL control and is almost always useful for projects that are regularly updated or gradually increase the number of pages.
For online stores, catalogs, news resources, multilingual sites, and large corporate projects, it's usually worth setting up an XML sitemap. On such sites, the structure changes more frequently, and the number of pages makes manual control more difficult.
What pages should be added to sitemap.xml?
The XML sitemap includes URLs that should be indexed and are considered primary versions of pages. The logic is simple: if a website owner submits an address to a search engine via a sitemap, that address must not simultaneously contradict the canonical, noindex, or current page state.
Before publishing the file, it's helpful to compare it with the actual site structure. A clean sitemap of up-to-date canonical pages is more valuable for SEO than a large file with technical URLs, redirects, and duplicates.
Which URLs should be included?
Sitemaps typically include pages with a 200 response code that are allowed for indexing and have a valid canonical URL. These can include categories, product cards, articles, services, landing pages, and separate language versions.
For each entry, you must use an absolute URL with the protocol and domain. If the site operates over HTTPS, the XML must include current HTTPS addresses. Old HTTP versions that lead via redirects do not need to be added to the working sitemap.
What URLs should not be included?
Deleted pages, redirects, technical duplicates, internal search results, unnecessary sorting parameters, and URLs closed via noindex are excluded from the map. The same applies to pages that declare a different canonical URL.
Online store filters require special attention. Some of these URLs may be fully functional SEO landing pages, while others create virtually endless combinations of parameters. Sitemaps include only those variants that are intentionally open to indexing.
What to do with canonical, noindex, and robots.txt?
The sitemap should adhere to the general indexing logic. If a page canonically points to a different URL, the canonical version is typically added to the sitemap. If a page is closed via noindex, it should not be included in the XML as the target indexed URL.
The situation is different with robots.txt: disabling crawling does not mean disabling indexing. Therefore, access rules, meta robots, and canonicals should be checked separately. Mixing these mechanisms often creates conflicting signals for search engines.
What are the requirements for an XML Sitemap?
A valid file contains absolute URLs and adheres to format restrictions. For most websites, a single sitemap.xml file is sufficient, but larger projects divide the URLs between multiple files and aggregate them through a sitemap index.
It's best to save the file in UTF-8 and keep it up to date. If a URL is deleted, redirected, or no longer canonical, it's best to remove it from the map during the next update.
Limits on the number of URLs and file size
A single sitemap can contain no more than 50,000 URLs, and the uncompressed file size must not exceed 50 MB. If a site exceeds one of these limits, multiple XML sitemaps and a separate sitemap index are created.
In practice, division is often done by content type. For example, products are placed in one set of files, categories in another, and articles in a third. This approach simplifies diagnostics and helps quickly identify which group contains errors.
What should the URLs be?
Sitemap URLs must be absolute: https://example.com/catalog/page/, not /catalog/page/. For a site with HTTPS, use the latest secure version. Old domains, mirrors, and URLs should not be left in the working file without a reason after the transfer.
It's recommended to include canonical URLs with a 200 status code that are accessible to search engines. If a site uses multiple languages, each indexed language page should have its own correct URL and consistent canonical and hreflang settings.
What do the loc and lastmod tags mean?
The loc tag contains the full URL of the page. It is a required part of a regular sitemap entry. The value must point to the actual URL of the site the sitemap refers to.
lastmod indicates the date of the last significant content change. It's useful to update it after a page is actually modified, rather than every time the XML is technically rebuilt. If the date constantly changes without any content changes, the signal loses its practical meaning.
Are priority and changefreq necessary?
For Google, the priority and changefreq values don't affect crawl priority in the way that older guidelines often describe. Google states that these values are ignored, so there's no need to fill them in for SEO purposes.
If a specific CMS automatically adds these fields, their mere presence doesn't pose a problem. Don't expect priority="1.0" to improve a page's ranking or encourage crawlers to visit it more often.
How to add sitemap.xml to robots.txt?
In robots.txt, you can specify the absolute address of the map using a separate directive:
Sitemap: https://example.com/sitemap.xml
If multiple sitemaps are used, it is permissible to add multiple Sitemap: lines or specify a single sitemap index. This directive does not need to be placed within a specific User-Agent group.
After changing robots.txt, check that the file is accessible at /robots.txt and that the specified sitemap opens without error. For additional verification, you can use a separate robots.txt tester and sitemap validator.
How to submit a sitemap to Google Search Console?
Once the file is uploaded to your site, you can submit it to Google via Search Console. To do this, open the desired resource, go to the Sitemap section, enter the file's address, and submit it for processing.
Search Console displays the file reading status and helps detect technical errors. A successful submission means Google was able to retrieve the file, but it doesn't automatically index every URL.
Adding a sitemap
Before submitting, make sure the correct Search Console resource is selected and the sitemap belongs to its domain. For a regular file, simply specify the path to the sitemap in the appropriate section of the interface.
After processing, periodically compare the number of URLs in the sitemap with the actual site structure. A sharp increase in the number of URLs may indicate the presence of parameters, duplicates, or erroneous page generation.
What errors should be checked after submission?
Check for inaccessible XML files, invalid URLs, server errors, and domain mismatches. It's also worth checking for URLs that have already been removed, redirected, or should no longer be indexed.
If Search Console reports a problem, first check the sitemap itself, then the HTTP response and page settings. Rebuilding the file without understanding the cause is usually useless.
How to create a sitemap for a large website?
It's more convenient to divide large online stores and portals into multiple maps. This simplifies updates and diagnostics, especially if different sections are created independently.
For example, products, categories, and articles can be placed in separate sitemaps. If the issue only appears in product cards, this approach quickly reveals the relevant section of the site.
When should you split your Sitemap into multiple files?
Splitting is mandatory when exceeding the 50,000 URL or 50 MB limit for a single uncompressed file. Even with fewer pages, splitting can be useful for managing a large project.
It's better to choose boundaries based on a logical structure rather than a random number of URLs. This makes it easier to understand reports and associate technical errors with a specific section.
What is a sitemap index?
A sitemap index is an XML file containing links to other sitemaps. The index is passed to the search engine, which then retrieves the addresses of individual sitemaps.
This option is suitable for catalogs with a large number of products, news resources, and projects with multiple page types. Each child file must remain accessible and correct.
Should I create separate Sitemaps for different types of pages?
This isn't a requirement for a small project. As the site grows, separating URL types significantly simplifies file management and updating.
For a large store, it makes sense to separate categories from products, and for media, separate articles from service sections. The main thing is that the division corresponds to the actual structure and does not create duplicates between files.
Sitemap for an online store and dynamic website
An online store is constantly changing: products, categories, and landing pages are added, while some pages disappear or are redirected. Static XML quickly becomes outdated, so the sitemap must be updated along with the site structure.
Particular attention should be paid to filters, sorting, and parameters. Automatically adding all possible combinations to a sitemap is not possible unless they are intended for search results.
Which online store URLs should I include?
Indexed categories, product cards, information pages, and individual SEO landing pages are added to the sitemap. URLs must return a 200 status code and match the selected canonical version.
A product that is permanently deleted and returns a 404 error should be removed. If the card is redirected to a new page, the final, current URL should be left in the XML.
What to do with filters and URL parameters?
Indexable filters can be enabled if they are created as full-fledged landing pages, have a unique URL, useful content, and a correct canonical. Technical combinations of sorting and service parameters are usually excluded.
There's no single rule for all filters. The decision depends on the semantics, demand, catalog structure, and the chosen indexing strategy.
Should I update my Sitemap automatically?
For a dynamic project, automatic updates are preferable to manually uploading a new file after each change. The CMS or server can add new canonical URLs and remove outdated entries.
An online sitemap generator remains useful as an independent check. It allows you to compare the actual site structure with what the CMS generates.
Online generator, CMS, or manual sitemap creation – which one to choose?
The method depends on the site's size and frequency of changes. For a small, one-time task, it's convenient to create a sitemap using the sitemap.xml generator. For a store with daily product updates, it's better to use automatic generation.
Manual XML is only worthwhile for a short and stable list of pages. The larger the project, the higher the risk of forgetting to delete an old address or add a new one.
Online Sitemap Generator
This online service is suitable for small and medium-sized websites, for initial sitemap preparation, and for technical verification. Users receive results without server configuration or plugin installation.
If you need an XML sitemap generator for a one-time task, this option is usually the fastest. After receiving the file, you should still check the URL and upload it to the correct domain.
Automatic generation via CMS
WordPress and many other CMSs support sitemap generation natively or through extensions. For a regularly updated project, this is more convenient, as the file changes along with the content.
Before using the automatic map, check what page types your CMS includes. Sometimes plugins include archives, tags, and other sections that aren't useful for search.
Manual XML creation
The manual method is suitable for a small site with several stable URLs. You can create the file yourself if you understand the XML structure and don't need to constantly update the list.
For hundreds or thousands of pages, this approach quickly becomes inconvenient. Errors during updates are more common, and managing deleted and new URLs takes too much time.