Google Search Console connector tools

  • Updated

The Google Search Console connector tools in Optimizely Opal let you access and analyze your site's Google Search performance data directly within Opal, without switching between platforms. Use these tools to inspect URL indexing status, audit submitted sitemaps, query search analytics by keyword, page, device, or country, and submit or resubmit sitemaps to prompt a Google re-crawl. All tools operate on Google Search Console properties that your connected Google account owns and has access to.

First, an Opal administrator must connect Opal with Google Search Console using Optimizely Connect Platform (OCP). After installing the connector in OCP, Opal users and agent builders can log in to Google Search Console from Opal to access their data. Administrators only need to install the Google Search Console connector in OCP once.

Connect Opal with Google Search Console

Complete the following steps to enable the Google Search Console tools in Opal.

Install Google Search Console in OCP

Before you can call the Google Search Console connector tools, an administrator must add the connector tool in OCP.

In the OCP App Directory, complete the following:

  1. Click the Google Search Console connector tool.
  2. Click Install App.
  3. Log in to Google Search Console.

Authenticate with Google Search Console

After an administrator adds the Google Search Console connector tools, log in from Opal to access your information. The Google Search Console connector tools use user-level authorization, so each Opal user can only access the data they are permitted to view in Google Search Console.

To authenticate, complete the following steps in Opal:

  1. Go to Tools > Connectors.
  2. Click Connect for the Google Search Console tools.
  3. Log in to Google Search Console. 

After you connect to Google Search Console, the Google Search Console connector tools become available in Opal Chat, agents, and workflows.

Google Search Console connector tools

After an administrator installs Google Search Console in OCP and you log in to Google Search Console using Authenticate with Google Search Console, you can call the following tools in Opal. 

Click a tool's name to expand it and learn when to use the tool, required and optional parameters, and example prompts on how to call the tool. If you do not provide a required parameter, Opal prompts you for it.

google_search_console_inspect_url – Inspects the Google Search index status of a single URL on a connected Google Search Console property.
  • When to use
    • Check whether a specific page is indexed by Google.
    • Diagnose why a page is not showing up in Google search results.
    • See when Google last crawled a URL and which crawler was used.
    • Find which canonical Google selected versus the one the page declares.
    • Check whether a URL is blocked by robots.txt or noindex.
  • Parameters
    • site_url – The connected property the URL belongs to, for example "https://example.com/" or "sc-domain:example.com".
    • inspection_url – The full page URL to inspect. Must be under site_url and start with http:// or https://.
  • Example prompts
    • Is https://example.com/blog/my-post indexed by Google?
    • Check the index status of https://example.com/products/widget on my Search Console property sc-domain:example.com.
    • Why isn't https://example.com/landing-page showing up in Google search?
    • When did Google last crawl https://example.com/about?
google_search_console_list_sitemaps – Lists the sitemaps submitted for a connected Google Search Console property and reports each sitemap's health.
  • When to use
    • Check whether a site's sitemaps are healthy (errors or warnings).
    • See when Google last read a sitemap.
    • Find how many submitted URLs got indexed.
    • List which sitemaps are submitted for a property.
    • Drill into a sitemap index to list its child sitemaps.
  • Parameters
    • site_url – The connected property whose sitemaps to list, for example "https://example.com/" or "sc-domain:example.com".
    • (Optional) sitemap_index – Full URL of a sitemap index file to drill into. Lists that index's child sitemaps instead of the top-level sitemaps. Must start with http:// or https://.
  • Example prompts
    • List all sitemaps for my site https://example.com/.
    • Are there any errors or warnings on my sitemaps?
    • Show me the child sitemaps inside https://example.com/sitemap_index.xml.
    • When did Google last download my sitemap?
google_search_console_list_sites – Lists the Google Search Console properties (websites or sites) the connected Google account can access.
  • When to use
    • Discover which sites or properties the connected account can access.
    • Resolve the site_url to pass to the other Search Console tools.
    • Check the permission level the account has on a property.
    • Start any "analyze, audit, check, or improve my site" request when the user has not yet specified which property.
  • Parameters
    • This tool takes no parameters.
  • Example prompts
    • What Search Console properties do I have access to?
    • List my connected Google Search Console sites.
    • Which websites can I manage in Search Console?
google_search_console_query_search_analytics – Queries Google Search Console search performance data for a connected website, returning keywords, pages, devices, and countries with clicks, impressions, click-through rate (CTR), and average position.
  • When to use
    • Analyze, audit, check, or improve a site's search engine optimization (SEO) and search performance with Google Search Console data.
    • Find top-performing keywords or discover what a site ranks for.
    • Surface high-impression, low-CTR pages or queries ranking in positions 5–20 as the basis for SEO improvement plans.
    • Compare mobile versus desktop traffic, or break performance down by country.
    • See what queries a specific page ranks for.
  • Parameters
    • site_url – The connected property, for example "https://example.com/" or "sc-domain:example.com".
    • start_date – Start of the date range, inclusive, YYYY-MM-DD.
    • end_date – End of the date range, inclusive, YYYY-MM-DD.
    • (Optional) dimensions – Comma-separated group-by from query, page, country, device, or date.
    • (Optional) type – Search type — web (default), image, video, news, discover, or googleNews.
    • (Optional) filters – JSON array of {dimension, operator, expression}, combined with AND.
    • (Optional) row_limit – Max rows, 1–1000 (default 100).
    • (Optional) data_state – final (default) or all (includes fresh data).
  • Example prompts
    • Show me my top 10 keywords for the last 30 days.
    • What are the top pages by clicks on https://example.com/ from June 1 to June 30, 2026?
    • Compare mobile versus desktop search performance for my site last month.
    • Which queries drive traffic to my blog pages? Filter by pages containing "/blog/".
    • Show me daily clicks and impressions trends for my site over the past week.
google_search_console_submit_sitemap – Submits (or resubmits) a sitemap to Google Search Console for a connected property, asking Google to (re)crawl it.
  • When to use
    • Submit a sitemap to Google for the first time.
    • Resubmit an existing sitemap to prompt a re-crawl.
    • Tell Google about an updated sitemap after you publish content.
  • Parameters
    • site_url – The connected property the sitemap belongs to, for example "https://example.com/" or "sc-domain:example.com".
    • feedpath – Full URL of the sitemap file to submit. Must start with http:// or https://.
  • Example prompts
    • Submit https://example.com/sitemap.xml to Google Search Console.
    • Resubmit my sitemap to prompt Google to re-crawl it.
    • I just published new content — submit https://example.com/sitemap_index.xml to Search Console for sc-domain:example.com.

If you use Opti ID, administrators can turn off generative AI in the Opti ID Admin Center. See Turn generative AI off across Optimizely applications.