Solutions after a bad use of the Google Indexing API

mboss

Newbie
Joined
Jan 10, 2024
Messages
6
Reaction score
1
Hello, im pretty sure one of my sites got hit cause a bad use of the Google Indexing API.

Question is: anyone has gotten out of this scenario? if so, how?


Edit:
This is an informative website that has several subdomains(/it - /fr .. etc) - in different languages, in the google cloud account I created a project for subdomain in order to have 200 requests per day per subdomain.

The first day that the api registered activity was the 21st of november.

The case is that the web had more than 2000 urls indexed and a few days after starting to use the api, we saw how all the urls that were missing to be indexed were indexed without problem. Attached image:
1704913406568.png

A few days later, as you can see, specifically on November 28th, they dropped drastically. Leaving only the home page of each subdomain.

We made some changes in the web and updated most of the urls, both in content and the updatedTime field (this was on November 23rd).

Therefore, from the 21st to the 28th practically all urls were sent again to index with the Google Indexing API.


It should be noted that in the rest of the search engines the web works better than ever and the number of indexed pages is increasing.
 
Last edited:
Do you have more details on "bad use" of the G API?
 
if the scenario is you used a lot of accounts to bypass the limit then probably is pretty hard to get out from that "sandbox"
 
if the scenario is you used a lot of accounts to bypass the limit then probably is pretty hard to get out from that "sandbox"
Does it count as more accounts have multiple projects in the same account? I updated the main post with more details.
 
The mere fact of using the Indexing API incorrectly does not penalize the site. It just calls the analyzer, which examines the site in more detail from all sides, as spam sites usually use API incorrectly.
If the analyzer has decided that your site is low-quality and reduced its ranking, you will have to get out of this filter for a very long time, if at all you can.
 
I updated the main post with more information about the problem
But this is not bad use of the API.

I'm afraid but have the feeling that you are not giving all details.
 
But this is not bad use of the API.

I'm afraid but have the feeling that you are not giving all details.
What do you mean by not giving all details? Tell me if you need anything else, ive no problem in being clear.

As far as i Know i did nothing against Google algorithm itself
 
The mere fact of using the Indexing API incorrectly does not penalize the site. It just calls the analyzer, which examines the site in more detail from all sides, as spam sites usually use API incorrectly.
If the analyzer has decided that your site is low-quality and reduced its ranking, you will have to get out of this filter for a very long time, if at all you can.
Ive being thinking that for a while now, but as theres no real confirmation of whats the issue and ive seen a lots of dudes calling for the same problem after using the api. I just want to be 100% sure of whats going on
 
What do you mean by not giving all details? Tell me if you need anything else, ive no problem in being clear.

As far as i Know i did nothing against Google algorithm itself
Updating your website has nothing to do with the Google API as such. So, what did you do with the API?
 
Ive being thinking that for a while now, but as theres no real confirmation of whats the issue and ive seen a lots of dudes calling for the same problem after using the api. I just want to be 100% sure of whats going on
Google employees in conversations mentioned changes to the Indexing API back in January-March 2023.
They told us that they will now pay close attention to sites that submit pages through the Indexing API in bulk.

Our several teams conducted different tests throughout the year, trying to find out the threshold of acceptable submission limit for different types and structures of sites. The results were shared in the Telegram channel. You are guaranteed to fall under the work of this algorithm, there are no other options.

At the same time, Google employees told that for this algorithm, there are modified rules on the coefficients of copies and distribution of materials, they are much lower than the usual check.
If the usual check you have on your site is allowed 60% of copies and 40% of their materials, then with this check 25% of other people's materials will lead to a sharp drop in the rating.
 
Google employees in conversations mentioned changes to the Indexing API back in January-March 2023.
They told us that they will now pay close attention to sites that submit pages through the Indexing API in bulk.

Our several teams conducted different tests throughout the year, trying to find out the threshold of acceptable submission limit for different types and structures of sites. The results were shared in the Telegram channel. You are guaranteed to fall under the work of this algorithm, there are no other options.

At the same time, Google employees told that for this algorithm, there are modified rules on the coefficients of copies and distribution of materials, they are much lower than the usual check.
If the usual check you have on your site is allowed 60% of copies and 40% of their materials, then with this check 25% of other people's materials will lead to a sharp drop in the rating.
Have you seen any web sites recover from this? Something very similar has happened to me, what do you recommend me to do?

- Redirect everything to a new DOMAIN and put everything the same without using the API?

- Change the content to have 25% or less similarity?
 
Have you seen any web sites recover from this? Something very similar has happened to me, what do you recommend me to do?

- Redirect everything to a new DOMAIN and put everything the same without using the API?

- Change the content to have 25% or less similarity?
If sanctions have already been applied, it is very difficult and time-consuming to undo them.
Yes, moving to a new domain would be the best solution in this case.

And no more poisoning pages after the move via Indexing API at all.
It is better to send Google mobile bot in small batches to the heaviest pages of the site from where there are many links to other pages of the site.
 
Hey i have a domain where i post 5000 jobs daily and I use service account of the corresponding domain(200 quota) and also another service account not from the corresponding domain email (where i have 80k quota) to post jobs via Indexing API. After 14-21 days the Googlebot stopped visiting my domain and apparently, it stopped visiting for any new jobs, But I can see bot visits for older jobs daily. Can someone help me out with what is wrong?
 
The mere fact of using the Indexing API incorrectly does not penalize the site. It just calls the analyzer, which examines the site in more detail from all sides, as spam sites usually use API incorrectly.
If the analyzer has decided that your site is low-quality and reduced its ranking, you will have to get out of this filter for a very long time, if at all you can.
Can you please define/elaborate on what does "using the Indexing API incorrectly" in your words?
 
Can you please define/elaborate on what does "using the Indexing API incorrectly" in your words?
Google's help is very clear and comprehensive about what to use it for and how to use it. Everything else is misuse.
 
Google's help is very clear and comprehensive about what to use it for and how to use it. Everything else is misuse.
i have a domain where i post 5000 jobs daily and I use service account of the corresponding domain(200 quota) and also another service account not from the corresponding domain email (where i have 80k quota) to post jobs via Indexing API. After 14-21 days the Googlebot stopped visiting my domain and apparently, it stopped visiting for any new jobs, But I can see bot visits for older jobs daily. Can someone help me out with what is wrong? Can u help on this?
 
i have a domain where i post 5000 jobs daily and I use service account of the corresponding domain(200 quota) and also another service account not from the corresponding domain email (where i have 80k quota) to post jobs via Indexing API. After 14-21 days the Googlebot stopped visiting my domain and apparently, it stopped visiting for any new jobs, But I can see bot visits for older jobs daily. Can someone help me out with what is wrong? Can u help on this?
You've got it all wrong. If you haven't announced on your homepage and service pages that you're an official job aggregator and where you get your jobs from, then you're in violation of everything you can - you don't belong on Google's current job listings. He announced this already a year ago.

If you are not an aggregator - you can't have so many jobs, you are a spammer. You will be penalized by Google and you will start losing positions to complete zero, although the old index will most likely remain intact, usually such penalty just stops processing and pages remain in the index as they are no longer processed by Google at all.
 
You've got it all wrong. If you haven't announced on your homepage and service pages that you're an official job aggregator and where you get your jobs from, then you're in violation of everything you can - you don't belong on Google's current job listings. He announced this already a year ago.

If you are not an aggregator - you can't have so many jobs, you are a spammer. You will be penalized by Google and you will start losing positions to complete zero, although the old index will most likely remain intact, usually such penalty just stops processing and pages remain in the index as they are no longer processed by Google at all.
Oh is it really! if you don't mind can you send me a sample of how to announce that on the homepage and service pages so that I can overcome the situation?
 
Oh is it really! if you don't mind can you send me a sample of how to announce that on the homepage and service pages so that I can overcome the situation?
Use a google search and see what the official job site says.
 
Back
Top