What really separates one generator from another
Business owners usually compare generators on convenience or price. For search, the deciding question is different: does the sitemap update itself when you add a product, publish an article or remove an old page? If it does not, the file becomes a snapshot of your site on the day it was created.
A stale snapshot causes two problems. New pages are missing, so search engines find them later. Deleted URLs stay in the file, and crawlers keep returning to pages that now show an error.
Built-in CMS tools and plugins
If your site runs on a popular CMS or a website builder, start with its own sitemap. It updates together with your content, and nobody has to remember a manual export. Most online store platforms behave the same way, adding products and categories automatically.
SEO plugins give you finer control over what is included, but they come with familiar traps. After installing one, check four things:
- tags, attachments and author archives that you do not want in search have not slipped into the file
- pages marked noindex are excluded
- the lastmod date reflects a real change, not just the date someone re-saved the page
- the CMS is not producing a second sitemap alongside the plugin's; there should be only one
Online generators and crawlers
An online tool follows links across your site and hands you a ready file. For a business card site or a short landing page that rarely changes, that is enough. For a living site the drawbacks add up: the sitemap is static, free plans often cap the number of pages, and you must upload the file to the server yourself.
There is another catch. The tool includes whatever it finds through links, including parameter URLs and utility pages, and it will never see a page that nothing links to. A desktop crawler works similarly but lets you filter the results, keeping only pages that return 200, carry no noindex and use their canonical address. It is still a one-time snapshot.
Custom-built sites and large stores
When a site is built on a framework, the sitemap is better generated by code straight from the database, either on request or at build time. You decide which page types go in and keep drafts, private areas and service pages out. The price is developer involvement: whenever a new page type appears, the generation logic needs to be extended.
For a big catalogue, splitting the sitemap into several files by page type works well: products, categories, articles. Search engine reports then show exactly where indexing problems start.
Which sitemap generator to choose
A simple rule: the more often your site changes, the more automatic the method should be.
- Site on a CMS: the built-in sitemap or an SEO plugin
- Online store: generation from the database, split by page type
- Custom-coded site: a script or route that builds the sitemap from your data
- Small static site: an online generator or crawler, repeated after every edit
Bilingual sites: Russian and Uzbek
Many businesses in Tashkent and the regions run their sites in two languages. A typical failure is a multilingual plugin and an SEO plugin configured separately, so only the main language reaches the sitemap. Uzbek pages then get indexed more slowly, and the cause can stay unnoticed for months.
A practical fix is an index file with a separate sitemap for each language. In Search Console you can then follow the indexing of the Uzbek version independently from the Russian one.
What to do after generating
A generator does not guarantee quality; it only does what you configured. Open the file and read through the URLs, run it through a validator, confirm the main domain and protocol are correct, add the sitemap path to robots.txt and submit it in Search Console and Yandex Webmaster. A few days later, look at the processing reports.
The biggest mistake is creating a sitemap once and forgetting it. If your method is not automatic, put sitemap updates into your content publishing routine. If you want to see how the sitemap fits into your wider SEO plan, the markdev team can talk through your situation and help pick an approach that suits your site.
FAQ
Is an online sitemap generator good enough?
Yes, for a small site that hardly changes, such as a business card site or a landing page. If pages are added regularly, automatic generation through a CMS, plugin or code is the safer choice.
How many sitemaps should a site have?
One entry point. It can be an index file linking to several sitemaps by page type or language. Two independent sitemaps from a CMS and a plugin only create confusion.
Why are my Uzbek pages missing from the sitemap?
Most often the multilingual plugin and the SEO plugin are not aligned, and only the main language is exported. Check both settings and open the file manually.
Do I need to update a sitemap manually?
Only if it was created statically, through an online tool or crawler. In that case, make the update part of your content publishing routine.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.