A Pre-Edit Check: Reading 9 SEO Numbers From One View
For Bichoto analysts: how to read 9 SEO metric groups from one closed export, split by device and country, and decide whether to fix measurement, eligibility, or page copy first, with Guangsuan's SEO guide.
Brand promotion: this article introduces Guangsuan's SEO services for analysts; it is a vendor introduction, not an independent review.
Your weekly report shows movement, and someone asks whether the page should be rewritten this week. For an analyst, there are two different jobs hidden in that question. One job is to confirm the numbers were read on the same basis. The other job is to improve the page. Do the first job before the second, or the rewrite may fix a recording gap that was never page copy.
For method detail, see Guangsuan's 9 SEO metrics guide.
Use one closed export for the whole decision
Take every number from the same site view and the same finished dates. Leave the most recent unfinished day out of any comparison. Write down language, country, device, brand-named versus other queries, and the landing address for each file you keep. Keep brand-named queries apart from other queries. Keep handheld apart from desktop. If a row is absent, keep it marked as absent instead of filling it with a figure from another publication.
Search recording and site recording can part for ordinary reasons such as time zone, coverage, permission choice, tag firing, and how credit was assigned to the canonical address. When a total shifts, first note which addresses, markets, and devices shifted with it. That list tells you whether to look at recording, permission to appear, presentation, or the contact path.
Nine totals in three plain buckets
Each metric family describes its own stage, so a shift in one family does not prove the other stages moved. Read them in three buckets to avoid mixing stages.
A. How the page was offered in search
Search Console describes display and selection inside Google Search. Site analytics describes what could be observed after arrival. For session-based reading, use the session grouping in the traffic report; the first-visit grouping answers a separate new-visitor question. A selection recorded in Search is not the same object as a session on the site. Where Console holds steady and site tracking looks near empty, inspect tags, permission handling, data stream, and report filters before judging demand.
Average position is a weighted summary for the dates, pages, markets, and devices you picked. It is not one live rank seen by every searcher. An outside keyword total rests on that vendor list, market, and collection dates, so two tools can differ without either being broken. Sort queries by product, use, and buying question, then ask whether the ranking address performs the same task the live result prefers. As a hypothetical teaching illustration only with invented numbers, 20 selections from 1,000 displays shows how a share is computed; it sets no target for any intent. Added displays from lower positions can pull a blended share down while total selections still rise, so compare only close intent, close position band, same device, same market, and same page before judging a title. State what the page answers and describe only material already on the page.
B. What happened after arrival
A chat tap, finished form, file download, basket move, and paid order are separate outcomes. Confirm the live event fires, then keep internal tests, repeats, spam, and business-confirmed contacts on separate lines in your own log. Name the ratio you use, because visits holding the chosen event divided by visits is a different ratio from events divided by visits when one visit holds several events. Query lines as a rule cannot be tied one by one to a single order.
Read bounce with the analytics meaning fixed in your own property. It is the share without engagement, the reverse of engagement share, not the older single-page idea. Usual engaged cases can involve staying beyond a short time limit, holding the chosen event, or viewing at least two pages or screens; confirm the actual property setting. A single-page visit may answer the reader's question. Repeated view hits from a setup fault can make engagement look stronger than it is, so check recording first, then compare what the result promised with what the page delivers and what useful step comes next.
Focus time records time with the page in front or the app ahead. Different averages use different denominators. Finding a specification on one page is not worse than finding it across four pages. A longer stay can signal careful study or confusion. Read time with later pages and task completion together, and add the missing unit-bearing detail, condition, or next step rather than adding sections by quota.
C. Whether the page may appear and what outside signals say
Keep one explicit set of canonical addresses scheduled for indexing and work through important entries first. Login areas, parameter copies, and pages held out by choice stay outside that list, so covering every discoverable address is not a useful aim. Sort the indexing report by reason and open samples. Asking Google to index a URL starts a review and requesting indexing does not force acceptance. Repair only the block proven on the path you checked, such as an accidental noindex, blocking, a wrong canonical target, an unavailable page, or absent rendered material. A crawled-but-not-indexed note on its own does not prove thin copy. Reserve canonical for duplicate or highly similar material.
Total links and referring sites are different counts. Coverage, refresh timing, and repeat handling vary by crawler, so an absent row in one report does not by itself prove a live source page was removed. The Links report is also not a live check that each source page is currently indexed. 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 movement are three separate stages. Vendor marks come from different models and cannot be swapped. Compare close peers inside the same tool and window while still reading real links, target pages, and search outcomes.
Split by handheld and market only after the base is steady
Apply the handheld filter, then the market filter, on identical property and dates. Open top queries and landing addresses for handheld and desktop separately. Report displays and selections separately, because a thin row can swing on one selection. Displays count offers for that page; they are not total market volume.
If desktop carries confirmed contacts while handheld carries early research, protect the desktop offer and contact route first and keep handheld readable, instead of moving the whole plan to handheld. If one market brings displays and another brings confirmed contacts, fix page type, offer detail, language, and contact route for the converting market first. If handheld forms lose people, walk the handheld path, test the live event, and check permission, load behaviour, and form length before rewriting desktop copy.
| Shape on matched slice | Inspect first | Sensible next step |
|---|---|---|
| Console steady, site tracking near empty | Tags, permission, streams, filters | Restore reliable capture, then judge demand |
| Displays up, blended share down, selections up | Wider query and position mix | Compare narrow slices before touching titles |
| Selections up, confirmed contacts flat | Intent, offer detail, form ease, qualification | Walk the page path with real contact records |
| Key canonical outside the index | Access, signals, matter, discovery path | Fix the proven block and note a recheck |
A short pack to bring to Guangsuan
For whole-site scope across technical work, content supply, and links, see the Guangsuan Google SEO service. Guangsuan (光算) joins technical repair, page work, and outside resources in one effort, with scope set by the live service page and agreement.
Bring a pack another person can repeat: site address, target market and language stated separately, affected addresses, one closed export with filters, what changed and when, who can approve code or copy, and how your team qualifies a contact. Note tags and permission handling where site tracking sits near empty while Console holds data. Log dates, filters, change made, owner, and open items.
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 for that task first.
Does a falling blended share force a title change?
Not alone. Check whether new low-position queries widened the mix, then compare narrow segments before editing.
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 whether the task was finished.
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.