Maple Orbit

MAPLE ORBIT FIELD GUIDE

Read country and device breakdowns correctly

Understand where your website appears and how reported performance differs across devices.

Ask for a breakdown first

Show Web search performance grouped by country and device for the last complete 28-day period. Keep country codes and device values from the source. Include clicks, impressions, CTR and average position.

This groups your selected website’s results. It does not measure all searches performed in each country, and it does not identify individual visitors. Country is a reporting dimension, not proof of a shopper’s delivery address.

Use the result to choose a question

A Canadian shop might investigate why much of its visibility comes from outside its delivery area. A different device mix might prompt a mobile shopping review. Those are reasons to inspect the experience, not evidence that a checkout or layout is broken.

Compare an appropriate baseline rather than assuming the largest country must also have the highest CTR. Query intent and ranking mix can differ between groups.

Grouping is different from filtering

The current connector supports country and device dimensions but does not expose server-side country filters. Asking an assistant to retain Canadian rows from a returned query-and-country list is an analysis of that subset. It is not equivalent to asking Google for the top Canadian queries before the row limit is applied.

If a decision depends on a complete country-specific shortlist, use the native Search Console country filter until Maple Orbit supports that request directly. The same care applies to filtering for an individual page.

Keep the next step practical

Check whether your website explains currency, delivery area and support clearly to the audience you serve. Do not claim a local office or inventory location based on search geography.

Further reading

Official Google documentation. Product instructions distinguish the browser beta from the invited connector pilot. Educational guidance does not imply an automated feature.

← Back to the learning library