Data Studio: building reports with AutoPSEO data

AutoPSEO does not publish a connector for Data Studio, Google's dashboard tool formerly called Looker Studio. You can still chart its numbers there in three ways: Google's own Search Console connector for the raw data, a CSV exported from an AutoPSEO report, or a Google Sheet that a scheduled script fills from AutoPSEO's REST API. Which one suits you depends on how fresh the dashboard must be and whether it needs AutoPSEO's analyses or only the raw metrics.

Option 1: Google's Search Console connector

Google's connector reads Search Console directly, so it brings the raw metrics and none of AutoPSEO's analysis. According to Google's guide to the connector:

• It offers two tables, Site Impression and URL Impression, and one data source uses one of them. Add two data sources to a report to show both.
• You need at least view permission on the Search Console property, signed in to both products with the same Google account.
• Site Impression covers web, image, video and news results; URL Impression adds Discover and Google News.

To add it, choose Create → Data Source → Search Console, pick the site, the table and the default search type, then Connect.

Option 2: upload a CSV from AutoPSEO

For a one-off or monthly dashboard, export a table from any report (Exporting data) and add it with Data Studio's CSV file upload connector. Google's upload requirements decide how to export:

• Fields must be separated by commas, so set Account → CSV export format to Standard (US / UK) first.
• The file must be UTF-8 with a header row, which AutoPSEO's exports are.
• Every file added to a dataset must have exactly the same columns in the same order, so export the same report with the same columns and comparison setting each time.
• New files are appended and duplicates are not removed, so do not upload overlapping date ranges.
• A file can be up to 100 MB, and each user gets 2 GB of upload storage.

Percentages are exported with a percent sign (27.03%), so check the field types after an upload.

Option 3: a Google Sheet fed by the REST API

For a dashboard that keeps itself current, have a scheduled job write AutoPSEO's numbers into a Google Sheet and connect the sheet. Google's Sheets connector checks for changed values and new rows whenever the report queries it.

1. In AutoPSEO, open MCP & API and create an API key with Read only scope. It is shown once, so store it in your job's secrets.
2. From the scheduled job (Google Apps Script, a cron job or a workflow tool), call the REST API and write the rows to the sheet.
3. In Data Studio, add the sheet with the Google Sheets connector and tick Use first row as headers.

A call for the top queries of the last 28 days looks like this:

curl -s "https://app.autopseo.com/v1/properties/sc-domain%3Aexample.com/queries?range=28d&limit=1000" \
  -H "Authorization: Bearer apk_live_..."

Each response is JSON, with the result under data and details of the call under meta. The REST API serves the same 19 Search Console and GA4 tools as the MCP server: properties, search analytics rows, top queries, pages and countries, period comparison, rank changes, new and lost rankings, content decay, cannibalisation, CTR benchmark, page poaching, URL inspection, sitemaps, annotations, and the GA4 overview, breakdown and key events. Top queries and top pages return up to 1,000 rows, top countries up to 300, and search-analytics up to 5,000 raw rows for one or two dimensions. Calls are limited to 60 a minute per key and 1,000 an hour per account, and the OpenAPI 3.1 document at https://app.autopseo.com/v1/openapi.json describes every parameter.

Which option to choose

If the dashboard exists mainly to show a client the numbers, a shared report link or a scheduled Slack or Teams report may be less work. Our FAQ on Search Console in Looker Studio covers Google's connector in more depth.