After publishing or editing a page, you want to confirm that Google can view the correct version. Google Search Console’s URL Inspection tool answers that question for a specific address. It does not replace overall site monitoring. However, it makes it possible to spot a directive noindex, an unexpected canonical, a fetch error, or an older version still known to Google.
To inspect a WordPress URL in Search Console effectively, first check the public page. Then compare the index data with the live page test. This distinction helps you avoid thinking too quickly that Google is ignoring your change.
Open the inspection with the correct address
In Google Search Console, select the property that covers your site. Then paste the full public address into the inspection bar at the top of the interface. Use the final URL you want to see in the results, with the correct protocol, the correct subdomain and the correct path.
Avoid addresses with tracking parameters, a preview or an old URL that redirects. After an address change, inspect the new URL first. Also inspect the old one separately to confirm that it redirects properly to the intended destination.
The tool shows the status known in the index, lets you test the live accessible URL and can give you access to an indexing request. Google describes these functions in its getting started documentation with Search Console.
Distinguish the indexed version from the live page
The first screen shows the information Google already knows in its index. This data may therefore correspond to a crawl that happened before your change. In particular, look at the date of the last crawl. If it is earlier than your change, Google may not have retrieved the new version yet.
Then run the live URL test. This check shows what Google can retrieve now. As a result, a page that is accessible today may still have an old state in the index. Conversely, a page that is indexed may have become inaccessible after a recent change.
Crawling consists of retrieving a page. Indexing, on the other hand, refers to Google’s decision to keep that page in its index. A successful crawl therefore does not guarantee an immediate presence in the results or a specific position.
Read the important signals in the report
Indexing status and detailed reason
Start with the overall verdict and the reason shown. If Search Console indicates that the URL is indexed, it may appear in the results. That does not mean it will rank for all queries or at a given position.
If Google does not index the URL, the explanation points to the next check. A directive noindex, a crawl block, a server error or a missing page require different fixes. Correct the cause before requesting a new crawl.
A page must be accessible to Google and its content must be able to be indexed. Google’s Search technical requirements also specify that Google does not index pages that return an HTTP error.
Crawling, fetching and rendering
Check the date of the last crawl and the fetch result. A successful fetch indicates that Google was able to retrieve the page. However, an error 404, 403, 5xx or redirect requires a fix at the source before any new request.
Also review the rendering when the tool displays it. The main content, headings and useful internal links should appear in the version Google consults. An extension, a firewall or a blocked resource can prevent normal loading. The inspection then helps identify the gap between your browser and what Google retrieves.
Declared canonical and selected canonical
Compare the canonical URL declared by your page with the one Google selected. Ideally, they match when you want this page indexed. If Google prefers another address, look for a similar variant, duplicate content, a redirect, or conflicting signals.
Before changing an SEO setting, consult this guide to understanding canonical URLs in WordPress. A canonical does not solve an accessibility problem. It also does not replace a redirect when an old page needs to send visitors to a new page.
Requesting a new crawl judiciously
When the live test confirms that the page is accessible and indexable, you can request indexing. This action is especially appropriate for an important new page or a substantial change. For example, you revised the main content, removed a directive noindex, corrected a canonical, or resolved an error.
However, do not repeat the request for the same URL without a new change. Google explains that a request does not guarantee either indexing or a specific timeframe. Repeated requests also do not speed up crawling. Processing can take from a few days to a few weeks depending on the site and the URL, as the documentation on requesting a recrawl.
For several dozen changed pages, instead favour an up-to-date XML sitemap and consistent internal links. You can follow this procedure to check and fix the WordPress XML sitemap. The sitemap helps Google discover your URLs, without forcing it to index them all.
WordPress checks before drawing a conclusion
Before rerunning the inspection, open the page in a private window. Confirm that it displays the correct content, that it does not require a login, and that it does not redirect to another address by mistake. Also check that the post is published, rather than in draft or password-protected.
- The page responds normally for a visitor who is not logged in.
- The main content appears without any special interaction.
- The page does not contain a directive noindex if you want it indexed.
- The canonical matches the URL you want to prioritise.
- At least one relevant internal link points to this page.
- The sitemap includes the URL if it deserves to be discovered.
For a revised article, also preserve its search intent and the information useful to readers. This approach complements the advice for updating an old WordPress post without losing its search intent.
Adopting a routine after a major change
Publish the change and open the public URL. Then inspect it in Search Console. Read the index data first. Run the live test if the last crawl is old or if the report reveals a problem. Fix what is actually blocking the page, request a new crawl only once when it is justified, then give Google time to process the URL.
This routine provides a concrete diagnosis without turning every small fix into an SEO emergency. Above all, it helps you confirm that Google can access the page, understand the canonical address, and become aware of your changes.









