Google Search Console for WordPress Owners

A Domain property covers protocol and subdomain variations. It requires DNS verification. A URL-prefix property covers its specified prefix and supports other verification methods, including an HTML tag or file. Choose based on the access you actually have, not the method that looks shortest. Keep the verification record, tag or file in place: Google can recheck it later. Google’s ownership verification instructions.

For example, a business owner might control the domain account while a contractor controls WordPress. A practical handover should record where verification lives and who maintains it. Do not put a contractor’s temporary access at the centre of the owner’s reporting setup. This is a handover recommendation, not a Google requirement.

If the site is already verified, review its existing setup before adding a new method. A theme replacement can remove a verification tag; a domain migration can leave a DNS record behind. Include verification in your launch checklist alongside backups and working enquiries.

Begin with this division of work:

• Performance: investigate search traffic and queries.

• Page indexing: identify groups of URLs that are not indexed and their reported reasons.

• Sitemaps: check whether Google can process the sitemap you submitted.

• URL Inspection: investigate a particular URL and, when needed, test its current live version.

Do not treat these as interchangeable. A sitemap can be processed successfully while a listed page remains unindexed. A live test can succeed while the indexed version is older. The indexed inspection and the live test answer different questions; a positive test is not a guarantee of inclusion in search. Google’s URL Inspection guide.

A useful practical habit is to note which report supplied each observation. “Live fetch succeeded” is more precise than “Google has approved the website.”

Google’s Page Indexing report distinguishes discovery, crawling, duplication and exclusions. A non-indexed URL is not automatically a problem. For example, an intentional redirect or duplicate may not need its own indexed entry. “Discovered — currently not indexed” means Google found the URL but has not crawled it. “Crawled — currently not indexed” means it fetched the page but has not indexed it; that status alone does not prove the content is poor. Google’s indexing status definitions.

The following checks are diagnostic suggestions, not guaranteed explanations for a status:

• An important page has noindex: inspect Settings → Reading and the page-level controls in your SEO plugin. Also consider headers or theme code that could add directives.

• An unexpected canonical is selected: compare the public URL with its alternatives, the declared canonical and links pointing to it.

• A service URL redirects: check whether the destination is deliberate. A renamed service needs a relevant destination, not a blanket redirect to the homepage.

• A page is discovered but uncrawled: confirm that visitors can reach it through meaningful internal links. Review server availability if crawl problems appear elsewhere.

• A page is crawled but unindexed: read it beside the closest competing page on your own site. Is it a distinct answer, or a slight variation with a different title? Record your findings before changing it.

WordPress has a site-wide “Discourage search engines from indexing this site” setting. On a public production site intended for search, check that it was not left enabled after development. It asks search engines not to index the site; it is not an access-control system for confidential staging content. WordPress Reading settings documentation.

Check the public response after a settings change. Purging the appropriate cache may be necessary before a visitor sees the new output. Record what you changed so a later developer can distinguish a deliberate exclusion from a launch mistake.

For the wider implementation checklist, use the existing WordPress technical SEO guide. This article is about diagnosis, not a replacement for that checklist.

Imagine a business has /services/bookkeeping/ and a campaign URL with a tracking parameter. This is a hypothetical example, not a client result.

First, decide whether the campaign page is genuinely different. If the parameter only measures a visit, it probably does not describe a second service. If it changes the offer substantially, the decision needs more care.

Next, inspect both variants. Compare their content, canonical declarations and internal links. Google treats canonical declarations as signals rather than an absolute command, so keep signals consistent. Link internally to the preferred URL and include preferred URLs in the sitemap. Google’s canonical guidance.

Write a short decision note: “The campaign parameter tracks visits; the main service URL is the intended search destination.” That gives the developer something concrete to verify. Do not change every archive to noindex because one parameter URL appeared in a report. For implementation options, read duplicate content fixes for WordPress.

Find the actual sitemap your site serves. Its address depends on the setup; do not assume every WordPress site uses the same filename. Open it publicly and check that the important canonical pages appear. Submit its URL in the Sitemaps report, then review processing errors and the last-read information. Submitting gives Google the location of the file; it is not an upload of your pages into the index. Google’s Sitemaps report documentation.

Keep the responsibilities separate: WordPress or your build process generates the file, your host serves it, and Search Console reports Google’s processing. If a new page is absent from the XML, fix the generator rather than repeatedly submitting the same unchanged file. The existing sitemap and robots.txt guide covers the file-level details.

After a meaningful update, you can request indexing for selected important URLs. Google recommends URL Inspection for a few URLs and a sitemap for larger sets. Crawling can take days to weeks; requests do not guarantee indexing, and repeated submissions do not accelerate the same URL. Google’s recrawl guidance.

Performance includes clicks, impressions, click-through rate and average position. You can group results by pages, queries, countries and devices. Use those dimensions to ask a narrower question instead of treating the site-wide average position as a rank for every service. Google’s Performance report guide.

For a worldwide business, review country patterns without creating dozens of country pages merely because a report lists them. The useful editorial question is whether the landing page answers the visitor’s need. Geography alone does not supply a distinct service offer.

Compare similar date ranges and keep an annotation of releases. If impressions rise while enquiries stay flat, investigate the landing page and enquiry path separately. That is an analysis suggestion, not proof that the copy or form is the cause. Search clicks and accepted enquiries are different measurements.

Use this as a proposed working routine, not a promise that every investigation takes ten minutes:

1. Review unexpected movement in your important landing pages.

2. Check new indexing issues for those pages before worrying about every archive URL.

3. Inspect one representative URL from a problem group.

4. Write down the observation, your intended behaviour and one next action.

5. Recheck the result after the fix and after Google updates its reporting.

Keep a small log: date, URL, report, observation, change and verification. For example, “Removed accidental production noindex; public HTML checked; waiting for Google’s next crawl.” Separate completed technical work from pending search processing.

If a report points to a problem you cannot explain, send the affected public URLs, the reported status and any recent changes. Start with WordPress performance and maintenance, or WordPress development for implementation work.

Send your project brief. Do not include passwords or private customer data in the enquiry. A useful first step is a diagnosis and scoped plan, not a ranking guarantee.