Connect a Google account

Open Opportunity Hunter → Connect and select Connect Google Search Console. Sign in with a Google account that can view the property you want to analyse and approve the read-only permission.

The permission cannot edit Search Console, change a property or access Google Analytics, advertising, email or unrelated Google services. The WPGator authorization service completes the OAuth callback and token refresh so a shared Google client secret is not distributed inside the WordPress plugin.

Select a property

Choose a property from the dropdown and save it. One property is active per WordPress installation. Switching properties does not mix datasets because each completed import retains its property identifier.

Synchronization is administrator-initiated. It retrieves six datasets and builds them separately from the last completed reports:

Reporting windows end three complete days before synchronization so Google’s most recent and potentially incomplete reporting days are not treated as finalized.

Large datasets use Search Console API pages of up to 25,000 rows. Visible progress identifies the active dataset. An incomplete run remains isolated, and the previous reports stay available until all six replacement datasets finish successfully.

Reported metrics

Comparison states

Opportunity labels

Opportunity Hunter applies transparent signals using the connected property’s own visibility distribution. Each result states the evidence that produced its label. The coloured summary cards are clickable filters.

These are review categories, not instructions. They do not determine business value, conversion intent, cannibalization or the cause of a performance change.

Global filters apply across Opportunities, Queries, Pages and their relevant drill-downs. They persist through sorting and tab changes until cleared.

Available lenses

Add relevant location names and abbreviations under Opportunity Hunter → Connect → Query lens settings, one per line. Up to 100 local entries can be saved.

Lenses are neutral filters, not intent judgments. When a lens is active, Pages remain visible and show their number of matching queries beside View queries. Query rows similarly show matching landing-page counts beside View pages.

Queries

The Queries report retains New, Persistent and Lost rows through a full-outer comparison of the two 28-day periods. Select a sortable column heading to reorder results.

Select View pages to see every associated landing page, current and previous impression share, current and previous primary pages, and whether the primary page changed.

The Multiple landing pages indicator is neutral. It may represent intentional regional coverage, product variants or a possible overlap issue. Opportunity Hunter surfaces the relationship without diagnosing cannibalization.

Pages

The Pages report aggregates the Query + page dataset by landing URL. Select View queries to inspect associated queries while retaining active filters and lenses.

Queries and Pages display the first 200 matching rows. An expanded page displays up to 1,000 matching queries. CSV exports include every matching record beyond those screen limits.

Open a query’s landing pages and select Check mentions. The plugin fetches that public page on demand and counts the exact query phrase in:

Checks are case-insensitive but retain the exact wording and punctuation. They are not scored, scheduled or persisted. Results stay visible while reviewing the current report and disappear when the admin page reloads.

The target must be a known query-and-page pair on the current WordPress host. It must be public, return HTTP 200 without redirecting, provide inspectable HTML and remain within the response-size limit.

CSV exports

Opportunities, Queries and Pages each provide an export containing all matching records with the active search, type, impression, click, position, lens and sort settings. Query-to-page and page-to-query drill-downs have their own contextual exports.

Downloads require manage_options and a time-limited WordPress nonce. Copying an export URL to a signed-out or unauthorized browser does not grant access. Values that could be interpreted as spreadsheet formulas are safely prefixed.

Data lifecycle

Allow popups for the WordPress administration page and try again. Confirm the WordPress server can make outbound HTTPS requests to Google and wpgator.tech.

Open Google Search Console with the same Google account and confirm it can view at least one verified property, then return to Opportunity Hunter and use Check connection.

Only one synchronization can run at a time. Allow the active run to finish before retrying. If a prior run became stale, starting again safely discards its incomplete temporary data while the last completed reports remain available.

New, low-volume and privacy-protected queries may produce few or no rows. The report also deliberately excludes Google’s most recent three reporting days.

This is normally caused by Google’s different property and page aggregation methods. Use Site query for query-level totals and Query + page for landing-page relationships and impression share.

Confirm the URL belongs to the current WordPress host, is the final canonical URL, returns HTTP 200 without redirecting and is publicly accessible. PHP DOM is required. Protected, external, redirected, oversized and non-HTML responses are rejected.

The main reports show the first 200 matching rows and expanded page queries show the first 1,000. The record-count message shows the full result size, and CSV export includes every matching row.

Opportunity Hunter is restricted to WordPress administrators with manage_options. Copied report, action and CSV URLs do not bypass capability or nonce checks.