Brian August 28, 2015 Analytics, PHP, SEO, Web Dev

Google API – Access Google Search Analytics from Google Search Console

In early August Google announced that they have released an API to the Google Search Analytics data from Google Search Console (formerly Google Webmaster Tools).

I started building upon this API and was able to import data into a MySQL database. All was going well, and then I ran into my first snag in that my computer died. It took me a few weeks to be able to at least recover the code from the localhost dev site I was building this at.

So fast forward a few weeks and I have the code back and a computer to develop it on. All is going fine, my import to MySQL from Google Search Console (Google Webmaster Tools) is working great for the one website I was testing this with. Then I start to explore adding more websites, and nothing but errors. I confirm that I’m making a successful OAuth2.0 connection to Google, etc. Insert too much time spent in frustration, analyzing code, debugging, etc.

Bottom line was this – though you have granted access to the API via OAuth2.0, you still need to grant access to your user in Google Search Console for each website you are attempting to access.

Contents

1 Grant Access to Google Search Console from a Google Developers Console API User
2 Google Search Console API – PHP
3 Import Google Search Analytics Data from Google Search Console to MySQL
4 Help / Troubleshooting

Grant Access to Google Search Console from a Google Developers Console API User

Let me expand on that just a bit because this was all kind of confusing to me.

In the Google Developers Console, you first need to create a project if you haven’t done so already.

Next, you need to add access to the Google Search Console API. This is done within the Google Developers Console while your project is active.

Choose APIs & auth -> APIs
In the search field, search for Google Search Console API
Choose this API from the list.
Click the Enable API button.

Then also within the project, configure two sets of credentials – an OAuth2.0 client ID and a Service account.

OAuth2.0 client ID
- As I understand it, this is the basic authentication level that I believe is required to get your API calls access. Typically, this level of access should prompt an authorization screen that the user would click a button to grant access. In my case, I want the authentication built into a configuration script and thus I need to add a Service account as well.
Service accounts
- These allow you to authenticate the user in the code base and thus skip the authentication screen when the application needs to grant access. This requires programming in your authentication information.

google api google search analytics credentials — Create an OAuth2.0 client ID and a Service account within the Google Developers Console

Now that you have your authentication credentials setup, you need to grant access to this API “user” within Google Search Console (Google Webmaster Tools). To do this, you’ll need to copy the email address displayed for the Service account. Then head over to Google Search Console.

Log into Google search console
From the right hand side of the screen for a website, choose Manage property -> Add or remove users
Choose ADD A NEW USER
Enter the email address you copied above from Google Developers Console in the User email field.
Set the Permissions drop-down to FULL
Click the ADD button

google search console grant user access — Grant access to Google Search Console data for a Google Developers Console user via API access and OAuth2.0 authentication.

This now grants the Google Developers Console API user access to the Google Search Console website property, and thus it’s data as well.

This should be everything you need to have your program talk to Google Search Console (Google Webmaster Tools) via API authenticated via OAuth2.0

Google Search Console API – PHP

I’m a PHP developer for the back end, so that’s my language of choice. But there are other languages that can access the API – but that’s out of scope of this article.

I’m not going to go into detail on how to program access to the API in this post. But Google does offer a PHP library for accessing their APIs. Feel free to explore an use that as you wish.

Import Google Search Analytics Data from Google Search Console to MySQL

Again, there are many ways to accomplish the task of importing your search analytics data from Google to a locally hosted location, but I’m not going to go into full detail on how to accomplish that.

What I will do however, is share with you a github repository that offers a set of instructions and a tool to copy your data from Google Search Console to your own MySQL database.

Import Google Search Console data to a locally hosted MySQL Database

I should note – I’m the developer of that github repository and would love input and/or feedback on the project. At the time of writing this it is in it’s infancy, but I intend to develop this into a more full suite of tools in the future.

Help / Troubleshooting

If you install and run the Organic Search Analytics tool to manage your own data and run into issues or something that just isn’t quite right, please look to the official github page for this project. Feel free to reach out for help as well if needed, posting any error messages or strange situations you may find on the github repository by creating an issues. This is where the codebase lives, gets updated, and I as the developer as well as other users can help you find a resolution to any issues you may come across.

Issues
- Search old issues to see if someone else has encountered the same issue as you
- Report an issue or bug
- Request new features
Pull Requests
- Offer suggestions for code changes
Wiki
- The “Owners Manual” for Organic Search Analytics
- Roadmap

33 Comments

Add yours

Adam says:
September 21, 2015 at 10:17 PM
Hi, sorry for the rather amateur question, I’ve set the script up in a Amazon MC2 instance and is running perfectly in terms of connecting and retrieving data from Google and Bing, however I am completely lost when it comes to set up cronjob, could you show me know how to set it up please? Thanks in advance :)
Reply
- Brian says:
  September 21, 2015 at 10:55 PM
  Adam,
  Implementing a cronjob is something that has been on my todo list but I have not actually tested or fully built out yet at this time. My intentions are to have the ability to make one cron task run and it would import all of the scripts – much like the “Import All” button on the Data Capture screen. Sadly, that was implemented via Javascript and I don’t feel there would be a way to make that work quickly/easily.
  But you should be able to run a cronjob on this currently, you’ll just need to implement one cronjob per domain and search engine you wish to capture. I was just working on adding some documentation to the wiki this morning around how to do this. The page is incomplete at this time, but there should be enough information for you to get the basics working.
  https://github.com/PromInc/organic-search-analytics/wiki/Import-Parameters
  It’s pretty straight forward though – make your cronjob call the data-capture-run.php script with the correct query parameter set and you should be all set to go.
  A few things to keep in mind though – Google typically offers data from 3-4 days prior to today. That’s why in the GUI you’ll see that the most recent date you can ever import is 4 days old. So when writing your cronjob ensure that you set the date offset correctly to account for this.
  Bing provides ALL of their data in one feed which is reported on a weekly basis – not daily like Google. The Bing import script does account for the long list of data and only imports new/missing data, so there are not duplicates. But because of this, a date is required to be passed to the data-capture-run.php script however it’s actually irrelevant. So any date works.
  I think that should be all of the information you’d need to get this setup. Like I said, this isn’t a fully vetted out solution as you’ll need multiple cronjobs but it should work at this time. I’m always working on improving the tool, so if you have any suggestions or wish to contribute to the code base I’m open to anything you’d be willing to offer! This is a project that I’m building to replace some overly large Excel spreadsheets and make my efforts easier – I figured it was worth sharing with the community!
  Reply
  - Adam says:
    September 22, 2015 at 2:11 PM
    Wow, thanks for the pointers! I certainly will give it a try. You are my rock star!
    Reply
    - Brian says:
      September 22, 2015 at 5:44 PM
      Good to hear!
      I love feedback, so thanks for the comments.
      I’ve updated the Wiki pages on GitHub yesterday.
      I’m also working on some nice updates to the reporting portion of the tool – I don’t have a timeline of when those will be released, but they are coming together nicely and make this much more valuable.
      Always so much to do and so little time…
      Reply
      - Adam says:
        September 24, 2015 at 9:36 PM
        Hi Brian:
        I’ve had a look today, am I right in thinking in order to set up cronjob for automation, the data-capture-run.php will need to be modified as the arguments passed over by cron can only be captured by $_SERVER[‘argv’][1];? is there any more elegant interim solutions you could recommend?
      - Brian says:
        September 28, 2015 at 6:18 PM
        Adam,
        Sadly I don’t have the capacity at the moment to setup and test a CRON scenario.
        But I wasn’t aware that passing GET parameters via CRON is different than a web browser request.
        I think you are right that the script will need to be modified to make this work. I would like this change to be a part of the repository however, so I’m hoping that you can help in ensuring this is all configured correctly.
        I have modified data-capture-run.php to accommodate this needed change on a new branch – CRON Functionality. FYI – I’m not sure what happened, but I think that branch may have some older code in it… I suggest only downloading the data-capture-run.php file from that branch and updating your local copy.
        One concern I’ve had about calling this via a CRON is the 4 day offset required for the date to trigger a Google request – can you confirm that this is capable via CRON? If not, I may have to add another parameter that allows triggering the request without having the date set.
        I know others have done some programatic calls to this utility and having the CRON piece available and a part of the repository is valuable. For that reason, as well as keeping all details in one location, I’d like for this conversation to be a part of the GitHub repository. I’ve opened an issue for this matter and would appreciate if we could continue this conversation there. Github Issue #7 – CRON Functionality
        Thanks Adam for your help on this!
Gary says:
November 10, 2015 at 2:58 AM
Hi Brian,
Thank you for the instructions. How ever I have an issue that I cannot solve atm. I followed everything step by step. I have MAMP setup / copied repository under htdocs. Once I started it asked me to configure the settings which I did with email / p12 name. It was done corectly. How ever now when I go on the site and hit RUN under Data Capture – Nothing happens no pop ups / no dialog nothing. Also when I click on Settings on the top page I get a BLANK page.
What can I be doing wrong??
Thank you
Reply
- Brian says:
  November 10, 2015 at 8:46 AM
  Gary, sorry to hear you’ve run into some issues in getting this set up. Please see some comments in the issue on Github related to this question. https://github.com/PromInc/organic-search-analytics/issues/9
  Reply
  - Gary says:
    November 11, 2015 at 11:32 PM
    Brian thank you for all the help the other day.
    Quick Question.
    The data that this tool is pulling for ex date 10/30/2015 is different than actual google search console data. Is there a reason why this is happening.
    For ex.
    Both using same parameters
    10/30/2015 (Google Search Console) = 30k Impressions
    10/30/2015 (Organic Search Analytics Tool) = 13k Impressions
    Thanks.
    Reply
    - Brian says:
      November 11, 2015 at 11:54 PM
      Interesting that you are seeing that drastic of a difference… And typically it’ll be flipped the other way. Let me explain a bit.
      First off, yes it is common that the data will be slightly different based on how Google has designed their system. Google Search Console provides up to 1,000 records per report. But this tool is utilizing the API access data, which provides 5,000 records per report. That is one of the reasons it pulls data on a daily basis – to ensure that it captures as much data as possible. That’s my reasoning for saying that typically this tool will show more data than GSC would.
      Also to note, when you pull data for one day it actually pulls three reports – Web, Image, and Video. In GSC you can only view one of these at a time, where as in this tool you can view them as combined or separate.
      But probably the biggest reason for the discrepancy is that Google doesn’t even display their data accurately in their own tool – and this is intentional. I heard Google’s own John Mueller explain this scenario within the past month or two but can’t recall exactly where to link to it. My assumption is that your 30k impressions number you found at the top of the GSC page just above the chart. As I understand it, that is a “fairly accurate” number from Google’s eyes and it’s intended to be all encompassing of the real world scenario of what happened on their site. However, if you were to click the download button at the bottom of a GSC report page and total up the impressions that you get in that report (which is the same as what is shown on the website) it will never match up to the number you saw at the top of the page. Again, this is an intentional “feature” that Google provides. Bottom line – they don’t provide you with all of the data.
      For that reason, each and every marketer gets to make their own opinion about if they choose to use this data or not, and if so at what level do we rely on this data. I see it as this data is great at identifying overall site trends. I take the assumption that Google provides a completely random sample of data as opposed to selectively excluding data on an algorithm of what they want to provide you. Also to note, Google Analytics does something kind of similar… They record and provide you all of your data until a report gets too large and then they randomly sample it in your reports. Despite this being frustrating and potentially invalid data, a large majority of businesses rely on Google Analytics to make business decisions.
      I hope that makes sense and helps you to understand the tool and it’s data a bit more – it’s designed to do the best it can with what information it is provided.
      One last thing to point out is as of right now the reporting tool does not display Bing data (if you captured it). It will be added at some point, but for now it collects and stores Bing data only and is holds it until it gets added to the reporting tool.
      Reply
      - Gary says:
        November 12, 2015 at 5:52 AM
        That makes sense. I noticed that after pulling from google search console and using your tool.
        Thank you for the detail description. It really helps. Keep up the great work.
        -Gary
Gary says:
November 12, 2015 at 7:47 AM
Hey Brian,
Quick question. I think I figured out why data was way off Tool vs Google Search console. I believe there is some data that does not have a device for ex mobile or desktop it’s just blank. In order to pull that data would I have to alter any code or can that be done as well where it would pull data even if it does not have device attached to it.
Thanks
Reply
- Brian says:
  November 12, 2015 at 10:17 AM
  Google offers three search types in their data – web, image, or video. Additionally data can be classified under a device type. Data is captured based on the search type and under each search type it is classified by device type.
  If you are capturing data from Bing as well, Bing does not provide search type or device type data, and thus those fields will be blank.
  I haven’t personally seen blank data for these two fields come from Google, but anything is possible I guess.
  If you did want to attempt modifying the code, there is an array that lists the search types that will be captured via the API to Google. This is on line 148 of dataCapture.php. However your comment mentioned that it is the device type that you are finding to be blank, and that is not something that is being set by the tool – line 23 specifies that we want to capture that dimension and thus it should simply pull all of the data it finds in that dimension.
  Feel free to play with it – I am open to hearing about any findings you come across that could improve the accuracy of the data. I’m not able to replicate an instance that Google data is coming in as blank sadly.
  Reply
  - Gary says:
    November 12, 2015 at 11:51 PM
    Hmm k thanks i’ll check this out.
    Reply
  - Gary says:
    November 13, 2015 at 12:28 AM
    So here’s something interesting.
    When I use Google APIs Explorer and search query with certain filters and parameters the result that i get is for ex 9mil impressions.
    When I use the tool and use same exact query with filters and parameters the result that i get is for ex 5.3Mil impressions.
    The Google API Explorer gave me exact number that I had to get manually searching by each category and its exactly what I am looking for.
    For the life of me I cannot figure out if the tool is doing the same exact thing where its pulling 5000 rows why is the result so different.
    Keep in mind these are results with all 3 search types added together.
    -Gary
    Reply
    - Brian says:
      November 13, 2015 at 2:38 AM
      Interesting findings Gary.
      I ran some tests as well and posted what I found on as issue #9 in GitHub. My findings aren’t as drastic as yours, but still don’t match 100%.
      Lets continue the conversation on GitHub but at this time I don’t have any more insights other than there may be a difference between the API Explorer and the Google PHP API library.
      Reply
Jonathan says:
February 19, 2016 at 1:37 PM
Hi Brian – running into an issue with this! I’ve followed the instructions to the letter. When I add the MySQL database and the OAuth2.0 stuff during setup and click next I get a 500 internal server error and a blank page. Not sure why this would be the case? I’ve checked CHMOD settings and the .htaccess file and they look fine.
You can see what I mean here:
http://vlexo.net/searchconsoledata/
Any help would be lovely!
Reply
- Brian says:
  February 19, 2016 at 6:55 PM
  I can’t seem to get the screenshot to load – just returns a blank page. But no worries there.
  A 500 could be due to a webserver not running, possibly a code error (which I think is unlikely as this codebase has worked for others), or attempting to access a URL that doesn’t exist.
  I’m assuming you are using a Windows/XAMPP configuration? If so, my first thought is to check that XAMPP is running. If it is, there should be an XAMPP icon in you icon tray by the clock in the Windows task bar. It may be hidden by the “show more” triangle. If that is there, right-click on it and open the console (I think that’s what it’s called). Ensure that both Apache and MySQL are running – if not start those services. If the icon is not in the tray, then go to the start menu, search for XAMPP to start it and then start Apache and MySQL.
  If you are using a Mac with MAMP this will be similar, only you’ll have to open MAMP from your applications folder and ensure the webserver is running from the control panel.
  With XAMPP or MAMP running the URL to the Organic Search Analytics utility should be:
  http://localhost/organic-search-analytics/organic-search-analytics/
  or
  http://127.0.0.1/organic-search-analytics/organic-search-analytics/
  If you are using another hosting solution you should just need to change the domain name of the above URL.
  And not to confuse matters more, but the above URL is accurate if you copy the entire directory from the Github download to a folder. But technically you only need the sub-folder “organic-search-analyitcs”. The root level folder contains some github files that aren’t needed for your local instance. So really you could just use the sub-folder and shorten up the URL to only be http://localhost/organic-search-analytics. If this doesn’t make sense though, just ignore this paragraph. ;)
  I guess the other thing is that the files don’t exist at the path that you are requesting via the web browser. In other words, you didn’t copy the files out of the .zip download or the files aren’t where they are expected to be. With XAMPP it should typically be C:/xampp/htdocs/ In that directory is where you’d put the Organic Search Analytics files. To be honest I forget what the default directory is for MAMP…
  I hope those thoughts help. Let me know if that helps or not. Any specifics about your configuration can help in further troubleshooting as well.
  Reply
  - Jonathan says:
    February 20, 2016 at 4:39 AM
    Hi Brian,
    Thanks for the response!
    The URL I sent wasn’t actually a screenshot!
    I’ve removed the config file so you can see that I can see the setup screen:
    http://vlexo.net/organic-search-analytics/settings-configure.php
    It’s whenever the config file has been created – I get the blank screen and also the 500 server error.
    I’m on an Apache server, so this should technically work. It’s whenever I enter the details, I get met with a blank screen (500 server error).
    Not sure why this is the case to be honest with you. Could possibly it not being able to connect to the MySQL database be the cause or would it throw up an error message if that were the case?
    Reply
    - Brian says:
      February 20, 2016 at 4:49 AM
      Ok, thanks for the clarification.
      You’re closer than you think Jonathan. The issue is in the configuration file. It could be that it’s not connecting to MySQL, but I’m thinking it’s more the Google .p12 file. In the past, I know others have run into a similar issue when they didn’t include the file extension on the P12 file. Make sure you are using the FULL file name with extension – example: “myGoogleP12File.p12”
      https://github.com/PromInc/organic-search-analytics/issues/9#issuecomment-155534145
      If that doesn’t fix the issue, then you might be right that the database connection isn’t working. I’d ensure that your credentials are correct and that you can access the DB using those credentials using a tool like MySQL Workbench.
      Reply

Hello Brian,

I’ve changed my windows, the old windows i have in another HDD. I copied files from HDD to SSD with new windows and now doesnt work your script. Can you helo me pls ?
I have this error when i try to see reports:
Fatal error: Uncaught exception ‘Google_Auth_Exception’ with message ‘Error refreshing the OAuth2 token, message: ‘{ “error” : “invalid_grant”, “error_description” : “Invalid JWT: Token must be a short-lived token and in a reasonable timeframe” }” in C:\xampp\htdocs\gsc2\apis\Google\Auth\OAuth2.php:363 Stack trace: #0 C:\xampp\htdocs\gsc2\apis\Google\Auth\OAuth2.php(314): Google_Auth_OAuth2->refreshTokenRequest(Array) #1 C:\xampp\htdocs\gsc2\inc\code\gapiOauth.php(45): Google_Auth_OAuth2->refreshTokenWithAssertion() #2 C:\xampp\htdocs\gsc2\inc\code\dataCapture.php(43): GAPIoAuth->LogIn() #3 C:\xampp\htdocs\gsc2\inc\html\reportSettings.php(9): DataCapture->getSitesGoogleSearchConsole() #4 C:\xampp\htdocs\gsc2\report.php(54): include_once(‘C:\\xampp\\htdocs…’) #5 {main} thrown in C:\xampp\htdocs\gsc2\apis\Google\Auth\OAuth2.php on line 363

OSA is not able to communicate properly with Google to authorize access.

In the config folder ensure that you have your .p12 file that is provided to you from the Google Developer Console.

The next thing to verify is that your config.php file in that same config directory is there and has the correct information in it. It should look something like the code below. You’ll of course have values in all of the quotes. The OAUTH_CREDENTIALS_EMAIL and OAUTH_CREDENTIALS_PRIVATE_KEY_FILE_NAME constants are the two that are at question for your particular issue. Ensure they are set correctly. The email is provided to you in the Google Developer Console and the key file name is the name of the file discussed above. MAKE SURE you add the .p12 to this file name.


<?php
    class Config
    {
        const DB_CONNECTION_DOMAIN = '';
        const DB_CONNECTION_USER = '';
        const DB_CONNECTION_PASSWORD = '';
        const DB_CONNECTION_DATABASE = '';

        const OAUTH_CREDENTIALS_EMAIL = 'biglongemailaddressprovidedinthegoogledeveloperconsole@developer.gserviceaccount.com';
        const OAUTH_CREDENTIALS_PRIVATE_KEY_FILE_NAME = 'yourp12filename.p12';

        const CREDENTIALS_BING_API_KEY = '';
    }
?>

<?php

class Config

{

const DB_CONNECTION_DOMAIN = '';

const DB_CONNECTION_USER = '';

const DB_CONNECTION_PASSWORD = '';

const DB_CONNECTION_DATABASE = '';

const OAUTH_CREDENTIALS_EMAIL = 'biglongemailaddressprovidedinthegoogledeveloperconsole@developer.gserviceaccount.com';

const OAUTH_CREDENTIALS_PRIVATE_KEY_FILE_NAME = 'yourp12filename.p12';

const CREDENTIALS_BING_API_KEY = '';

}

Teodoresc Catalin says:
May 9, 2016 at 12:46 PM
Thank you, Brian!
Was a little space in the code. Now it’s fixed ! :)
Reply
- Jhunior says:
  July 10, 2016 at 7:50 AM
  Hello … I have the same problem, I have done all the steps, but can not find the mistake, you mean when you say “It was a little space in the code. Is now fixed! :)”
  Reply
  - Brian says:
    July 11, 2016 at 6:22 PM
    I believe he means a space in between the single quotes.

Teodoresc Catalin says:
May 27, 2016 at 2:49 PM
Hello Brian,
How you give me an example how to export click, position for one query in API Explorer ? I want to check something
Reply
- Brian says:
  May 27, 2016 at 5:29 PM
  This is the same set of rules that the tool is using.
  
  A few things to note though:
  - Search Type The tool loops through the three search types – web, mobile, and tablet.
  - dimensionFilterGroupsThe Organic Search Analytics tool never calls this. Leaving this blank will give you ALL queries. And that’s the goal of this tool, so this is never called. All queries are imported into the database and then SQL queries are used to mimic this functionality. This was added here to match your request however.
  Reply
Andy says:
November 10, 2016 at 7:08 AM
This tool is soooo good! Thanks a lot Brian.
Reply
- Andy says:
  November 10, 2016 at 7:09 AM
  You need to polish this up and market it, as a wordpress plugin or something
  Reply
  - Brian says:
    November 10, 2016 at 9:23 AM
    If only I had the time… I have a laundry list of features I’d love to build into it yet. It’s far from a finished product in my mind.
    Reply
Teodoresc Catalin says:
April 5, 2017 at 1:28 PM
Hello Brian,
Today I was surprised to see a server error, same as last date with Auth problem. I tried to download new version, override and but same problem…
Fatal error: Uncaught exception ‘Google_Auth_Exception’ with message ‘Error refreshing the OAuth2 token, message: ‘{ “error” : “invalid_grant”, “error_description” : “Invalid JWT: Token must be a short-lived token and in a reasonable timeframe” }” in C:\xampp\htdocs\gsc3\apis\Google\Auth\OAuth2.php:363 Stack trace: #0 C:\xampp\htdocs\gsc3\apis\Google\Auth\OAuth2.php(314): Google_Auth_OAuth2->refreshTokenRequest(Array) #1 C:\xampp\htdocs\gsc3\inc\code\gapiOauth.php(45): Google_Auth_OAuth2->refreshTokenWithAssertion() #2 C:\xampp\htdocs\gsc3\inc\code\dataCapture.php(77): GAPIoAuth->LogIn() #3 C:\xampp\htdocs\gsc3\inc\html\reportSettings.php(9): DataCapture->getSitesGoogleSearchConsole() #4 C:\xampp\htdocs\gsc3\report.php(57): include_once(‘C:\\xampp\\htdocs…’) #5 {main} thrown in C:\xampp\htdocs\gsc3\apis\Google\Auth\OAuth2.php on line 363
Reply
Teodoresc Catalin says:
April 5, 2017 at 2:25 PM
I’ve checked config.php file all seems to be ok, no space, no problems… it worked ten days ago… I dont understand why ? Should i try to create again this credential from another account ?
Reply
- Brian says:
  April 5, 2017 at 7:00 PM
  The tool is working still in my testing. Assuming you did not change/modify/update any code it implies that the issue is not in the Organic Search Analytics tool code.
  I would log into the Google Developer Console and look for clues there as to why you are not able to authorize with the Google servers. The most likely reason in my mind is that you are hitting quota limits of some sort.
  Google Analytics API Access Quotas and Limits
  The other possibility that comes to mind is that roughly a year ago Google did some slight reorganization of the Developer Console and the steps it takes to create a project for granting access to the API. It’s possible something in that shift (if you haven’t touched it since then) changed on their end. So you could poke around and see that all looks good or simply follow the steps on the Github instructions page to create a new project in the Google Developer Console, obtain a new .p12 file to put on your server and switch to that project moving forward. Theoretically that should resolve the issue.
  I hope that helps!
  Reply

Grant Access to Google Search Console from a Google Developers Console API User

Google Search Console API – PHP

Import Google Search Analytics Data from Google Search Console to MySQL

Help / Troubleshooting

Top Related Posts