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与数字营销

What 9 SEO Metrics Mean Before You Change a Page

An analyst briefing that defines 9 SEO metric groups, separates definitions from diagnosis, and shows when to repair measurement or indexing before rewriting a page.

Bichoto Blog for Bichoto Blog SEO与数字营销

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

Short answer with a condition: the nine metric groups answer different questions. A move in one number is evidence about that number only. Before rewriting copy, lock one finished date range, one property view, search type, query group, page address, country and device, then read capture, eligibility and page task in that order. For method detail, see Guangsuan's 9 SEO metrics guide.

What each of the 9 metrics actually measures

Use one frozen scope for every check below. Note language, brand against non-brand, landing page, country and device on each export. Leave an unfinished day out of the comparison.

1. Organic traffic: Search shows against site sessions

Search Console shows impressions and clicks in Google Search. GA4 measures observable behaviour after arrival. A Search Console click is not a GA4 session. Time zones, scope, consent, tag execution and canonical attribution can create differences between the two totals. When Console is steady and GA4 is near empty, repair tags, consent handling, data stream and report filters before judging demand. Then list which landing pages, countries and devices moved.

2. Query coverage and average position

Average position is a show-weighted summary for the view selected, not one live rank every searcher saw. Outside keyword totals depend on that vendor list and collection dates. Group queries by product family, application and buying question. For a representative query, ask whether current results favour a product, tutorial, video or local answer, then ask whether your page serves that same task.

3. Click-through rate inside close segments

Compare click-through rate only inside matched intent, position band, device, market and page. Added low-position shows can pull a blended rate down while total clicks rise. As a hypothetical teaching illustration only, 20 selections from 1,000 shows is arithmetic for 2%. That line shows the maths and is not a target for every intent. Edit a title or snippet-relevant passage only when the same narrow segment shows many shows with few selections and the shown title misstates the page answer. Describe only genuine page material.

4. Qualified leads and conversion ratios

A chat tap, finished form, file download, basket move and paid order are separate outcomes. Test the live event, then separate tests, repeats, spam and business-confirmed contacts in your own log. Sessions holding the event divided by sessions is different from events divided by sessions when one visit holds several events. Label the ratio in use. Review landing-page sessions, sessions with the intended event and business-verified leads together. Search query rows as a rule cannot be tied one by one to a single order.

5. Bounce and engagement rate under GA4 rules

In GA4, bounce is the share of sessions without engagement, the reverse of engagement share for the same slice. Confirm the actual property setting. One answered question on a single page can still satisfy the reader, while duplicated view hits from a setup fault can inflate engagement. Check capture first, then compare the search promise with the delivered answer and next step.

6. Engagement time and depth against the task

GA4 focus time records time with the page in front or the app in the foreground. Longer time can signal careful study or confusion. Finding a specification on one page is not worse than needing four pages. Read time with later pages and task completion together, then add the absent specification, condition, worked check or next step.

7. Indexing from a canonical list

Maintain a defined list of canonical pages intended for indexing and work important entries first. Login pages, parameter copies and material held out by choice stay outside that list. Group indexing report entries by reason and open samples. Inspection separates the stored copy from the live test. A crawled but currently not indexed note alone does not prove thin copy. A correctly merged duplicate is not by itself a removal job. Use canonical only for duplicate or highly similar material. Where access is in doubt, check the exact robots rule path with user-agent, then repair only the block proven on that path, for example accidental noindex, blocking, wrong canonical target, unavailable page or absent rendered material.

8. Backlinks and referring domains apart from later movement

Total links and referring sites are different counts. Coverage, refresh timing and de-duplication differ across crawlers, so one absent row does not prove a live link vanished. Google's Links report is not a current indexing test for each source page. Where outside help is used, match source address, target address, anchor, attribute, availability and check time against the delivery list. Going live, becoming indexed and later movement remain three separate stages.

9. Third-party scores inside one tool

Scores from different vendors come from different models and cannot be swapped. 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.

Definitions are not the same as diagnosis

A definition states what is counted on top and below and which window makes it comparable. A diagnosis opens the moved address, its query list with shows, selections and position, and the live result or inspection record on identical filters. An improvement action changes only the layer proven by that diagnosis: capture, eligibility, presentation, contact path or outside resources. Record dates, filters, what changed, owner and what stays open. Keep absent data marked as absent instead of filling it with another benchmark.

Change the page or repair measurement first

Observation on matched scopeCheck firstSensible next move
Console steady, analytics near emptyTags, consent, streams, filtersRestore reliable capture, then judge demand
Shows up, blended rate down, picks upQuery and position mixCompare narrow segments before rewriting titles
Picks up, confirmed contacts flatIntent, market, mobile form, qualificationWalk the product path and read actual enquiry records
Key canonical outside the indexAccess, signals, material, discovery pathFix the proven block and log a recheck

Impressions count presentations in Search under the filters picked. They do not count market-wide demand, reads of your title or orders. If the query asks for model, delivery or compatibility and the ranking address only explains ideas, the wrong page type is ranking. Add product or comparison material and an enquiry entry before wording tweaks. For whole-site scope across technical work, content supply and links, see Guangsuan Google SEO service. For people-first checks, see Google guidance on creating helpful, reliable, people-first content.

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 for that task 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 before editing.

Does longer focus 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 completed.

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