Brand promotion: this article introduces Guangsuan's SEO measurement guidance and services.
When pipeline review mixes visibility, visits and enquiries, hold page edits until you know what each number counts. These nine groups answer different questions, so a move in one total is evidence about that total only. Fix one comparison frame for every pull: same property view, same search type, one finished date range, one query group, one page, one country, one device. Record language, branded versus non-branded queries, and landing page on each export.
Short answer: measure first, then page
If Search Console looks steady while site analytics records almost nothing, check tags, consent choices, data stream and report filters first, then judge demand. If impressions rise, blended click-through rate falls and clicks rise, check query and position mix before rewriting titles. If clicks rise but business-confirmed contacts stay flat, check intent, market, mobile forms and qualification before editing copy. If an important canonical page is outside the index, check access, signals, material and discovery path on that exact URL, then log a recheck.
What each of the 9 groups counts
1. Organic traffic: Console clicks are not site sessions
Search Console reports visibility and clicks inside Google Search. GA4 reports observable activity after people reach your site. For session-based acquisition, use the session channel grouping in Traffic acquisition and select Organic Search; the first-user grouping in User acquisition answers a different question. Time zones, scope, consent, successful tag execution and canonical attribution can all create differences between the two totals. Do not force them to match. Locate landing pages, countries and devices driving the change, then verify measurement before investigating seasonality, availability, rankings or content.
2. Queries and average position: keep conditions fixed
Average position is an impression-based summary for the selected scope, not one live rank seen by every searcher. Third-party keyword totals rest on their own lists, markets and collection dates. Group queries by product family, application and buying question. Record language, country, device, branded versus non-branded queries, and relevant landing pages. Use Google click, impression and position definitions when reading the data. Open a representative query that fell or looks useful and ask whether the current result favours a product, tutorial, video or local page, then review whether your page performs that task.
3. Click-through rate: compare inside close groups only
Compare matched intent, position band, device, market and page before judging a title. New low-position impressions can pull a blended rate down while total clicks still rise. As a hypothetical teaching illustration with invented numbers only, 20 clicks from 1,000 impressions is 2%. That arithmetic shows the calculation and sets no target for brand, informational and buying queries. State what the page answers and describe only genuine page material. Do not add an unverified certificate, test claim or performance figure to win clicks.
4. Qualified contacts: name both sides of the ratio
A chat tap, completed form, download, basket action and paid order are separate outcomes. Test the actual event implementation, then keep tests, repeats, spam and genuine business enquiries on separate lines in your own log. GA4 session key event rate uses sessions containing a key event divided by sessions; events divided by sessions is a different measure when one visit holds several events. Label the calculation you use. Check mobile forms, contact routes and duplicate events. Query rows as a rule cannot be tied one by one to a single order.
5. Bounce and engagement: use your GA4 definition
In GA4, bounce is the share of sessions without engagement, the reverse of engagement share for the same slice. It is not the old single-page-session idea. Default engagement includes lasting more than 10 seconds, having a key event, or at least two page or screen views; check the actual property configuration. A single-page visit may answer the reader question. Duplicated view events from a setup fault can inflate engagement. Check capture first, then compare promise, answer and next step. No single rate by itself proves a search penalty.
6. Time and depth: read them with task completion
GA4 focus time records time with the page in front or the app in the foreground. Averages with different bases answer different questions. Needing four pages to find a specification is not necessarily better than finding it on one. Longer time can mean useful study or confusion. Interpret time, later pages and task completion together, then add the missing specification, condition, example or next step. Do not add headings or images by quota.
7. Indexing: start from the canonical list you want in
Keep a defined set of canonical pages intended for indexing and work important ones first. Login areas, parameter copies and pages held out by choice stay outside that aim, so covering every discoverable address is not a useful goal. Group Page indexing entries by reason and open samples. The inspection tool separates the stored copy from the live test. Requesting indexing does not force acceptance. Fix only the proven block on the checked path, 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.
8. Backlinks and referring domains: keep delivery apart from later movement
Link totals and referring-site totals are different dimensions. Discovery coverage, refresh timing and de-duplication vary by crawler, so one missing 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 address, target address, anchor, attribute, availability and check time against the delivery list. Going live, entering the index and later ranking movement stay three separate stages. Guangsuan's backlink combinations retain quality-and-quantity, complementary resource and layered building across its GPB, GNB and GMB lines, with counts, attributes, upkeep and indexing terms checked against the chosen plan.
9. Vendor scores: stay inside one tool
Moz Domain Authority is a vendor prediction, not a grade issued by Google. DA, Ahrefs DR and other tools come from different models and are not interchangeable units of link equity. Compare close peers inside the same tool and time window while still reading real links, target pages and search outcomes. Do not tune a vendor score apart from technical repair, page material and checked enquiries.
Decide: repair capture, eligibility, message or contact path
Use one finished export with identical filters. Open the moved address, then its query list with impressions, clicks and position. Keep intent, band, device and market fixed. Console steady, analytics near empty: repair tags, consent, streams and filters, then judge demand. Shows up, blended rate down, picks up: check query and position mix and compare narrow slices before title work. Clicks up, confirmed contacts flat: walk the product path, check intent, market, phone form and qualification, and read actual enquiry records. Key canonical outside the index: check access, signals, material and discovery path, repair the evidenced block, then log date, filters, owner and recheck. Record what changed, who owns it and what stays unverified. Keep missing data marked as missing.
What to bring to Guangsuan
For method detail, see Guangsuan's 9 SEO metrics guide. For whole-site scope across technical repair, content supply and links, see Guangsuan Google SEO service, where counts, attributes, upkeep and indexing terms are checked against the chosen plan. Guangsuan (光算) groups site work, content and external resources together. Bring site address, target country and language on separate lines, affected addresses, one finished Console export with filters, what changed and when, who can approve code or copy, and how your team qualifies an enquiry.
FAQ
Do flat impressions require a rewrite? No. Flat impressions mean the page is seldom offered for that 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 success? No. Longer time can mean careful study or confusion. Add the missing condition or next step and check whether the task was completed.