Just because you write and publish a new post in WordPress does not mean it immediately appears in Google search results.
In particular, when you check your site with a site: search and find that only one of your recent posts does not appear, it may feel at first as if a problem has occurred with the indexing itself.
However, you cannot judge that the entire site has an indexing problem simply because a new post on the day of publication is not searched.
Even in the case I checked, existing posts were confirmed with site: search, but there was a situation where only the post written on that day did not appear in the search results.
In this case, you must first distinguish between a site-wide setting problem and a simple indexing delay.
Checking if the new post is included in the sitemap
In a WordPress site, the sitemap plays an important role for Google in discovering posts.
On the site I checked, the following sitemap was set up:
sitemap_index.xml
If recently written posts are normally included in the sitemap, you can at least confirm that the site is registering the URL of the new post in the sitemap.
However, there is something to be careful about here.
Just because a URL is in the sitemap does not mean that Google will necessarily index it immediately.
A sitemap is a means of notifying Google of URLs, not a feature that forcibly executes search result registration.
Therefore, a situation where a new post is in the sitemap but is not searched right away can easily occur.
You must also check robots.txt
The next part to check is robots.txt.
The setting I was using was in the following form:
User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php
User-agent: Yeti Allow: /
Sitemap: https://newspaperioccasionallyread.com/sitemap_index.xml
The important part here is /wp-admin/.
Since the WordPress admin area is an area that general visitors do not need to search, it is common to restrict access by search crawlers.
On the other hand, there should be no rules blocking general post URLs.
For example, if there is a setting that blocks all posts like the following, it could be a problem.
Disallow: /
This kind of setting and the current /wp-admin/ block are completely different issues.
Therefore, when looking at robots.txt, you should not judge that there is a problem simply because the word Disallow exists.
Normal robots.txt does not guarantee indexing
Here, one thing must be distinguished.
robots.txt is basically a rule regarding which areas of a site crawlers can access.
Therefore, just because robots.txt is normal does not mean a specific post is necessarily registered in Google search.
Conversely, just because a URL is included in the sitemap does not mean it will be indexed immediately.
In the end, the following elements play different roles:
robots.txt: Crawler access rules sitemap: Delivering site URLs to search engines Crawling: The process where Google actually checks the content of the URL Indexing: The process of including the checked page in the Google search database Search exposure: The process where the indexed page actually appears in search results
If you think of all these as the same thing, it becomes difficult to find the problem.
The most accurate check method is Search Console’s URL Inspection
To check if a new post is really not indexed, it is better to use Google Search Console’s URL Inspection rather than simply looking at a site: search.
If you enter the exact URL of the new post, you can check Google’s processing status for that URL.
For example, if the URL is not yet registered with Google, you can confirm in Search Console that it is in an unindexed state.
What is important here is to distinguish between simply “it does not appear in search results” and “Google has not yet indexed the URL.”
site: search is convenient as a simple check method, but Search Console’s URL Inspection is more direct as a tool for diagnosing the current status of a specific URL.
If only one new post does not appear, there is no need to hastily suspect the entire site
For example, you can think of a situation like this:
Existing posts are searched on Google. Some recent posts are also searched. The new post is also included in the sitemap. robots.txt is not blocking general post URLs. However, only one post written today is not visible in site: search.
In this case, there is insufficient basis to immediately judge that the entire site’s indexing system is broken.
Especially if it is right after publication, there is also a possibility that Google has not yet crawled or indexed that URL.
Therefore, you should look at a single new post not being searched and the entire site not being indexed as separate issues.
Index requests can be used when necessary
In Search Console’s URL Inspection, you can request indexing for individual URLs.
If an important page does not appear on Google after publishing a new post, you can use this feature.
However, just because you made an index request does not mean it will necessarily be registered in search results immediately.
Also, repeatedly requesting the same URL does not necessarily mean it will be indexed any faster.
Therefore, rather than an all-powerful button to solve problems, it is appropriate to understand index requests as a feature to request Google to check that URL.
Order to check when new post indexing is delayed
If a new post does not appear on Google, you can check in the following order:
Check actual publication status
Check if the post is normally made public in WordPress.
Check exact URL
Check if the address is incorrect or if it is a redirecting URL.
Check sitemap
Check if the URL of the new post is included in the sitemap.
Check robots.txt
Check if there are rules blocking general post URLs.
Search Console URL Inspection
Inspect the URL directly to check what status Google sees it in.
Request indexing if necessary
If it is an important post, you can use index request in URL Inspection.
What was actually the problem?
In the situation I checked, several recently written posts were included in the sitemap, and existing posts could also be confirmed through site: search.
And among the newly written posts, there was a situation where only the post written on that day was not confirmed in the search results.
In such a case, if the sitemap or robots.txt is normally configured, it is more accurate to check the Search Console status of that URL rather than immediately tearing down and fixing settings.
In particular, because the time it takes to appear in search results may not be the same for all posts, you should not judge it as an index failure simply from the fact that it is not searched right after publication.
Wrapping up
When a new post in WordPress does not appear in Google search, the first thing to do is not to change this and that setting.
You should first check and distinguish between sitemap, robots.txt, and Search Console’s URL Inspection results.
The key points are as follows:
Just because it is in the sitemap does not mean it is indexed immediately. Just because robots.txt is normal does not guarantee indexing. site: search can be used for a simple check. Search Console’s URL Inspection is more direct for exact URL status. There is no need to judge it as an issue with the entire site simply because a single new post on the day of publication is not searched.
If a new post continues to not be indexed, then it is not simply a matter of waiting, but it is important to check the cause by distinguishing whether that URL was not discovered or whether it was crawled but not indexed in Search Console.