Skip to main content

​
Direct answer

Open Monitor > Source Explorer and rank your own source URLs within a defined period and filter set. Then inspect the answers and prompts behind each URL. A high count describes the selected stored dataset; it does not prove page quality, traffic, or future citation behavior.

​
Data required

Use stored answers, recorded citation URLs, SELF and DIRECT source classification, configured prompts, providers, topics, tags, and a fixed period. Use Page Performance or GSC only as separate contextual datasets.

​
Workflow

1

Set a comparable scope

Choose the period, providers, topics, and prompt set. Keep those filters visible when comparing URLs.
2

Rank SELF source URLs

In Source Explorer, filter to your domains and review citation occurrences and distinct answers. Do not combine these units.
3

Inspect supporting answers

Open representative answers for each leading URL and note the prompt, provider, topic, surrounding claims, and other cited sources.
4

Compare with page context

Review Page Performance or connected GSC data separately to identify pages worth investigating, without merging unlike metrics into a single conclusion.

​
Interpretation

A citation is a source URL recorded with an answer; it neither implies a mention nor confirms a click. In the product, Citation Rate is answers citing a SELF source divided by answers citing at least one SELF or DIRECT source. Counts can be concentrated in repeated prompts, providers, or topics, so inspect distribution as well as totals.

​
Possible next actions

  • If one page appears across several relevant prompt and provider slices, test whether its evidence or format can inform other pages.
  • If citation counts come from one narrow prompt group, avoid generalizing the pattern to the whole site.
  • If an important page is absent, test whether another first-party page better answers the observed questions.

​
Limitations

Qwairy observes citations in selected stored answers, not the complete output of any provider. Citation counts are sensitive to monitoring configuration and period. The REST source-URL endpoint is a separate contract; verify its fields, filters, and units before comparing it with the product.

Source URLs in Looker Studio

Build reporting from the documented Looker Studio source.

Source URLs API

Use the endpoint’s documented fields and units.

Source Explorer

Review citation-source behavior in the product.

Visibility over time

Compare stable cohorts across periods.

Gap to article

Test a publishing hypothesis.

Provider mentions

Analyze mentions separately from citations.

Choose what to create

Prioritize content using observed evidence.