Sources and signals

Search Console history

Synced clicks, impressions, queries, and average positions describe searches Google reported for your property. Page Rankings compares per-page averages over selected trailing windows and previous periods. It also compares search-visible pages with sitemap coverage.

Averages are not daily keyword checks. Visibility alone does not establish credible demand, and a page without impressions in a window is not necessarily unindexed.

Demand screening

The demand screen considers search history and supporting evidence. Its verdict distinguishes confirmed, unproven, and refuted demand. The interface also identifies evidence it has not screened. A missing verdict is not a finding of no demand.

Blog Studio can refuse generation and show the reason. You can override a refusal when you have relevant context, with that choice recorded.

Page audits and query overlap

Site Audit reads a live URL or pasted HTML and records content and metadata findings. Site Clusters groups pages using overlapping queries. These findings provide candidates for the recommendation queue; they are not proof that a specific edit will improve traffic.

Modeled market demand

Some keyword-target candidates use stored modeled market demand rather than the property's own observed history. The recommendation identifies that basis and source. Read these estimates differently from counted impressions and clicks.

Publishing channels and outcomes

Blog Studio prepares new content and refreshes. Google Business has its own post generation, review, scheduling, and publishing workflow, with profile performance alongside it.

For published blog content, outcome reporting requires the live URL and available search data. It records observations, not causal proof. See Blog Studio and the recommendation queue.