Connecting Search Console to WordPress

Updated 2026-08-07

Four ways to verify a WordPress site, where each SEO plugin puts your sitemap, and why the plugin dashboards show less than Search Console itself.

WordPress makes Search Console verification easy in four different ways, which is exactly why people get stuck choosing. Here is what each costs you later.

The four options, best first

1. DNS record. Add the TXT record at your registrar and verify a domain property. Nothing is installed, nothing breaks on a theme change, and you get every subdomain in one property. If you can edit DNS, stop here.

2. Your existing SEO plugin. Yoast, Rank Math, All in One SEO and SEOPress each have a field for the Search Console verification code — usually under a "webmaster tools" or "site verification" section. Paste the content value from the HTML-tag method. Zero code, survives theme updates, but tied to that plugin remaining installed.

3. Site Kit by Google. Google's own plugin. It verifies, connects Analytics too, and shows some Search Console data in the WordPress admin. Convenient, and heavier than the alternatives — it is a full OAuth integration doing more than verification.

4. A child theme or code snippet. The meta tag in wp_head. Works, and the classic mistake is editing the parent theme directly, where the next update deletes it. Use a child theme or a snippets plugin.

Avoid the HTML file upload method. It means FTP or a file manager, and it is the first thing lost in a migration.

Your sitemap is already there

You almost certainly do not need to generate one. Submit whichever of these exists:

• WordPress core (5.5 and later) — /wp-sitemap.xml
• Yoast SEO — /sitemap_index.xml
• Rank Math — /sitemap_index.xml
• All in One SEO — /sitemap.xml

An SEO plugin disables the core sitemap when it provides its own, so submit the plugin's. Do not submit both — you would be advertising two sets of the same URLs. Details in submitting a sitemap.

WordPress.com is different. On the hosted service, plugins and header edits need a paid plan. Free and Personal plans have a built-in Search Console verification field in the site settings — use that. Self-hosted WordPress has all four options.

The WordPress-specific things that hurt indexing

• "Discourage search engines" left ticked. Settings → Reading. It sets noindex sitewide. Staging sites go live with this on constantly, and it is the first thing to check when nothing indexes.
• Tag and category archives. A tag used once creates a near-empty page. Dozens of them are a large share of thin URLs, and they show up as crawled — currently not indexed. Noindex tag archives unless you have deliberately built them out.
• Attachment pages. Older setups generate a page per uploaded image. Every modern SEO plugin can redirect these to the file; make sure yours does.
• Paginated comments and archives producing endless crawlable combinations.
• Both www and non-www resolving. Pick one, 301 the other. A domain property reports them together and hides the split.

On the plugin dashboards

Site Kit and the paid tiers of some SEO plugins surface Search Console data inside wp-admin. Handy, but they show a summary — usually top queries and pages over a short window. Comparison periods, the country and device breakdowns, search-appearance filtering and the full 16 months are all only in Search Console itself. Treat the plugin view as a glance and go to the source for anything you plan to act on.