Skip to main content

SEO Performance

Enriching and publishing is half the job. The other half is knowing whether it worked: does Google show your pages more, do people click them, and did the last re-enrichment help or hurt?

Clione answers that with your own Google data, in three places:

  • the SEO Performance page, for the whole store;
  • the Insights tab of each product, category, collection and page;
  • the History tab of each of them, which splits the numbers by enrichment version.

All three read Google Search Console. Nothing here spends credits.

Connect Search Console and GA4 first​

Both connections live in Store Settings → Integrations, and an owner or admin makes them. Each one is a Google sign-in followed by choosing the property that belongs to this store. The step-by-step, and what to do when Google shows no property, is in Google integrations.

  • Google Search Console is what this page is built on: impressions, clicks, click-through rate (CTR) and average position for every URL of your store. If it isn't connected, the SEO Performance page lets you connect it from the page itself.
  • Google Analytics 4 adds what Search Console can't see: the sessions and revenue that AI assistants (ChatGPT, Perplexity, Claude, Gemini, Copilot and others) send to each URL. Those numbers appear in Attribution (on plans that include it) and in branded reports, not on the SEO Performance page.

Clione refreshes Search Console and GA4 data once a week. Google itself publishes search data a few days late, so the most recent days are never in.

The SEO Performance page​

Open a store and click SEO Performance in the store menu. The header shows the connected property and when the data was last fetched.

Four totals: impressions, clicks, unique queries and URLs with traffic.

Two tables, the top 20 of each, sorted by impressions:

  • Top queries — what people searched for to find your site.
  • Top URLs by impressions — your most visible pages in Google Search.

Both show impressions, clicks, CTR and average position (lower is better; 1 is the top organic result). The tables cover the most recent two-week window Google had published at the last refresh. There are no filters or date pickers.

Enrichment impact appears once there are enriched products to compare. It reads, for products, how impressions moved after enrichment:

  • Enriched URLs · impressions Δ against Site total · impressions Δ, so you can tell your enrichments apart from a site-wide trend.
  • Enrichment cohorts — products enriched on the same day, grouped, comparing the 7 days before the enrichment with the 7 days after.
  • Top winners and Top losers — the enriched URLs that gained and lost the most impressions. The losers are your candidates to re-enrich.

The Insights tab​

Every product, category, collection and page has an Insights tab. Its Search performance section shows, for that one URL:

  • impressions, clicks, average position and CTR for the last 28 days, each with the change against the 28 days before;
  • the top queries that bring traffic to that URL.

What you may see instead of numbers:

  • No storefront URL yet — the entity has never been published, so Clione doesn't know its URL. Publish it once.
  • Not connected — Search Console isn't connected for this store. The link takes you to Integrations.
  • No data — Google has nothing for this URL in the last 28 days. A newly indexed page can take one to two weeks to appear.

Per-version results in History​

Each enrichment saves a version. The History tab of each entity has a Search attribution by enrichment window table that shows, for every version, what Google recorded while that version was the live one: impressions, clicks, CTR and average position.

  • Window — from the day the version was enriched until the next version replaced it. The current version reads "Since … (current)".
  • n = days observed — how many days of data the window holds. Compare versions with a similar n: two days and twenty days are not on equal footing.
  • Change vs the previous version — under each value. Percentage for impressions and clicks, percentage points for CTR, positions for average position. Green means better (for position, lower is better).

Two states are deliberately not shown as numbers:

  • Not measured — there is no data for that window. That is a gap, not zero traffic.
  • Partial — the window started before the oldest data Clione keeps, so its figures are a floor ("at least this much") and no change is calculated against it.

If a re-enrichment made things worse, you can restore the previous version from the same History tab; see Rollback.

Alerts​

After each weekly refresh, Clione checks two patterns and tells you in the notifications bell; owners also get an email unless they turned those emails off.

  • A title that ranks but doesn't get clicked. A URL on the first page of Google for a query with many impressions and a CTR under 1%. The alert names the query and suggests re-enriching that URL.
  • A drop. A URL (or a URL and query) whose impressions fell sharply or whose position worsened by several places compared with the previous two weeks.

These are suggestions. Re-enriching is still your call, and it uses a credit like any other enrichment.

Search Console makes re-enrichment better​

When Search Console is connected, every enrichment of a product, category, collection or page that has search data includes the top queries Google sends to that URL. The AI is asked to work them into the title and description, to rewrite around a query that gets impressions but few clicks, and not to invent unrelated keywords. Without Search Console, enrichment works exactly the same, just without that context.