Skip to content
Runner AI
Analytics and SEO
English
Esc
navigateopen⌘Jpreview
On this page

Search performance

Read domain, organic traffic, keyword, and top-page estimates without treating them as guaranteed rankings.

Search performance helps you identify which queries and pages appear most important in the data available to Runner.

Conditional: These estimates appear only after an eligible SEO analysis returns provider data. A new or low-traffic domain may have little or no data.

Entry path

Open a store project → GrowSEOSearch performance card → Open.

English annotations: A new store must complete the SEO publication prerequisite before using reports. The sample-data preview is illustrative; no analysis result is shown here.

English callouts highlight the controls. Select the image to enlarge it.

A new store must complete the SEO publication prerequisite before using reports. The sample-data preview is illustrative; no analysis result is shown here.

Before you start

If SEO shows the first-store setup checklist, complete its publication requirement before expecting report data. Values labeled Preview · sample data are examples, not your store’s results. The steps below are conditional on the corresponding report becoming available.

  • Complete a successful SEO analysis for the public target.
  • Use the analyzed domain shown by Runner, especially when the project has more than one domain.
  • Read provider estimates as directional signals; they may not match first-party analytics exactly.

Main sections

Section What it means
Estimated organic traffic A provider estimate of visits from unpaid search.
Organic keywords Search terms for which the domain has available visibility data.
Domain rank A comparative authority or visibility measure from the available provider.
Top 3 keywords Keywords estimated to rank near the top of search results.
Top keywords Queries with their available position or traffic information.
Top pages Public pages receiving the strongest estimated organic visibility.
Ask Runner Creates a new Runner conversation with the saved report evidence and a suggested improvement request. It does not edit or publish the store by itself.
See 5 quick wins Creates the same evidence-grounded Runner handoff so you can ask for prioritized opportunities in chat. Review any proposed work before applying or publishing it.
Analyze again Requests a new snapshot; it does not change content or ranking.

Review search opportunities

  1. Open Search Performance after analysis completes.
  2. Confirm the analyzed domain is the public storefront you intended.
  3. Read the summary metrics as a baseline, not a promise.
  4. Scan Top keywords for terms that match the products and audience.
  5. Open or note the corresponding Top pages.
  6. Compare the page content with the shopper question behind each useful keyword.
  7. Make storefront changes through Runner or the store editor, then publish them separately.
  8. Return later and select Analyze again when enough time has passed for public sources to change.

Troubleshooting

State Meaning and next step
No organic data The provider may not have enough information for the domain. Confirm publication and try again later.
Keyword but no matching page Open the page list and public site; the provider may attribute the query to a different URL.
Estimate differs from Analytics Analytics records store events; SEO uses external search estimates. Align the question before comparing them.
Newly published content is absent Search discovery is not immediate. Confirm the page is public and wait before refreshing.

Choose one reviewable improvement

Use Keywords and Pages in the opened report to connect a useful query to a public page. If Open fix queue is shown, inspect the proposed fix and its affected page before starting work with Runner.

Checkpoint: You can name the query, page, and change to review. External search figures are estimates. An optional Google Search Console connection can supply first-party clicks when available; it is not connected automatically and should not be confused with the estimates.

Last updated on September 8, 2026

Was this page helpful?