Reference & Lookup Data · Integration
Google Search Console
Add Google Search Console to your product for your customers, and give your AI agents governed access to it.
Search Console reports on how a customer's own site performs in Google search, and the API is a query surface rather than a feed. You ask for clicks, impressions, position and click-through rate broken down by query, page, country or device, and the shape of that request is the whole integration. Two things surprise people: data lags by a couple of days, so today is never complete, and rows are omitted for privacy when a query is too rare, which means totals will not reconcile against the sum of the rows. Each customer authorises their own verified properties, so your product sees exactly the sites that person already owns. fastn owns the consent flow and the refresh.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Search Console so search performance for their properties appears inside your product.
Query clicks, impressions and position by page or query, rather than exporting and recomputing.
List the properties a customer has verified, so they select one instead of pasting a URL.
Submit or check a sitemap from your product when content it manages changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries which pages lost impressions and reports what changed.
An agent submits a sitemap within governed permissions, with the action audited per tenant.
An agent compares two periods and explains whether a ranking move was seasonal.
Example prompt
Which pages lost the most clicks this month, and did their average position move?
Set up Google Search Console in 4 steps
- 01Enable the Google Search Console connector from your fastn dashboard.
- 02Have each customer authorise their own Google Search Console account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Google Search Console integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google Search Console integration without building it. Your customers connect their own Google Search Console account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google Search Console update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google Search Console connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
SemrushWorks well with
Google AnalyticsOften used alongside
Tools the same teams tend to run next to Google Search Console, across other categories.
Salesforce
HubSpot
Notion
SnowflakeGoogle Search Console integration FAQ
How do I add a Google Search Console integration to my product?
Enable the Google Search Console connector in your fastn dashboard, then let each customer authenticate their own Google Search Console account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google Search Console client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Google Search Console account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google Search Console account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Google Search Console integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent queries which pages lost impressions and reports what changed.
Who maintains the Google Search Console integration?
fastn does. When Google Search Console changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Google Search Console lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Google Search Console results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Google Search Console is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Google Search Console integration?
A common starting point: let a customer connect their own Search Console so search performance for their properties appears inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Google Search Console integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google Search Console does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google Search Console to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.