Posted by briangormanh
If you’’ ve been an SEO for even a brief time, you ’ re most likely knowledgeable about Google Search Console (GSC). It’’ s an important tool for getting info about your site and its efficiency in natural search. That stated, it does have its restrictions.
In this post, you’’ ll find out how to get better-connected information out of Google Search Console along with boost the size of your exports by 400%.
.Google Search Console constraints.
While GSC has a variety of areas, we’’ ll be concentrating on the ““ Performance ” report. From the GSC control panel, there are 2 methods you can access this report:
Once inside the ““ Performance ” report, information for pages and questions can be accessed:
This exposes among the problems with GSC: Query and page information is separated.
In other words, if I wish to see the inquiries a particular page is ranking for, I need to very first click ““ Pages, ” choose the page, and after that click “ back ” to “ Queries. ”It ’ s a really troublesome experience.
The other( two-part )problem is with exporting:
. Efficiency information for pages and inquiries need to be exported separately.Exports are restricted to 1,000 rows.
We ’ ll seek to resolve these problems by making use of the GSC API.
. What is the Google Search Console API?
Now we understand the GSC interface does have constraints: Connecting question information with page information is difficult, and exports are restricted.
.
If the GSC UI represents the factory default, the GSC API represents our custom-made settings. It takes a bit more effort, however offers us more control and opens more possibilities( a minimum of in the world of question and page information ).
.
The GSC API is a method for us to link to the information within our account, make more personalized demands, and get more tailored output. We can even bypass those factory default settings like exports restricted to 1,000 rows.
. Why utilize it?
Remember how I stated previously that question and page information is separated in the “ vanilla ” GSC UI? Well, with the API, we can link inquiry information with the “page that question ranks for, so say goodbye to clicking backward and forward and waiting on things to load.
.
Additionally, we saw that exports are restricted to 1,000 rows. With the API, we can ask foras much as 5,000 rows, a boost of 400%!
.
So let ’ s hook in, make our demand, and return a more significant and robust information set.
. Setup.
Log in to the suitable GSC account on this page ( upper ideal corner). If my site is example.com and I can see that Search Console account under admin@email.com, that ’ s the account I ’ ll indication into.
.
Enter the URL of the proper GSC account:
. 
.
Set up your demand:
. Set startDate. This need to be formatted as: YYYY-MM-DD. Set endDate.Set measurements.A measurement can be: querypagedeviceand/or countrySet filters (optional ). A filter should consist of: measurement (a measurement can be: question, gadget, nation, or page) operator( an operator can be: consists of, notContains, equates to, notEquals) expression( an expression can be any worth related to the measurements) Set the rowLimit. With the GSC API, you can ask for approximately 5,000!
The page shared in action one makes all of this setup quite easy, however it can be laborious and even puzzling for some. I ’ ve done all the fussing for you and have actually produced JSON you can modify rapidly and quickly to get’the API return you ’d like.
. Unfiltered demand.
The following demand will be unfiltered. We ’ ll set our chosen dates, measurements, and a row limitation, and after that make our demand’.
.
The order in which you put your measurements is the order in which they ’ ll bereturned.
.
The API will return information for desktop, mobile, and tablet, separated out. The numbers you see in the GSC interface– clicks, for example– are an aggregate of all 3 (unless you use gadget — filtering).
.
Remember, your measurements can likewise consist of “ nation ” if you ’d like.
.
.
” startDate”:” 2019-11-01” “,
.
“endDate”:” 2020-01-31 “,
” measurements “:
[
.
” question”,
” page”,
” gadget”
],
” rowLimit”: 3000
.Filtered demand.
This variation of our demand will consist of filters in order to be more particular about what is returned.
Filters are mentioned as dimension/operator/expression. Here are some examples to reveal what’’ s possible:
.question consists of go fish digitalpage equates to https://gofishdigital.com/ gadget notContains tablet.
It appears like you can just use one filter per measurement, much like in the regular GSC interface, however if you understand in a different way, let us understand in the remarks!
” startDate”: “2019-11-01”,
” endDate”: “2020-01-31”,
” measurements”:
[
” inquiry”,
” page”,
” gadget”
],
” dimensionFilterGroups”:
[
” filters”:
[
]
],
” rowLimit”: 3000
Choose a design template, unfiltered or filtered, and fill in your customized worths (anything after a colon need to be upgraded as your own worth, unless you like my presets).
.Perform the demand.
So there you have it! 2 demand design templates for you to pick from and modify to your preference. Now it’’ s time to make the demand. Click into the ““ Request body ”, choose all, and paste in your customized JSON:
This is where you might by hand establish your demand secrets and worths, however as I mentioned previously, this can be tiresome and a little complicated, so I’’ ve done that work for you.
.
Scroll down and click ““ Execute. ” You might be triggered to sign-in here.
If whatever was gotten in properly and the demand might be pleased, the API will return your information. If you get a mistake, audit your demand initially, then any other actions and inputs if required.
Click into package in the lower right (this is the action from the API), choose all, and copy the details.
Convert from JSON to CSV.
Excel or Sheets will be a better method to deal with the information, so let’’ s transform our JSON output to CSV.
.
Use a converter like this one and paste in your JSON output. You can now export a CSV. Update your column headers as wanted.
.Question your own information.
Most SEOs are quite comfy in Excel, so you can now query your demand output any method you’’d like.
.
One of the most typical jobs carried out is trying to find information connected with a particular set of pages. This is done by including a sheet with your page set and utilizing VLOOKUP to suggest a match.
The API output remaining in a spreadsheet likewise enables the most typical actions in Excel like arranging, filtering, and chart production.
.Get more out of Google Search Console.
GSC provides essential information for SEOs, and the GSC API output uses not just more of that information, however in a format that is far less troublesome and more cohesive.
Today, we conquered 2 barriers we typically deal with in the basic GSC interface: the query/page connection and restricted exports. My hope is that making use of the Google Search Console API will take your insights and analyses to the next level.
While my JSON design templates will cover the most typical circumstances in regards to what you’’ ll be intrigued in asking for, Google does provide documents that covers a bit more ground if you’’ re interested.
Do you have another method of utilizing the GSC API? Exists another API you typically utilize as an SEO? Let me understand in the remarks!
Sign up for The Moz Top 10 , a semimonthly mailer upgrading you on the leading 10 most popular pieces of SEO news, suggestions, and rad links revealed by the Moz group. Consider it as your unique absorb of things you do not have time to pursue however wish to check out!
Read more: tracking.feedpress.it