Tools

Search Console tools

Your own sites' clicks, rankings, sitemaps, indexing and crawl issues from Google Search Console and Bing Webmaster Tools, and sitemap and URL submission. Free.

Read your own sites' search data: clicks, impressions, rankings, sitemaps, indexing and crawl issues, from Google Search Console and Bing Webmaster Tools. Ask Google and Bing to crawl your new or changed pages. The data comes from your own accounts, so these tools cost no credits. They are rate limited per workspace instead.

Connect your accounts. The console tools work with the accounts you connect to your workspace. Open Connections in the app:

  • Google Search Console. Connect an account with Google sign-in. Manifold asks for access to view and manage your Search Console data, and your Google Analytics data for the analytics tools.
  • Bing Webmaster Tools. Connect an account with sign-in, or paste an API key. Sign-in asks to view and manage your Bing Webmaster Tools data. To get a key, open Settings in Bing Webmaster Tools, then API access, and copy it.

You can connect one engine or both, and more than one account for each. If your agent calls a console tool for an engine you have not connected, or its access was revoked, the tool returns NotConnected with a connect_url. Your agent can send you there, and retry when you have connected.

Properties. A property is one of your sites, as the engine knows it. Every console tool except console_list_properties takes a property, so start there. Pass the property value from its rows exactly as it is:

  • A Google domain property looks like sc-domain:example.com.
  • A Google URL-prefix property, or a Bing site, looks like https://www.example.com/.

Most tools take an engine, google or bing. Three tools cover one engine each: console_inspect_url is Google only, and console_get_crawl_issues and console_submit_urls are Bing only.

A good first audit takes two steps. Run console_list_properties, then console_get_search_analytics by query and by page. For site health, add console_get_sitemaps and console_inspect_url.

Getting pages indexed. Two tools change something in your accounts. console_submit_sitemap submits or resubmits a sitemap to Google or Bing, which then reads it, usually within hours. console_submit_urls asks Bing to crawl up to 500 specific URLs, within the daily quota Bing sets for your site; it reports what is left. Google has no API to request indexing of one URL, so on Google, resubmit the sitemap and check a page with console_inspect_url. If you connected before these tools existed, your connection may have read access only; the tool says so, and you reconnect to allow submitting.

To connect these tools to your agent, see the Google Search Console MCP or Bing Webmaster Tools MCP page.

ToolWhat it doesCost
console_list_propertiesList your connected sitesFree
console_get_search_analyticsGet your search analyticsFree
console_get_sitemapsGet your sitemapsFree
console_inspect_urlInspect a URL in GoogleFree
console_get_crawl_issuesGet crawl issues from BingFree
console_submit_sitemapSubmit your sitemapFree
console_submit_urlsSubmit URLs to BingFree

List your connected sites

Toolconsole_list_properties

The Search Console and Bing Webmaster properties the workspace's connected accounts can read. The first console call; every other console tool takes a property from here.

Good for

"what sites are in my Search Console", before any console_get_* call, or to check which engine is connected.

Not the tool for
What you get

A list. Each row has engine (google | bing), property (the id to pass on: sc-domain:example.com, https://example.com/ or a Bing site URL), permission (Google: siteOwner, siteFullUser, siteRestrictedUser, siteUnverifiedUser; Bing: null), verified. NotConnected when no account of that engine is connected; its connect_url is where the user connects one.

Cost

0 credits. The user's own data is free; 60 console calls per minute per workspace. Cached 1 hour.

Parameters

ParameterDefault and notes
engineOne of google, bing, all. Which connected accounts to list. Default all.
Example input
{
  "engine": "all"
}

Get your search analytics

Toolconsole_get_search_analytics

Clicks, impressions, CTR and average position from the user's own Search Console or Bing data, grouped by query, page, country, device or date.

Good for

"which queries bring traffic to my site", "how did page X do last month", "impressions by country", finding queries that rank on page two, a rank check on the user's own site.

Not the tool for
What you get

A list, most clicks first, ties broken by impressions descending. Each row has query, page, country (ISO alpha-3), device, date (the dimensions asked for; null otherwise), clicks, impressions, ctr (0 to 1), position (average, 1-based). Google data lags about two days and keeps 16 months; Bing query and page rows are the last weeks with no date range, its date rows are daily totals. Totals (sum of clicks, impressions) differ by grouping due to Google's aggregation; this is normal Google behaviour.

Cost

0 credits. Cached 6 hours.

Parameters

ParameterDefault and notes
propertyRequired. A property id from console_list_properties: sc-domain:example.com or https://example.com/ for Google; site URL for Bing.
engineDefault google. Which connected account: google or bing.
dimensions[]Default ["query"]. Group by query, page, country, device, date. Bing takes exactly one of query, page, date. At most 3.
start_dateDefault 28 days before end_date.
end_dateDefault 3 days ago, the freshest complete day.
search_typeDefault web. One of web, image, video, news, discover, googleNews. Google only.
filters[]Google only. All filters must match. At most 10.
limitMax rows per page. Default 100, cap 1000. Google serves up to 25,000 rows per query; page on with cursor.

It also takes the common parameters cursor.

Example input
{
  "property": "sc-domain:example.com",
  "dimensions": [
    "query",
    "page"
  ],
  "start_date": "2026-08-01",
  "end_date": "2026-08-31"
}

Get your sitemaps

Toolconsole_get_sitemaps

The sitemaps submitted for one of the user's properties, with when they were read, how many URLs they carry and their errors.

Good for

"is my sitemap picked up", "how many URLs did Google read from the sitemap", checking a submission after a site change.

Not the tool for
What you get

A list. Each row has path, type, submitted_at, last_read_at, pending, is_index, urls_submitted, urls_indexed (Google reports 0 today), warnings, errors. null = the engine does not say.

Cost

0 credits. Cached 10 minutes.

Parameters

ParameterDefault and notes
propertyRequired. A property id from console_list_properties: sc-domain:example.com or https://example.com/ for Google; site URL for Bing.
engineDefault google. Which connected account: google or bing.
Example input
{
  "property": "https://www.example.com/"
}

Inspect a URL in Google

Toolconsole_inspect_url

Google's index status for one URL of the user's property: indexed or not and why, last crawl, canonical, mobile usability and rich results.

Good for

"why is this page not in Google", "when was this page last crawled", "which canonical did Google pick", checking a page after a fix.

Not the tool for
  • Many URLs at once (Google allows 2,000 inspections per property per day, shared by everyone on the property), use console_get_search_analytics with dimension page to find which pages get impressions.
  • The page's own HTML, use seo_get_page.
  • Bing, which has no inspection.
What you get

One record with verdict (PASS | PARTIAL | FAIL | NEUTRAL), coverage_state (Google's sentence, for example Submitted and indexed), indexing_state, robots_txt_state, page_fetch_state, last_crawl_at, crawled_as, google_canonical, user_canonical, referring_urls[], sitemaps[], mobile_usability and rich_results (each a verdict with its issues), inspection_link. null = Google did not report it.

Cost

0 credits, Google only. Cached 24 hours.

Parameters

ParameterDefault and notes
propertyRequired. A Google property id from console_list_properties: sc-domain:example.com or https://example.com/
urlRequired. A URL under the property.
Example input
{
  "property": "sc-domain:example.com",
  "url": "https://www.example.com/pricing"
}

Get crawl issues from Bing

Toolconsole_get_crawl_issues

URLs Bing had trouble crawling on the user's property: HTTP errors, redirects, robots.txt blocks, DNS and timeouts, with the inbound link count of each.

Good for

"what is Bing failing to crawl", "which of my pages 404", a Bing-side health check.

Not the tool for
What you get

A list, one row per URL and issue. Each row has url, issue (Code301, Code302, Code4xx, Code5xx, BlockedByRobotsTxt, ContainsMalware, ImportantUrlBlockedByRobotsTxt, DnsErrors, TimeOutErrors), http_status, inlinks, seen_at. Fixed issues stay listed a few days.

Cost

0 credits, Bing only. Cached 6 hours.

Parameters

ParameterDefault and notes
propertyRequired. A Bing site URL from console_list_properties: https://example.com/
limitMax rows. Default 100, cap 1000.

It also takes the common parameters cursor.

Example input
{
  "property": "https://example.com"
}

Submit your sitemap

Toolconsole_submit_sitemap

Submits or resubmits a sitemap for one of the user's properties, asking Google or Bing to read it again. A write to the user's own account.

Good for

"get my new pages indexed", "I just published", "tell Google about the sitemap", after a site change or migration. Resubmitting the same sitemap is how to say it changed.

Not the tool for
What you get

One record with engine, property, sitemap_url, submitted_at (when Manifold sent it). The engine reads it later, usually within hours; console_get_sitemaps shows when.

Cost

0 credits. Never cached. A connection made with read access only answers NotConnected; the user reconnects to grant submit access.

Parameters

ParameterDefault and notes
propertyRequired. A property id from console_list_properties: sc-domain:example.com or https://example.com/ for Google; site URL for Bing.
engineDefault google. Which connected account: google or bing.
sitemap_urlRequired. The sitemap or sitemap index URL, under the property.
Example input
{
  "property": "sc-domain:example.com",
  "sitemap_url": "https://www.example.com/sitemap.xml"
}

Submit URLs to Bing

Toolconsole_submit_urls

Asks Bing to crawl specific URLs of the user's site now, within Bing's daily quota for the site. A write to the user's own account.

Good for

"get these pages into Bing", "I just published this post", a page Bing has not crawled yet, a fixed page that should be recrawled.

Not the tool for
What you get

A list. Each row has url (sent to Bing). quota: daily_remaining, monthly_remaining, left after this call. errors[]: URLs not under the site (InvalidTarget) and URLs over the quota, not sent (ProviderUnavailable).

Cost

0 credits, Bing only. Never cached. Bing's quota starts near 10 URLs a day for a new site and grows with its age.

Parameters

ParameterDefault and notes
propertyRequired. A Bing site URL from console_list_properties: https://example.com/
urls[]Required. URLs under the property, at most 500, never more than today's quota. Duplicates are dropped.
Example input
{
  "property": "https://www.example.com/",
  "urls": [
    "https://www.example.com/blog/new-post"
  ]
}