Skip to main content
Site Readiness tests whether a search crawler can discover, fetch, render, index, and present a project’s pages. Agent Readiness remains available in its own tab for emerging agent protocols and machine-facing capabilities.

​
Mission Control

New Site Readiness runs do not use an overall score. They report five operational metrics:
  • Search eligibility — eligible, at-risk, blocked, and unknown pages.
  • Important pages at risk — confirmed and inferred priority pages.
  • Search exposure affected — pinned GSC clicks and impressions for the exact affected cohort.
  • Measurement coverage — explicit denominators for each evidence source.
  • Change since prior — introduced, resolved, regressed, persistent, and incomparable findings.
The search-system rail separates Discover, Fetch, Render, Index, Experience, and Appear. Unknown evidence stays Unknown; it is never counted as passing.

​
Issues, pages, and graph

Issues groups durable root findings and keeps the observation, interpretation, proposed action, verification method, source, freshness, coverage, confidence, and applicability together.

​
Fix packages

Each supported finding resolves to Generate now, Clarify first, or Guided engineering. OpenLens asks at most two scoped questions, then produces a validated package with a target, copyable change, expected result, verification, rollback, and evidence provenance. Deterministic builders handle bounded directives and configuration. Metadata and JSON-LD synthesis uses a fixed model and structured output only when the confirmed evidence is sufficient. Stale evidence invalidates the package. The only execution action is Copy fix package. OpenLens does not write to the site, mark a copied fix as applied, or claim indexing, ranking, or traffic gains. A later Site Readiness run determines whether the finding resolved. Pages is the normalized page inventory. It includes discovery source, response and canonical state, crawl depth, internal links, intent, importance, eligibility, Google evidence, and open findings. Site Graph visualizes observed internal links. Sitemap membership is a declaration, not hierarchy. Search covers the full inventory even when the rendered graph is bounded. Maximize, zoom, pan, filters, node detail, and the accessible page table share one selection state.

​
Performance

Performance contains the Google evidence that previously lived under Search & Traffic.

​
Connect Google

Open Settings → Platforms → Google integrations. Search Console and GA4 use separate, read-only organization connections. Assign the appropriate GSC and GA4 property to each project, then run Site Readiness again.

​
Run-pinned evidence

Each run stores a privacy-safe aggregate snapshot for its 28-day evidence window:
  • GSC property totals and page rows joined to normalized readiness URLs.
  • GA4 AI-referral sessions, key events, revenue when present, and aggregate landing-page rows.
  • Collection time, reporting window, source delay, matched and unmatched coverage, and row-limit state.
Reopening an old run shows its original snapshot, not today’s live Google data. GSC usually lags two to three days. GA4 AI-referral attribution is a lower bound because native apps and copied links often omit referrers. OpenLens stores no user-level GA events, identities, or raw journeys in readiness evidence. OAuth tokens remain encrypted in the existing Google connection store.
Observed traffic helps prioritize technical work. It does not prove that a technical finding caused traffic movement.

​
Running a scan

Choose a project, page scope, and optional path prefix. Results stream while OpenLens discovers pages and runs the technical checks. Every run records its assessment version, evidence sources, coverage, partial failures, and terminal state. Historical mixed runs remain readable as Legacy reports with their historical score. New Site Readiness runs are scoreless.

​
Scope and allowances

Effective scope is the smallest of requested pages, the tier’s run cap, and remaining monthly allowance. OpenLens reserves the requested allowance at start and refunds unused pages after completion.

​
Through MCP

  • run_readiness_check starts a readiness run.
  • get_readiness_run reads status, metrics, and evidence subject to plan gating.
  • list_readiness_runs lists project history.
  • get_gsc_search_analytics and get_ga4_ai_traffic expose the connected Google sources to the private agent surface.
The client role cannot start or view readiness runs.