SEO myths and dead features guide
Can Google's Indexing API Index Ordinary WordPress Blog Posts?
No. Google documents the Indexing API for pages with JobPosting or livestream BroadcastEvent markup only. A successful response means a notification was received, not that a page was indexed.
On this page
No. Google’s documentation limits the Indexing API to pages with JobPosting structured data or a BroadcastEvent embedded in a VideoObject, which covers job postings and livestream videos. An ordinary blog post, service page, or product page is outside that scope. For those pages, the documented routes are a sitemap, internal links, and URL Inspection in Search Console for a few individual URLs.
Google’s Indexing API quickstart, checked September 27, 2026, states that the API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject. The same page says all submissions undergo spam detection, that attempts to abuse the API, including using multiple accounts to exceed quotas, may result in access being revoked, and that Google still recommends a sitemap for coverage of the entire site.
Identify the eligible content types
Eligibility depends on what the page is and the structured data it carries, not on the plugin that sends the notification. This table applies Google’s stated scope to common WordPress page types:
| Page | Structured data | Eligible for the Indexing API? |
|---|---|---|
| Blog post | Article or none |
No |
| Service or landing page | Any | No |
| Product page | Product |
No |
| Category or tag archive | Any | No |
| A single job posting page | JobPosting |
Yes |
| A livestream video page | BroadcastEvent inside VideoObject |
Yes |
Adding JobPosting markup to a page that is not a job posting does not make it eligible; it breaks Google’s rules for that markup. Google’s job posting structured data guidelines, checked September 27, 2026, say the markup must only be used on pages that contain a single job posting, and that violations may lead to manual action. If a plugin or service offers instant Google indexing for every post, compare its description with Google’s quickstart page and decide for yourself whether its use fits the stated scope.
Read API responses accurately
Part of the confusion comes from what a successful call returns. Google’s guide to using the Indexing API, checked September 27, 2026, describes two notification types, URL_UPDATED for new or changed pages and URL_DELETED for removed ones. For an update, it says an HTTP 200 response means Google may try to recrawl the URL soon.
That is a statement about receiving a notification, not about the result:
| What you see | What it means | What it does not mean |
|---|---|---|
200 to a URL_UPDATED notification |
The notification was accepted; Google may recrawl | The page is indexed, or will be |
A metadata GET showing the last notification time |
Google received a notification at that time | Google has crawled or indexed the page; the guide says the request does not tell you when Google indexes a URL |
| A tool’s “submitted” or “indexed” status | Whatever the tool defines it as | Check the tool’s own definition; it may only record a 200 |
The same guide notes that up to 100 calls can be batched in one HTTP request, with each call still counted against quota. The quickstart describes a default quota of 200 for onboarding and testing, with further use requiring approval.
The Indexing API pages cited here do not say what Google does with notifications for pages outside the eligible types. The quickstart does say that all submissions undergo spam detection and that abuse may lead to revoked access. Do not treat a 200 for an ineligible page as evidence that the approach works. To see whether a page is indexed, use the URL Inspection tool in Search Console, not the API response. Google’s Page indexing report help, checked September 27, 2026, says that report is not meant for checking specific pages and points to URL Inspection for the index status of a single page.
Choose the ordinary discovery route
For blog posts and other ordinary pages, use the routes Google documents for them.
- A sitemap. Submit the sitemap index once in Search Console. New posts appear in it as you publish. Google’s sitemap guidelines, checked September 27, 2026, call a submitted sitemap a hint that does not guarantee Google will download it or use it for crawling. If you use WP Visibility, Submit Your Sitemap has the steps.
- Internal links. Link new posts from relevant existing pages and from category pages or the blog index, so crawlers find them by following links. Google’s link best practices, checked September 27, 2026, say Google uses links to find new pages to crawl and that every page you care about should have a link from at least one other page on your site.
- URL Inspection for a few URLs. Google’s recrawl documentation, checked September 27, 2026, recommends URL Inspection for just a few URLs and a sitemap for many. It says there is a quota, that requesting a recrawl repeatedly for the same URL does not make it faster, that crawling can take anywhere from a few days to a few weeks, and that a request does not guarantee inclusion in results.
If an important post is not indexed after that, look for a cause on the page or the site: a noindex, a canonical naming another page, a fetch problem, or a page Google has crawled but not indexed. The same Page indexing report help describes each of these as a reason a URL is not indexed. A faster notification method does not fix any of those. Why a WordPress page is missing from your XML sitemap covers one common gap.
Where IndexNow fits
IndexNow is a different protocol, unrelated to Google’s Indexing API. A site tells participating search engines which URLs have changed. The IndexNow site, checked September 27, 2026, lists support from Microsoft Bing, Naver, Seznam.cz, Yandex, and Yep, and its FAQ, checked September 27, 2026, also lists an Amazon endpoint. Google is on neither list, so IndexNow is not a route to Google indexing.
WP Visibility includes an optional IndexNow module, off by default. When it is on, it submits a post’s URL when the post is published, updated, or unpublished, and skips draft saves, password-protected posts, and noindexed content. It does not send anything to Google’s Indexing API. The outbound requests listed in the plugin’s privacy manifest are the update check, license activation, IndexNow submissions when that module is on, and drafting requests to the site’s own AI provider when the optional Assist module is on. Details are in Turn On IndexNow. As with any notification, an IndexNow submission tells an engine a URL changed; the IndexNow FAQ says the engine then evaluates whether to crawl it based on its crawl quota, scheduling logic, and quality signals.
A quick check before you install an indexing tool
- Is the page a single job posting or a livestream video with the matching structured data? If not, the Indexing API is outside its documented scope.
- Does the tool say which API it calls and what its “indexed” status measures?
- Is the site’s sitemap submitted and working in Search Console?
- Are new posts linked from existing pages?
- For a specific post that is missing, have you checked URL Inspection for the reason?
If the answers to the last three are yes, the post is on the documented path. What remains is Google’s crawl schedule and its indexing decision, which no notification method controls.