[graeme]

Note that this almost certainly uses Google's indexing API. rshzrh, please correct me if this isn't the case: https://developers.google.com/search/apis/indexing-api/v3/qu...

It's intended use is for job postings and short lived pages:

>Currently, the Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject. For websites with many short-lived pages like job postings or livestream videos, the Indexing API keeps content fresh in search results because it allows updates to be pushed individually.

Not too long ago some SEOs figured out it would get any page indexed. A bunch of services similar to this sprung up.

Currently this method works and incurs no penalty. However, it doesn't followed Google's intended use of the API and it's not impossible that some future algo update could downrank pages indexed via this method.

Search console allows you to manually request indexing for 10 pages per day. This seems to really work when google hasn't reviewed a page. I would love to use a service that took a queue of urls and indexed ten per day using the search console request form. I'm not sure if this is technically possible however. It is tedious to do ten pages per day, every day.

[rshzrh]

You’re right, IndexBlaze does leverage Google’s Indexing API to speed up the indexing process. While the API’s official use case is for job postings and short-lived pages, it can effectively get any page indexed, which many SEOs have discovered.

I understand the concern about potential future changes in Google’s algorithms. However, as it stands, using the Indexing API doesn’t incur any penalties and remains a valid method.