Google launches the Search Console URL Inspection API
A new tool designed for developers and SEOs, who can debug and optimize the pages of their sites using the official data of the Search Console integrating them into their favorite analytics tools: This is how Google presents the launch of the Search Console URL Inspection API, which precisely allow programmatic access to data at the URL level for properties managed in GSC.
Search Console URL Inspection APIs, what they are and how they work
Search Console APIs are a way to access data outside of Search Console, via external applications and products, and already allow you to create custom solutions to view, add or remove properties and sitemaps and to perform advanced queries on search performance data.
Thanks to the API Search Console URL Inspection, made official a few days ago by an article by Daniel Waisberg and a tweet by @googlesearchc, we can now access programmatically the data and reports generated by the tool with the same name, also through external apps and softwares (and even Seozoom will soon be able to integrate this information).
Through APIs – which stands for Application Programming Interface, basically a bridge between two software programs to allow dialogue – we can check the information related to indexing status, the multimedia results and the usability on mobile devices of any URL of which we verified the access in Google Search Console also outside of this tool.
How to use APIs for the Search Console URL Inspection tool
As clarified by the post, to use the API you must refer to the method: index.inspect, which provides to use as parameters of the request the URL we want to check and the URL of the property as defined in Search Console, inserted with gRPC transcoding syntax.
The answer includes the results of the analysis containing information from Search Console, starting from the indexed or indexable status of the URL provided: it is important to note that, at the moment, the API analyze the status of the page scanned with the inspector, and not the “live” status, and thus all