Brand promotion: this article introduces Guangsuan's SEO measurement guidance for month-end reviews.
Short answer for a monthly close: these nine groups of metrics answer different questions, so a move in one number is evidence about that number only. Before you edit an analysis page, lock one comparable view — same site view, same search type, one finished date range without today, same query cluster, same page, same country and same device — then work in order: recording, then eligibility, then wording and enquiry route. For method detail, see Guangsuan's 9 SEO metrics guide. For whole-site scope across repair, content and links, see Guangsuan Google SEO service.
Start the close with one repeatable frame
Write the frame on the export itself: which view, which search type, which closed dates, which query cluster, which address, which country and which device. Keep brand demand separate from non-brand demand, and read phone separately from desktop. Keep a blank row marked as blank; do not fill it with another site's benchmark.
Search Console shows how often a page surfaced and was selected inside Google Search. GA4 shows what could be observed after arrival. A click recorded in Search Console does not equal a session recorded in GA4. Clock skew, view scope, consent handling, tag firing and canonical assignment can pull the two totals apart, so do not force them to agree. When Console holds rows while analytics is almost empty, restore tags, consent handling, data stream and report filters before you judge demand.
Session scope and first-user scope answer separate questions. Do not mix them when you pull organic acquisition. A smaller organic share after paid expansion does not by itself prove discovery failed.
What the nine groups actually count
1. Arrivals from search
Find the addresses, countries and devices behind the shift before you judge copy. Verify recording first, then consider season, availability, ranking or wording.
2. Query cover and mean position
Mean position is a show-weighted summary for the filters you picked, not one live rank every searcher saw. Outside keyword totals rest on their own lists, markets and collection dates. Sort queries by product, use and buying question, note tongue, nation, device and landing address, and use Google's click, impression and position definitions when you read the table. For a query that slipped, open live results and ask whether they favour a product, tutorial, video or local answer, then check whether your page serves that same job.
3. Selection share
Read share only inside matched intent, position band, device, market and page. Added low-position shows can drag a blended share down while total selections still climb. As a hypothetical teaching illustration with invented numbers only, 20 clicks from 1,000 impressions is 2%. That line shows arithmetic and sets no target for brand, research or buying tasks. State the genuine page answer and describe only real page material.
4. Contacts and ratios
A chat tap, finished form, download, basket move and paid order are separate outcomes. Try the live event, then keep tests, repeats, spam and genuine enquiries on separate lines. Name the ratio you use, because visits holding an event divided by visits differs from events divided by visits when one visit holds several events. Query rows as a rule cannot be tied one by one to a single order. Check phone forms, contact routes and repeated events together with business-confirmed contacts.
5. Bounce under your own GA4 setting
In GA4 bounce is the share of sessions that were not engaged, the opposite of engagement rate. It is not the old single-page idea. Usual engagement covers staying beyond a short threshold, holding a key event, or at least two views, but confirm the actual property setting. One answered question on a single page can still satisfy the reader, while repeated hits from a setup fault can inflate engagement. Check capture first.
6. Focus time and depth by task
Focus time records time with the page in front or the app in the foreground, with different averages using different bases. Finding a specification on one page is not worse than needing four pages. Longer time can reflect careful study or confusion. Read time, later pages and completion together, then add the missing specification, condition, example or next step. Do not add headings or images by quota.
7. Eligibility from a wanted list
Maintain a defined set of canonical pages intended for indexing and prioritise important pages within it. Login areas, parameter copies and material held out by choice stay outside that aim. Group 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 absent rendered material. A crawled-but-not-indexed note alone does not prove thin copy, and a correctly merged duplicate is not by itself a removal job. Use canonical only for duplicate or highly similar material.
8. Outside links kept apart from later movement
Total links and referring-site totals 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 address, target address, anchor, attribute, availability and check time against the delivery list. Going live, entering the index and later ranking better remain three separate stages.
9. Vendor marks kept inside one scale
Moz Domain Authority and other tools' metrics 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. Delivery terms for a Guangsuan product remain governed by that product's actual terms.
High shows, few picks: narrow the slice first
Open the moved address on one closed export, then open its query list with shows, picks and mean position together. Keep one query cluster, one page, one nation and one device in view. Tag new, continuing and off-task queries instead of sorting by rate alone.
- Shows flat: the page is seldom offered for that query. Confirm eligibility, entry links and whether the page type fits what results favour.
- Shows up, blended share down, picks up: review query and position mix before title work. Compare narrow slices with matched intent, band, device and market.
- Same narrow slice shows many shows with few picks and the shown wording misstates the genuine answer: revise the title or snippet-relevant passage to state the genuine answer.
Show counts in your file record how often your own pages surfaced. They are not total market size. For people-first checks, see Google guidance on creating helpful, reliable, people-first content.
Repair recording or edit the page
Use one closed file with identical filters. Record dates, filters, what changed, owner and what stays open.
- Console steady, analytics near empty: check tags, consent, streams and filters. Restore reliable capture, then judge demand.
- Shows up, blended share down, picks up: check mix. Compare close slices before title edits.
- Picks up, confirmed contacts flat: review intent, market, phone form and qualification. Walk the product path with real enquiry records.
- Key canonical outside the index: check access, signals, matter and discovery path on that exact address, including the exact robots rule path with user-agent, canonical target, stored copy against live test, availability and rendered material. Fix the proven block and log a recheck.
What to bring before asking Guangsuan for help
Bring facts another person can repeat: site address, target nation and tongue 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 where analytics sits near empty while Console holds data. This note uses hypothetical teaching numbers only, not a client case.
FAQ
Do flat shows require a rewrite? No. Confirm eligibility, entry links and whether the page type fits what results favour first.
Does a falling blended share force a new title? Not alone. Check whether new low-position queries widened the mix, then compare narrow slices.
Does longer reading prove success? No. Longer time can mean study or confusion. Add the missing condition or next step and check whether the task was completed.