Indexing API

Well, there both is - and isn't an API. I have this habit of choosing names that indicate what a software does.  Like my EU e-Privacy Directive plugin - it was designed to help you comply with the EU e-Privacy Directive.  Kind of taking the mystery out of plugin selection.  Need a plugin that enhances Meta Robots - I happen to have a plugin to do that, it's named Meta Robots.  It's a sort of theme, or maybe a character flaw.

Content - Indexing API was named after the Google Web Content Indexing API service (you can see the theme, surely).  So it's not specifically designed to be an API - but it does have an interface for you to call.  It's very small, and calling it is super easy, barely an inconvenience.

Read more: Where is the API?

The Content - Indexing API plugin is designed to issue an indexing request to Google and/or Bing (via IndexNow) on content updates.  It was built to initiate indexing on the built-in Joomla content types, but there are many 3rd party components that can generate content.  In this example, we'll examine a unique combination in core Joomla components that I chose NOT to implement in Content - Indexing API specifically to allow me to use it as an example for 3rd party triggers.  This way, we can go through all of the parts of this plugin using features present in ALL Joomla installations.

Read more: Trigger Indexing API for Contact on Linked User Update