{"id":5682,"date":"2024-07-30T12:37:30","date_gmt":"2024-07-30T12:37:30","guid":{"rendered":"https:\/\/www.cueforgood.com\/blog\/?p=5682"},"modified":"2025-11-13T15:56:51","modified_gmt":"2025-11-13T10:26:51","slug":"download-404-errors-google-search-console-linking-pages","status":"publish","type":"post","link":"https:\/\/www.cueforgood.com\/blog\/download-404-errors-google-search-console-linking-pages\/","title":{"rendered":"How to download 404 errors from Google Search Console with Linking pages"},"content":{"rendered":"\n

Update:<\/strong> I feel really sad to inform that google has discontinued the Google Search Console API Explorer. Due to this, this method doesn\u2019t work anymore.\n<\/p><\/div>\n\n\n\n

The Google Search Console is of great help to Webmasters with several useful features like sitemap submission, search analytics, links to your site, crawl errors report. With the GSC, the SEO specialists have a powerful tool at their fingertips to direct the course of their SEO requests.<\/p>\n\n\n\n

However, the Google Search Console also has several aspects that are somewhat frustrating. For eg; the \u201cLinks to your site\u201d feature only shows a maximum of 1000<\/strong> domains. Now, Imagine how many domains link to a site like Moz or Buzzfeed! Do you think the Google Search Console serves them well?<\/p>\n\n\n\n

The sitemap tool shows how many URLs were indexed but does not distinguish between the non-indexed and indexed URLs<\/span>. And well there are other similar annoyances. (Update: <\/strong>Google is testing a beta feature called Index Coverage report <\/strong>that will show indexed pages count and reasons why some pages could not be indexed. Read more on Google Webmaster Blog<\/a><\/span>.<\/em>)<\/span><\/p>\n\n\n\n

Another point that annoys Google Search Console (GSC) users is the Crawl Errors report<\/strong>. The Search Console shows us the crawl errors, the HTTP status code of the error (404, 503 etc), and also the source of the error. The bothersome part is you have to click on each URL to view where the error originates from.<\/p>\n\n\n\n

\"Search<\/a><\/figure>\n\n\n\n

Another problem is the 1,000 errors limit. You\u2019ll have to fix the existing ones to view newer ones.<\/p>\n\n\n\n

Solution: Download crawl errors with source using Google API Explorer<\/h2>\n\n\n\n

The Google API explorer<\/strong><\/a> is a savvy tool to communicate with numerous Google APIs. But we need to concern ourselves only with the Search Console API<\/strong><\/a>.<\/p>\n\n\n\n

You\u2019ll need Full Access to use the API and Search Console account, so make sure you have them beforehand.<\/p>\n\n\n\n

Once logged in, you\u2019ll notice the Search Console API offers several Services<\/b>, 13 services to be exact. But our focus here is the one labeled <\/span>webmasters.urlcrawlerrorssamples.list<\/b>.<\/span> So, go ahead and click on it.<\/span><\/p>\n\n\n\n

The next screen will look like the image below. Beyond this point it\u2019s a simple 3 step process:<\/p>\n\n\n\n

\"404<\/a><\/figure>\n\n\n\n

1. Fill in the parameters and Execute the query<\/h2>\n\n\n\n

The fields you notice on the next screen read as follows:<\/p>\n\n\n\n