Does Lyro get the same access as our Search Console owner?

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.

Can Lyro inspect a large batch of URLs at once?

Inspect URL is metered by Google and high-volume use returns 429 quota errors, so it suits priority URLs rather than a whole-site crawl. For breadth, Search Analytics Query covers many pages in one call and List Sitemaps gives indexed counts per sitemap.

If a page is missing from the performance report, does that mean it is not indexed?

No. Search Analytics Query only returns URLs with at least one impression, so a page can be indexed and still be absent. Inspect URL is the action that answers indexing status, and its results can lag real changes by several days because Google serves cached data.

What stops the wrong property from being unregistered?

Delete Site permanently removes a property from the connected account, so it belongs behind the same review as any destructive action. The safe pattern is confirming the target with Get Site or List Sites first and using the site_url exactly as Search Console returns it, including protocol, sc-domain prefix, and trailing slash.

Google search console MCP integration

Pulls clicks, impressions, and position data from a live property, inspects URLs that will not index, and submits or audits sitemaps.

Connect Google search console See all integrations

9actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Search analytics query
Lyro 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.
Inspect URL
Lyro 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.
Submit sitemap
Lyro 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.

See all 9 actions

How businesses use Google search console + Lyro

Each card is one request a support team gets, and the Google search console actions Lyro runs to close it.

Answer search performance questions with real numbers
Lyro 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.
Search Analytics QueryList SitesGet Site
Diagnose a page that is not appearing in Google
Lyro 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.
Inspect URLGet Sitemap
Register a property and push its sitemap for crawling
When a new site or a rebuilt sitemap goes live, Lyro adds the property in the right URL-prefix or domain format and submits the sitemap file for indexing without anyone opening the console.
Add SiteSubmit Sitemap
Audit which sitemaps and properties are still tracked
Lyro 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.
List SitemapsDelete Site

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Google search console actions it has and picks the ones a request needs.

01
Connect Google search console
Authorize the Google search console account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Google search console actions that close it and chains as many as the request needs.
03
Watch it work
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 free

Google search console · Lyro

Everything else about Google search console

Setup, permissions, and the limits of what Lyro 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.

Every action available in Google search console

All 9 actions your agent can call on Google search console, straight from the live MCP connection.

Add site
Adds a site to the set of the user's sites in Google Search Console.
Delete site
Removes a site from the user's Google Search Console sites.
Get site
Retrieves information about a specific Search Console site.
Get sitemap
Retrieves sitemap metadata (submitted/indexed counts, errors, warnings, last-submission timestamps) for a specific sitemap in Search Console.
Inspect URL
Inspects a URL for indexing issues and status in Google Search Console.
List sitemaps
Lists all sitemaps for a site in Google Search Console.
List sites
Lists all verified sites (properties) owned by the authenticated user in Google Search Console.
Search analytics query
Queries Google Search Console for search analytics data including clicks, impressions, CTR, and position metrics.
Submit sitemap
Submits a sitemap to Google Search Console for indexing.