If I could only use one SEO tool for a WordPress site, it would be Google Search Console. It’s free, the data comes directly from Google, and it answers the questions that matter most: Is Google finding and indexing my pages? Which searches bring visitors? Is anything broken? Has my site been hacked or penalised?
Despite this, many site owners either haven’t set it up or log in once a year and feel overwhelmed. The interface has a lot of reports, and not all of them need regular attention.
Here’s how I set up Search Console for WordPress sites and which reports I actually check.
Setting up and verifying your site
Choose the property type
Search Console offers two property types:
- Domain property: covers every version of your domain, including http, https, www, non-www and all subdomains. Verified through a DNS record.
- URL-prefix property: covers only URLs starting with a specific prefix, like https://example.com/. Can be verified several ways, including an HTML file, meta tag or Google Analytics.
I recommend the domain property, because it gives a complete view and catches problems on subdomains you might not think about. If you can’t edit DNS, a URL-prefix property for your main address is fine.
Verify ownership
For a domain property, add the TXT record Search Console provides to your DNS settings. For a URL-prefix property, many WordPress SEO plugins have a field for the verification meta tag, or you can upload the HTML file to your site root.
Keep the verification method in place permanently. If you remove it, you lose access.
Add users carefully
Under Settings, then Users and permissions, you can add other people. Give full access only to people who need it. Review this list periodically. Attackers who compromise sites sometimes add themselves as owners, so an unfamiliar owner is a serious warning sign.
Submit your sitemap
WordPress generates a sitemap automatically at /wp-sitemap.xml, and SEO plugins usually replace it with their own, often at /sitemap_index.xml. In Search Console, go to Sitemaps and submit your sitemap URL.
Check back after a few days to confirm Google read it successfully. The report shows how many URLs were discovered. If the sitemap shows errors or far fewer URLs than expected, investigate.
Make sure the sitemap only lists pages you want indexed. Sitemaps that include redirected URLs, noindexed pages or thin archives send mixed signals.
The Performance report
This is the report I use most. It shows how your site appears in Google Search:
- Clicks: how many times people clicked through to your site.
- Impressions: how many times your pages appeared in results.
- Average CTR: the percentage of impressions that became clicks.
- Average position: the average ranking of your pages.
You can view data by queries, pages, countries, devices, search appearance and dates.
Useful ways to use it
Find your best queries and pages. Sort by clicks to see what brings traffic. Make sure these pages are well maintained and link to your conversion pages.
Spot opportunities. Filter for queries where your average position is between about 8 and 20. These are close to page one or at its bottom. Improving those pages can bring significant gains.
Improve click-through rates. Look for pages with many impressions but low CTR. Rewriting titles and meta descriptions to better match search intent can increase clicks without any ranking change.
Compare periods. Compare the last three months with the previous period or the same time last year. Pages and queries with significant drops need investigation.
Check device and country performance. If mobile performance lags far behind desktop, check your mobile experience.
Understand the limitations
Search Console data is sampled and filtered for privacy, especially for rare queries, so totals may not add up exactly. Average position is an average across many searches and locations, so treat it as a guide rather than an exact ranking.
The Page indexing report
This report shows which of your pages are indexed and why others aren’t. It’s essential for diagnosing problems.
Pages are grouped into indexed and not indexed, with reasons for the latter, such as:
- Excluded by noindex tag: a page has a noindex directive. Check that this is intentional.
- Page with redirect: the URL redirects elsewhere. Usually fine, but check that your sitemap and internal links don’t point to redirected URLs.
- Not found (404): the page doesn’t exist. Fine for deleted content, but fix internal links pointing to it and add redirects for valuable old URLs.
- Alternate page with proper canonical tag: Google indexed a different version as canonical. Usually fine.
- Duplicate without user-selected canonical: Google found duplicates and chose one itself. Consider adding canonical tags.
- Crawled, currently not indexed: Google crawled the page but decided not to index it, often a quality or uniqueness signal.
- Discovered, currently not indexed: Google knows about the page but hasn’t crawled it yet.
- Blocked by robots.txt: robots.txt prevents crawling.
- Soft 404: the page returns a success status but looks like an error or empty page.
Not every excluded page is a problem. Many are expected, like redirects and intentional noindex pages. Focus on important pages that should be indexed but aren’t, and on sudden increases in errors.
My separate guide on fixing indexing issues goes deeper into each status.
URL Inspection
The URL Inspection tool, at the top of Search Console, shows detailed information about a specific URL:
- Whether it’s indexed.
- The canonical URL Google selected.
- When it was last crawled.
- Whether the page is mobile friendly.
- Detected structured data.
You can also test the live URL to see how Google currently renders it, and request indexing after making changes.
I use URL Inspection constantly: after publishing important content, after fixing problems, and when investigating why a page doesn’t rank. It’s also invaluable for detecting cloaking, where hacked sites show spam to Google but normal content to visitors.
Requesting indexing has a daily limit and doesn’t guarantee indexing. Use it for important pages, not for every post.
Core Web Vitals
This report shows real-user performance data for your pages, grouped into good, needs improvement and poor, for mobile and desktop. It’s based on the Chrome User Experience Report and requires enough traffic to display data.
Use it to identify groups of pages with problems, then investigate specific URLs with PageSpeed Insights. Remember that the data is a rolling 28-day window, so improvements take time to appear.
HTTPS
The HTTPS report shows whether your pages are served securely. Pages served over HTTP or with certificate problems appear here. It’s a quick check after migrations or SSL changes.
Enhancements and structured data
If your site uses structured data, Search Console shows reports for detected rich result types, such as breadcrumbs, products, reviews, events and videos. Each report lists valid items, warnings and errors.
Errors can make pages ineligible for rich results. Check these reports after theme changes, plugin updates and redesigns, because structured data often breaks silently.
Security issues and manual actions
These two reports should be empty. If they’re not, act immediately.
- Security issues flag hacked content, malware, phishing and harmful downloads detected on your site.
- Manual actions are penalties applied by Google’s reviewers for violating spam policies.
Both reports include details and a way to request a review after you fix the problem. Search Console also emails verified owners when these issues are detected, so make sure notifications reach someone who reads them.
Links
The Links report shows your top linked pages, top linking sites and internal link counts. It’s useful for a basic view of external links and for checking that important pages receive internal links.
Settings and crawl stats
Under Settings, the Crawl stats report shows how often Googlebot crawls your site, response times and response codes. Sudden spikes in server errors or response times can signal hosting problems. It’s especially useful for large sites and after migrations.
A simple routine
You don’t need to check everything constantly. Here’s a practical routine:
Weekly or whenever you have a few minutes:
- Glance at the Performance report for unusual drops.
- Check for any new messages or alerts.
Monthly:
- Review top queries and pages, and look for opportunities.
- Check the Page indexing report for new errors.
- Check Core Web Vitals and enhancement reports.
After major changes, like migrations, redesigns or big content updates:
- Submit the sitemap again.
- Inspect key URLs.
- Monitor indexing and errors closely for several weeks.
Always:
- Act immediately on security issues and manual actions.
Connect Search Console with other tools
Linking Search Console with Google Analytics lets you see organic search queries alongside on-site behaviour. Many SEO plugins also display Search Console data inside the WordPress dashboard, which can make it easier to check regularly.
Frequently asked questions
Is Search Console the same as Google Analytics?
No. Search Console shows how your site performs in Google Search before people click: impressions, rankings and clicks. Analytics shows what visitors do on your site after they arrive, from all sources.
Why is my new page not showing in Search Console?
New pages take time to be discovered, crawled and indexed. Make sure the page is linked internally and included in your sitemap, then use URL Inspection to request indexing.
Why don’t Search Console clicks match Analytics sessions?
They measure different things, use different methods and apply privacy filtering differently. Some difference is normal. Look at trends rather than exact matches.
How far back does Search Console data go?
The Performance report shows up to 16 months of data. Export data regularly if you want a longer history.
Final thoughts
Search Console is the closest thing you have to a direct line to Google about your site. Set it up with a domain property, submit your sitemap, use the Performance report to find opportunities, watch the Page indexing report for problems, inspect important URLs and respond immediately to security or manual action warnings. A few minutes a week with Search Console will teach you more about your site’s search performance than any paid tool.




