Sébastien Laframboise

Add a WordPress site to Google Search Console and verify its ownership

Add a WordPress site to Google Search Console and verify its ownership

Setting up Google Search Console for WordPress lets you track your site’s presence in Google results. You can then check page indexing, spot issues, and analyze the searches that generate clicks.

The first step is to add a property and prove that you actually control the site. This choice matters, because a poorly defined property can split your data across multiple URL variants.

What is Google Search Console for WordPress used for?

Google Search Console provides data on crawling, indexing, and how your site appears on Google. The tool doesn’t replace WordPress or your analytics tool. It’s used to understand what Google sees before a visitor reaches your site.

After verification, you can view clicks, impressions, queries, and pages in the Performance report. You can also use URL Inspection to check the indexing status of a specific page. Google describes these features in its Search Console beginner’s guide.

Before creating your property, make sure your site’s primary address is stable. If you’re still changing your permalink structure, start by see the guide to. This will help you avoid monitoring URLs that change shortly after launch.

Choosing between a domain property and a URL-prefix property

Search Console offers two approaches. A domain property is generally better when you control the domain’s DNS settings. A URL-prefix property works when you want to track an exact site version or can’t change DNS.

Domain property: the most comprehensive option

A domain property aggregates data for all URLs under the same domain. It includes both HTTP and HTTPS, versions with or without www, and subdomains. For example, a property for example.com could cover https://www.exemple.com/ and https://blog.exemple.com/.

Google recommends this approach when possible, since it gives an overall view rather than separate reports for each variant. Verification, however, requires adding a DNS record—typically a TXT record—at the provider that manages your domain. See the official explanation on domain properties in Google Search Console before you start.

URL-prefix property: a precise scope

A URL-prefix property tracks only addresses that begin exactly with the entered URL. Thus, https://exemple.com/ does not automatically represent https://www.exemple.com/, http://exemple.com/ or a subdomain.

This option is useful if you manage a specific section, like https://exemple.com/boutique/, or if you don’t have DNS access. In return, you must carefully choose the canonical URL actually used by your WordPress.

Add your property to Google Search Console

  1. Open Google Search Console with the Google account that will administer the site.
  2. In the property selector, choose the option to add a property.
  3. Select Domain if you control the DNS, or URL prefix if you need to verify a specific address.
  4. For a domain property, enter only the domain name, without https://, without www and without a path.
  5. For a prefix property, copy the full address shown in WordPress, including https:// and the trailing slash.
  6. Proceed with the verification method proposed by Google.

Don’t create multiple properties by reflex. If you have DNS access, a domain property reduces omissions across variants. However, keep a URL-prefix property if you have a specific tracking need or an existing verification method.

Verify a domain property using DNS

Google provides a verification value. You must add it as a TXT record in the domain’s DNS zone. That zone is often at the domain registrar but can also be managed by your host or a separate DNS service.

Copy the value exactly as Google displays it. Don’t add quotes or extra characters unless the DNS interface requires them. Then save the change and return to Search Console to start verification.

DNS updates can take some time to propagate. If verification fails immediately, first check that you modified the correct DNS zone and that the value is complete. Avoid deleting the TXT record after validation, as Google may recheck ownership later.

Verify a URL-prefix property in WordPress

For a URL-prefix property, the HTML tag method is often convenient with WordPress. Search Console gives you a meta tag containing a unique value. This tag must appear in the <head> section of the site’s homepage.

Google confirms that the tag google-site-verification can be used to verify site ownership. The attribute values name and content must match exactly those provided. See the documentation on Meta tags supported by Google for this requirement.

Add the tag without needlessly modifying the theme

In WordPress, use a header script slot if your theme or an existing plugin provides one. Paste the full tag, save, then clear your site and CDN cache if needed.

Avoid inserting the tag directly into parent theme files. An update could erase your change. Also, don’t install a plugin just for this short verification if an existing solution already meets the need.

Before clicking «Verify,» load your homepage in a browser. Use the view source function, then search for google-site-verification. If the tag doesn’t appear, Google won’t be able to confirm your ownership.

Avoid URL variant errors

The most common errors concern the address added in Search Console. Compare it with the address configured in WordPress and with the one shown in the browser bar after any redirect.

  • HTTP or HTTPS: use the secure version if your site redirects to HTTPS.
  • www or non-www: follow your site’s canonical variant.
  • Subdomain: a subdomain, such as store.example.com, is a separate address in a prefix property.
  • Subdirectory: a prefix property can target a specific section, but it does not cover the rest of the domain.

Consistent navigation also helps Google and your visitors reach your important pages. If needed, review how create a clear, effective WordPress navigation menu to check the visible links on your site.

Which reports should you review after verification?

Initial data may be limited on a new site. Still start by checking the status of an important page with the URL inspection tool. You’ll learn whether Google knows the address, if indexing is possible, and, in some cases, why a page isn’t appearing yet.

Next, view the Performance report to track clicks, impressions, click-through rate, and average position. Focus on trends and pages that are gaining or losing visibility. A request to index doesn’t guarantee immediate appearance in results; Google says crawling can take from a few days to a few weeks.

Finally, submit your sitemap only after you’ve validated its content. The sitemap helps Google discover URLs, but it doesn’t replace accessible pages or a good internal structure. Follow the method explained in Check and fix the WordPress XML sitemap to submit the correct sitemap index.

Manage access carefully

After verification, review the list of users and permissions in the property settings. Grant access only to people who need it. If a vendor or agency stops working on your site, remove their access and check for unused property tokens.

This initial check establishes a reliable baseline. You can then use Google Search Console WordPress to monitor indexed pages, detect issues, and choose data-driven improvements rather than guessing.