Datapipe
Read and report
One project, original domain and authenticated account stay bound. Current inventory ignores report dates; ranking history uses up to 100 inclusive days. No audits, ranking refreshes or keyword changes are triggered.
Read & reportRead-only source
Keep your agency's SE Ranking project in client reports.
Read the selected project's current summary, keywords and available ranking history with your agency's own account.
Sheets
Looker Studio
BigQuery
Drive
CSV
Claude
ChatGPTUpdated November 2026
What you can do with SE Ranking
Read-only source
This integration reads SE Ranking data for reports and analysis. Source write actions are not available in Datapipe.
Use your reports in a sheet, a warehouse or a connected assistant, according to your plan and setup.
Examples for your team
Illustrative workflows using the supported capabilities. Connect your own account to work with your data.
Review native keyword movement
Keep each keyword's check date and configured search engine together. Retain negative rank changes and native zero values without inventing first-place ranks.
Keep project context visible
Use the project's current summary and configured engine locale beside ranking history. Forecast and visibility units retain provider definitions and do not imply measured visits or advertising spend.
Reports you can build
4 reporting datasets with their own fields. Choose a dataset in the app, then select the columns you need.
See included datasets and what they report
- Current project summary
Current provider summary for one connected SE Ranking project. Report dates do not reconstruct historical summary values. Average rank, top-keyword counts, processing percentage points and native visibility/traffic-forecast units retain provider definitions; they are not additive daily observations, measured visits or ad spend. Missing values stay empty. No checks, audits or changes are triggered.
- Project search engines
Current search-engine configurations for the connected project, independent of report dates. Project-local engine IDs remain distinct from the provider search-engine IDs. Region, language and Maps configuration are not combined across engines.
- Current project keywords
Current keyword inventory for the connected project, independent of report dates. Target URL, first-check date, group and native tag/engine ID arrays remain separate from historical ranking observations. No keywords are added or refreshed.
- Keyword ranking history
One native keyword/ranking-check date per configured project search engine within inclusive report dates, up to 100 days per pull. Engine locale and keyword identity stay attached. Zero/native rank values are preserved rather than promoted to first place. Rank changes can be negative. No rows are invented for missing checks. Volumes and competition are provider statistics, not measured traffic. Provider financial-report prices and billing values are excluded.
Current summaries and inventories ignore report dates. Ranking rows use provider check dates, retain their search engine and preserve native zero values. Visibility and traffic forecasts are provider units, not measured visits. Available history and reporting access depend on the agency account’s plan.
Metrics and dimensions
48 report fields across 4 datasets.
Browse the documented fields below. In the app, choose your project connection to load its field list. Availability depends on API permissions, report type, and compatible field combinations. Property-specific custom fields appear after connecting.
No fields match. Try another search or choose All.
Send SE Ranking data anywhere
Google SheetsA sheet that refreshes every morning.Looker StudioCharts that read the same numbers.BigQueryA warehouse table for the same columns.Excel / CSVA Drive file you can open in Excel.ClaudeAsk Claude about these numbers in a sentence.ChatGPTAsk ChatGPT about these numbers in a sentence.APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Better than exporting by hand
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- Each search can show clicks and how high you ranked.
Start from a goal
Current project summary
Current provider summary for one connected SE Ranking project. Report dates do not reconstruct historical summary values. Average rank, top-keyword counts, processing percentage points and native visibility/traffic-forecast units retain provider definitions; they are not additive daily observations, measured visits or ad spend. Missing values stay empty. No checks, audits or changes are triggered.
Use thisProject search engines
Current search-engine configurations for the connected project, independent of report dates. Project-local engine IDs remain distinct from the provider search-engine IDs. Region, language and Maps configuration are not combined across engines.
Use thisCurrent project keywords
Current keyword inventory for the connected project, independent of report dates. Target URL, first-check date, group and native tag/engine ID arrays remain separate from historical ranking observations. No keywords are added or refreshed.
Use thisKeyword ranking history
One native keyword/ranking-check date per configured project search engine within inclusive report dates, up to 100 days per pull. Engine locale and keyword identity stay attached. Zero/native rank values are preserved rather than promoted to first place. Rank changes can be negative. No rows are invented for missing checks. Volumes and competition are provider statistics, not measured traffic. Provider financial-report prices and billing values are excluded.
Use thisHow it works
- Create a project and choose SE Ranking in Connections.
- Paste your agency’s dedicated key and the numeric project ID. The account must have access to that project and its original domain.
- Pick where it goes. Choose current project data or up to 100 inclusive days of available ranking history, then a reporting destination.
Sample report
Sample
| Project ID | Project domain | Project title | Latest average rank | Previous average rank | Keywords in top 10 | Visibility (percentage points) | Project engine ID |
|---|---|---|---|---|---|---|---|
| 1,240 | northwind.example | 1,240 | 4.2 | 4.2 | 1,240 | 4.2% | 1,240 |
| 640 | harbor.example | 640 | 8.6 | 8.6 | 640 | 2.8% | 640 |
| 210 | acme.example | 210 | 12.1 | 12.1 | 210 | 1.1% | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Read one agency-owned SE Ranking project: current summary, search-engine configurations, keyword inventory and available keyword ranking history for up to 100 inclusive days. Project, original domain and authenticated account remain bound. No checks, audits, keyword changes, Data API research purchases or source mutations.
Questions
Free to start. Paid plans add more connections and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 connections.
No. Name a project, add a connection, then choose a report and destination.
This integration is read-only in Datapipe. You can read the supported reports, share them with reporting destinations and ask a connected assistant about the available data. Sending report output to a destination does not grant editing access to this source. Read-only in Datapipe using the agency’s SE Ranking API key and eligible Project API account. The same key can authorize broader provider operations; Datapipe only reads the documented Project API routes. MCP OAuth is a separate interface; REST OAuth is not claimed. Agency plan entitlement and limits apply.
This page lists 48 report fields across 4 datasets. You pick the columns when you build the report.
Read one agency-owned SE Ranking project: current summary, search-engine configurations, keyword inventory and available keyword ranking history for up to 100 inclusive days. Project, original domain and authenticated account remain bound. No checks, audits, keyword changes, Data API research purchases or source mutations. Account permissions and the records available from the provider determine which rows can be read.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
ActiveCampaign
Airtable
Asana
Attriboo