Here is how to add a website property to your Search Console account. Note that you must be able to prove that you own the site (or appropriate section of that site) in order to add it to your Search Console account. You can create a property that includes an entire domain (example.com) or a property that is limited to a single branch

Types of website properties

Search Console supports the following website property types:

Add a new property

To add a new property:

  1. Open the property selector dropdown in any Search Console page.
  2. Select + Add property on the dropdown.
  3. Choose the type of property to add:
    1. URL-prefix property
      • Specify the URL of your property exactly as it appears in the browser bar, including the final / mark. Any URLs that start with this prefix are included in your property.
      • If your site supports multiple protocols (http and https), you must add a separate property for each protocol. Similarly, if you support multiple subdomains (such as example.com, m.example.com, and www.example.com) you must add a separate property for each subdomain.
      • If you support other variations in your domain or protocol (m.example.com, http://example.com, https://example.com), consider telling Google which URLs are canonical.
      • If you need to track data separately for multiple subsections of your site, consider creating a Search Console property for each domain or subpath that you want to track separately, as well as a property that contains them all. For example, if you have a travel site with specific subfolders covering Ireland, France, and Spain, you might create accounts for the following URL-prefix properties:
        • https://www.example.com/ (or a Domain property for example.com)
        • https://www.example.com/france/
        • https://www.example.com/ireland/
        • https://www.example.com/spain/
        • http://m.example.com/ (for your mobile site)
    2. Domain property

      Specify the domain to cover. See below to learn the supported URL syntax and which URLs are included in your property. A Domain property requires DNS record verification to prove ownership, unless the property is on a Google product such as Blogger or Google Sites.

      Syntax

      A Domain property URL is a URL without a protocol (http/https) or any directory parts (/some/path/). Note that the public suffix (.org, .com, and so on) is part of the property name, so the Domain property “example.com” does not include “example.org” or “example.il.com”.

      The following URLs are all valid Domain property definitions:

      • m.example.com
      • example.com
      • support.m.example.org
      • support.m.example.co.es

      www is ignored. If you add www to your property name, the www will be ignored. For example, if you specify www.example.com as your property URL, the property will be created as example.com

      Coverage

      A Domain property aggregates data for all subdomains, protocols, and subpaths of the property. For example, if you define a Domain property as “example.com”, the data includes example.com, any subdomains of example.com (for example, m.example.com, support.m.example.com, www.example.com, and so on), and any subpaths of any of those domains, on http, https, and ftp.

      Here are some example Domain properties, and what they aggregate:

      This domain … … includes these URLs.
      example.com
      • http://example.com
      • https://example.com
      • http://m.example.com
      • http://a.b.c.example.com
      • https://m.example.com/any/path/here
      fish.example.com
      • http://fish.example.com
      • https://fish.example.com
      • https://support.fish.example.com
      • https://support.fish.example.com/any/path/here
      • NOT example.com
      example.co.cn
      • http://example.co.cn
      • https://example.co.cn
      • https://support.example.co.cn
      • https://support.example.co.cn/any/path/here
      • NOT example.co

       

      If you want to separate your Domain property data by subdomain, path, or protocol, use one of the following techniques:

      • Add a page filter in the Performance report to see data for specific protocols or subdomains
      • Create additional URL-prefix properties for segments of the Domain property; for example for the Domain property example.com, create additional properties for m.example.com, http://example.com, https://example.com/spain/, and so on.
    3. Google-hosted property

      If you own a Google-hosted property, such as a Sites or Blogger site, or a G Suite account, you can create either a URL-prefix or Domain property, as appropriate, depending on whether you own the domain or just a subpath below the domain. Verification will happen automatically, if you are signed in with the same account as the Google-hosted property.
  1. You will be given a selection of verification methods to use for your property. When you choose a verification method in Search Console you will be shown the required verification steps for that method. You can verify immediately or save your settings and resume the process later:
    • To verify immediately, follow the verification steps described without closing the popup window, then click Verify in the popup window. If it will take you some time to perform these steps, you can always save your settings and resume the process later (described next).
    • To pause and resume the process later, click Verify later to save your current state, close the popup, and verify your site at your convenience. After you have performed the required verification steps, finish verification by selecting the saved (but unverified) property in the property selector in the navigation bar, and selecting Verify.
  2. Data should begin to appear in your property in a few days. Data collection for a property starts as soon anyone adds the property in any Search Console account, even before verification. Data collection continues as long as any user has that property in their account, whether or not it has a verified owner. If your property has no data several days after verification, it is possibly because the site hasn’t been seen in Google Search, or that you have specified the wrong URL (for example, you specified http instead of https for your URL-prefix property).
Share

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.