New Google Search Console Url Inspection API Integration Process Though Screaming Frog

New Google Search Console Url Inspection API Integration Process Though Screaming Frog

Google’s new URL Inspection API allows software tools like Screaming Frog to gain access to Google Search Console and import data into the tool.

API stands for Application Programming Interface. It’s like a bridge between two software programs that allows both of them to connect to share data and achieve a certain level of integration between the two programs.

URL inspection API

Usage Limits:

2K URLs per property a day

Here’s the integration procedure we have done for your campaign:

#Step 1

To connect, go to ‘Configuration > API Access > Google Search Console’, connect to your account, choose your property.

After that proceed to click ‘Connect to New Account’ as shown here:

And then select the desired Google account to receive the verification code. A message will appear in the browser like this:

And you will need to select the desired property from the dropdown:

Next, tick the ‘Enable URL Inspection’ checkbox as stated below:

After integrating the Search Console API with Screaming Frog crawl the website:

#Here’s to the goal of new API filters:

URL Is Not on Google – The URL is not indexed by Google and won’t appear in the search results. This filter can include non-indexable URLs (such as those that are ‘noindex’) as well as Indexable URLs that are able to be indexed. It’s a catch-all filter for anything not on Google according to the API.

Indexable URL Not Indexed – Indexable URLs found in the crawl that are not indexed by Google and won’t appear in the search results. This can include URLs that unknown to Google, those that were discovered but not indexed, and more.

URL is on Google, But Has Issues – The URL is indexed and can appear in Google Search results, but there are some problems with mobile usability, AMP or Rich results that might mean it doesn’t appear in an optimal way.

User-Declared Canonical Not Selected – Google has chosen to index a different URL to the one declared by the user in the HTML. Canonicals are hints, and sometimes Google does a great job of this, other times it’s less than ideal.

Page Is Not Mobile Friendly – The page has issues on mobile devices.

AMP URL Is Invalid – The AMP has an error that prevents it from being indexed.

Rich Result Invalid – The URL has an error with one or more rich result enhancements that will prevent the rich result from showing in the Google search results.

Based on the above-mentioned filters here are the overall API data we get after full crawling:

#Action plan moving forward with this GSC API data:

  • You need to run the inspection through GSC. It is to fetch the Indexable URLs in Google for Indexable URL Not Indexed (122 URLs)
  • You need to optimize the URLs from the list. And make it available to indexed in Google in terms of URL Is Not on Google (169 URLs)