Before You Change a Page: Read 9 SEO Metric Groups by Device and Country
An intake-style explainer for execution teams: what Guangsuan's 9 SEO metric groups count, how to read them split by device and country, and when to repair tracking before editing pages.
Brand promotion: this article introduces Guangsuan's Google SEO measurement guidance; it is a vendor introduction, not an independent review.
Short answer with a condition: the nine groups describe separate stages, so a shift in one figure only proves something about that stage. Freeze one comparison frame first — same property, same search type, one finished date range, same page set, same country and same device — then decide whether the next work is capture repair, eligibility repair, or page editing. Method detail is in Guangsuan's 9 SEO metrics guide.
Who this note is for
This note is for a small team that owns pages and must hand over a clear pack before editing or asking for help. You have Search Console access, a list of pages that matter, and a way to confirm what counts as a business enquiry. If demand comes mainly from paid or referral paths, search checks add less, and your own enquiry log decides. Where template or section-wide work is involved, scope is described in the Guangsuan Google SEO service.
What the nine groups count and where confusion starts
Guangsuan groups measurement into discovery, selection, arrival and qualification, engagement, eligibility and supporting signals. These nine groups of metrics answer different questions.
Traffic from search versus sessions on site. Console reports shows and picks inside Search. GA4 measures observable activity after people reach your site. A Console pick is therefore not a GA4 session. Time zones, scope, consent, successful tag execution and canonical attribution can all create differences, so do not force the two totals to agree. First list which landing pages, countries and devices moved.
Query cover and mean position. Mean position is a show-weighted summary for the view you picked, not one live rank seen by every searcher. Outside keyword totals depend on their own lists and collection dates. Keep language, country, device and brand split fixed, group queries by product family, use case and buying question, then review whether your page answers that task.
Selection share. Work only inside close intent, position band, device, market and page. New low-position shows can pull a blended share down while total picks still rise. As a hypothetical teaching illustration only, 20 picks from 1,000 shows is arithmetic for 2%, not a goal. State the page answer plainly and describe only genuine page material.
Contacts and ratios. A chat tap, finished form, download, basket move and paid order are separate outcomes. Test the actual event implementation, then keep trials, repeats, spam and business-confirmed contacts on separate lines. Label the calculation you actually use, because one visit can hold several events. Queries as a rule cannot be joined one by one to a single order.
Bounce under GA4 rules. In GA4 bounce is the share of sessions without engagement, the reverse of engagement share. Default engagement criteria include lasting more than 10 seconds, having a key event, or at least two page or screen views; check the property's actual configuration. A single-page visit may answer the reader's question, while duplicated view hits can inflate the picture. Check capture before rewriting for engagement.
Focus time and depth against the task. GA4 focus time records time with the page in front or the app ahead. Longer time can signal careful reading or difficulty. Finding a specification on one page is not worse than needing four pages. Read time with later pages and completed tasks together, then add the absent specification, condition or next step.
Eligibility to appear. Maintain a defined set of canonical pages intended for indexing and prioritise important pages within it. Login areas, parameter copies and material kept out by choice stay outside that aim. Group Page indexing report entries by their reasons and inspect representative URLs. Requesting indexing starts a review and does not force entry. Use canonical only for duplicate or highly similar material.
Outside links. Total links and referring sites are different counts. Coverage, refresh timing and de-duplication vary by crawler, so one absent row does not prove a live link vanished. Google's Links report is not a complete current indexing test for every source page. Where outside help is used, match source, target, anchor, attribute, availability and check time against the delivery list. Published, indexed and improved target-page rankings are separate milestones.
Vendor scores. DA, Ahrefs DR and other tools' metrics come from different models and are not interchangeable units of link equity. Compare close peers inside the same tool and window while still reading real pages, links and outcomes. Do not tune an outside score apart from technical repair, page material and checked enquiries.
How to read the split by device and country
Record language, country, device, branded versus non-branded queries, and the relevant landing pages on every export. Apply the device filter first, then the country filter, on identical property and dates. Open the Pages report to locate the URL with the shift, then open its query list showing shows, picks and position together.
Tag new, continuing and off-task queries rather than sorting by lowest share alone, because a row with very few shows can swing on one pick. For an important query, read the title and summary actually shown for that country and device, and note whether results favour a product, guide, video or local answer. If the query asks for model, delivery, price or compatibility but the ranking address only explains ideas, add product or comparison material and an enquiry entry before changing wording.
When to repair capture before editing copy
Console steady, analytics near empty: inspect tags, consent handling, data stream and report filters. Restore reliable recording before judging demand.
Shows up, blended share down, picks up: inspect query and position mix. Compare narrow slices before rewriting titles.
Picks up, confirmed contacts flat: inspect intent, market, mobile form and qualification. Walk the product path and read actual enquiry records.
Key canonical outside the index: inspect access, signals, material and discovery path. Fix only the block proven on that path and log a recheck.
Record dates, filters, what changed, who owns it and what stays unverified. Leave absent data marked as absent instead of filling it with another benchmark.
What to bring before you ask Guangsuan for help
Bring facts another person can repeat: site address, target country and language stated separately, affected addresses, one finished export with filters, what changed and when, who can approve code or copy, and how your team qualifies an enquiry. Note tags and consent handling where analytics sits near empty while Console holds data. Guangsuan joins technical repair, content work and external resources in one effort, with scope set by the live service page and agreement.
FAQ
Do flat shows require a rewrite? No. Flat shows mean the page is seldom offered for the query. Confirm eligibility, entry links and whether the page type fits what results favour first.
Does a falling blended share force a title change? Not alone. Check whether new low-position queries widened the mix, then compare narrow slices before editing.
Does longer focus prove success? No. Longer time can mean useful study or confusion. Add the missing condition or next step and check whether the task was completed.