Google Search Console Download Error More Than 1000
Update: I experience really sad to inform that google has discontinued the Google Search Console API Explorer. Due to this, this method doesn't work anymore.
The Google Search Console is of slap-up 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.
Nevertheless, the Google Search Panel also has several aspects that are somewhat frustrating. For eg; the "Links to your site" feature only shows a maximum of thou domains. Now, Imagine how many domains link to a site like Moz or Buzzfeed! Do you recall the Google Search Console serves them well?
The sitemap tool shows how many URLs were indexed but does non distinguish betwixt the not-indexed and indexed URLs . And well there are other similar annoyances. (Update: Google is testing a beta feature calledAlphabetize Coverage written report that will show indexed pages count and reasons why some pages could not be indexed. Read more than on Google Webmaster Blog.)
Another point that annoys Google Search Console (GSC) users is the Crawl Errors report. The Search Console shows u.s.a. the crawl errors, the HTTP status code of the error (404, 503 etc), and too the source of the error. The bothersome part is you have to click on each URL to view where the error originates from.
Some other problem is the ane,000 errors limit. Y'all'll have to fix the existing ones to view newer ones.
Solution: Download crawl errors with source using Google API Explorer
The Google API explorer is a savvy tool to communicate with numerous Google APIs. But we need to business concern ourselves merely with the Search Console API.
You'll need Full Access to use the API and Search Console account, then make certain you accept them beforehand.
Once logged in, yous'll find the Search Console API offers several Services , 13 services to be exact. But our focus here is the ane labeled webmasters.urlcrawlerrorssamples.list . And so, get ahead and click on it.
The next screen will look like the image below. Across this point information technology's a simple 3 stride process:
1. Fill up in the parameters and Execute the query
The fields y'all notice on the next screen read every bit follows:
- Site URL – Quite self-explanatory
- Category – This field is for cogent the type of errors you lot'd like to filter information technology with. Luckily for u.s.a., it offers an like shooting fish in a barrel to use drop down with possible fields. For 404 errors, choose notFound every bit the choice.
- Platform – This refers to the user agent or simply the type of device y'all wish to retrieve errors for. Again an piece of cake drib downward to aid us out. We'll be selecting spider webfor now.
- Fields – This specifies the data you desire to remember forth with crawl errors like source, error detected on date, last crawled engagement, error code etc.
Use the fields editor to select required fields. The available ones are:
- urlCrawlErrorSample – Provides data about the sample URL and its crawl fault
- first_detected – Know the date when the error was beginning detected
- last_crawled – Is the date when the URL was start crawled
- pageUrl – The URL of crawl error
- responseCode – duh
- urlDetails – To recollect more details about error URL. Selecting information technology gives you ii options:
- containingSitemaps – Sitemap URLs pointing to the crawl mistake
- linkedFromUrls – Source of the clamber fault. The root of all the fuss!
I prefer selecting all the data and filtering information technology down later. You are free to choose your path.
Oh! Do turn on the Qualify requests using OAuth 2.0 button on summit right (marked with an orange rectangle in the paradigm)
or
Once all the fields are set, just click the Qualify and execute push button.
Yous'd exist greeted with a popup before the report runs, like in the epitome below:
Check both options and hit the Authorize and execute push button.
2. Catechumen the output JSON to a CSV
If everything goes well, y'all should see a status 200 OK message with a JSON output like to the image below
Copy the output after the beginning curly bracket { till the last } curly subclass in the finish.
At present, head over to a JSON to CSV converter. I prefer https://konklone.io/json/ for the uncomplicated interface, a preview window, and the ability to download the CSV.
Note: I tried another converter as well but the written report wasn't 100% accurate. Test your converter before you finalize on a study.
Paste the JSON output and convert information technology into a CSV.
3. Download the CSV and Gear up 404 errors
This is pretty much self-explanatory! Download your CSV and first fixing those 404 errors.
Word to the wise: Google Search Console may not listing sources or linking domains for all errors. And so don't worry if some rows returned are empty.
Decision:
404 errors may not seem critical but fixing them helps saves crawl budget, improves user feel, and besides helps retain link value.
You may utilise the same process to observe and fix other errors. The API includes 9 types of errors in the Google Search Console that you lot can fix. Yous don't have to wreck your brain to search them out; we have listed all error types below.
- authPermissions
- flashContent
- manyToOneRedirect
- notFollowed
- notFound
- other
- roboted
- serverError
- Soft404
I hope you find this useful! Now head to your laptop and start fixing those 404 errors.
Rajiv Singha
I am part of the CueBlocks Organic Search(SEO) team. I love playing football and reading almost Technical SEO.
MORE POSTS
DOWNLOAD HERE
Posted by: thomasrebt1992.blogspot.com
0 Komentar
Post a Comment