Search opportunities
Combine audited content with Google Search Console performance when available.
Search opportunities combine what Sight can observe on the audited website with first-party performance data when Google Search Console is connected. Without Search Console, suggestions describe content structure and relevance found during the crawl. They do not claim keyword volume, live rankings, or traffic impact.
With Search Console, query and page performance can be read beside the audited content that earned those impressions and clicks. Use the date window, property, and page match as part of the evidence. Prioritize changes where search demand and a concrete content or technical gap support the same decision.
Treat an opportunity as a hypothesis that combines demand evidence with an observable page condition. Review the current query intent, the page that receives impressions, the page content, and any technical obstacles before proposing a rewrite or new page. After publishing a change, compare a suitable later Search Console period and keep seasonality, indexing delay, and unrelated site changes in mind.
Without Search Console
Sight derives opportunities from the content it crawled. These are content suggestions, not claims about live ranking or search volume.
Use crawl-derived opportunities to improve clarity, structure, internal linking, and topical coverage that Sight can observe directly. Validate the audience need through other research before estimating commercial impact. These suggestions become stronger when paired with first-party demand or conversion evidence.
With Search Console
Connect a verified Search Console property to add clicks, impressions, click-through rate, and average position for queries and pages.
Search Console adds observed performance but not intent certainty. Compare queries with the content and purpose of the matching page, exclude periods affected by major tracking or site changes, and keep the property and date window attached to any exported opportunity list.
- 1
Connect Google
Open Integrations or Search opportunities and authorize access to Search Console.
Use an account with access to the intended property and review the requested authorization in the Google flow. Organizational Google policies can block or limit the connection even when the user can open Search Console separately.
- 2
Choose the property
Sight selects the closest matching property and lets you switch among properties available to the account.
Compare domain and URL-prefix properties carefully. Select the property whose population matches the audited hostname and market, then document that choice because switching properties can change every query and page total.
- 3
Choose the date window
The current endpoint defaults to the last 28 days ending three days ago.
Use a window long enough to reduce daily noise but short enough to reflect the current site. Keep processing delay, seasonality, launches, migrations, and campaign activity in mind when comparing against another period.
- 4
Review queries and pages
Use audited page context with Search Console evidence to prioritize updates.
Look for a coherent relationship between the query intent, receiving page, impressions, clicks, and audited content. Prioritize evidence-backed mismatches and record the baseline so the effect of a later change can be reviewed.