If you have just published a page, made an important content change or deleted a URL, choose the tool based on the type of change: sitemap for a list of URLs updated regularly, Reindex pages in Yandex Webmaster for a URL that needs to be submitted manually, and IndexNow for an automated workflow that reports newly created, changed or deleted URLs. None of these methods guarantees that a URL will be indexed or rank.
By the end of this article, you will have chosen and used one method, recorded its response and identified the next check. The WordPress website SaibABC.Com is used as an example; this does not prove that the website is connected to or verified in Yandex, or that it has any particular status there.
Choose the method based on the situation
| Situation | Priority | Limitation to remember |
|---|---|---|
| Many URLs updated in a sitemap | Sitemap | Provides additional information about URLs and site structure; it is not an instruction to index each page. |
| A new post or an important post that was just edited | Reindex pages | Submits the URL to the recrawling process; it does not guarantee that the URL will appear in search results. |
| A website that frequently publishes, updates or deletes URLs | IndexNow | Automates notifications through an API or plugin; it still does not guarantee indexing. |
| A URL that has been deleted or redirected | IndexNow and the appropriate deletion-handling process | Reporting a change does not mean that the URL will be removed from search results immediately. |
Yandex describes sitemaps, requests to recrawl new or updated pages, and IndexNow as different notification methods (according to yandex.com). If you do not know which sitemap is active, first identify the actual WordPress sitemap before sending additional data.
Prepare the URL before submitting it
Where to work: in your browser and on the website you manage. Continue only after you have a real URL. For SaibABC.Com, retain the placeholders below if you have not yet verified the address:
[URL chính thức của website][URL bài viết công khai][URL trang đã xóa]
Open the URL in a private window, wait for it to finish loading and record the final address. The address must use the correct http or https, domain name and www www prefix, if applicable. Do not turn the sample website name into a real URL yourself.
- The page opens without signing in, and the content changes have been saved.
- The URL is not a draft, an administrative page or a members-only page.
- You have classified the change as new, updated, deleted or redirected.
- Preliminary checks
robots.txt,noindex, redirects and whether the page responds. - Record the date, reason for submission and method in your log.
If you cannot identify the canonical address or the page is not publicly accessible, stop. Submitting multiple URL variants will not clarify the cause.
Request a recrawl of one URL in Yandex
Open the form and submit the URL
- Where to work—Yandex Webmaster: select the correct website, then open the section named something like Indexing → Reindex pages. Menu names may differ by language or version; look for the form that lets you enter a URL to request a recrawl.
- Enter the data: enter the complete
[URL bài viết công khai]URL you verified. Do not enter a sitemap URL,robots.txtor an XML file in this form. - Submit and record: record the URL, time and displayed status immediately after clicking Submit.
Commonly displayed statuses include:
- In queue: The URL has been added to the queue.
- Request processed: The bot has visited the URL; this does not prove that the URL has been indexed.
- Error: Check the URL, server response, redirects, access permissions or the content received by the bot.
Yandex states that a queued status may take up to approximately three days, and search data may require additional time after the bot visits the page; this is not a guarantee for every website (according to yandex.com).
Check: The status code 200 OK only indicates that the server responded successfully at the time of that check. Keep the evidence for “submitted,” “bot visited,” “processed in search” and “appeared in results” separate.
What Is IndexNow, and When Should You Use It?
IndexNow is a protocol that allows a website to notify search engines directly when a URL is created, updated or deleted. The website sends the notification through an API or CMS plugin. Yandex requires the website to prove that it is managed by the site owner by placing a key in a publicly accessible file before accepting the notification (according to yandex.com).
IndexNow is worth considering when a website undergoes frequent changes, the publishing workflow knows exactly which URL has changed, or you need to reduce manual submission work. A small website with infrequent updates can use Reindex pages when needed; there is no need to install a plugin just to submit a single URL.
Submit a URL with IndexNow
Minimal API Workflow
- Create an IndexNow key as required by the service.
- Place the key file in a publicly accessible location on the website.
- Send the URL, key and key-file location to the IndexNow endpoint.
- Record the response code, then check the URL in Yandex Webmaster.
Run the command below in Terminal or PowerShell on a computer with curlinstalled. Replace https://example.com/bai-viet/, KEY_THAT_YOU_CREATED and the key-file URL with the actual values. Do not run the template as written:
curl --get "https://yandex.com/indexnow" \
--data-urlencode "url=https://example.com/bai-viet/" \
--data-urlencode "key=KEY_THAT_YOU_CREATED" \
--data-urlencode "keyLocation=https://example.com/KEY_THAT_YOU_CREATED.txt"The URL in the parameter url must be the URL being submitted; keyLocation it must point to the actual key file if the key is not placed in the default location. The expected result is for Terminal to display an HTTP response code. Record that code, along with the time and URL, in the log.
Yandex describes keys as containing 8 to 128 characters and using only letters, digits or hyphens; the API documentation also specifies limits for requests containing multiple URLs (according to yandex.com). A code 200 or 202 only reflects that the API accepted or processed the request according to the returned status; it is not evidence that the URL has been indexed. For 403, 422 or 429, check the key, URL, format and submission frequency against the specific response.
Implementing IndexNow on WordPress
Where to work: WordPress → the plugins area. Choose only one IndexNow solution. The official plugin on WordPress.org describes the ability to create a key file and send notifications when a URL is created, updated or deleted; check the WordPress version, update history, plugin permissions and logs before enabling automation (according to WordPress.org).
- Record which SEO plugin or tool currently generates the sitemap and sends URL notifications.
- Enable only one solution with IndexNow; do not enable multiple plugins with the same function.
- Check the URL scope: include only published public content, excluding drafts, administration pages and URLs deliberately excluded from search.
- If a test mode or limited scope is available, use it first.
- Update one test URL, open the plugin log, and record the URL, time and response.
- Check the URL in Yandex Webmaster; do not treat the plugin’s “sent” label as evidence of indexing.
If the plugin has no clear log or does not let you control the URL scope, keep the current configuration and use Reindex pages for manual submissions.
Deleted or Redirected URLs
IndexNow can notify search engines about a URL returning 404, 410, 301 or 302. This notification reports a change; it is not a request to remove the URL from search results immediately.
- Check the URL’s current HTTP status code.
- Determine whether the URL redirects to a replacement page.
- Remove the old URL from the sitemap if it is no longer valid.
- If the URL still appears and needs to be removed from search, use Yandex’s appropriate removal process.
Do not conclude that the URL has disappeared simply because a removal notification was submitted.
Tracking sheet and error handling
| Field | Value to record |
|---|---|
| URL | [URL bài viết công khai] |
| Change type | New / updated / deleted / redirected |
| Method | Reindex pages / IndexNow / sitemap |
| Time | [ngày và giờ thực tế] |
| Initial response | In queue / Request processed / HTTP status code / Error |
| Follow-up check | URL, response code, bot visit and search status |
| Conclusion | Submitted / bot visited / processed / no data yet |
Issues to isolate
- Wrong URL variant: compare HTTPS, www and the final address after the redirect.
- URL is not publicly accessible: open it in a private window; it must not require a login, CAPTCHA or internal permissions.
- Bot received an error: check the HTTP status code, redirects,
robots.txt,noindexand the security layer. Do not disable all security controls because of a single failure. - IndexNow key error: check the exact filename, key contents, public read permissions and
keyLocation. - Duplicate submission: check the plugin, cron or publishing workflow; keep one automated process and record the previous configuration before disabling redundant processes.
- Request processed but not visible in search: record the exact status and check the URL in the indexing inspection area; do not make bulk changes without evidence of the cause.
If you need to understand how to read the status area after verifying the website, read the Yandex Webmaster dashboard correctly.
Practical exercise and next steps
Choose a real, publicly accessible URL on a website you manage. If you do not yet have a verified URL, leave [URL bài viết công khai] unchanged and complete only the preparation section. Record the following:
- The final address after opening it while logged out.
- The change type.
- The selected method and why you did not choose the other two methods.
- The response immediately after submission.
- The status and evidence at the next check.
The exercise is complete when you can distinguish four statuses: submitted, bot visited, processed in search, and appeared in search results. If evidence is missing, record “no data yet.” The next article in the series covers how to classify errors, excluded pages and statuses that require waiting, using this tracking sheet.
Reference source
