Skip to main content

​
Direct answer

Qwairy cannot directly measure when a model ingests or learns a page. You can record publication time, compare it with a page identity’s retained firstSeenAt, check whether the URL later appears as a citation, and review relevant stored answers. Report each milestone separately.

​
Data required

Use the final public URL, publication timestamp, deployment and update log, reconstructible normalized paths, retained first and last observed times, daily occurrence rollups, coverage state, stored answers, citation URLs, configured prompts, providers and models, topics, and run dates.

​
Workflow

1

Record the release

Save the canonical URL, publication time, content scope, sitemap or internal-link state, and the prompt cohort relevant to the page.
2

Check the first retained crawler observation

In Crawler Analytics, find the reconstructible page identity and review firstSeenAt, lastSeenAt, occurrence rollups, status-code groups, and coverage. firstSeenAt is the first retained HTTP 2xx page observation, not a raw-event sequence.
3

Check recorded citations

In Source Explorer, look for the published URL in comparable stored-answer runs. Keep citation presence separate from SELF mentions.
4

Review answer changes

Read relevant answers before and after publication and document any changes with the same provider, model, prompt, and topic filters.

​
Interpretation

The interval to the first retained crawler observation, first recorded citation, and first relevant answer change are different measures. None proves indexing, training, or causation. A citation URL can appear without a SELF mention, and a SELF mention can appear without citing the page.

​
Possible next actions

  • If no page observation is retained, check coverage, discoverability, and access configuration before changing the content.
  • If crawling is observed without citations, test whether the page addresses the monitored audience need with verifiable evidence.
  • If an answer changes before a citation appears, investigate other sources and model changes rather than attributing it to the page.

​
Limitations

There is no universal or guaranteed pickup timeline. firstSeenAt is durable but Crawler Analytics does not retain raw request events; page rollups retain 30 analytic days. Visibility also depends on supported User-Agent identification, delivery coverage, provider behavior, and source availability.

Source URLs in Looker Studio

Report URL-level milestones.

Crawler Analytics

Review retained crawler observations and coverage.

Crawler configuration guide

Read additional technical guidance.

Campaign impact

Compare stable campaign cohorts.

Pages cited by AI

Review recorded citation URLs.

Prioritize providers

Choose the provider cohort to monitor.

Gap to article

Run an evidence-led publishing experiment.