Table of Contents
Most WordPress guides stop the moment Google Search Console (GSC) shows a green "Ownership verified" banner. That's the easy part. The hard part — and the part that actually moves traffic — is using the data GSC collects to fix the indexing quirks WordPress creates by default, and then turning impressions into clicks. WordPress is wonderful at publishing content fast, but it's equally good at generating category archives, tag pages, author archives, attachment URLs, and paginated lists that quietly dilute your crawl budget and confuse Google's index.
This guide covers both halves. First, the cleanest way to verify and connect your WordPress site to Google Search Console, including the real trade-offs between the Site Kit plugin, an SEO-plugin HTML tag, and DNS verification. Then the ongoing optimization loop: reading Index Coverage like a WordPress person (so "Discovered – currently not indexed" stops being a mystery), submitting the right sitemap, and running a repeatable workflow to find striking-distance posts, rewrite weak titles, and prune the thin pages dragging your domain down.
If you've never created a property at all, start with our walkthrough on how to add a website to Google Search Console, then come back here for the WordPress-specific decisions.
Choosing a verification method for WordPress
There are three sane ways to verify a WordPress site, and the right one depends on whether you want GSC data inside wp-admin, how many subdomains you run, and how comfortable you are touching DNS. Here's the honest comparison.
| Method | How it works | Best for | Downside |
|---|---|---|---|
| Site Kit by Google plugin | Installs Google's official plugin, signs in with OAuth, auto-verifies | Owners who want GSC + Analytics charts inside wp-admin | Adds a plugin; dashboard is a simplified subset of GSC |
| SEO plugin HTML tag (Yoast / Rank Math / AIOSEO) | Paste the google-site-verification meta tag into a settings field | Sites already running an SEO plugin, no extra software | Verifies one URL-prefix property only; breaks if you switch plugins and remove the tag |
| DNS TXT record | Add a TXT record at your domain registrar | Domain properties covering http/https + www + subdomains | Requires registrar access; propagation can take minutes to hours |
A few recommendations. If you want to glance at clicks and impressions without leaving wp-admin, install Site Kit. If you already run an SEO plugin and don't want another, the HTML tag method is the lowest-friction path — every major SEO plugin has a dedicated field for it. If you want the most complete data (a Domain property that merges https://, http://, www, and any subdomains into one view), use DNS verification; it's the option we recommend for anyone serious about long-term measurement.
You can combine methods. A common setup is a DNS-verified Domain property for complete data plus Site Kit installed for the in-dashboard convenience. Verifying twice does no harm.
Verifying with Site Kit by Google
In wp-admin go to Plugins → Add New, search "Site Kit by Google," install and activate. Open Site Kit → Dashboard, click Sign in with Google, and pick the Google account that should own the property. Site Kit creates and verifies the Search Console property for you and writes the verification token automatically — no copy-pasting. Grant the Search Console scope when prompted and you're done.
Verifying with the HTML tag (Yoast / Rank Math / AIOSEO)
In GSC, add a URL prefix property (e.g. https://example.com/), expand the HTML tag option, and copy the value inside content="..." — just the token, not the whole tag, depending on the field.
- Yoast SEO: SEO → General → Webmaster Tools → paste into "Google verification code."
- Rank Math: Rank Math → General Settings → Webmaster Tools → "Google Search Console."
- AIOSEO: All in One SEO → General Settings → Webmaster Tools → "Google Search Console."
Save, then click Verify in GSC. The plugin injects the meta tag into your <head> site-wide.
Verifying with DNS
In GSC choose Domain property, enter example.com, and copy the TXT record. Log in to your registrar (or wherever DNS is hosted — Cloudflare, your host, etc.), add a TXT record with the supplied value at the root (@), save, wait for propagation, and click Verify. This is the most resilient method because it survives plugin and theme changes.
Connecting Site Kit to see GSC data in wp-admin (and its limits)
Once Site Kit is connected, Site Kit → Dashboard shows Search Console clicks, impressions, average position, and your top queries and pages over the last 28 days, plus a per-post panel when you edit individual content. For a quick pulse check without logging into GSC, that's genuinely useful.
Be clear about the limits, though. Site Kit's dashboard is a read-only summary, not the full console. You can't:
- Build complex query/page filters or use regex.
- Use the URL Inspection tool or request indexing.
- See the full Index Coverage ("Pages") report with per-issue URL lists.
- Compare arbitrary date ranges or export large datasets.
Treat Site Kit as the dashboard widget and the real Google Search Console (search.google.com/search-console) as the workshop. The optimization workflow below assumes you're in the full GSC interface. If you want a broader orientation to the platform itself, see our Google Search Console guide.
Submitting your WordPress XML sitemap
WordPress generates an XML sitemap automatically. If you run an SEO plugin, use its sitemap and disable the core one to avoid duplicates:
- Yoast:
https://example.com/sitemap_index.xml - Rank Math:
https://example.com/sitemap_index.xml - AIOSEO:
https://example.com/sitemap.xml - WordPress core (no SEO plugin):
https://example.com/wp-sitemap.xml
In GSC open Indexing → Sitemaps, enter the path (e.g. sitemap_index.xml), and click Submit. Within a day or two the status should read "Success" with a discovered-URL count. If you see "Couldn't fetch," open the sitemap URL in your browser first — a redirect, a stray noindex, or a caching plugin serving a stale file is usually the culprit.
One WordPress-specific tip: open your SEO plugin's sitemap settings and exclude post types and taxonomies you don't want indexed (more on which ones below) so your sitemap only advertises pages you actually want ranking. For deeper sitemap troubleshooting, see our Google Search Console sitemap guide.
Common WordPress indexing problems in GSC
Open Indexing → Pages (the report formerly called Index Coverage). WordPress sites tend to produce the same recurring issues. Here's how to read and fix them.
Archive bloat: categories, tags, and author pages
By default WordPress creates an archive page for every category, every tag, and every author. On a blog with hundreds of tags, that's hundreds of thin, near-duplicate listing pages competing with your real content. In GSC you'll often see these under "Excluded" buckets like "Duplicate without user-selected canonical" or "Crawled – currently not indexed."
The fix lives in your SEO plugin. In Yoast → SEO → Search Appearance (or Rank Math → Titles & Meta), set Tag archives and usually Author archives to noindex. Keep category archives indexable only if you use them as genuine hub pages with intro copy. To see how many archive URLs Google is even aware of, use the page filter in GSC's Performance report with a regex (Custom → Page → Matches regex):
/(category|tag|author)/
That RE2-flavor pattern surfaces every archive URL in one view so you can judge whether any of them earn clicks before you noindex them.
Attachment pages
WordPress can create a standalone URL for every uploaded image (example.com/photo-name/). These are pure thin content. Yoast and Rank Math both redirect attachment URLs to the parent post by default now — confirm the setting is on (Yoast: Settings → Advanced → Media; Rank Math: General Settings → Links → "Redirect Attachments"). If you find attachment URLs lingering in GSC, that toggle is your fix.
"Discovered – currently not indexed"
This is the most-asked WordPress GSC question, and it almost always means one thing: Google found the URL but didn't think it was worth crawling yet. It's a quality and priority signal, not a technical error. Common WordPress causes:
- Thin or templated posts (auto-generated, very short, or near-duplicate).
- Orphaned posts with no internal links pointing to them.
- A flood of low-value archive/tag URLs eating crawl priority.
The fix is rarely "request indexing." It's to improve the page (depth, uniqueness), add internal links from related posts, and reduce the low-value URL count so Google spends crawl budget where it matters. Our guide to Index Coverage errors breaks down each status and the right response.
Paginated archives
Blog pagination (/page/2/, /page/3/) shows up as crawled-but-not-indexed, which is normal and fine — Google uses those pages to discover posts, not to rank them. Don't noindex page 2+; just let them be discovery paths. Make sure each post is also linked from somewhere more permanent (a related-posts block or a hub page) so it isn't reachable only via deep pagination.
The setting that hides your whole site
If new content simply won't index, check Settings → Reading → "Discourage search engines from indexing this site." When that box is checked, WordPress adds a site-wide noindex and a Disallow directive — the single most common reason a freshly launched WordPress site never appears in Google. Designers leave it checked during development and forget to uncheck it at launch. Uncheck it, save, then use URL Inspection in GSC to confirm the page is "indexable" and request indexing.
The ongoing optimization loop
Verification and clean indexing are table stakes. The compounding wins come from a repeatable loop you run monthly: find pages on the edge of page one, fix titles that under-earn clicks, and prune content that's dragging you down.
Step 1: Find striking-distance posts
"Striking distance" means queries where you rank roughly positions 8-20 — close enough that a modest improvement can push you onto page one, where most clicks live. In GSC, open Performance → Search results, set the date range to the last 3 months, and add the Average position metric. Sort by position and look for queries with meaningful impressions sitting just below page one.
In WordPress terms, these are usually posts that are almost there: the topic is right but the content is a little thin, the title doesn't match intent, or internal linking is weak. Add a paragraph that directly answers the query, strengthen the H2 that targets it, and link to the post from 2-3 related articles. Our deep dive on finding striking-distance keywords in Search Console shows how to isolate these queries precisely.
Manually pivoting GSC's query and page tables to find these is tedious. Search Console Tools is a free tool that connects to your GSC data via Google OAuth and surfaces striking-distance and low-CTR opportunities automatically — turning them into prioritized content briefs so you skip the spreadsheet step. Worth a look once you've got the manual workflow down.
Step 2: Fix low-CTR titles
A page can rank well and still bleed clicks if the title and meta description don't earn them. In Performance, click a page to filter to it, then switch to the Queries tab to see what it ranks for. If a post sits in position 4-6 but its CTR trails the typical range for that position (top-3 results commonly see double-digit CTR; positions 4-10 fall off sharply), the title is the lever.
Rewrite it in your SEO plugin's SEO title field — Yoast and Rank Math both show a snippet preview as you type. Lead with the primary keyword, add a specific hook (a number, a year, a benefit, "[2026]"), and keep it under roughly 60 characters so it doesn't truncate. Change the title, note the date, and check CTR again in 2-4 weeks. Our low-CTR fix guide covers title patterns that consistently lift click-through.
Step 3: Prune thin content
Old WordPress sites accumulate dead weight: short posts that never ranked, near-duplicate articles, seasonal content that's irrelevant now. These pages can suppress overall site quality and waste crawl budget. To find them, look in GSC for pages with impressions but near-zero clicks over 6+ months, plus posts sitting in "Crawled – currently not indexed."
For each, decide: improve, merge, or remove. Improve the ones with potential. Merge two thin posts on the same topic into one strong post and 301-redirect the loser (a redirect plugin or your SEO plugin's redirect manager handles this). Delete the truly worthless and let it 410, or redirect it to the closest relevant page. Then resubmit your sitemap so GSC re-evaluates.
Power tip: regex filters for WordPress URL structures
GSC's regex filters are the fastest way to slice WordPress's predictable URL patterns. A few RE2 examples to paste into Custom → Page → Matches regex:
^https?://example\.com/blog/ # only blog posts
/(category|tag|author)/ # all archive pages
/page/[0-9]+/ # paginated URLs
\?(s|p)= # internal search + ID-based URLs
Combine these with date comparisons to isolate exactly which slice of your site is growing or shrinking. See our regex filters guide for more patterns.
Frequently Asked Questions
Do I need an SEO plugin if I use Site Kit for Google Search Console?
No — Site Kit only connects WordPress to Google's products; it doesn't manage titles, meta descriptions, or sitemaps. For on-page SEO control you still want Yoast, Rank Math, or AIOSEO. Many sites run both: an SEO plugin for optimization and Site Kit for in-dashboard reporting.
Should I noindex my WordPress category and tag pages?
Tag archives are almost always worth setting to noindex because they're thin and duplicative. Category archives can stay indexed if you treat them as real hub pages with unique intro content and internal links; otherwise noindex them too. Set this in your SEO plugin's Search Appearance / Titles & Meta section.
Why does Google Search Console say my WordPress posts are "Discovered – currently not indexed"?
It means Google found the URL but decided it wasn't a high enough priority to crawl and index yet — a quality/priority signal, not a technical error. The fixes are improving the content's depth and uniqueness, adding internal links to the page, and reducing the volume of low-value URLs (tags, thin archives) competing for crawl budget.
Which XML sitemap should I submit for WordPress?
Submit your SEO plugin's sitemap if you have one: sitemap_index.xml for Yoast and Rank Math, or sitemap.xml for AIOSEO. If you don't run an SEO plugin, submit the WordPress core sitemap at wp-sitemap.xml. Don't submit two sitemaps for the same URLs, and exclude post types and taxonomies you've set to noindex.
My new WordPress site won't appear in Google. What's wrong?
First check Settings → Reading and make sure "Discourage search engines from indexing this site" is unchecked — that box adds a site-wide noindex and is the most common cause. Then verify the page is indexable using GSC's URL Inspection tool, confirm your sitemap is submitted successfully, and give Google days to weeks for a brand-new domain.
Is the Site Kit dashboard a full replacement for Google Search Console?
No. Site Kit shows a read-only summary of clicks, impressions, position, and top queries inside wp-admin, but it lacks the full Pages (Index Coverage) report, URL Inspection, regex and advanced filters, and large exports. Use Site Kit for quick checks and the full Search Console interface for real analysis and troubleshooting.
Run a Free AI Citation Audit
Are you in the AI Overview? Get a free report showing how often ChatGPT, Claude, and Gemini cite your brand, plus the 3 blockers preventing your discovery in 2026.
No spam. 1-click unsubscribe. Join 1,200+ SEO teams managing the GEO pivot.