Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Setup & site building · Guide

How to Connect Google Search Console to WordPress

Short answer

To connect Google Search Console to WordPress, add your site as a property in Search Console and prove you own it, either with Google's Site Kit plugin or by adding a verification tag. Site Kit is the simplest route: install it, connect your Google account, and it verifies the site and links Search Console for you. Then submit your sitemap under Indexing > Sitemaps and wait a few days for data to appear.

Key takeaways

  • A Domain property covers every protocol and subdomain of your domain; a URL-prefix property covers one exact address.
  • Site Kit verifies your site and links Search Console without any code.
  • The DNS TXT record is the only way to verify a Domain property.
  • WordPress has built a sitemap into core since 5.5, at /wp-sitemap.xml.
  • A single sitemap holds at most 50,000 URLs or 50 MB, according to Google.

What is Google Search Console?

Search Console is Google's tool that shows how Google finds, crawls, and lists your site in search results.

Open it at search.google.com/search-console. It reports which pages Google indexed, which search queries bring visitors, and which pages have crawl errors.

It does not rank your site or send traffic by itself. It shows data about how Google sees your site, so you can fix problems and track whether pages appear in search.

Search Console data also helps you judge which pages need work. If a page gets clicks but visitors leave fast, our guide on whether page speed affects SEO explains one common cause.

What do you need before you connect it?

You need a Google account, a live WordPress site, and admin access to the site.

Site Kit's plugin page states that your site must be live and publicly accessible, since a site in maintenance mode or behind a password cannot show data. The same page lists WordPress 5.2 or newer and PHP 7.4 or newer as the minimum versions.

Decide which property type to add. A Domain property covers every protocol and subdomain of your domain, while a URL-prefix property covers one exact address, such as https://example.com. Google's verification help page notes that Domain properties include data for all protocol and subdomain variations.

Use the Domain property when you run both www and non-www or http and https. Use URL-prefix when you only manage one exact address.

Anyone with a Google account can add a property, but only an owner can verify it. Google's verification help page says that if you cannot verify ownership, you should ask a current owner to grant you access instead.

How do you add your site as a property?

Open Search Console, click Add property, type your domain or URL, and click Continue.

  1. Sign in to Search Console with your Google account.
  2. Click Add property in the property selector.
  3. Pick Domain and type example.com, or pick URL prefix and type the full address.
  4. Click Continue and pick a verification method.

Search Console then shows the verification methods that fit your property. Google's verification help page says the page lists which methods are available and recommended for your site.

How do you verify ownership with Site Kit?

Install Site Kit by Google, connect your Google account, and the plugin verifies the site for you.

  1. Go to Plugins > Add New, search for Site Kit by Google, then install and activate it.
  2. Open the new Site Kit menu and sign in with your Google account.
  3. Follow the setup flow and connect Search Console when asked.
  4. Open the Site Kit dashboard to see Search Console data inside WordPress.

Site Kit is Google's official WordPress plugin, and its plugin page says it connects Analytics, Search Console, AdSense, and PageSpeed in one dashboard. Version 1.192.0, updated on 16 November 2026, was tested up to WordPress 7.1.

Each WordPress admin must connect their own Google account to see the plugin data, according to the same plugin page. If several people manage the site, each one signs in separately.

How do you verify ownership with an HTML tag?

Paste the meta tag Search Console gives you into your site header, then click Verify.

  1. In Search Console, pick the HTML tag method and copy the meta tag.
  2. Paste it in your theme header or your SEO plugin's verification field.
  3. Open your home page source and confirm the tag is there.
  4. Click Verify in Search Console.

Search Console looks for the tag on the page a logged-out visitor reaches when they open your property URL. Google's verification help page warns that the tag must sit on that page, not on a login screen.

Google uses the Google Site Verifier user agent to perform site verification, according to the same help page. If your security plugin blocks unknown user agents, allow that one through or verification will fail.

Do not remove the tag after verification. Google's help page explains that removing a verification token removes that owner's verification, so the property can drop out of your account.

How do you verify ownership with a DNS record?

Add the TXT record Google gives you at your domain registrar, then click Verify in Search Console.

This is the only way to verify a Domain property, according to Google's verification help page. The other methods cannot prove ownership of a whole domain.

  1. Pick the Domain name provider method in Search Console and copy the TXT record.
  2. Open your registrar DNS settings and add the TXT record at the root.
  3. Wait for the record to spread, then click Verify.

DNS records take time to spread. If verification fails, wait an hour and try again before you change anything.

MethodNeedsBest for
HTML file uploadFile upload to the site rootSites with file access
HTML tagEdit the site headerMost WordPress sites
Google Analytics codeAnalytics on the siteSites already running Analytics
Google Tag ManagerTag Manager snippet on the siteSites already running Tag Manager
Domain name provider (DNS TXT)DNS access at the registrarDomain properties; only method for them

How do you submit your sitemap?

Open Indexing > Sitemaps in Search Console, paste your sitemap URL, and click Submit.

WordPress has built a sitemap into core since version 5.5. The Make WordPress Core announcement says the sitemap index lives at /wp-sitemap.xml and covers public post types, taxonomies, author archives, and the home page.

If you run Yoast SEO or Rank Math, the plugin replaces the core sitemap with its own at /sitemap_index.xml. Our guide to fixing a sitemap that does not work covers the case where the address shows nothing.

Google's sitemap guide says a single sitemap is limited to 50 MB uncompressed or 50,000 URLs. The WordPress core index can hold up to 50,000 sitemaps, with each sitemap holding up to 2,000 entries, according to the Make WordPress Core announcement.

Submitting a sitemap is only a hint. Google's guide notes that it does not guarantee Google will download the sitemap or use it for crawling.

You can also list the sitemap in robots.txt. Google's sitemap guide gives the format: a line that reads Sitemap: followed by the sitemap URL. Google finds it the next time it crawls your robots.txt file.

How do you check that the connection works?

Open Search Console and look for a green verified mark, then confirm the property shows your site data.

Check Settings > Ownership verification to see your methods. Google's verification help page says you can add more methods there at any time.

Open the Performance report after a few days. If it lists search queries and clicks, Google is reading your site. If it is empty, check that the property matches your live address.

If the Sitemaps report shows Could not fetch, open the sitemap URL in a browser. Our guide to fixing a Yoast sitemap 404 covers the most common cause for Yoast users.

Open the Sitemaps report again after a week. It shows when Googlebot last read the sitemap and any processing errors, according to Google's sitemap guide.

Search Console shows search data, while Analytics shows what visitors do next. Our comparison of Google Analytics with privacy-friendly options covers the Analytics side.

How long does it take for data to appear?

Expect a few days before Search Console shows useful data, even when verification works at once.

Verification itself takes minutes once the tag or record is in place. Data is slower, because Google must crawl the site and process the results.

Site Kit's plugin page says it can take a few days after connecting a Google service for data to begin to display in your dashboard. New sites take longer than established ones.

Do not re-verify or remove the tag while you wait. The reports fill in on their own once Google has crawled the site.

The first data to appear is usually the sitemap status and the indexed page count. Query data takes longer, because it needs real searches to happen after verification.

What mistakes should you avoid?

Do not verify the wrong property, do not remove the verification tag, and do not submit a sitemap from a staging site.

  • A URL-prefix property for http://example.com will not show data for https://example.com. Add the exact address your visitors use.
  • Removing the HTML tag or DNS record can unverify the property. Keep the method you used in place.
  • A staging copy has its own address. Verifying it and submitting its sitemap sends Google to pages that should stay private.
  • Do not chase every warning at once. Fix crawl errors first, then work through coverage issues one group at a time.
  • If you move domains later, use the Change of Address tool. Google's help page says you must own both properties under the same Google account, and the tool works only on domain-level properties.

Frequently asked questions

Do I need Google Analytics to use Search Console?

No. Search Console works on its own, and its verification methods include Analytics as one option, not a requirement. You can verify with an HTML tag or a DNS record and never touch Analytics. Site Kit can link Analytics later if you want both tools in one dashboard.

Can I add more than one person to Search Console?

Yes. The property owner can add users with full or restricted access from Settings. Each person signs in with their own Google account. Site Kit works the same way: each WordPress admin connects their own Google account to see the data.

Why does Search Console say my site is not verified?

The tag or record is missing, on the wrong page, or not yet spread through DNS. Open your home page source and look for the meta tag, or check the TXT record at your registrar. DNS changes can take hours, so wait before you try again.

What is the difference between Search Console and Google Analytics?

Search Console shows how Google finds and lists your site in search, with queries, clicks, and crawl errors. Analytics shows what visitors do after they arrive, with sessions, pages, and conversions. Our guide comparing Google Analytics with privacy-friendly options explains the Analytics side.

Should I submit a sitemap if my site is small?

Yes. A sitemap helps Google find new pages fast, even on a site with ten pages. WordPress builds one for you at /wp-sitemap.xml, so submission takes a minute and costs nothing.

Sources

  1. Verify your site ownership Google Search Central
  2. Build and Submit a Sitemap Google Search Central
  3. Site Kit by Google WordPress.org
  4. Site Kit documentation Google
  5. New XML Sitemaps Functionality in WordPress 5.5 Make WordPress Core
  6. Change of Address tool Google Search Central

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test