Pulls clicks, impressions, and position data from a live property, inspects URLs that will not index, and submits or audits sitemaps.
9actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro pulls search performance data including clicks, impressions, and CTR from Google Search Console. You answer questions about site visibility and keyword performance with real metrics.
Ayro checks whether a specific URL is indexed by Google and flags any issues. You quickly diagnose why a page might not be appearing in search results.
Ayro submits a sitemap to Google Search Console to ensure all pages are discovered. New content gets indexed faster so customers can find it through search.
Each card is one request a support team gets, and the Google search console actions Ayro runs to close it.
Ayro runs a search analytics query against the property and returns clicks, impressions, CTR, and impression-weighted average position, so a question about last month's traffic is settled from Search Console rather than a stale export.
Ayro inspects the exact URL for its indexing status and reads the sitemap it should have arrived through, including the submitted, indexed, error, and warning counts behind it.
When a new site or a rebuilt sitemap goes live, Ayro adds the property in the right URL-prefix or domain format and submits the sitemap file for indexing without anyone opening the console.
Ayro lists every sitemap registered against a property so stale or failing ones surface, and unregisters a site the team no longer tracks in the account.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Google search console actions it has and picks the ones a request needs.
Authorize the Google search console account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Google search console actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeGoogle search console · Ayro
What can you do in Google search console without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Google search console.
It gets exactly what the connected Google account has, and that varies per property. List Sites returns a permissionLevel on each entry, so a site where the account is only a restricted user will not accept Submit Sitemap, which requires site owner or full user permissions.
All 9 actions your agent can call on Google search console, straight from the live MCP connection.
Adds a site to the set of the user's sites in Google Search Console.
Removes a site from the user's Google Search Console sites.
Retrieves information about a specific Search Console site.
Retrieves sitemap metadata (submitted/indexed counts, errors, warnings, last-submission timestamps) for a specific sitemap in Search Console.
Inspects a URL for indexing issues and status in Google Search Console.
Lists all sitemaps for a site in Google Search Console.
Lists all verified sites (properties) owned by the authenticated user in Google Search Console.
Queries Google Search Console for search analytics data including clicks, impressions, CTR, and position metrics.
Submits a sitemap to Google Search Console for indexing.
Same connection, same setup. Pick the next one your team already uses.
Places visitors by IP and coordinates, scores addresses for fraud and Tor exposure, and validates form details against live lookups.
Opens headless imports, uploads the customer's file, and reads back which rows failed validation - without an agent touching the spreadsheet.
Runs extraction workflows and returns their data, defines schemas, surfaces validation anomalies, and subscribes to source change events.
Resolves a typed address into coordinates, names the place behind a coordinate pair, and returns either as GeoJSON, XML, or JSONP.
Scrapes pages that block ordinary requests, crawls whole sites, captures screenshots, and returns extracted fields instead of raw HTML.
Finds the closest Turso region, validates an API token and its expiry, and streams committed table changes on request.

Authorize the account and your agent has all 9 actions from the first conversation.
