If you are looking for a way to submit a WordPress sitemap to Yandex, do not begin by trying a long list of paths. Identify the sitemap the website is actually generating, check that the file is publicly accessible, and only then submit an appropriate URL in Yandex Webmaster.
After reading this article, you will know how to find WordPress core sitemaps or sitemaps generated by a plugin, distinguish a sitemap index from a child sitemap, check URLs before submission, and read the processing status. The article does not claim that SaibABC.Com has been connected, has submitted a sitemap, or has data in Yandex.
Illustration guidance for editors: if an image is created solely with AI, use a conceptual diagram showing “website → sitemap → search bot → report.” Do not use an AI-generated image that pretends to be the Yandex Webmaster or WordPress interface. If a genuine interface screenshot has been lawfully obtained, it may be added with the interface version identified where necessary.
Prepare before finding the sitemap
You need:
- A WordPress website that opens in a browser.
- The website’s official URL, including the protocol
httporhttpsand whether it does or does not usewww. - Verified access to the website in Yandex Webmaster, or authorization to perform the submission step.
- Permission to view the configuration of WordPress, the SEO plugin, or
robots.txt. If you do not have access, note who needs to provide assistance. - A place to record the sitemap URL, the date checked, and the status after submission.
If you have not finalized the official URL or do not yet have permission to manage Yandex Webmaster, complete the preparation first. You can also review the Yandex Webmaster connection preparation checklist before continuing.
For the example website SaibABC.Com, retain the placeholder [URL chính thức của website] until the actual address has been checked. Do not turn the example website’s name into a fictitious URL.
How does a sitemap index differ from a child sitemap?
A sitemap is a file that lists URLs to provide search engines with additional information about a website’s structure. Yandex supports XML and TXT sitemaps, with XML recommended; a sitemap does not guarantee that every URL it contains will appear in search results (according to yandex.com).
A small website may have only one XML sitemap. Larger websites commonly use a sitemap index, an index file containing links to multiple child sitemaps, such as sitemaps for posts, pages, or categories.
If you open a file and see multiple links pointing to other XML files, it is usually a sitemap index. In that case, prioritize recording the URL of the main sitemap index rather than submitting multiple child sitemaps.
Find the sitemap WordPress is generating
Check WordPress core sitemaps
WordPress has included XML sitemaps since version 5.5. The default path is usually:
https://ten-mien-cua-ban.example/wp-sitemap.xmlReplace https://ten-mien-cua-ban.example with the verified official URL, then open the path in a private window. In the default configuration, the core sitemap uses wp-sitemap.xml as its sitemap index (according to WordPress.org).
- XML opens: Record the URL and proceed to check its contents.
- Returns 404: The core sitemap may be disabled, the website may use an SEO plugin, or rewriting may not be working. Do not install another plugin simply to generate a different sitemap.
- Redirects: Record the final URL after the page finishes loading and compare it with the website configured in Yandex Webmaster.
- Requests a login or is blocked: The sitemap is not ready for submission because external bots may be unable to access it.
Check a sitemap generated by an SEO plugin
If /wp-sitemap.xml does not exist or the website uses an SEO plugin, open the settings area for the active plugin. Menu names and paths vary by plugin, version, and configuration; do not assume a specific path.
Look for items or links with names such as XML Sitemap, Sitemap or View sitemap. Open the link in a browser while signed out, then record the final URL.
Do not enable another sitemap generator just because you have not found the URL. WordPress core, an SEO plugin or the hosting system may already be generating a sitemap. If two generators are active, it becomes difficult to determine which file is the primary source and is being updated.
Look for clues in robots.txt
Open the following address in a browser:
https://ten-mien-cua-ban.example/robots.txtLook for a line that begins with:
Sitemap:Open each declared URL to check it. Use only URLs belonging to the correct website, and record which URL is the sitemap index and which URLs are child sitemaps. Yandex allows you to declare a sitemap in robots.txt or add it directly on the Sitemap files page in Yandex Webmaster (according to yandex.com).
robots.txt only provides instructions for bots; it does not protect private data. The Sitemap: line also does not replace opening and checking the actual URL.
Check the sitemap before submitting it
| Check | Required result | If it does not pass |
|---|---|---|
| Correct website | Correct protocol, domain and prefix www | Stop and identify the official URL |
| Publicly accessible | No login, password or CAPTCHA required | Check the protection layer and access permissions |
| Server response | HTTP 200 OK or a redirect to a valid final URL | Check the server, HTTPS and redirects |
| Correct file type | XML or TXT containing a valid sitemap | Do not submit an HTML page, RSS feed or error page |
| URLs inside the sitemap | Belong to the correct website and are public URLs you want to monitor | Check the plugin, canonical URLs and exclusion settings |
A sitemap should be hosted on the same domain as the website it describes. The server should return HTTP 200 OK, and the content must meet the requirements for format, number of links and file size. When you need to verify the format, use Yandex's Sitemap validator before submitting it (according to yandex.com).
Check it in a browser
Open the sitemap URL in a private window. If you see XML or a list of XML links, check several URLs inside it:
- Can the URL be opened without signing in?
- Does the URL belong to the correct domain version?
- Are these pages that you want search engines to know about?
- Does the sitemap index point to child sitemaps that are accessible?
You do not need to manually assess every URL in a large sitemap. Check the sitemap index, several child sitemaps and a selection of representative URLs to identify obvious configuration errors.
Check it with Sitemap validator
Where to do this: Yandex Webmaster → the Sitemap validator tool, or an equivalent section. Choose URL input and paste:
[URL sitemap đã kiểm tra]Replace the bracketed placeholder with the actual URL, then click the check button. If the tool reports an error, record the error verbatim and fix the sitemap generator before submitting it. If you do not yet know whether the problem is in WordPress, the plugin or the server, do not create another sitemap to test.
Submit the sitemap to Yandex Webmaster
- Where to do this — Yandex Webmaster: select the correct verified website. Compare the protocol, domain and
wwwprefix with the URL you just checked. - Open Indexing → Sitemap files, or the equivalent section if the interface uses another language.
- Enter the complete sitemap URL, for example
https://ten-mien-cua-ban.example/wp-sitemap.xml. Replace the sample domain with the actual value; do not enter a post URL, a shortened domain or the placeholder[URL sitemap đã kiểm tra]. - Click the button to add or submit the sitemap.
- Record the submission date, submitted URL, and status shown immediately after the action.
Yandex places the added sitemap in a processing queue. Official documentation states that the bot may take up to two weeks to download the file; this does not guarantee that every URL within it will be indexed or appear in search results (according to yandex.com).
Reading the status after submission
| Status or indicator | Safe interpretation | What to do |
|---|---|---|
| Added or processing | Yandex has accepted the sitemap URL | Record the submission date and check again later |
| Unable to process | The URL, website, response, or file format may be incorrect | Check the file, HTTP 200 response, and validator |
| Not indexed | This does not automatically mean that the sitemap is broken | Check the submission time, accessibility, and detailed message |
| Document contains no text or has been removed from the index | A sitemap is not a standard content page intended to appear in search results | Use Sitemap validator to check the file; do not use the standard URL report to conclude that the sitemap is not working |
Key point: Yandex accepting a sitemap, downloading it, and indexing its URLs are different statuses. A successful submission does not prove that all URLs have been crawled, indexed, or ranked.
Troubleshooting common errors
Not sure whether to submit the sitemap index or a child sitemap
If the sitemap index opens and lists active child sitemaps, submit the primary sitemap index. Submit an individual child sitemap only for a clear administrative reason, such as needing to monitor a specific group of files or when the sitemap index is unusable.
/sitemap.xml returns 404
This is not evidence that the website has no sitemap. Try /wp-sitemap.xml, check robots.txt and inspect the active SEO plugin. Do not enable multiple sitemap-generation features at the same time to “fix” the error.
The sitemap opens for me, but Yandex does not process it
A browser may receive a different response from a bot because of a login session, cache, firewall, CAPTCHA, IP restriction, or redirect. Check the sitemap URL while logged out and make sure the file is publicly accessible, returns the correct content, and does not require private access. Do not disable all security measures just for testing.
URLs inside the sitemap use a different domain version
For example, the website uses https://www.example.com but the sitemap contains http://example.com. Check the website URL configuration, canonical URLs, HTTPS, and the sitemap-generating plugin. Do not make bulk changes before identifying the source that generates the URLs.
The sitemap contains URLs you do not want indexed
Do not treat a sitemap as a list of every URL that has ever existed. If the file contains draft pages, administrative pages, parameterized URLs, or content you do not want to make public, check the content-type settings in WordPress or your SEO plugin. Removing a URL from the sitemap does not by itself replace noindex, access controls, or handling for a URL that has already appeared in search results.
Exercise: Create a sitemap checklist
Fill it in with verified data:
- Official website URL:
[URL chính thức của website] - Verified sitemap URL:
[URL sitemap đã kiểm tra] - File type:
[sitemap đơn / sitemap index] - Verification date:
[ngày, tháng, năm] - Publicly accessible URL:
[đạt / chưa đạt] - HTTP response or status:
[kết quả đã kiểm tra] - Date submitted to Yandex Webmaster:
[ngày, tháng, năm / chưa gửi] - Status after submission:
[ghi nguyên văn] - Next action:
[theo dõi / sửa lỗi URL / kiểm tra định dạng / nhờ quản trị viên]
The exercise is complete when you can identify exactly which sitemap was submitted, which website it belongs to, how it opens, and what status Yandex displays. Do not enter “indexed” simply because Yandex accepted the sitemap.
Next step
After identifying and submitting the sitemap, the next step is to check robots.txt, the noindex tag, and other directives that could prevent bots from accessing the site or prevent URLs from appearing in search results. You can continue with Check robots.txt and noindex so Yandex can crawl the right pages to check these layers of directives.
If you want to check a specific post, use a verified public URL and record the date, response, Yandex status, and supporting evidence. A sitemap provides additional information about site structure and URLs; it does not guarantee indexing or rankings.
Reference source
- Using the Sitemap file — Yandex Webmaster.
- Sitemap files — Yandex Webmaster.
- Sitemap validator — Yandex Webmaster.
- The Sitemap directive — Yandex Webmaster.
- WP_Sitemaps – Class — WordPress Developer Resources.
- Version 5.5 – Documentation — WordPress.org.
