If your website has already been added to Yandex Webmaster and is waiting for verification, you only need to complete one suitable method. With WordPress, a meta tag is often the most practical starting point if you can insert code into the <head>. If you do not have that access, consider using an HTML file or DNS TXT record.
After completing this article, you will identify the correct URL, choose a method based on your actual access, add the correct code supplied by Yandex to the website, and check the status after clicking Verify. This article does not claim that the example website SaibABC.Com has been verified.
Before changing WordPress, uploading a file, or modifying DNS, record the current configuration and make sure you have a way to undo the change. Do not use an unverified verification code, URL, or status as factual evidence.
Check that you have selected the correct website before choosing a method
In management workflows, different protocol versions and domain prefixes may be treated as separate addresses. Therefore, https://example.com and https://www.example.com should not be entered interchangeably; compare the final address shown in your browser with the website selected in Yandex Webmaster (according to yandex.com).
- Open the website in a private window.
- Record the final address after the page finishes loading:
httporhttps, and whether it haswwwor not. - Open that exact address in Yandex Webmaster and confirm that it is the website awaiting verification.
- Record the access you have: WordPress, hosting/server, DNS, or content-editing access only.
For SaibABC.Com, keep the placeholder [URL chính thức của website] until the actual address has been checked. The example website's name does not prove that the website has been added or verified.
Choose a method based on the access you have
| Access available | Suitable method to consider | Evidence to check |
|---|---|---|
Can edit code in the <head> of the WordPress homepage | Meta tag | The tag appears in the public HTML, between <head> and </head>. |
| Can access the document root serving the website | HTML file | The file has the correct name and content and opens at a public URL. |
| Manage the domain's DNS | DNS TXT record | The record has the correct type, name/host, and value supplied by Yandex. |
| Can only write posts or edit content | Not enough access to choose independently | Ask the WordPress administrator, hosting manager, or DNS administrator for help. |
Yandex documentation describes commonly used methods, including a meta tag on the homepage, an HTML file in the document root, and a TXT record in DNS; you only need to complete one method that matches your access (according to yandex.com).
Quick selection rule: If you can insert code into the head section, start with the meta tag; if you can upload files but cannot edit WordPress, choose the HTML file; if you manage only the domain, choose DNS TXT. If you do not have the necessary access, note who needs to help instead of making trial changes.
Main workflow: verify with a meta tag in WordPress
The meta tag is a line of HTML supplied by Yandex. The tag must be output in the <head> of the publicly accessible homepage, not in the post content, footer or an HTML block inside the page body.
Obtain the correct verification tag
- Where to work — Yandex Webmaster: open the website awaiting verification and go to the access-management or ownership-verification screen.
- Choose the method labelled, or equivalent in meaning to, Meta tag. The button name may differ depending on the interface language and version.
- Copy the complete tag supplied by Yandex. The example below illustrates the structure only; it is not the code to use:
<meta name="yandex-verification" content="[mã xác minh do Yandex cung cấp]" />
Replace [mã xác minh do Yandex cung cấp] with the exact value in your account. Do not create a string yourself, use a code from another website, rename the property or omit any characters.
Insert the tag into the head section
Where to work — WordPress: use an available administration field or tool to insert the code into the head. The exact menu name depends on the theme, plugins and website implementation, so do not follow an unverified menu path.
- If there is a field for head code, paste the complete tag into that field and save it.
- If you use a code-management plugin, first confirm that the code is output on the publicly accessible homepage, rather than being visible only in the administration area.
- If you edit the theme or child theme, back it up first and continue only if you know how to undo the change. WordPress provides hooks
wp_headthat allow themes or plugins to add content to the head section; this is a technical mechanism, not the name of a required menu (according to WordPress.org).
Do not edit the active theme file directly simply because it is the only method you know. Direct changes may be lost when the theme is updated. Before saving, record the insertion location, the previous content and the restoration procedure.
Check the code in the public HTML
- Where to work — browser: open the publicly accessible homepage, not the WordPress administration area.
- Open View Page Source or View source. This is the HTML sent by the server to the browser, which differs from the editor view.
- Find
yandex-verificationor part of the verification code. - Confirm that the tag is between
<head>and</head>, and that thecontentvalue matches the code supplied by Yandex character for character.
Expected result: you can see the correct tag in the homepage source code. If it is missing, check whether the change was saved, the scope of the code-insertion tool and the cache. If you have cleared the cache according to your administration procedure and the tag is still absent from the HTML, stop and ask an administrator to investigate; do not keep clicking Verify repeatedly.
Click Verify and read the status
- Where to work — Yandex Webmaster: return to the verification screen for the correct website.
- Click the button labelled, or equivalent in meaning to, Verify or Verify.
- Record the URL, method, date of the action and displayed message in your log.
A successful status means that Yandex has accepted the evidence that you control the website. It does not prove that the website has been crawled, indexed, ranked or received additional traffic.
Two alternative methods
HTML file in the root directory
Choose this method if you have hosting or server access to place a file in the root directory currently serving the website. The file name and contents must come from the Yandex screen; do not choose a name or create substitute contents yourself.
- Where to work — Yandex Webmaster: select the HTML-file method and record the supplied file name and contents.
- Where to work — hosting/server: place the file in the website’s correct root directory, not arbitrarily in a subdirectory.
- Where to work — browser: open
https://example.com/[tên-tệp-do-Yandex-cung-cấp]replace both the domain name and the file name with the verified details. - Confirm that the URL is publicly accessible, does not require sign-in, does not return the homepage instead of the file, and serves the content exactly as required.
- Return to Yandex Webmaster and click Verify.
If the URL returns a 404 error, requests sign-in, serves the homepage, or redirects unexpectedly, stop. Check the root directory, file name, read permissions, and server configuration; do not delete or modify other files. After verification, if your administrative policy permits removing the file, record the action and delete only the verification file.
DNS TXT record
Choose DNS TXT when you manage the domain’s DNS or can ask the appropriate DNS administrator to do it. This method does not require changes to WordPress, but a mistake could affect other records.
- Where to work — Yandex Webmaster: select the DNS method and copy the supplied name/host and TXT value exactly.
- Where to work — the domain registrar or DNS provider: create a record of type
TXTusing Yandex’s name/host and value exactly as provided. - Before saving, record the relevant DNS configuration and make sure you are working with the authoritative DNS provider.
- Check that the record has appeared in the public DNS, then return to Yandex Webmaster and click Verify.
If Yandex cannot find the record, check the record type, name/host, value, domain, and DNS provider. DNS may not update immediately; no fixed timeframe applies to every provider. Do not delete existing records in bulk. If you need to roll back the change, delete only the specific verification record after assessing the impact and recording its previous value.
Acceptance checklist before concluding

| Check | Pass condition | If it does not pass |
|---|---|---|
| Website address | The protocol and www/non-www prefix are correct. | Stop and verify the official URL. |
| Method | Choose only one method that matches your actual permissions. | Change methods or ask someone with the required permissions. |
| Meta tag | Appears in the <head> of the homepage HTML. | Check the insertion location, whether the change was saved, and the cache. |
| HTML file | The file URL is publicly accessible and the content is exact. | Check the root directory, file name, and read permissions. |
| DNS TXT | The type, name/host, and value are correct. | Check the DNS provider and update status. |
| Yandex Webmaster | The ownership confirmation screen shows confirmation. | Record the error verbatim before making further changes. |
If the browser can open the page or file but Yandex reports that it cannot access it, review the response provided by the tool and check security layers, sign-in requirements, redirects, or access restrictions. Do not disable all security controls just to test verification.
Common errors and misconceptions
- WordPress permissions do not imply DNS permissions: permission to publish posts may not allow you to insert code in the header, install plugins, or edit files.
- Inserting the tag in post content is the wrong location: the tag must be output in the
<head>of the homepage. - Adding a website is not verification: adding an address only puts the website on the list; you still have to provide proof that you control it.
- Verification is not indexing: after verification, crawling and indexing remain separate statuses.
- You do not need to use all three methods: one valid piece of evidence accepted by Yandex is sufficient.
- Do not use screenshots of an outdated interface as evidence: menu names may change; rely on the screen’s purpose and the results of actual checks.
- robots.txt does not protect private data: it provides instructions to bots and does not replace authentication or access-control mechanisms.
Exercise: complete one method and save the evidence
Apply this to a website you manage; do not use fictional data for the final result. Select exactly one method and complete the following template:
URL đã thêm vào Yandex Webmaster: [URL chính thức của website]
Phương pháp đã chọn: [thẻ meta / tệp HTML / DNS TXT]
Quyền dùng để thực hiện: [WordPress / hosting / DNS]
Bằng chứng trước khi bấm xác minh: [mã nguồn / URL tệp / bản ghi DNS]
Kết quả Yandex: [đã xác minh / chưa xác minh / thông báo lỗi]
Ngày kiểm tra: [ngày, tháng, năm]
The exercise is complete when you can answer three questions: Where is the evidence located? Can people outside your organization access it? What status does Yandex display after the check? If verification has not succeeded, preserve the error message and proceed to troubleshooting; do not change DNS or disable security controls broadly.
Next step
After successful verification, retain the method log and the person responsible. This result allows you to continue checking the website’s reports in Yandex Webmaster, but it is not evidence that the URL has been crawled or indexed.
If verification is unsuccessful, record the error message verbatim and identify whether you are using a meta tag, HTML file, or DNS TXT record. Then go to Verification Troubleshooting using the series shortcode: Can’t Verify Your Website on Yandex? Find the Failure Point
For SaibABC.Com, the series records a status only after the URL, code or record, and result in Yandex Webmaster have been verified in practice.
Reference source
- Verifying the site rights — Yandex Webmaster.
- Getting started — Yandex Webmaster.
- My sites — Yandex Webmaster.
- wp_head – Hook — WordPress Developer Resources.
- wp_head() – Function — WordPress Developer Resources.

