An XML sitemap is essentially a complete map of your website for search engines, explaining which pages exist, when they were last updated and which ones matter most. Although in 2026 Google is perfectly capable of finding most sites without a sitemap, having one noticeably accelerates the indexing of new pages and for larger sites it remains an almost mandatory piece of infrastructure. Submitting your sitemap through Google Search Console also gives you visibility into which URLs ran into problems and makes indexing reports significantly more actionable.
Why a sitemap matters
Search crawlers usually discover sites through links, but if a new page has not yet received any inbound link or your site architecture is unusually deep, the crawler may simply miss it. A sitemap solves this by handing the crawler a direct list and ensuring no important page is overlooked. This is especially critical for fresh domains, blogs with few backlinks and e-commerce stores with thousands of product pages where a sitemap becomes the single most effective tool for accelerating indexation.
The structure of a sitemap
A standard XML sitemap starts with a urlset element, and each page lives inside its own url block. The core field loc contains the full URL, lastmod the date of the last modification, changefreq the expected update frequency and priority a relative importance value. In practice Google mostly ignores changefreq and priority, but it pays close attention to lastmod, so only refresh that date when the content has genuinely changed or you will gradually erode trust in your sitemap.
Protocol rules
A single sitemap file may contain a maximum of 50,000 URLs and weigh no more than 50 MB uncompressed. If your site exceeds either limit, create a sitemap index file that points to several smaller sitemaps. Every URL must be canonical and written in absolute form such as https://sayt.uz/blog/post, never relative. Pages that return 404, carry a noindex meta tag, redirect elsewhere or point to a different canonical should never appear in the sitemap, since including them only degrades the perceived quality of your file.
Specialised sitemap formats
Beyond the standard URL sitemap there are specialised variants. Image sitemaps describe images and help them surface in Google Images, while video sitemaps carry titles, durations and thumbnails for video content. News sitemaps are reserved for publishers approved in Google News and list articles from the last 48 hours. For most businesses a plain URL sitemap is sufficient and the other formats should only be added when there is a clear, concrete need such as a large product image library or a video-driven catalogue.
Dynamic sitemap.php
A static XML file works well for small sites, but blogs and online stores with frequently changing content benefit from a PHP script that generates the sitemap on demand. This kind of script pulls fresh data straight from the database, so the sitemap stays current without anyone having to regenerate files manually. The simplest version sets an XML content-type header, selects slug and updated_at from the published rows through PDO, loops through them outputting url blocks and closes the urlset tag at the end. The big benefit is that every new article appears in the sitemap automatically without any manual step.
robots.txt and Search Console submission
Point search engines to your sitemap by adding Sitemap: https://sayt.uz/sitemap.xml to robots.txt — this is the standard discovery mechanism every major engine respects. Then open Google Search Console, navigate to the Sitemaps section and submit the URL. Within a few days Google will process it and start reporting indexing statistics. Submit the same file to Bing Webmaster Tools and Yandex Webmaster as well — for audiences in Central Asia this is particularly worthwhile since Yandex still commands a meaningful share of regional search traffic.