Google Index API is not working with the new website

[movieniche]

Yep, this has stopped working and I doubt it will come back for indexing purposes of blog posts, it's been done on purpose as bit of a coincidence after they said this - https://www.searchenginejournal.com/google-adds-spam-warning-to-indexing-api-documentation/526839/

It was never meant to be used for the reasons we do.

Shame as I used it, but been trying the last few days and no visit at all after submitting.

 

[GoogSEO]

This is weird. I do the same like you (via google APIs explorer) on my legit blog, and I cant see the type and notifytime in response. And, googlebot doesn't visit my page.

View attachment 378180

That's probably why no one will tell you how to do it, so that everyone can't do it again and make Google restrict these ways too.
And it's good, I see that the creators of dorways don't use api anymore, too complicated for them, they switched to work parasites now, the latest dorways are all indexed with their help.

 

[ron66]

As mentioned before the API was always meant for specific tasks (job posting for example). Google never enforced it, it seems that now they do.

 

[claymancz]

That's probably why no one will tell you how to do it, so that everyone can't do it again and make Google restrict these ways too.
And it's good, I see that the creators of dorways don't use api anymore, too complicated for them, they switched to work parasites now, the latest dorways are all indexed with their help.

As mentioned before the API was always meant for specific tasks (job posting for example). Google never enforced it, it seems that now they do.

But it doesn't work even for my jobposting schema page, will give it some time.

 

[netproxy]

Make sure Google will be delayed. Check if your robots.txt file is blocking Google. Good luck for you

 

[Mazaaa1]

That's probably why no one will tell you how to do it, so that everyone can't do it again and make Google restrict these ways too.
And it's good, I see that the creators of dorways don't use api anymore, too complicated for them, they switched to work parasites now, the latest dorways are all indexed with their help.

What do you mean that they switched to work parasites now , can you explain ?

 

[GoogSEO]

What do you mean that they switched to work parasites now , can you explain ?

Use the site search here, it's been discussed and more than once.

 

[Mazaaa1]

Use the site search here, it's been discussed and more than once.

Their is no such topic about people indexing millions of page for doorways with work parasite, thats why I'm asking here

 

[TOR SEO]

I've used the Google Index API and it shows success, but when I check Google Search Console, I don't see any Googlebot crawling. Has anyone used the Google Index API for a new website and had Googlebot crawl it immediately?

Read it about google indexing api updates https://www.seroundtable.com/google-updates-indexing-api-spam-detection-38056.html

 

[2Index]

Google API doesn't work like it used to. Now job pages are indexed 100%, but they won't tell you what exactly you need to do. There are other methods, they are already actively used.

 

[claymancz]

Google API doesn't work like it used to. Now job pages are indexed 100%, but they won't tell you what exactly you need to do. There are other methods, they are already actively used.

Hell yeah, I tried Job pages and API was not working. Have you tried too?

 

[iliag]

I have noticed recently that Indexing API doesn't return URL_UPDATED in urlNotificationMetadata for new Google Cloud projects / service accounts with the default quota of 200 requests per day. Probably it's a part of their new policies regarding Indexing API. And I've been trying to use it legitimately, i.e. for jobs pages with jobPosting structured data.

The old projects work just fine.

 

[claymancz]

I have noticed recently that Indexing API doesn't return URL_UPDATED in urlNotificationMetadata for new Google Cloud projects / service accounts with the default quota of 200 requests per day. Probably it's a part of their new policies regarding Indexing API. And I've been trying to use it legitimately, i.e. for jobs pages with jobPosting structured data.

The old projects work just fine.

Does jobposting work for you? For me not..

 

[dghdavidbrown]

Googlebot's crawling takes a while

 

[iliag]

Does jobposting work for you? For me not..

It works, but it's very unstable. Probably they are still figuring out how to fight the Indexing API abuse.

So basically having a job board and proper jobPosting structured data on your job pages doesn't necessarily mean that the Indexing API would work for you.

 

[embossitworld]

Yes, the Google Indexing API can help speed up indexing, but it's mainly for pages with quick-changing content, like job postings or live events. Even if the API shows "success," it doesn't guarantee immediate crawling or indexing, especially for new websites. Googlebot follows its own schedule and priorities for crawling, so it may take time for Google Search Console to show activity. If your website is new, building backlinks and regularly updating quality content can encourage faster indexing.

 

[djg3577]

It works, but it's very unstable. Probably they are still figuring out how to fight the Indexing API abuse.

So basically having a job board and proper jobPosting structured data on your job pages doesn't necessarily mean that the Indexing API would work for you.

I'm working with a job board and using Google’s Indexing API to submit indexing requests. When I send a POST request through the API, I receive a 200 response, and the URL appears in urlNotificationMetadata. However, when I try to check the status of the request using the GET endpoint (https://indexing.googleapis.com/v3/urlNotifications/metadata), I get a 404 error stating, "Requested entity was not found."

I've confirmed that the URL is correctly encoded in the GET request, but I still can’t verify whether the original POST request is being processed for crawling. I know it can take time, but after waiting two weeks, the pages still haven’t been indexed.

For context, my site is verified in Google Search Console, and manual indexing requests work fine there. I’m using a service account with a secret key, and the POST request is authenticated per the API guidelines. Despite this, I’m not seeing any new pages indexed on the Google Search Console side after using the API.

How long does it typically take to see results on Google’s job board, and have you used the Get notification status endpoint to check request statuses?

 

[iliag]

I'm working with a job board and using Google’s Indexing API to submit indexing requests. When I send a POST request through the API, I receive a 200 response, and the URL appears in urlNotificationMetadata. However, when I try to check the status of the request using the GET endpoint (https://indexing.googleapis.com/v3/urlNotifications/metadata), I get a 404 error stating, "Requested entity was not found."

I've confirmed that the URL is correctly encoded in the GET request, but I still can’t verify whether the original POST request is being processed for crawling. I know it can take time, but after waiting two weeks, the pages still haven’t been indexed.

For context, my site is verified in Google Search Console, and manual indexing requests work fine there. I’m using a service account with a secret key, and the POST request is authenticated per the API guidelines. Despite this, I’m not seeing any new pages indexed on the Google Search Console side after using the API.

How long does it typically take to see results on Google’s job board, and have you used the Get notification status endpoint to check request statuses?

For me 100% of the jobs submitted to the API are being accepted. The issue is that Googlebot doesn't seem to come for them. It depends on a specific job board. Some of the websites are being visited by the bot instantly and the others are being ignored. It looks like there's some flag assigned by Google.

Regarding your issue with getting the status, you can verify it with the API explorer in Google Cloud Console. I am not doing it programmatically but the API explorer shows correct status for my submissions..