"google search console" matching MCP tools:

• list_propertiesA

  QuerySail: Google Search ConsoleA

  Use this when the user asks which Google Search Console sites or properties they can access, or to find the exact property_id for a site. Returns exact property IDs (Domain properties look like 'sc-domain:example.com', URL-prefix properties like 'https://example.com/'), the permission level, and connection status. The same site is listed once even if several connected Google accounts can see it. A site name can match more than one property, for example a Domain property and a URL-prefix property. Read-only. Does not change anything in Google Search Console.

  ConnectorOAuth

• analytics_list_propertiesA

  Manifold MCPA

  The Google Analytics 4 properties the workspace's connected Google account can read, with the account each sits under. The first analytics call; the other analytics tools take a property from here. Use when: "what's in my Google Analytics", "which GA4 property is example.com", before any analytics_get_* call. Not for: Search Console sites, use console_list_properties. Traffic to a site the user does not own, use seo_get_traffic_estimates. Returns: List. rows[]: property (the id to pass on: properties/123456789), property_name, property_type (PROPERTY_TYPE_ORDINARY, SUBPROPERTY or ROLLUP), account (accounts/123), account_name. NotConnected when no Google account is connected, or when the connected one has not granted Analytics; its connect_url is where the user connects or reconnects. Cost: 0 credits. The user's own data is free; it shares the console's 60 calls per minute per workspace. Cached 1 hour. Example: {}

  ConnectorAPI key

• marketing_get_reportA

  Google Analytics (unofficial)A

  Primary reporting tool for a given GA4 property or site. Use for totals, trends, and breakdowns by dimension across GA4 website traffic and app analytics, Google Search Console site traffic, and Bing Webmaster — including last-30-days summaries, revenue, leads, sessions, users, engagement/time-on-page (average_session_duration, user_engagement_duration), and period-over-period comparisons. Drill deep: GA4 supports up to 9 grouped dimensions (date/hour, geo, device/browser/OS, source/medium/channel, landing_page/page_path, etc.). Defaults to all mapped connected sources merged into one standardized view, aligned on the shared grain (typically landing_page) so a page row blends GA4 sessions+engagement with Search Console/Bing clicks/impressions/CTR/position; per-source detail (e.g. full query lists) stays in sourceSections. Note GA4 has no `query` dimension and Search Console/Bing have no sessions/engagement, so those cannot share one row — query is a Search Console/Bing breakdown. Narrow with sources or sourceMode='single'. Any GA4 dimension/metric name not in the catalog is passed through to the GA4 API automatically; metricMode='source_native' forces a pure GA4-native report. Pass one date range for a single window or two date ranges for period-over-period comparison.

  ConnectorNo auth

• save_keywordsA

  MarkA

  Saves keywords (from research or Search Console) and sets their tags, exclusion and rank tracking, in one call. New keywords are tracked and audience-checked (one Google top 10 fetch each) unless track is false or they are excluded. Exclude a keyword whose searchers aren't the buyer; it stops tracking. If this refuses because the workspace is not set up, call get_setup_status. Related: research_keywords, list_saved_keywords, set_up_market.

  ConnectorOAuth

• query_search_consoleA

  BlogSEOA

  Queries Google Search Console live for the website, or Bing Webmaster Tools with search_engine bing: clicks, impressions, CTR and average position over any period, grouped by query, page, country, device, date or search appearance, with filters (contains, equals, regex). Unlike get_keyword_rankings (tracked keywords synced daily), it reads everything the engine reports; Google works before the website has a plan. Examples: one page's queries (filter page equals its URL); positions 5 to 15 by impressions; brand vs non-brand (query regex filters). Rows are ordered by clicks unless sort is set; metric filters and sort apply to the top 25000 Google rows by clicks. At most 500 rows per call, paged with start_row. Google covers 16 months and lags 2 to 3 days; Bing groups by query, page or date, weekly for queries and pages. 200 calls per hour per website. If it is not connected, the error says where to connect it. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_performanceA

  QuerySail: Google Search ConsoleA

  Use this to retrieve Google Search Console search performance (clicks, impressions, CTR, average position) for one property. With no dimensions it returns property totals. Add dimensions to break results down by date, hour, query, page, country, device or searchAppearance, and filters to narrow to specific queries, pages, countries, devices or search appearances (for example mobile traffic to pages containing '/blog/'). search_type selects web (default), image, video, news, discover or googleNews results; discover and googleNews have no queries. For what happened in the last hours or days, group by hour (data_state 'hourly', last 10 days only, preliminary). Dates are Pacific Time. If no dates are given it uses the last 28 finalized days (or yesterday and today for hourly) and reports the exact dates it used. Covers one period at a time. Rows are bounded (default 20, max 100); page through with the returned cursor. Google returns only top rows for query/page breakdowns, so results are not guaranteed to be complete, and a missing row does not mean zero. Figures are observed values and do not identify causes. Read-only; cannot request indexing or change anything in Search Console.

  ConnectorOAuth

• compare_performanceA

  QuerySail: Google Search ConsoleA

  Use this when the user asks what changed between two periods, why traffic went up or down, or which pages, queries, countries or devices gained or lost. Compares clicks, impressions, CTR and average position for one property between a current period and the previous period (default), the same weekdays a year earlier, or explicit dates. Returns both totals with absolute and percent changes, the click change split into an impressions part and a CTR part, and, with a dimension, the top gainers and losers ranked by change in clicks or impressions. Dates are Pacific Time; with no dates the current period is the last 28 finalized days. Filters and search type apply to both periods. Changes are observed differences and do not identify causes. Read-only; does not change anything in Search Console.

  ConnectorOAuth

• create_gsc_propertyA

  SEO GSC Wizard MCPA

  Creates one or more URL-prefix properties in Google Search Console (Webmasters sites.add) and registers them in GSC Wizard. Use this to add folder-level properties (e.g. https://example.com/blog/) that do not yet exist in Search Console. They are auto-verified if the connected Google account owns the parent domain property. `parentSiteUrl` is an existing GSC Wizard property whose Google account has access; the new properties inherit it. Every property URL must be under the `parentSiteUrl` domain (that domain or a subdomain of it). Created properties are added hidden and consume no plan slot until you show them with set_dashboard_visibility, which enforces the dashboard limit. For properties that already exist in GSC, use add_site instead.

  ConnectorOAuth

• get_merchant_listings_performanceA

  SEO GSC Wizard MCPA

  Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline, and the top pages (product URLs) behind it. Answers "how visible are my product results in Search, and which products carry it". Search Console merchant listings counts enriched product results in web Search only, while Google Merchant Center free-listing numbers (get_organic_shopping_performance) cover the Shopping tab, Images, Lens, YouTube and Maps too, so the two do not reconcile to one figure. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

  ConnectorOAuth

• disavow_fileA

  AskYourStackA

  Write the disavow file for Google's disavow links tool (https://search.google.com/search-console/disavow-links). Google has no API to upload it, so you give the user the file and they upload it themselves. Disavowing is rarely needed and can lower rankings when good links are thrown away: use it after a manual action for unnatural links in Search Console, or for links the site clearly paid for or built in a scheme; Google already ignores ordinary spam links, so a high spam score alone is not a reason. Pass the domains (whole sites, the usual choice) and/or single URLs to disavow, each with a short reason, from the user's backlink data (Ahrefs, Semrush, SE Ranking, bing_backlinks, an attached export). Each upload REPLACES the list Google has, so if the user already uploaded one, ask them to download it from the tool and pass it as current: this tool keeps its lines and adds the new ones. remove takes lines back out (links the user no longer wants disavowed). Answers with the whole file, what was added, kept and dropped, and how to upload it. It works only for a URL-prefix property in Search Console (https://www.example.com/), not a Domain property.

  ConnectorOAuth

• get_search_console_sitemapsA

  MisarSEO MCP ServerA

  Search Console sitemaps.list/sitemaps.get: every sitemap submitted for the connected property and its processing status (pending, last downloaded, warning/error counts, per-content-type submitted counts), or one named sitemap. Read-only — needs only the `webmasters.readonly` scope this deployment's Search Console connection already requests. Submit/delete need the broader `webmasters` scope and are deliberately not offered. Free (no credits) but spends one call of Google's per-property quota. Omit `feedpath` to list every sitemap; pass one (a sitemap's own URL) to fetch just that one instead — either way the response is `sitemaps`, a one-entry array for `feedpath`. `lastSubmitted`/`lastDownloaded`/`warnings`/`errors` are absent, not zero, when Google has nothing to report for that field.

  ConnectorNo auth

• google-maps.place_typesA

  Vee3A

  List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.

  ConnectorNo auth

• google-search-console.list_sitemapsA

  Vee3A

  List sitemaps submitted for a Search Console property. Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response. Returns sitemap paths plus submission, download, warning, and error details. Use an exact path from this response with get_sitemap, submit_sitemap, or delete_sitemap. Cost = 5 tokens.

  ConnectorNo auth

• google-search-console.list_sitesA

  Vee3A

  List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens.

  ConnectorNo auth

• get_search_consoleA

  KleapA

  Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).

  ConnectorOAuth

• get_search_consoleA

  KleapA

  Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).

  ConnectorNo auth

• list_keywordsA

  BlogSEOA

  Lists the website's tracked keywords (Google, in the website's default locale) with volume, difficulty, CPC, opportunity score/label, search intent, favorite flag, topic cluster label and the latest Google Search Console position, clicks, impressions and top ranking page. Pages of 50; sort by opportunity (default), volume, position (best first, unranked last) or recent. Use search to filter by keyword text and favorites_only to keep starred keywords. Positions are null when Google Search Console is not connected. Returns keyword_id values used by every other keyword tool. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_keywordA

  BlogSEOA

  Returns one keyword with its metrics, the last 90 days of Google Search Console position history (per day and country), the scheduled and generated articles targeting it, and up to 20 sibling keywords of the same topic cluster. Position history is empty when Google Search Console is not connected. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• my_search_consoleA

  Peak AnswerA

  Google queries where the signed-in brand ranks between positions 5 and 15, from their connected Search Console. Use this when the user asks about quick SEO wins or what is close to page one. For any other Search Console question, such as top queries, pages, countries, devices, filters or a daily trend, use gsc_query.

  ConnectorOAuth

• list_gsc_sitesA

  AdLoopA

  List all Google Search Console properties the authenticated user can access. Serves as the discovery step for the site URLs that search analytics reports (run_gsc_report) take. Returns the site URL and permission level for each property. Search Console API: https://developers.google.com/webmaster-tools

  ConnectorAPI key

• inspect_urlA

  Shopify SEO Expert: Digital DartsA

  Definitive index check for ONE page, straight from Google's URL Inspection API: indexed or not, coverage state, verdict, last crawl, and whether Google chose a different canonical. Slower than get_indexing_status because it makes a live call per URL, so use it to confirm a specific page rather than to sweep the store. Needs owner-level access to the Search Console property; anything less comes back unavailable with an explanation.

  ConnectorAPI key