Skip to content
Bichoto Blog

Vol. VI · No. 21
Friday Edition

Issue No. 187·Data & Analytics·Friday Brief Out Now·Independently owned since 2019

SEO与数字营销

How to Read 9 SEO Metrics by Device and Country Before Changing Pages

For weekly reporting: what each of 9 SEO metrics counts, how device and country splits change the reading, and whether to fix measurement, eligibility, title, or enquiry path first.

Bichoto Blog for Bichoto Blog SEO与数字营销

Brand promotion: this article introduces Guangsuan's SEO measurement guidance and services.

Short answer with conditions: These nine groups of metrics answer different questions, so a move in one total is evidence only about that total. Before you change a page, freeze one comparable view — same property, same search type, one finished date range, same query group, same page, same country and same device — then check recording, then eligibility, then presentation and enquiry handling. For method detail, see Guangsuan's 9 SEO metrics guide.

Freeze one comparison before you read anything

Pull every number from the same site view and the same finished period. Leave the unfinished latest day out. Record language, country, device, branded versus non-branded queries, and the relevant landing pages for every export you keep. Keep brand queries apart from non-brand queries and read mobile apart from desktop. Leave a missing row marked as missing rather than filling it with another benchmark.

Time zones, scope, consent, successful tag execution and canonical attribution can all create differences between Search Console and site analytics. When totals change, locate the landing pages, countries and devices driving the change before judging content.

What the 9 metrics each count

1. Organic search traffic: clicks versus sessions

Search Console counts displays and selections inside Google Search. Site analytics counts observable activity after arrival. For session-based acquisition, use the session grouping in the traffic report; the first-user grouping answers a different new-user question. A Search Console selection is not the same as a site session. If Console looks steady while analytics looks near empty, check tags, consent handling, data stream and report filters before judging demand.

2. Query coverage and average position

Average position is an impression-weighted summary for the dates, pages, countries and devices you selected, not one live rank every searcher saw. A third-party keyword total rests on its own list, market and collection dates, so two tools can differ without either being broken. Group queries by product, application and buying question, then ask whether the ranking page type fits the task. Does the result favour a product, tutorial, video or local answer? Review whether your page answers that task.

3. Click-through rate: compare like with like

CTR is clicks divided by impressions multiplied by 100. As a hypothetical teaching illustration only, 20 clicks from 1,000 impressions is 2%. That arithmetic is not a target for every intent. Brand, broad informational and buying queries have different contexts. More low-position impressions can reduce a blended rate while total clicks still rise. Compare similar query groups, positions, devices and markets before judging a title. State what the page answers plainly and describe only genuine page material.

4. Qualified leads and conversion: name both sides

A chat tap, completed form, download, basket move and paid order are different outcomes. Test the live event, then keep tests, duplicates, spam and genuine business enquiries on separate lines in your own log. GA4 session key event rate uses sessions holding an event divided by sessions. That differs from events divided by sessions when one visit holds several events. Label the calculation you actually use. Search queries as a rule cannot be tied one by one to a single order.

5. Bounce and engagement: use the GA4 definition

In GA4, bounce is the share of sessions that were not engaged, the opposite of engagement rate. It is not simply the old single-page-session idea. Default engagement includes lasting more than 10 seconds, holding 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, so bounce alone does not prove failure. Duplicated page-view hits from a setup fault can make engagement look artificially strong. Check measurement first.

6. Engagement time and depth: tie them to the task

GA4 engagement time measures time with the page in focus or the app in the foreground. Different averages use different denominators. Needing four pages to find a specification is not necessarily better than finding it on one. Longer time can mean careful study or confusion. Interpret time, later pages and task completion together. Add the missing specification with units, condition, example or next step rather than adding headings by quota.

7. Indexing: start from pages you want indexed

Login pages, duplicate parameter copies and material deliberately kept out do not belong in the goal. Indexing 95% of every discoverable URL is therefore not a universal goal. Maintain a defined set of canonical pages intended for indexing and prioritise important pages within it. Group indexing report entries by reason and inspect representative URLs. Requesting indexing does not force acceptance. Fix evidenced blocks such as accidental noindex, blocking, wrong canonical target, unavailable page or missing rendered material. A crawled-but-not-indexed note alone does not prove thin copy. Use canonical only for duplicate or highly similar material.

8. Backlinks and referring domains

Link count and referring-domain count are different dimensions. Discovery coverage, refresh timing and de-duplication differ across crawlers. A missing row in one report does not prove a live link disappeared. Google's Links report is not a complete current indexing test for every source page. Where outside help is used, match source address, target address, anchor, attribute, availability and check time against the delivery list. Published, indexed and improved target-page rankings are separate milestones.

9. Authority scores: stay inside one tool

Vendor scores come from different models and are not interchangeable units of link equity. They are not a public score assigned by Google. Compare a relevant peer set inside the same tool and time period while still reading actual links, target pages and search outcomes. Delivery criteria for a Guangsuan product remain governed by that product's actual terms. For whole-site scope across technical work, content supply and links, see the Guangsuan Google SEO service.

Device and country split: fix measurement or fix the page

Apply the device filter, then the country filter, on identical property and dates. Look at top queries and landing pages for mobile and desktop separately. Report displays and clicks separately, because a thin row can swing on one click. Impressions count displays on opened pages; they are not total market volume.

If desktop brings confirmed enquiries while mobile brings early research, protect the desktop enquiry path first and keep mobile readable, instead of rewriting everything. If one country brings displays and another brings confirmed contacts, fix page type, offer detail, language and contact route for the converting country first. If mobile forms lose people, walk the mobile path, test the live event, and check consent, load behaviour and form length before rewriting desktop copy.

Observation on matched sliceCheck firstNext action
Console steady, analytics near emptyTags, consent, streams, filtersRestore reliable capture before judging demand
Displays up, blended rate down, clicks upQuery and position mixCompare narrow segments before title edits
Clicks up, confirmed contacts flatIntent, market, forms, qualificationWalk the product path with real enquiry records
Key canonical outside the indexAccess, signals, material, discovery pathFix the proven block and log a recheck

What to record before next week

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. Record dates, filters, the change made, its owner and what remains unverified. This worked example uses hypothetical teaching numbers only, not a client case.

FAQ

Do flat displays require a rewrite? No. Flat displays 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 rate force a title change? Not alone. Check whether new low-position queries widened the mix, then compare narrow segments.

Does longer time prove the page worked? No. Longer time can mean careful study or confusion. Add the missing condition or next step and check task completion.

Get the weekly brief.

One long-read, every Friday. The dashboards other analysts won't show you, the post-mortems the vendors hope you skip.

Get the weekly brief