
The indexing API receives many requests from bloggers attempting to appear legitimate. Google responds with increased caution and spam detection. Google has warned that misuse can trigger spam-related handling and that unsupported content will not work through the indexing API. The API is intended only for job postings and live stream content. Guidance also emphasizes stopping use for other content types. Some users report that content may be indexed quickly at first but later drops out of search results, indicating unreliable outcomes when used outside supported purposes.
"“The indexing API is inundated by bloggers trying to act like legitimate sites.” This means that Google needs to be more careful about who and what they accept through the Google indexing API."
"“I'm not aware of any particular issues, but I know the indexing API is inundated by bloggers trying to act like legitimate sites, so I imagine they're just a bit more cautious nowadays.” John has been telling folks to stop using the Indexing API for unsupported content."
"As a reminder, the Google Indexing API should just be used for job postings and live stream content - nothing else. Google has said if you use it for other purposes it won't work. Many who have tried it over the years said it works to get your content indexed fast but then it drops out of the index quickly after."
"Google posted a warning about spam detection for the Google Indexing API. Also, John Mueller of Google said most sites wrongfully using the indexing API are spammy anyway."
Read at Search Engine Roundtable
Unable to calculate read time
Collection
[
|
...
]