Site verification

Prove ownership with DNS, a meta tag or a file; differences in speed and page limit.

Verification is not required; it is a perk. If you show that you own the site, the crawl is faster and larger. You can crawl any public site without verifying it.

#What verification changes

• The domain lock applies to everyone: the same domain can be in only one crawl at a time, no matter who requested it. While a crawl is queued or running, a new one does not start (no tokens are deducted).
• In the future, verification will also unlock extra features such as Search Console data; these do not exist yet.

#Verification methods

When you add a site, a code is generated just for you (a 32-character value starting with alatliseo-). In the dashboard, the Verification code card in the Site settings tab shows the code and ready-made values. One of the three methods is enough; below, write your own code in place of CODE.

#1. DNS TXT record

Add a TXT record to the DNS of the domain. The record name can be _alatliseo.example.com or example.com.

alatliseo-dogrulama=CODE

It can take a while for DNS changes to propagate.

#2. Meta tag

Add it to the <head> section of the home page. The tag must be within the first 512 KB of the page. Both https://example.com/ and https://www.example.com/ are tried.

<meta name="alatliseo-dogrulama" content="CODE">

#3. File

Upload a .txt file named after your code to the root directory of the site, with your code as its content.

https://example.com/CODE.txt

Content of the file: CODE

#How is verification checked?

• After adding the code, you run the verification in the Site settings tab. If it does not match, it says which method failed and why.
• Verification is checked again every time a crawl starts. If you remove the proof from your site, the site counts as unverified and the crawl runs with the unverified-site rules (speed, page limit, daily limit). Keep the code on your site.
• More than one user can verify the same domain (e.g. an agency and its client).
• Verification requests go only to ports 80 and 443; requests to local and private network addresses are rejected.