How do you set up a Google Search Console account?
To set up a Google Search Console account, sign in with a Google account, add your website as a property, and verify that you own or manage it. Choose either a domain property for complete site coverage or a URL-prefix property for a specific version of your site, then submit your sitemap and allow Google to begin collecting data.
Set up a Google Search Console account by signing in with a Google account, adding your website as a property, verifying that you manage it, and submitting your XML sitemap. Choose a Domain property if you want to monitor the whole domain, or a URL-prefix property if you need to monitor a specific version or section of the site.
Before you begin
Make sure you can access the website’s DNS settings or content management system. The verification method available to you depends on the access you have. If another person or organisation manages your domain, you may need their help to add a DNS record. You should also identify the correct version of your website, including its protocol and subdomain. For example, the HTTP and HTTPS versions of a site are treated differently when using a URL-prefix property.
You do not need to create a separate Google account specifically for Search Console. You can use an existing Google account, provided it has the appropriate access and your organisation’s account policies allow it.
Open Google Search Console and add a property
- Sign in to Google Search Console with the Google account you want to use.
- Select Add property from the property selector.
- Choose either Domain or URL prefix.
- Enter the domain or URL exactly as required, then select Continue.
A Domain property covers the entire domain, including all subdomains and protocols. For example, it can include the HTTP and HTTPS versions of the site, as well as subdomains such as www or shop. Domain properties are generally the most complete option, but they require DNS verification.
A URL-prefix property covers only URLs that begin with the address you enter. This means that the protocol, hostname, path and trailing slash can affect the scope. A property for an HTTPS version will not automatically include the HTTP version, and a property for the main site will not necessarily include a separate subdomain or subdirectory. Use this option when you cannot edit DNS records or when you need reporting for a specific part of a website.
Verify ownership of a Domain property
Google normally verifies a Domain property by asking you to add a TXT record to the domain’s DNS configuration. Copy the verification record provided in Search Console and add it through your domain registrar or DNS hosting provider. The record must be added to the correct domain, not to a page within the website.
After saving the record, return to Search Console and select Verify. DNS changes can take time to become available, so verification may not work immediately. Check that the TXT value has been copied without alteration and that it has been added to the correct DNS zone. Do not remove the record after verification, as Search Console may use it to confirm continued ownership.
Verify ownership of a URL-prefix property
URL-prefix properties offer several verification methods. The most suitable method depends on how your website is managed:
- HTML file: download the verification file supplied by Google and upload it to the root directory of the selected website version. It must remain accessible at the specified address.
- HTML tag: copy the meta tag provided by Google into the head section of the site’s home page. This is usually handled through your content management system, theme settings or a site-wide code area.
- Google Analytics: use an existing Analytics installation if the same Google account has the required permissions and the tracking code is correctly implemented on the site.
- Google Tag Manager: use an existing container if the account and container permissions meet Google’s verification requirements and the container is installed correctly.
After implementing the selected method, return to Search Console and select Verify. If verification fails, check that you used the exact property address, that the file or tag is publicly accessible, and that caching or security settings have not removed or blocked it.
Choose the property that matches the site
Property selection affects the data you see. If the website uses redirects, several subdomains, international versions or both HTTP and HTTPS, a Domain property gives the broadest view where DNS access is available. You can also add URL-prefix properties when separate reporting is useful, such as monitoring a specific subdirectory or staging-related configuration that is accessible to Google.
Do not add a staging or development environment unless it is intended to be crawled and indexed. If a test site is publicly accessible, protect it appropriately and ensure it cannot create duplicate or misleading data in your reports.
Submit the XML sitemap
Once the property is verified, open the Sitemaps report and enter the sitemap path, such as sitemap.xml, rather than creating a complete address if Search Console already displays the site prefix. Submit the sitemap and check its status after processing.
A sitemap should contain the canonical, indexable URLs you want Google to discover. Confirm that it uses the correct HTTPS version, does not include blocked or redirected pages, and is not inaccessible because of login requirements or server rules. Submitting a sitemap is a discovery aid; it does not guarantee that every listed URL will be crawled or indexed.
If your website has several sitemap files, submit the sitemap index where possible. This allows Search Console to process the related sitemap files from a central location. Keep the sitemap updated as pages are added, removed or replaced.
Check that the setup is working
Search Console may not show complete performance and coverage data immediately after verification. Allow time for Google to crawl the site and process reporting data. In the meantime, use the inspection feature to test important URLs and check whether Google can access them.
Review the following configuration points:
- The preferred site version redirects correctly and uses HTTPS where appropriate.
- Important pages are not blocked by robots.txt, noindex directives or access controls.
- Canonical tags point to the intended versions of pages.
- The sitemap is available, valid and submitted to the matching property.
- Search Console is verified under an account that your team can maintain.
If the website changes domain, protocol, subdomain structure or ownership, update the relevant Search Console properties and verification records. Keep the original property where historical data remains useful, and add the new property before or during the migration so that indexing and performance changes can be monitored.
For ongoing SEO work, Search Console should be treated as a source of diagnostic and search performance data rather than a replacement for broader site checks. Use its reports alongside your technical audits, analytics implementation and campaign reporting to identify crawl issues, indexing changes, search queries and pages that may need optimisation.
Setting up a Google Search Console account involves adding your website as a property and verifying that you manage it. The property type you choose determines which URLs and versions of the site are included in your reports.
A Domain property provides the broadest coverage, including subdomains and both HTTP and HTTPS versions, but it requires access to your domain’s DNS settings. If you cannot edit DNS records, create a URL-prefix property instead. This covers only the exact protocol, hostname and path you enter, so check the address carefully.
- Use DNS verification for a Domain property.
- Use an HTML file, meta tag, Analytics or Tag Manager verification method for a URL-prefix property.
- Submit the XML sitemap that contains your canonical, indexable URLs.
After verification, allow time for data to appear. Use URL inspection to check important pages while Google processes your site, and keep the verification record in place so access is not lost.