How to Add Google Search Console to WordPress (Step-by-Step)

Summarize this article with AI

ChatGPT Claude Perplexity Google AI

You're stuck on the ownership screen, and the WordPress menu in front of you looks nothing like the one in the tutorial. There's more than one answer to how to add Google Search Console to WordPress, and the right one depends on your setup. You'll find plugin connections and manual verification here, plus error checks and what to hand off after setup.

I've handled Search Console verification and analytics on WordPress sites, and on Wix and Ghost ones as well. Follow along and you'll confirm ownership in a way that survives site changes. Indexing gets its own check.

How to add Google Search Console to WordPress: quick answer

Add your website in Google Search Console, then verify ownership through a plugin connection, an HTML tag or file, DNS, or an eligible Google Analytics or Google Tag Manager setup.¹ First, check WordPress → Settings → General → Site Address (URL). For a URL-prefix setup, enter that public address with its matching http or https and www or non-www form.

Whatever tools you already have are the natural starting point (plus a Google account to sign in with). Going through a plugin means being a WordPress Administrator. DNS or file verification is different; there, what you need is access to the DNS or the files.

Your setup or goal	Start here	Access or prerequisite
Want Google's WordPress connection and dashboard views	Site Kit by Google	WordPress Administrator; public production site
Already use Yoast SEO	HTML tag in Site connections	Plugin settings access; public homepage
Already use Rank Math	Webmaster Tools code field or Analytics connection	Plugin settings access; free Rank Math account for the connection
Already use All in One SEO	Connect to Google Search Console button	Plugin settings access and Google sign-in
Use Jetpack or WordPress.com	Jetpack's Traffic verification settings	Manual tag or available auto-verification
Need coverage across protocols and subdomains	Domain property with DNS	DNS provider access
Have file access and prefer no added plugin	HTML verification file	Ability to publish at Google's specified URL
Need a header field without an SEO plugin	WPCode Lite	Plugin installation and settings access
Already have Analytics or Tag Manager installed	Google's matching verification option	Correct account permissions and snippet placement

Key takeaways:

• A WordPress Domain property requires DNS verification.² A URL-prefix property supports the other Google verification options too.
• Plugin sign-in can handle ownership without manually pasting a token. Check its requirements before starting.
• Successful verification confirms ownership, not indexing. Keep the token, check WordPress's indexing setting, and review the reports afterward.

Choose the right website property

In Google Search Console, open the property selector and choose + Add property → Website property.² The dialog also offers Platform and Google-hosted properties; WordPress uses the website route.

Domain property: covers every variant of your domain (www, non-www, http, https, and subdomains) under one property.² For WordPress, this requires DNS verification at your provider.¹

A URL-prefix property includes URLs that start with the specified prefix, including its protocol.² It supports all five verification methods in this guide: HTML file upload, HTML tag, DNS, Google Analytics, and Google Tag Manager.¹

For example, http://example.com/ does not include https://example.com/ or http://www.example.com/.² Start with a URL-prefix property when using the manual tag, file, Analytics, or Tag Manager instructions below; choose Domain when combined coverage matches your reporting needs and you control DNS.

Use the Site Address (URL), not the WordPress Address: when WordPress is installed in its own directory, the two differ, and visitors reach the site at the Site Address.³ If you need to gather credentials first, Verify later saves the unverified property.²

Use Site Kit by Google

Site Kit takes care of ownership verification for you, then puts a simplified view of your Google Search Console data right inside the WordPress dashboard. Google's own verification help points WordPress users to it and calls it the only plugin Google officially sponsors.¹ No SEO plugin hooked up to Google yet? Then this is your route.

Its setup requires a WordPress Administrator, WordPress 5.2 or later, PHP 7.4 or later, and a modern browser.⁴ Staging or private sites won't do. Think live, public site with the WordPress REST API switched on. Got a password wall, maintenance mode or coming-soon page up? Pull it down before you continue, and give Tools → Site Health a look too.

1. Install and activate Site Kit by Google in WordPress.
2. Open Site Kit → Dashboard, then click Sign In with Google.
3. When Google asks, pick whichever account should own the connection and allow the permissions it requests.
4. Complete the verification and Google Search Console connection prompts.

Site Kit checks whether the site is already verified.⁴ When verification is needed, it first tries a virtual HTML verification file, then falls back to an HTML tag if that attempt fails.⁵ And if the site isn't in Google Search Console yet, Site Kit adds it.

Site Kit creates a URL-prefix property when there's no Search Console property already tied to the site. An existing verified URL-prefix property connects automatically. A verified Domain property can connect when the site URL is at the root level and no manually verified URL-prefix property exists.⁵

Before you finish, check which property Site Kit connected to under Site Kit → Settings → Connected Services → Search Console.⁵ When Site Kit can't find its token, start with the error checks further down. If that doesn't fix it, Site Kit's help suggests verifying manually in Google Search Console and trying again.

If a WordPress SEO plugin is already installed

Find the plugin you've got installed below and ignore the others. Some of them sign in with Google for you, while others just want the HTML tag pasted in.

The HTML tag route for Yoast SEO and Rank Math

You'll want a URL-prefix property here, not a Domain one. The verification tag belongs in the <head> of the homepage shown to a visitor who isn't logged in.¹ That homepage cannot require authentication.

1. In Search Console's verification screen, open the HTML tag option and copy the meta tag it gives you.¹
2. Open the matching plugin setting:
   • Yoast SEO: Yoast SEO → Settings → Site connections, then paste the code under the Google field.⁶
   • Rank Math SEO: General Settings → Webmaster Tools tab → Google Search Console, then paste your verification code.⁷
3. Save the plugin settings.
4. Then comes the check: search the public homepage's source for google-site-verification. Your token should show up in the <head>.
5. Now go back to Google Search Console and click Verify.

Yoast outputs its meta tag in the homepage's <head>. It moved these settings in Yoast SEO 20.0 (January 2023), so a tutorial that sends you to SEO → Dashboard → Webmaster Tools predates the current menu.⁸

Rank Math: connect Google services

Rank Math's Analytics module can create and verify the property in Google Search Console automatically if you have not done so already.⁷ This connection needs a free Rank Math account.

1. Turn on the Analytics module from the Rank Math SEO dashboard.
2. Open General Settings → Analytics → Connect Google Services.
3. Complete the account connection, then check which property Rank Math selected in the Search Console section.

All in One SEO: use the connection button

All in One SEO's Connect to Google Search Console button adds and verifies the property and submits its generated XML sitemap.⁹ AIOSEO's current documentation uses this sign-in workflow rather than a field for pasting Google's code.

1. Open All in One SEO → General Settings → Webmaster Tools.
2. In the Google Search Console block, click Connect to Google Search Console.
3. Sign in to Google when prompted, grant the access it asks for, and then click Complete Connection.
4. Look at the property in Search Console, and at its sitemap submission, before you submit that sitemap again by hand.

Jetpack and WordPress.com

Under Jetpack → Settings → Traffic → Site verification, Jetpack offers both automatic and manual Google verification. Next, enable Verify site ownership with third-party services and pick Google. Prefer the manual route? Paste Google's meta tag, save, and only then click Verify in Search Console.

WordPress.com users will find the Google box under Site verification services, either in Jetpack → Traffic or in Jetpack → Settings → Traffic. Once the meta tag is pasted in, click Save settings. Plugin-enabled WordPress.com sites on Business and Commerce plans can use Auto verify with Google instead.

WordPress.com also supports a Domain property using a TXT record in Domains → DNS records. Its guide directs users to choose Any DNS Provider in Search Console. The HTML-tag and DNS routes apply to WordPress.com too.

Verify without an SEO plugin

An SEO plugin is optional. Choose URL prefix for the manual tag, file, Analytics, or Tag Manager method; each needs a publicly accessible page or file. Use DNS for a Domain property.

WPCode: place the tag in the header

If you don't run an SEO plugin, install WPCode (free, formerly Insert Headers and Footers) instead of hand-editing theme files.¹⁰ Use WPCode Lite for the header field.

1. First, get WPCode installed and activated.
2. Open Code Snippets → Header & Footer → Header.
3. The whole HTML meta tag from Google Search Console goes in that field, then hit Save Changes.
4. While logged out, the homepage source should show your token sitting in the <head>. If it is, click Verify in Search Console.

Why not just edit functions.php instead? That file belongs to the theme, which is the problem. Even a child theme's code stops running once that child theme is no longer the active one.

HTML file: test the exact verification URL

Download the HTML verification file from Google Search Console without changing its filename or contents.¹ Your host's file manager works for the upload, or any file-transfer tool you like. The file has to load at the exact URL listed in the verification details, because that's the only place Google checks.

That may or may not be the folder holding the WordPress core files. The URL Google requests is what decides. Ask your host if you can't tell which folder serves it. Then test it:

1. Open Google's exact file URL (something like https://example.com/google1234567890abcdef.html) in an incognito window.
2. Confirm that the expected file loads without a login or password prompt.¹
3. When it loads without a hitch, return to Google Search Console and click Verify.

URL not loading? Look at the published location and the server's response first; the fix depends on what you find there. Keep the file after verification succeeds; removing it causes loss of that verification.¹

DNS TXT record: verify at the provider

DNS verification of a URL-prefix property also automatically verifies the Domain property.¹ For a Domain property, it's the only route.²

If Search Console lists your DNS provider, select it, click Start verification, and sign in to complete that provider's verification process.¹ Otherwise, choose Any DNS provider and add the TXT record manually:

1. In Search Console, choose the DNS record verification option and copy the TXT value provided.¹
2. Log in to the company that runs your DNS. That's your registrar or DNS host, which may not be your WordPress host.
3. Add a new TXT record at the root of your domain with the value Google gave you.¹
4. Leave the Host/Name field blank or set it to @, whichever your DNS provider's documentation says, and put the TXT string in the value field.¹ Save, then return to Search Console and click Verify.

Google says a provider can take up to two or three days to start serving the record.¹ Verify failed? Run Google Admin Toolbox's TXT lookup to see what's being served, and if the value isn't visible yet, wait a day or two and retry. Coverage only flows down. A verified root domain takes its subdomains along with it, while verifying a subdomain leaves the parent domain unverified.

Already on Google Analytics or Google Tag Manager

These URL-prefix options work with an existing installation. Sign in to Google Search Console with the same Google account that has the required Analytics or Tag Manager permissions.¹

Verification option	Permission required	Placement Google requires
Google Analytics	Edit rights for the Google Analytics account	The non-logged-in homepage contains the unchanged analytics.js or gtag.js snippet in the <head>
Google Tag Manager	Publish or Admin permission for the container	The container's <noscript> portion sits immediately after the opening <body> tag

In Google Analytics 4, the verification code is associated with a Google Analytics stream.¹ Check the homepage and permissions before selecting this method.

In Search Console's verification options, select Google Analytics or Google Tag Manager.¹ Click the Verify button after checking these requirements. Use Google's returned error message if the attempt fails.

Verification errors and what they mean on WordPress

Read the message Google Search Console returns, then inspect the website you added. Confirm your change reached production before trying another code.

Message or failed check	What to inspect	Next action and success check
“Meta tag not found/in the wrong location”	Your token in the rendered <head> of the non-logged-in homepage	Save the correct tag and inspect the public output. For Rank Math's manual tag route, its help recommends clearing the site cache and retrying.
“Your meta tag is incorrect” or “Your meta tag is not formatted correctly”	Exact token and formatting, including an existing owner's tag	Compare with your verification screen without replacing another owner's token. Retry after correcting your tag.
“Your verification file was not found in the required location” or wrong content	Exact URL, filename, contents, and unauthenticated access	Publish the unchanged file where Google specifies; confirm it loads in incognito.
DNS verification fails after saving	TXT value served for the domain being verified	Compare a TXT lookup with Google's value; correct the entry or wait for the provider to serve it.
Analytics: “No Analytics code found,” “Snippet in wrong location,” or “Old Google Analytics snippet found”	Homepage <head> and snippet version	Check for the required analytics.js or gtag.js snippet in the specified location, then retry.
Analytics: Google Tag Manager code found instead	Whether the homepage has the required Analytics snippet	Choose Google Tag Manager verification if that is the installed setup and you meet its requirements.
Analytics or Tag Manager: insufficient permission; Tag Manager: “Wrong tag”	Signed-in account and access to the relevant account or container	Use the same Google account with Analytics edit rights or Tag Manager Publish or Admin permission.
Server timeout, invalid response, or unable to connect	Public access, host, firewall, and maintenance-mode configuration	Remove the identified access barrier; confirm the homepage or file loads without authentication.
Site Kit: necessary verification token could not be found	Public production site, host, firewall, and maintenance or coming-soon plugins	Follow Site Kit's access checks. If the error persists, verify manually in Search Console and retry Site Kit setup.

For tag-based verification, Google checks the page where a non-logged-in visitor lands after any redirect from the property's URL.¹ Inspect the destination page when checking your tag. Editing only a staging copy leaves the production output unchanged.

Google Site Verifier fetches Search Console verification tokens with the user agent Mozilla/5.0 (compatible; Google-Site-Verification/1.0).¹¹ Google's user-triggered fetchers generally ignore robots.txt rules. That makes robots.txt an unlikely suspect. Your firewall, a security plugin's bot rules or your host's protection are better places to look first. Before changing any rules, find that request in your host or firewall logs and look at the response it got.

Send your host a focused request to diagnose the failure. Include the public test result alongside Google's message:

Website/property URL:
Verification route:
Exact Google Search Console error:
Public page or file tested:
Incognito result:
Expected token location or DNS record:
Host/firewall response to Google-Site-Verification/1.0, if available:
Please check the identified access or publishing issue and report the retest result.

Keep verification from breaking later

Google Search Console comes back every so often to check that your token is still there and still valid. If it can no longer confirm verification, it notifies you; unresolved issues cause permissions to expire after a grace period.¹ Once every verified owner has lost access, so has every other user.

Before replacing plugins or templates, open Settings → Ownership verification in Google Search Console and add another method.¹ For a URL-prefix property verified with a website tag, DNS is a useful backup: its record lives at the provider.

The token only exists while whatever prints it on WordPress does, be that an SEO plugin setting, WPCode's header field, Site Kit or a theme's functions.php. So switching themes or deactivating a plugin can remove it without warning. Google's own example is a changed template that omits an Analytics tag.¹ After any change like that, check the homepage source to make sure the token is still there. The DNS record and any uploaded verification file should stay put, too.

Add another owner without replacing the first token

A Google Search Console property isn't limited to one verified owner. Owners can use the same or different methods, but must preserve each other's tokens.¹ Watch out for fields that only hold one Google code. Paste someone else's token into one of those and the existing code is gone.

Handing the property to a team? Go to Settings → Users and permissions. An owner can make someone a full user there, which means viewing all data and taking some actions. Delegated ownership is the other choice, and it needs no extra token. Match that role to the recipient's work.

Site Kit lets other WordPress Administrators run setup with their own Google accounts. Site Kit verifies an Administrator during setup if that person is not already a verified owner, and grants Owner permissions in Search Console.¹²

Once you're verified, check indexing, sitemaps and data

Verification proves ownership. It doesn't tell you anything about crawling or indexing yet, which is why the checks below are their own job.

Before closing the setup task, confirm:

• The saved Google Search Console property matches the website and scope you meant to monitor.
• Settings → Ownership verification shows the successful verification.
• The required token or DNS record remains in place.
• Everyone on the team who should have access does, and no existing owner's token got overwritten along the way.

Check WordPress's indexing setting

Open Settings → Reading → Discourage search engines from indexing this site. With the box ticked, WordPress adds a noindex,nofollow meta tag and turns off its core sitemaps. Verification will happily pass with indexing blocked. If the production site is supposed to show up in search, clear that box.

Search Console has no preferred-domain setting to pick. It was retired by Google in 2019. WordPress's Site Address (URL) defines its public address, and WordPress's canonical redirect function handles redirects such as www versus non-www based on that site URL. Google says you can signal preferred URLs with canonical tags or headers, sitemaps, or 301 redirects.

Canonical selection that needs work after setup is what the “Alternate page with proper canonical tag” workflow is for. Changing a redirect instead? The 301 versus 302 redirect guide walks through it.

Submitting the sitemap WordPress generates for you

Open the generated XML sitemap yourself before it goes anywhere near Indexing → Sitemaps in Google Search Console. Copy the generated sitemap's actual URL, then submit it to track its results.¹³

Sitemap generator	Where to check
WordPress core, version 5.5 or later	/wp-sitemap.xml; WordPress also references it in its generated robots.txt
Yoast SEO	/sitemap_index.xml; Settings → Site features → XML sitemaps
Rank Math	/sitemap_index.xml
Jetpack, with Sitemaps enabled	/sitemap.xml
WordPress.com	Usually /sitemap.xml; check the sitemap shown in its settings
All in One SEO	Its generated sitemap; the Google Search Console connection submits it for you

Running Yoast? It swaps the WordPress core sitemap for its own. The Sitemaps report shows sitemaps submitted through that report or the API, not those found only through a robots.txt reference.¹³ It's also scoped to the current property. If a submission seems to have vanished, check the protocol and hostname.

A sitemap can help Google discover pages faster. It can't promise they'll be crawled or indexed. Google can discover pages without a sitemap.¹⁴ Use this report for sitemap errors, and look at indexing on its own.

Wait for data, then review the Page indexing report

Google starts collecting data the moment anyone adds the property to Google Search Console, verified or not. Google says data takes a few days to accrue, with up to a week to generate data for a newly created site or one newly added to Search Console.¹⁵ Site Kit separately notes up to approximately 48 hours for data to populate its dashboard after connecting.⁵

The Search performance report shows how much traffic Google Search sends, broken down by queries, pages, and countries, with trends for impressions and clicks.¹⁴

If the property has no data several days after verification, check the URL-prefix scope again, including http versus https. Google also lists the site not yet appearing in Google Search as a possible reason for missing data.² Empty reports are no reason to pull a working ownership token.

Under Indexing, the Page indexing report shows which pages are indexed and which aren't, along with the reason for each. That reason decides what you do next, since “Crawled - currently not indexed” and “Discovered - currently not indexed” each get their own diagnosis workflow.

SEO Heatmap picks up from there once clicks show up, with every page's Search Console clicks by month or week, grouped by site section, and site-wide keywords on top. Sections that are picking up traffic stand out fast, and so do the pages worth a second look.

Frequently asked questions

Can I add my WordPress website to Google Search Console without installing a plugin?

Yes. Go with DNS or an HTML file and you won't need a WordPress plugin at all. Have Google Analytics or Google Tag Manager on the site already? That works for a URL-prefix property too, provided the permissions and placement check out. Pick based on the systems you actually control.

Should my WordPress site use a Domain property or URL prefix?

Choose Domain for combined protocol and subdomain coverage when you control DNS; choose URL prefix for the manual tag, file, Analytics, or Tag Manager routes. URL prefix is literal: it covers URLs starting with that exact prefix, and the protocol counts as part of it. That means an http://example.com/ property misses the https and www variants entirely.

Why does Google still say the verification tag is missing after I save it?

The token has to appear in the rendered <head> of the homepage that a logged-out visitor receives, or Google won't count it. Inspect the production page, including the destination after any redirect, and compare the token with your Google Search Console screen. For Rank Math's manual tag route, its help recommends clearing the site cache and retrying.

Where must Google Tag Manager code sit for Search Console verification on WordPress?

For this URL-prefix option, the <noscript> part of the Google Tag Manager snippet has to come right after the opening <body> tag. On top of that, your account needs Publish or Admin permission on the container. Then, using the same Google account in Search Console and Tag Manager, choose Google Tag Manager as your method and hit Verify.

What should I check after Google Search Console verifies my WordPress site?

Look at ownership and team access first, then WordPress's indexing setting and the generated sitemap. If the production site should appear in search, clear “Discourage search engines from indexing this site” under Settings → Reading. Submit the sitemap under Indexing → Sitemaps unless your All in One SEO connection already submitted it, then review the Page indexing report as data arrives.

How long can Search Console reports stay empty after WordPress setup?

Google says data takes a few days to accrue and can take up to a week to generate for a newly created site or one newly added to Search Console. Collection starts when anyone adds the property, even before verification. Site Kit separately notes up to approximately 48 hours for its dashboard to populate after connecting; if Search Console remains empty, check the URL-prefix scope and whether Google has seen the site in search.

Could a WordPress theme change put my team's Search Console access at risk?

It can. If the change removes the verification token, Google has no way left to confirm ownership. Google rechecks tokens from time to time and tells you when one fails. Leave the failure unresolved past the grace period and permissions expire. When every verified owner loses access, every user does too, so add a backup method under Settings → Ownership verification before you change templates or plugins.

Can a client and an agency use different Google accounts for the same WordPress property?

Yes. There's no need for separate copies per account, since multiple people can verify the same Google Search Console property. Just don't paste a second code over the first in a field that only holds one, because existing owners' tokens need to stay put. An owner can also add a full user or delegated owner under Settings → Users and permissions; delegated ownership needs no new token.

Once your WordPress site is verified and data starts arriving, connect that property to SEO Heatmap to plan your next SEO review. It is free for one Search Console property.

Sources (15)

SEO Heatmap Knowledge relies on primary sources: Google's documentation, web standards, peer-reviewed research, and vendors' own pages for their pricing and features. Our editorial standards

1. Google Search Console Help. “Verify your site ownership.”
2. Google Search Console Help. “Add a website or platform property to Search Console.”
3. WordPress. “Settings General screen.”
4. Google Site Kit. “Install and set up Site Kit.”
5. Google Site Kit. “Search Console.”
6. Yoast. “How to use Google Search Console: a beginner’s guide.”
7. Rank Math. “How to Verify Your Website on Google Using Rank Math.”
8. Yoast. “Yoast SEO 20.0.”
9. All in One SEO. “How to Verify Your Site with Google Search Console.”
10. WPCode. “WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager.”
11. Google. “List of Google user-triggered fetchers.”
12. Google Site Kit. “Permissions with Google services.”
13. Google Search Console Help. “Sitemaps report.”
14. Google Search Central. “Get started with Search Console.”
15. Google Search Console Help. “About Search Console data.”

About the author

Alex Gorovenko

Founder of SEO Heatmap

I’ve linked WordPress sites to Search Console and led two site redesigns, one with a CMS migration. That work makes me wary of verification codes tied to a theme or plugin. I want a method that survives the next rebuild. The green check proves ownership; I still check the Pages report to see whether Google indexed the pages that matter.