After you have accessed data on Search Console, you will have to transform it based on two main factors:
1. The limitations of the database that is going to be used
2. The type of analysis that you plan to perform
Each system has specific limitations on the data types and data structures that it supports. If you want to push data to Google BigQuery, you can send nested data like JSON directly. But when you are dealing with tabular data stores, like PostgreSQL, this is not an option. Instead, you will have to flatten out data before loading into the database.
Also, you have to choose the right data types. Again, depending on the system you will send the data to and data types that the API exposes to you, you will have to make the right choices. These choices are important because they can limit your queries’ expressivity and limit your analysts on what they can do directly out of the database.
Google Search Console data is modeled around the concept of a report, just like Google Analytics but with a much more limited number of dimensions and metrics.
In the end, you will need to map one report to a table on your database and make sure that all data is stored in it. Dimensions and metrics will become columns of the tables.
You need to take special care that the reports you will be getting from Google Search Console do not have primary keys given by Google to avoid duplicates.
For more information on how you can query your Search Analytics data, please see here.