SEO specialists
Track the queries and pages gaining or losing clicks, every morning.
Review search metrics and index checks, then approve one exact sitemap URL for the connected property.
Start free Connect Search Console
Updated November 2026
| Search | Clicks | Impressions |
|---|---|---|
| winter coats | 860 | 12,480 |
| canvas tote | 410 | 8,240 |
| brand name | 155 | 3,110 |
Track the queries and pages gaining or losing clicks, every morning.
Find pages with impressions but few clicks and rewrite them first.
Send each client a search report without copying numbers by hand.
Read search performance with native exact, contains and include/exclude RE2 filters, including dimensions outside the selected grouping.
The owner reviews the exact values and approves every proposed change before it is applied to Search Console.
All source conditions must match. Compare daily/hourly performance with native freshness metadata, read site/sitemap details and inspect selected URLs. Google returns top rows; index inspection describes current state.
Refresh query and page performance for the reporting period.
Limit: Use the report to choose which search opportunities deserve a closer look.
Propose one sitemap URL within the owner-selected origin/path prefix.
Limit: The owner reviews its existing registration when available and approves the exact submission. Separate write consent is required. Acceptance does not confirm crawling or indexing.
See the problem in your report, then propose the fix in Datapipe instead of opening Search Console, finding the record and retyping it.
Teammates and AI tools can suggest changes without getting edit access to Search Console.
You see the current and proposed value side by side, and every change is logged.
TodayLog in to Search Console, find the property and paste the sitemap URL.
With DatapipePropose the sitemap URL inside your allowed site prefix and approve it. Google still decides when to crawl.
TodayRepeat the same steps for every sitemap and keep notes on which ones you sent.
With DatapipePropose each sitemap from Datapipe. Every request and its result stays in the audit history.
Sends one owner-approved sitemap URL to the connected Search Console property, within the owner-selected URL prefix. Success confirms request acceptance, not crawling, indexing or ranking. An existing registration is shown when available. Ordinary read consent stays unchanged; separate webmasters consent and native owner/full-user access are required. Sitemap removal, site membership, content changes and batch submissions are excluded. Uncertain requests never retry automatically.
The owner selects supported writable fields for this action before teammates can propose changes.
| Field | Now | Request |
|---|---|---|
| Sitemap URL | — | https://example.com/sitemap-blog.xml |
Source changes use the separate Actions & approvals workflow in Datapipe. AI tools such as ChatGPT can propose changes but never approve them. Who can turn this on?
Provider permissions and submission quotas still apply. Acceptance confirms a request receipt, not crawling, indexing or ranking.
Only fields supported by an enabled action can be proposed; some actions also support individual owner-selected writable fields.
Sign in with Google.
Read access for reports. The change action needs edit access in Search Console and stays off until the owner turns it on.
A page filter affects aggregation even when page is not a report column. Google returns top rows, not a guaranteed full export.
Native source filters run before grouping across query, page, country, device and search appearance; every filter must match (AND). Regular expressions use Google's RE2 syntax. A page filter affects aggregation even when page is not a report column. Google returns top rows, not a guaranteed full export. Dates/hours use Pacific time and fresh/hourly results can change. URL Inspection describes the indexed version of one URL; it is not a live test or an indexing request.
4 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Search performance by day or hour, search term, page, country, device and appearance. Fresh and hourly data can change; include the first incomplete date/hour to identify it. Dates and hours use America/Los_Angeles time. Google returns top rows and does not guarantee every row, even after pagination. Filter at Google before grouping, including dimensions you have not added as columns. All source filters must match (AND). Include/exclude regular expressions use Google's RE2 syntax and are validated by Google; they are never evaluated locally. Up to 20 combined source filters, each expression at most 4096 characters. Google still returns top rows, not a guaranteed full export. Choose Web, Discover, News, Google News, Images or Video; set aggregation and data freshness in the report builder.
The connected property's URL and your permission level.
Submitted sitemap status and contents for the connected property.
Google's current information about the indexed version of one URL. This is not a live test or an indexing request. Report dates do not reconstruct past index state. URL Inspection quotas and property permissions apply. Optionally choose the language of issue messages.
51 report fields across 4 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also propose a Search Console change. Only the owner can approve it.
Which search queries in Search Console have over 5,000 monthly impressions but CTR below 2%?
Seven high-intent commercial queries identified where rewritten meta titles could capture significant search clicks.
Compare Search Console and Bing page performance, then use WordPress content to choose the next investigation.
See the example & prompts →SEO & contentCombine Search Console, current WordPress content and direct DataForSEO SERP research to decide what deserves a brief.
See the example & prompts →EcommerceCombine Search Console demand, GA4 engagement and Shopify stock before deciding which product pages to promote or improve.
See the example & prompts →SEO & contentSpot pages with plenty of search impressions and few clicks. Add visitor engagement and content context to decide which ones deserve a closer look.
See the example & prompts →SEO & contentUse Search Console to find declining pages, then add Analytics and WordPress context to build an editorial review list.
See the example & prompts →Client reportingPut changes in traffic, search clicks, and advertising spend in one review. Spend the call on what the numbers mean.
See the example & prompts →Sign in with Google.
Pick where it goes. This one sends the numbers to Claude.
You're done. It refreshes every day.
| Search | Clicks | Impressions | Click rate | Average rank | Page | Clicks | Impressions |
|---|---|---|---|---|---|---|---|
| winter coats | 860 | 12,480 | 4.2% | 4.2 | /pricing | 860 | 12,480 |
| canvas tote | 410 | 8,240 | 2.8% | 8.6 | /blog/spring-sale | 410 | 8,240 |
| brand name | 155 | 3,110 | 1.1% | 12.1 | / | 155 | 3,110 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
Only the workspace owner. Writes start disabled. The owner enables permitted actions and eligible teammates: owner only, all project operators and managers, or selected teammates. The owner can change this at any time, and saving new settings cancels pending proposals.
No. Teammates propose in Datapipe, and approved changes are applied through the connected Search Console account. Nobody else gets a Search Console login from this.
They can propose a change through Datapipe, the same way a teammate can. They can never approve it. Only the owner approves, in Actions & approvals.
Datapipe sends each approved change once and logs the result. If it cannot confirm that Search Console received it, the request is marked Uncertain and is never retried automatically, so you can check Search Console first.
Yes. Datapipe reads the reports on this page and can make one kind of change: submit an approved sitemap. Each one stays off until the owner turns it on, and every proposed change needs the owner's approval. Provider permissions still apply.
This page lists 51 report fields across 4 datasets. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each Search Console account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Search Console when you are ready.