Opportunity Hunter – Search Insights

By WPGator

0+ active installationsVersion 1.2.0

Turn your own Google Search Console data into focused, explainable search opportunities inside WordPress.

Description

Opportunity Hunter – Search Insights connects one WordPress site to Google Search Console through the WPGator OAuth relay. It imports finalized Web Search data into your local WordPress database and provides focused reports without adding front-end tracking scripts, analytics cookies, or page-speed overhead.

Reports compare the current and previous 28-day periods, with 90-day context. They include:

  • Explainable Defend, Recover, Grow, and Review performance signals.
  • Query and landing-page reports with bidirectional drill-downs.
  • Impression, click, and position filters, plus optional query lenses.
  • On-demand exact Search Term Mentions checks for local WordPress pages.
  • Complete, nonce-protected CSV exports.
  • Optional daily or weekly local dataset synchronization through WordPress Cron, disabled by default.
  • Token-protected, read-only MCP access for compatible agent harnesses.

Search data is stored on your WordPress site. WPGator’s OAuth relay handles Google authorization and token exchange but does not retain your Search Console report data.

External services

Opportunity Hunter – Search Insights uses two external services only when an administrator explicitly connects Google Search Console, checks the connection, synchronizes report data, or enables automatic synchronization.

Google Search Console API

The plugin sends the selected Search Console property, report date range, report dimensions, search type, aggregation type, and pagination offset directly from your WordPress site to Google’s Search Console API. Google returns query and landing-page performance data including clicks, impressions, click-through rate, and average position. Those report rows are stored in this site’s WordPress database and do not pass through WPGator.

Google terms and privacy information:

  • Google API Terms: https://developers.google.com/terms
  • Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
  • Google Privacy Policy: https://policies.google.com/privacy

WPGator OAuth relay

The WPGator authorization service handles Google sign-in, authorization-code exchange, and access-token refresh because a distributed WordPress plugin cannot safely contain a Google OAuth client secret. During connection it receives a one-time hashed claim, and during token refresh it receives the Google refresh token required to obtain a new short-lived access token. It does not receive, proxy, retain, or inspect Search Console report rows.

WPGator service information, terms, and privacy:

  • Opportunity Hunter – Search Insights: https://wpgator.tech/wpgator-search-insights/
  • Terms of Service: https://wpgator.tech/terms-of-service/
  • Privacy Policy: https://wpgator.tech/privacy-policy/

Installation

  1. Upload and activate Opportunity Hunter – Search Insights.
  2. Open Opportunity Hunter in WordPress admin.
  3. Connect your Google account and select a Search Console property.
  4. Synchronize the report data.
  5. Optional: choose a weekly or daily automatic synchronization schedule under Data.
  6. Optional: generate a token under Agent Access and follow your agent harness documentation for adding a remote Streamable HTTP MCP server.

FAQ

Does the plugin add Google Analytics or a front-end tracking script?

No. It reads first-party Search Console reporting data and adds no visitor tracking script or analytics cookie.

Does WPGator store my Search Console report data?

No. Imported report data is stored in your local WordPress database. The WPGator relay is used only for the OAuth authorization and token-exchange flow.

Are the opportunity labels SEO or conversion scores?

No. They are explainable views of changes in Search Console visibility and engagement. They do not predict business value, intent, or conversions.

Can an AI agent change my WordPress site or refresh Search Console data?

No. Agent Access exposes eight read-only MCP tools for the latest completed local datasets. It cannot edit WordPress, change plugin settings, initiate synchronization, or retrieve Google credentials. Agent Access is disabled until an administrator generates and enables a token.

How do I connect an agent application?

Generate a token under Agent Access, then follow the documentation supplied by your agent harness for adding a remote Streamable HTTP MCP server with bearer-token authentication. Configuration names and secret-storage methods differ between applications, so the plugin supplies the endpoint and credentials but does not prescribe a harness-specific configuration.

When does automatic synchronization run?

It is disabled by default. Administrators may select Weekly or Daily under Data. Runs use WordPress Cron, so the actual start time depends on site traffic and may be later than the displayed schedule.

Is compiled or minified source used?

No. The distributed PHP, JavaScript, and CSS files are the maintained source. No build step is required.

Screenshots

Changelog

1.2.0

  • Added optional weekly or daily automatic Search Console dataset synchronization, disabled by default.
  • Added token-protected, read-only MCP access with eight bounded reporting and inspection tools.
  • Added current and legacy MCP protocol compatibility, strict request validation and private tool-manifest caching.
  • Added explicit comparison-window, pagination, page-metric and query-lens scope metadata for agent clients.
  • Added in-plugin connection guidance that refers users to their selected agent harness documentation.

1.0.0

  • Initial public release.