Set Up Google Search Console for Your WordPress Website
Set up Search Console for WordPress, choose a property, verify ownership and submit your sitemap. Learn which reports help guide your next edits.

Quick answer: Add your website to Google Search Console, verify ownership using a supported method, submit the correct sitemap, and inspect an important public URL. Then use the search reports to understand discovery and clicks. Ownership verification alone does not guarantee indexing or rankings.
This is a setup checklist for a site you own or manage with permission. Keep control of the property in the business’s Google account and document how verification is maintained.
1. Choose the right property
Google’s property guide distinguishes two common options. A Domain property covers protocol and subdomain variations and uses DNS verification. A URL-prefix property covers the specified address prefix and supports several verification methods.
If you can manage the domain’s DNS, a Domain property is a useful broad view. If you can manage only the website, an exact URL-prefix property may be easier to verify. Copy the public address carefully, including HTTPS and any www hostname. A property for a different address can produce confusing results.
Write down the selected property, account owner and verification method. That small record helps when a developer leaves, hosting changes or a theme is replaced.
2. Verify ownership with the issued token
For DNS verification, add the exact TXT or CNAME record that Search Console supplies, using your DNS provider’s instructions. Add the record without replacing unrelated website or email records. Complete verification in Search Console and keep the verification record afterwards.
For a URL-prefix property, an HTML tag or verification file may be available. A tag belongs in the homepage’s HTML head, not in visible blog text. Use your platform’s supported verification setting or a maintained integration, then confirm that the exact issued token appears on the public page or required file.
Google’s ownership documentation explains each method and common errors. If verification fails, check the destination and token first; DNS records can take time to appear. Do not substitute a token copied from a tutorial.
3. Find and submit the sitemap
WordPress installations can expose a native sitemap, and SEO plugins may provide their own. Find the sitemap actually used by your site. Open it while signed out and check that it loads and contains the intended public URLs.
For example, StartMyWeb’s public sitemap index is https://startmyweb.online/wp-sitemap.xml. That is an example for this website, not a universal address for every installation.
Open the Sitemaps report in the verified property, enter the sitemap location and submit it. Check the resulting fetch status. The Sitemaps report documentation explains that successful submission tells Google where the file is; it does not guarantee every listed URL will be crawled or indexed.
4. Inspect an important public page
Start with the homepage or a useful service page. Use URL Inspection to compare the indexed information with the live page. If there is an indexing issue, read the reason before requesting anything. Check that the page is public, loads useful content and has the intended canonical address.
For a new or substantially updated eligible page, a crawl request may be appropriate. Google’s recrawl guidance says that requests do not guarantee inclusion and repeated requests do not make the process faster.
Use the not showing on Google checklist if the page is still absent. Keep the inspection result and test date instead of relying only on a manual search for the title.
5. Read the search reports with a clear question
The Performance report shows search clicks, impressions, click-through rate and average position. It can group results by queries, pages, countries and devices. These describe Google Search performance; clicks are not a count of unique visitors across every traffic source.
| Question | Useful starting view |
|---|---|
| Which guides are being discovered? | Pages and impressions |
| Which questions bring readers? | Queries and clicks |
| Does the title fit the search intent? | The page’s queries alongside its impressions and CTR |
| Is a mobile difference worth investigating? | Device comparison for the same page and date range |
Review a consistent date range and record edits so comparisons have context. Small samples can move sharply, so avoid rewriting every title after one quiet day. If a query reveals a missing step in a guide, improve that step before creating a nearly identical article.
6. Keep a small review routine
Maintain a weekly note with the important pages, relevant queries, unresolved indexing reasons and next useful edit. Track actual website users separately in an appropriately configured analytics system. The new WordPress SEO checklist covers the wider launch checks.
Need help preparing your site for measurement and search discovery? Share your website goal with StartMyWeb. Keep passwords and verification tokens out of public messages.
About StartMyWeb · Privacy policy
Editorial note: Prepared with AI assistance and checked against the official documentation linked above. Examples are illustrative; test changes on a recoverable copy before applying them to a live business website.
I can review the website, content structure and search setup and turn the findings into a practical improvement plan.
Published by Lookman at Start My Web, an independent web and WordPress service working online from Bengaluru. Examples are illustrative; project scope and third-party product terms should be confirmed for your requirements.