Using Google Search Console to Manage ‘Search Enhancement’ Validation Errors and Employ the API
As we conclude our series on Google Search Console, we’ll explore reporting features for front-end markup errors and some data management options. Note that we are discussing Google “Search Enhancements” validation errors, so for HTML and CSS validation, you’ll need to refer to other sources.
## Search Enhancements
We’ve previously discussed page-level error reporting using the URL Inspection Tool. The Enhancements section provides details on site-wide warnings and error reporting.
Here, information on Mobile Usability, AMP-HTML, and Rich results can be accessed when the corresponding markup is detected. Google offers a few dedicated validation services, and it’s beneficial to see some replication of these within Google Search Console. However, findings from Lighthouse are notably absent.
In the Mobile Usability report, you can identify errors not necessarily related to validation but flagged by Google as mobile-unfriendly.
Ideally, no errors will be present, but it’s essential to recognize that perfectly valid markup can be reported as having Mobile Usability “errors.” This knowledge is crucial when conveying Mobile Usability feedback to developers. The errors, in this case, indicate valid markup for a page that is otherwise not mobile-friendly.
Regarding AMP and Structured Data reporting, validation errors can broadly influence your appearance in Google Search, beyond just mobile search. Here, a data table with details is more useful than charts. It’s common to find only a fraction of your indexed pages in reporting. Google API documentation refers to this fraction as a “sample list.” These data hint at pages where detected markup could potentially enable corresponding Google “Search Enhancement” features.
## Security & Manual Actions
The most critical issues you might see reported in Google Search Console are located in the Security & Manual Actions section. It’s crucial to address these issues promptly, as they might cause you to be removed from search results until resolved and your site is deemed safe again.
## Links
Google is renowned for its deep analysis of the Web, beginning with the countless hypertext links among URLs. While links are generally significant, assuming that a high link count will always boost your rankings is overly simplistic. Even when legitimately avoiding buying links for artificial ranking purposes, you’ll likely notice plenty of unnecessary links in your GSC Links report due to the massive link-building economy around Google.
## Downloads & GSC API
Google Search Console downloads may be inadequate for anything beyond individual use. You can select your date range for up to 16 months of history and download in CSV or Google Spreadsheet format.
A quick CSV download can be imported to Excel to be customized for a stakeholder’s specific needs. Beyond this application, downloads are less useful since you already have Search Console charts and data tables available. You’re more likely to progress to using Google’s Search Console Data Studio connector.
For more advanced users, while the Search Console remains a valuable data resource, it’s more practical to perform certain tasks — such as tracking multiple accounts for critical information — by incorporating data into a business intelligence dashboard or programmatically.
## Google Search Console API v3
Writing applications for advanced purposes using the Google Search Console API v3 can save effort. You can use the API Explorer with an OAuth 2.0 authenticated browser, allowing you to explore using buttons, checkboxes, and fields.
The API Explorer enables you to produce JSON responses, including error messages, without setting up a separate Google API Console Security Key. However, you’ll need a Key for programmatic access to Google’s APIs.
The Web-facing Explorer creates REST application POST URLs for retrieving JSON responses that can assist in preparing larger applications. You’ll need to keep the v3 API documentation handy. Below is a list of the methods implemented with the Explorer User Interface.
The Explorer generates the POST request created from executing your query, allowing easy emulation using curl to retrieve JSON from the command line. Ultimately, you’ll want to do so programmatically. Once you have the API Key for authenticating your query, you can write POST request URLs with the curl utility or integrate them dynamically into a host application.
## Client Libraries
For projects that require integration with larger applications such as a BI dashboard, Google offers example Python (and Java) “Hello World!” sample applications. These can be used from your command line once the Python (or Java) client is installed. You can clone a sample application, insert your Key, and modify code to get started.
Beyond officially listed client libraries, a quick search may provide what you need. I found a CRAN distributed R package updated to the current v3 API. With references in both Python and R, you should be ready to go. Additionally, since the v3 API is a RESTful resource, with your API Key, you can use virtually any language you choose.
