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.
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.
Do not use this tool. Google representative John Mueller says this: "Like the documentation has stated for a long time, the Indexing API has a very limited set of use-cases that's supported. It's great to see passionate people try to do more with it, but a) it's often for spam & low-quality, and b) it's not supported."
Nice find. One tweet says this, hadn't seen this sort of data point before:
>Well 1) the site lost the index after he started using the api - the spam redirects worked before that :) 2) it is quite clear that API has to be used for jobs and videos 3) I have tested this with multiple domains and always after 3-9 months you get killed.
Great question. The big advantage of IndexBlaze is that it doesn’t require any programming knowledge. It’s super user-friendly—just sync your Google Search Console, submit your URLs, and we handle the rest. No coding, no hassle.
I’m a solopreneur. I know how growing with SEO is hard and time-consuming.
I realized I was constantly waiting for my new content to get indexed on Google, which slowed down my business growth. So I built IndexBlaze for 2 reasons:
1. Save time and focus on what matters: creating valuable content and growing my online presence. With IndexBlaze, my web pages are indexed on Google in less than 24 hours.
2. Avoid the headache of manual indexing: No more waiting weeks for Google to index my site. The automated bulk indexing feature saves me a lot of time and effort, especially for sites with a large number of pages.
I hope this tool will be as helpful to you as it is for me. Would love your feedback pls
Thank you for your comment. Here’s an explanation of how IndexBlaze works:
1. Integration with Google Search Console (GSC):
• Connect your GSC account to IndexBlaze.
• IndexBlaze retrieves the indexing status of your URLs from GSC.
• The dashboard displays which pages are indexed for easy monitoring.
2. Using the Google Web Indexing API:
• Submit new URLs through IndexBlaze.
• IndexBlaze sends these URLs directly to the Web Indexing API.
• Google’s crawlers are prompted to visit and index the pages promptly.
3. Bulk and Automatic Indexing:
• Supports bulk URL submission for efficiency.
• Manages submission rates to stay within Google’s quotas.
• Ensures your content remains up-to-date and visible on Google without manual intervention.
I’d love to hear your feedback on how it works for you!
We integrate directly with Google Search Console to check the indexing status of each link. When a new link needs indexing, we use the Google Indexing API to submit it. This speeds up the whole process without requiring any programming knowledge.
Google Cloud has an API to crawl a page, but it’s only meant to be used for job postings and live events, so they can add and remove the pages quicker than usual.
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.