Measure — AI Search Visibility

The Measure dashboard is the post-deploy view of your AI Search Visibility workspace. It replaces the standalone Microsite Health Tracker spreadsheet with a live, weekly-updated metric tree so you can see how your optimised pages are performing without maintaining a spreadsheet by hand.

​

How Measure is organised

Measure has three tabs:

​

The four areas

Every metric belongs to one of four areas, each rolling up from raw metrics (L2) into weighted composite scores (L1) and a top-level page count (L0): A Headline metric — Microsite Ready Pages — sits above the four areas as your at-a-glance progress number.

​

Refresh your data on demand

Measure normally updates on a schedule — each source pulls fresh data once a day, and the weekly metric tree is rebuilt every Monday. If you don’t want to wait for the next cycle, admins can pull and recompute right away:

• Sync now (per source) — open a source from its status pill and click Sync now to pull the latest Search Console or Analytics data immediately.
• Refresh metrics — the Refresh metrics button in the Measure header re-runs the weekly aggregation for the current week using whatever data has been captured, so the tiles move without waiting for Monday.

A Sync now also recomputes the current week automatically, so the numbers update in one step. To avoid hammering the underlying APIs, an on-demand sync is limited to once per source every 15 minutes, and Refresh metrics to once a minute.

​

Weekly dashboard summary

On the Overview tab you’ll see:

• The Headline value and its week-over-week trend.
• The four area page counts (how many pages are visible, discoverable, engaged, and monetised).
• Up to two key signals — the biggest movers of the week, good or bad.
• An overall data-quality indicator and a “Data current to …” note so you always know how fresh the numbers are.

​

Metric detail

On the Area tracker tab, open any area to expand its metrics. Each metric row shows:

• The current weekly value and its unit.
• Target vs. actual and the variance, when you’ve set a target.
• A trend chip. Trends are polarity-aware — for metrics where lower is better (bounce rate, average position, page age) a decrease is shown as an improvement.
• A weekly sparkline of the recent trend.
• A data-quality badge — Good, Approximate, or Pending — and a marker showing whether the value was measured automatically or entered manually.

Metrics with no data for the week show an explicit no data state — never a misleading zero.

​

Page and query detail

The Details tab breaks the weekly numbers down to individual pages and search queries. It has up to two sub-tabs, shown once the underlying data exists:

​

Existing vs microsite

Compares your Obvlo-built pages against your own existing pages, so you can see what the optimised pages are actually adding. It shows, per cohort:

• Winning targets and cited targets — how many of your strategy targets are ranking, and how many are being cited in AI answers.
• Median best rank and citation rate.
• A microsite pages table listing each deployed page with its score, target count, and deployment date.

​

Search Console

Available once Google Search Console is connected. It shows:

• Microsite cohort — which URL paths count as “the microsite” for Analytics and Search Console attribution.
• Indexed pages — a weekly count of indexed microsite pages.
• Page performance — impressions, clicks, CTR, and position per page.
• Post-deploy position trend — how rankings have moved since deployment.
• Untargeted queries — queries driving impressions to your deployed pages that aren’t in your strategy yet. Each one can be added to your strategy directly from this table.

​

Connecting your data sources

Measure draws on Google Search Console (Visibility and Discoverability) and Google Analytics 4 (Engagement and Monetisation). Both are connected from your domain’s settings, and both are read-only — Obvlo never requests write access. To connect Google Analytics on a Pro plan, click Connect Google Analytics:

1. Grant Obvlo read-only access to your Analytics data.
2. Pick the GA4 property you want to track.
3. From the next sync onward, the Engagement and Monetisation areas populate automatically.

Until GA4 is connected, those two areas show a Connect Google Analytics prompt rather than empty numbers. Disconnecting revokes Obvlo’s access at Google and stops future syncs; the history already collected is retained.

​

You only connect each website once

A Search Console or Analytics connection is stored against your website, not against an individual set of pages. If you run several Obvlo page groups on the same website, they all inherit that one connection — there’s nothing to connect a second time, and Obvlo won’t pull the same data twice. Where a particular set of pages genuinely needs its own Analytics tag or Search Console property, it can be pointed at one; that override replaces the shared connection for those pages only.

​

Site-wide vs Microsite

Your Analytics property usually covers your whole website, not just the pages Obvlo builds. So Measure splits every Engagement and Monetisation metric into two paired values:

• Site-wide — the whole Analytics property (every page on your site).
• Microsite — only the pages under your microsite’s path (the pages Obvlo optimised and deployed).

Seeing them side by side tells you how much of your engagement and revenue is coming from the Obvlo-built pages versus the rest of your site. The two cohorts are scoped slightly differently, to match how each metric actually behaves:

• Engagement (sessions, engaged sessions, engagement time, and so on) is counted per page — a metric belongs to the Microsite cohort when the page itself sits under your microsite path.
• Revenue and purchases are counted per session’s landing page — a purchase is attributed to the Microsite cohort when the visitor arrived on a microsite page in that session. This is because the purchase event fires on your checkout page, not on the content page, so counting it by the checkout page’s path would under-report the microsite’s contribution.

​

How rows are assigned

Because one website can host more than one set of Obvlo pages, every Analytics and Search Console row is assigned to the set of pages that owns it, matched on the longest matching URL path. A row that doesn’t sit under any Obvlo path falls into a rest of the site bucket rather than being dropped or double-counted. The same page classification is used everywhere — monitoring, effectiveness, and Measure all agree on which pages belong to your microsite, so your own existing pages are never counted as Obvlo-generated ones.

​

Targets, manual entries, and the change log

Team members with super-admin access can:

• Set targets for any metric (per week, or as a rolling default).
• Enter a value manually for metrics without an automated source — for example the Microsite Ready Pages headline or a manual site: index count — recording a data-quality status and an optional note on where the value came from.
• Override the data-quality status of a metric.

Every manual entry, target change, and quality override is written to an immutable change log (who changed what, when, and the before/after values), so the numbers are always auditable.

​

Data-source health

A data-source health matrix shows the connection state of each source (Google Search Console, Google Analytics 4, and AI citation data), including the last successful sync, with quick links to reconnect anything that needs attention.

​

Is your data actually flowing?

A source can be connected and still not be capturing anything — for example if the Analytics tag isn’t firing on your pages yet. Rather than showing a misleading green tick, each source in the Measure header shows one of three states: When Analytics is connected but showing 0 rows, the most common cause is that the GA4 tag isn’t firing on your site yet, or the property simply has no data for the window. Search Console with 0 rows usually means the property has no impressions in the window yet.

​

Inspecting captured data

Click any source pill to open its capture detail drawer. The drawer shows:

• The current capture state and, for a 0-rows source, the likely cause.
• The sync status, last sync time, and the row count and window of the most recent sync.
• Recent captured rows — the last few days of raw Search Console / Analytics rows exactly as they came in, before the weekly aggregation runs. This lets you confirm data is arriving even on a day when the weekly tiles haven’t updated yet.
• A Sync now button to pull the latest data for that source right away.

​

Related

• Reports
• AI Visibility Health Check methodology
• Microsite