How do I verify ownership in Search Console?

To verify ownership in Search Console, add your website as a property, select an available verification method, and complete the required steps. You can usually verify through a DNS record, an HTML file, an HTML tag, or an analytics-related setup, depending on your access and property type.

Ownership in Search Console is verified by proving that you control the website or part of it that you have added as a property. Start by adding the correct property, choose a verification method available for that property, complete the method’s instructions, and then select Verify. Once verification succeeds, you can access the property’s performance, indexing and security data.

Before starting, make sure you are signed in with the account that should manage the property. You will also need suitable access to the website, its domain’s DNS settings, or an existing measurement service, depending on the method you choose.

Choose the correct property type

Search Console supports two main property types:

  • Domain property: covers all subdomains, protocols and URL paths within the domain. For example, it includes both HTTP and HTTPS versions and subdomains such as www. Domain properties are verified through a DNS record.
  • URL-prefix property: covers only URLs that begin with the exact prefix entered. A property using https://www.example.co.uk/ does not automatically include the HTTP version, another subdomain or a different folder. It offers several verification methods.

Use a domain property when you control the domain’s DNS and want a complete view of its variations. Use a URL-prefix property when you need to verify a specific version, subdomain or path, or when DNS access is unavailable.

How to add a property

  1. Open Search Console and select the property selector.
  2. Choose + Add property.
  3. Select Domain or URL-prefix.
  4. Enter the domain or full URL, following the format requested on screen.
  5. Select Continue to see the verification options.

Check the property address carefully before verifying it. Common errors include entering the wrong protocol, omitting a subdomain, including a page path when a domain property was intended, or adding a trailing section that does not represent the required URL prefix.

DNS record verification

DNS verification is the required method for a domain property and can also be used for a URL-prefix property. Search Console provides a TXT record containing a unique verification value. Add that record to the DNS settings for the relevant domain, then return to Search Console and select Verify.

  1. Copy the TXT record supplied by Search Console.
  2. Open the DNS management area provided by your domain registrar or hosting provider.
  3. Create a TXT record at the domain or host specified by the instructions. Some providers use an @ symbol or leave the host field blank for the root domain.
  4. Save the record without changing the verification value.
  5. Return to Search Console and select Verify.

DNS changes may not be recognised immediately. If verification fails straight after saving the record, confirm that the TXT value was copied exactly and allow time for the record to become available before trying again. If other TXT records already exist, add the new record rather than replacing records needed for email or other services.

Keep the DNS record in place after verification. Removing it can cause ownership to be lost when Search Console checks the property again.

HTML file verification

HTML file verification is available for URL-prefix properties. Search Console supplies a file that must be uploaded to the root directory of the exact website property being verified.

  1. Download the verification file from Search Console.
  2. Upload it to the website’s root directory using your hosting control panel, file manager or an FTP tool.
  3. Check that the file can be reached at the exact URL shown by Search Console and that it has not been renamed or modified.
  4. Return to Search Console and select Verify.

The file must remain accessible after verification. Do not upload it only to a subdirectory, place it behind a login, or remove it when the check has completed. Caching, redirects, security rules and content delivery settings can also prevent Search Console from retrieving the file.

HTML tag verification

HTML tag verification uses a meta tag supplied by Search Console. Add the complete tag inside the <head> section of the homepage for the URL-prefix property, then publish the change and select Verify.

The tag must be present in the page source returned to visitors, not only in an editing interface or in code that appears after a browser-side script runs. If your website uses a content management system, add it through the site-wide settings or an appropriate SEO configuration area. Clear any page or server cache before retrying verification.

The tag should remain on the homepage after verification. Changing themes, templates or site settings can remove it, so check the verification status after major website changes.

Verification through an existing service

Search Console may offer verification through an existing analytics or tag-management setup. These methods depend on the signed-in account having the required permissions and the service being correctly installed on the same property. Select the available method and follow the instructions shown in Search Console.

If this option is unavailable, check that you are using the account with administrative access, that the tracking or tag code is present on the correct site version, and that the property URL matches the website configuration. DNS, HTML file or HTML tag verification is usually more suitable when access to the existing service is limited.

If verification fails

  • Confirm that you selected the correct property type and entered the correct URL or domain.
  • Check that the verification file, meta tag or DNS record exactly matches the value supplied by Search Console.
  • Make sure the change has been published and is publicly accessible without a login.
  • Check redirects, caching, firewall rules and security plugins that might block the verification request.
  • For DNS verification, confirm that the record was added to the authoritative DNS provider rather than only to a hosting control panel.
  • For HTML verification, confirm that the file or tag is on the exact protocol and subdomain being verified.
  • Try another verification method if you have the required access.

After successful verification, you can add other trusted users through the property’s user and permissions settings. Each person should use their own account rather than sharing login details. Keep at least one verification method active and review ownership permissions when staff, agencies or suppliers change.

Verification confirms control of the property; it does not guarantee that every URL will be indexed or that data will appear immediately. Search Console reports depend on the property scope, available crawl data and the website’s configuration. If the property is missing after verification, select it from the property list and check that you are using the account that completed or received access to the verification.

Ownership verification in Search Console confirms that you control the website property you want to monitor. Choose the property type carefully: a domain property requires DNS access and covers the domain’s protocols and subdomains, while a URL-prefix property covers only the exact address entered and can also be verified with an HTML file, HTML tag or an existing service.

Keep the verification record, file or tag in place after verification. Search Console may check it again later, and removing it can cause ownership to lapse. If verification fails, confirm that the code is unchanged, publicly accessible and applied to the correct domain, protocol and subdomain.

Need help verifying your Search Console property?

If you need help verifying your Search Console property, contact our support team with the property type and verification method you are using. We can help you identify the cause of failed DNS, HTML file or HTML tag verification.