SEO data without endless exports.
For every query and every page, the agent analyzes clicks, impressions and positions. It checks the index status of individual URLs and manages the sitemaps.
- Coverage: nearly complete
- 8 tools · 4 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- Performance data up to 25,000 rows per query, for web, image, video, news and Discover.
- Broken down by query, page, country, device, date or hour.
- Regex filters, for example to separate branded from non-branded searches.
- Index status of individual URLs: indexed, canonical, last crawl, mobile usability, structured data.
- Properties and submitted sitemaps, including errors and warnings.
What your agent can change
- Submit and remove sitemaps.
- Add new properties.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Google Search Console.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
Striking-distance keywords
Once a month- Find queries in positions 8–20 with high impressions
- Match each one to its page
- Suggest specific improvements per page
ResultA prioritized list of the pages with the best shot at page one.
- 02
Spot content decay
Every quarter- Compare clicks per page with the same period last year
- Flag pages with a clear decline
- List the queries each page lost
ResultThe content team gets a list of which pages need a refresh, and why.
- 03
Brand vs. non-brand
For every report- Filter out branded searches with a pattern
- Analyze non-brand traffic separately
ResultYou see how much organic traffic comes from new demand.
- 04
Index check after a relaunch
Right after go-live- Check index status and canonical for your key URLs
- Submit the new sitemap
- Flag pages that look off
ResultYou notice problems on day one, not four weeks later.
Built-in safeguards
- The agent sees exactly the properties the connected Google account has access to.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- Interface only: the page indexing report, Core Web Vitals, links, removals, manual actions and crawl stats.
- Google doesn't make the AI Overviews and AI Mode reports or the AI brand filter available through the API.
- “Request indexing” and the live URL test are interface only as well.
What's possible here depends on what Google Search Console offers through its API. We make available what the API allows, as ready-made tools or through the generic API request to Google Search Console, and we check new API versions regularly.
Connect Google Search Console to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.