SignalDig

// Features

Five data capabilities for five real research questions.

From search demand and AI visibility to competitors, backlinks and public conversations, each capability states where the data comes from, how it is measured, what it can deliver and what it cannot represent.

Data capabilities updatedActual data timing is shown in each research result.

Choose a research capability

01 / 05

Search and keyword research

Questions it can answer

What are people searching for, and what is still missing from the current results page?

Compare keyword metrics and current search results within one location, language and search-engine scope, keeping monthly volume, relative trend interest and live SERPs as distinct measurements.

Available data and definitions

  • Google Ads-based average monthly search volume, keyword ideas, related-keyword depth and search intent
  • Google Trends relative interest normalized to 0–100 for the selected location and period—not an absolute search count
  • Live Google or Bing organic results, including ranks, pages, snippets and observed SERP elements; the engine is selected per request
  • The keyword, location, language, device, search engine and data observation time retained with each query

Research output

  • A keyword-demand and intent snapshot
  • The current SERP landscape, ranking pages and question types
  • Content gaps and search directions worth validating
  • Sources, observation time, missing data and coverage limits

Limits and boundaries

  • This is not private click and impression data from Google Search Console or Bing Webmaster Tools.
  • Google and Bing are separate live SERP observations. Their coverage, ordering and available elements must not be treated as identical.

How an Agent uses it

Use $research-seo-signals to constrain the keyword, domain, market and language before SEO MCP retrieves the smallest sufficient data scope. Use $decide-content-opportunities only after the evidence is complete.

02 / 05

GEO and AI search visibility

Questions it can answer

Does a brand or page appear in current AI-search results and citation relationships?

Observe Google AI Mode, LLM mention metrics and frequently mentioned pages for a defined location, language and device, preserving the current data snapshot and query conditions together.

Available data and definitions

  • Search-volume estimates for AI search keywords
  • A live Google AI Mode snapshot for the specified location, language and device
  • Target or brand mention and visibility metrics from public LLM answers
  • Pages frequently mentioned or cited in public LLM answers

Research output

  • An AI-search visibility snapshot under defined conditions
  • Relationships among brands, targets and mentioned pages
  • Cited pages and sources available for further checking
  • Observation conditions, timing, coverage gaps and uncertainty

Limits and boundaries

  • This is not an official internal-query log or complete user-prompt record from ChatGPT, Claude, Gemini or another AI product.
  • AI results vary by time, location, language, device and model, and fields may be absent when they cannot be observed in the current result.

How an Agent uses it

Retrieve current GEO data through SEO MCP. The standard workflow still requires a matching Skill; without one, this is a custom integration and the Agent owns field interpretation and evidence boundaries.

03 / 05

Search competitor research

Questions it can answer

Which sites compete for the same search demand, and where do the keyword and results-page gaps come from?

Use keyword and search-result overlap to identify search competitors, then inspect modelled ranking-keyword and traffic estimates plus domain rank distribution. These estimates can differ from live Google rankings and site analytics. Search overlap shows visibility competition, not necessarily business competition.

Available data and definitions

  • Domain and keyword overlap
  • Competing sites that share the same search-results landscape
  • Modelled ranking-keyword estimates for a domain, subdomain or page, including estimated positions and related metrics
  • Modelled organic and paid search-traffic estimates for a domain, subdomain or page, plus domain-level rank distribution

Research output

  • A search-competitor set with overlap evidence
  • A modelled ranked-keyword estimate list for the requested target, not a live ranking export
  • Modelled search-traffic estimates for the requested target, not analytics measurements
  • Market, language, observation time and comparison limits

Limits and boundaries

  • Search competitors come from keyword and result overlap. They do not automatically share the same product, price or audience.
  • Ranking keywords, traffic and cost are model estimates and can differ from live Google results, Search Console and site analytics, and do not prove conversions, revenue or market share.

How an Agent uses it

Retrieve competitor, ranked-keyword and traffic-estimation data through SEO MCP, with a matching Skill constraining market, language, target format and comparison definitions. Direct calls without a Skill are a custom integration.

05 / 05

Social and content-demand research

Questions it can answer

What specific problems are people publicly discussing, repeating and responding to?

Retrieve public posts, articles, notes, profiles and trends under platform-specific query conditions while retaining source URLs and observation time. Social fields follow each platform's response model and are not directly interchangeable.

Available data and definitions

  • Public X posts and trends, plus public Reddit posts
  • Public Zhihu articles, Xiaohongshu notes and public account content
  • Public LinkedIn profiles and posts, plus public WeChat articles
  • Queries, time windows, sorting, pagination and public engagement metrics returned in that platform snapshot

Research output

  • Public conversations and content records with source links
  • Publication time, author context and native platform metrics
  • Repeated questions, user language and content-demand leads
  • Query conditions, pagination state and platform coverage limits

Limits and boundaries

  • Coverage is limited to publicly accessible content. It excludes private content, direct messages, inaccessible logged-in data and a complete firehose.
  • Retrieved results are a query-bound public sample. Engagement metrics differ by platform and cannot be added together or treated as proof of overall sentiment or purchase intent.

How an Agent uses it

Use $research-social-signals to turn a broad goal into focused queries, then let Social MCP retrieve public data while preserving sources, timing, native metrics and pagination state.

// Standard Agent workflow

MCP connects the capability. Skills constrain how it is used.

Connecting MCP alone is a custom integration. The standard workflow also needs matching Skills to constrain tool choice, request scope, field interpretation, evidence handling and decision boundaries. Thin data must remain uncertain.

See the complete Agent setup