{"id":9908,"date":"2022-02-04T20:26:05","date_gmt":"2022-02-04T20:26:05","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/04\/screaming-frog-adds-google-url-inspection-api\/"},"modified":"2022-02-04T20:26:05","modified_gmt":"2022-02-04T20:26:05","slug":"screaming-frog-adds-google-url-inspection-api","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/04\/screaming-frog-adds-google-url-inspection-api\/","title":{"rendered":"Screaming Frog Adds Google URL Inspection API"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

Screaming Frog didn\u2019t waste any time integrating Google\u2019s new URL inspection API that allows access to current indexing data. The new API allows Screaming Frog to include seven brand new filters that identify website problems in need of attention.<\/p>\n

In addition to the expanded usefulness of Screaming Frog the new update, code named Romeo, also patches a log4j vulnerability issue, adds new keyboard shortcuts and fixes some bugs to make it more stable.\n<\/p>\n

Seven More Ways to Fix Websites<\/h2>\n

Google\u2019s new URL Inspection API allows software tools like Screaming Frog to gain access to Google Search Console and import data into the tool.<\/p>\n

API stands for Application Programming Interface. It\u2019s 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.<\/p>\n

Screaming Frog\u2019s integration of the URL Inspection API allows the popular site auditing program to provide the following brand new troubleshooting filters.<\/p>\n

Seven New Auditing Filters:<\/h3>\n
\n
    \n
  1. \u201cURL Is Not on Google <\/strong>
    The URL is not indexed by Google and won\u2019t appear in the search results. This filter can include non-indexable URLs (such as those that are \u2018noindex\u2019) as well as Indexable URLs that are able to be indexed. It\u2019s a catch all filter for anything not on Google according to the API.<\/li>\n
  2. Indexable URL Not Indexed<\/strong>
    Indexable URLs found in the crawl that are not indexed by Google and won\u2019t appear in the search results. This can include URLs that are unknown to Google, or those that have been discovered but not indexed, and more.<\/li>\n
  3. URL is on Google, But Has Issues <\/strong>
    The URL has been 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\u2019t appear in an optimal way.<\/li>\n
  4. User-Declared Canonical Not Selected<\/strong>
    Google has chosen to index a different URL to the one declared by the user in the HTML.<\/li>\n
  5. Page Is Not Mobile Friendly <\/strong>
    The page has issues on mobile devices.<\/li>\n
  6. AMP URL Is Invalid <\/strong>
    The AMP has an error that will prevent it from being indexed.<\/li>\n
  7. Rich Result Invalid<\/strong>
    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.\u201d<\/li>\n<\/ol>\n<\/blockquote>\n

    The value of the URL Inspection Tool API integration is that now you can overlay the Search Console indexing data onto the Screaming Frog crawl data, which allows you to see all the on-page data points extracted by Screaming Frog juxtaposed with the indexing status.<\/p>\n

    Screaming Frog now gains a Rich Results inspection tool that allows bulk export of the data from the Bulk Export tab at the top menu.<\/p>\n

    Additional Updates<\/h2>\n

    Other updates, in addition to the aforementioned log4j vulnerability patch are the addition of keyboard shortcuts (ctrl + W to close crawling projects), they made the Word Cloud Visualization tool language-aware in order to improve word-filtering, fixed a Page Speed Insights bug, an issue with JavaScript crawls that would cause a stall, fixed CSS Path extraction to make it support leading and trailing slashes and various other fixes that make Screaming Frog run smoother.<\/p>\n

    Screaming Frog URL Inspection API Integration Part 1?<\/h2>\n

    The update announcement offered a statement that noted that there is still some more integration work to be done to make it even better.<\/p>\n

    Because of practical limitations in how data can be fit into the Screaming Frog interface not all of the URL inspection data could be fit into it. But they promised to listen to user feedback to include additional data if users feel it\u2019s important.<\/p>\n

    The Screaming Frog announcement noted:<\/strong><\/p>\n

    \n

    \u201cWith use and user feedback, the way we integrate the data to gain additional insights will be improved as well.<\/p>\n

    If you spot any issues, or would like to see additional data or reporting from the URL Inspection API \u2013 just let us know via support.<\/p>\n

    We already have a few items planned, but wanted to get the basic feature including the most important items out there for users to enjoy quickly.\u201d<\/p>\n<\/blockquote>\n

    So it looks like even more good things are coming our way from Screaming Frog.<\/p>\n

    Citation<\/h2>\n

    Read the Official Screaming Frog Announcement<\/h3>\n

    Screaming Frog SEO Spider Update \u2013 Version 16.6<\/a><\/p>\n<\/div>\n