The most common way to let Google know about new content on your site is by using XML sitemaps. However, some folks have started using Google’s indexing API to push new content to Google, but that’s likely not a good idea.
For more, check out the full post over on Search Engine Roundtable.
Subscribe! You can subscribe to this podcast on Apple Podcasts, Anchor, Google Podcasts, Spotify, Breaker, Pocket Casts, RadioPublic, Stitcher, Overcast, and a variety of other places. Be sure to rate the podcast wherever you choose to listen!
For years, most websites have provided Google with XML sitemaps to help Google see new content on the sites. Virtually every SEO-related plugin includes this feature, and it’s fairly easy to set up inside of Google Search Console.
However, some SEO folks have been encouraging people to configure and use Google’s “indexing API” as a way for Google to find (and index) your content more quickly. Google has just come out to say that you really shouldn’t be doing that.
In particular, Google’s John Mueller said:
“The indexing API is only for job posting and live stream structured data. For everything else, just use sitemaps”
He reiterated it in follow-up tweets with roughly the same info. Things may change in the future, but for now you should just stick to your XML sitemaps.
If you’re tempted to try this out anyhow, I like Barry Schwartz’s thoughts on the Search Engine Roundtable blog. Barry said:
“So for now – don’t use Google’s indexing API for all web content. It probably looks like it might work, but probably does not. And if too many people do it, Google might decide they want to take action. So be careful.”
At best, you might get your content indexed by Google a tiny bit faster. At worst, you might get penalized, so it’s not worth the risk.
If you’re not familiar with XML sitemaps or don’t use them on your site, research them a bit and try to get them added to Google Search Console. If you already use them, then you’re in good shape and you’d be wise to leave well enough alone.