9 SEO Metrics Explained Before You Rewrite a Landing Page
SaaS growth guide to 9 SEO metric definitions, GA4 and Search Console scope checks, and when to fix measurement before rewriting landing pages.
Brand promotion: this article introduces Guangsuan's SEO measurement guidance and services.
When pipeline is flat and a landing page looks weak, the choice is not automatically to rewrite. First settle what each number counts, then check whether the page could appear, then decide between copy changes and measurement repair. Guangsuan's 9 SEO metrics guide groups SEO into nine questions, and an improvement in one number is evidence about that number only.
Fix the comparison frame first
Use one site view, one search type, one finished date range, one query group, one page, one country, and one device for every export. Leave the unfinished current day outside the range. On each export, record language, country, device, branded versus non-branded queries, and the landing page involved. For people-first checks, see Google guidance on creating helpful, reliable, people-first content.
Which 9 metrics are defined and how they are calculated
1. Organic search traffic: clicks are not sessions
Search Console reports impressions and clicks inside Google Search. GA4 reports observable activity after people arrive. A Search Console click is therefore not a GA4 session. Time zones, scope, consent, successful tag execution and canonical attribution can all create differences, so do not force the two totals to match and do not apply a fixed tolerance to the gap. To find what moved, locate the landing pages, countries and devices driving the change. A smaller organic share can follow larger paid spend, so read share together with those splits.
2. Query coverage and rankings: keep observation conditions fixed
Average position is an impression-based summary for the selected scope, not one live rank seen by every searcher. Third-party ranking-keyword counts depend on their own lists, markets and collection dates. Group queries by product family, application and buying question. For a representative query that fell or looks promising, ask whether the ranking page type matches the task: does the current result favour a product, tutorial, video or local service, and does your page answer that task? Use Google's click, impression and position definitions when interpreting the data.
3. Click-through rate: compare only close groups
CTR is clicks divided by impressions, multiplied by 100%. As a hypothetical teaching illustration with invented numbers only, 20 clicks from 1,000 impressions is 2%. That arithmetic shows the calculation and is not a target for brand, informational and buying queries, which have different contexts. More low-position impressions can lower a blended rate while total clicks rise. Compare only matched intent, position band, device, market and page before judging a title. State what the page answers and describe only genuine page material.
4. Qualified leads and conversion: define both sides
A chat tap, completed form, download, basket action and paid order are different outcomes. Test the actual event implementation, then distinguish tests, duplicates, spam and genuine business enquiries in your operational records. GA4 session key event rate is sessions with the key event divided by sessions. Dividing event count by sessions gives a different measure when one session holds several events. Label the calculation you actually use. Review organic landing-page sessions, sessions with the intended event, and business-verified leads together, and check mobile forms, contact routes and duplicate events. Query rows as a rule cannot be joined one by one to a single order.
5. Bounce and engagement: use your GA4 definition
In GA4, bounce rate is the percentage of sessions that were not engaged, the opposite of engagement rate for the same scope. It is not the old single-page-session definition. Default engagement criteria include lasting more than 10 seconds, having 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 question, while duplicated page-view events can make engagement look artificially strong. Check measurement first, then compare the search promise with the actual answer, reading experience and usable next steps.
6. Engagement time and depth: relate them to the task
GA4 user engagement time measures time with the web page in focus or the app in the foreground. Average engagement time and average engagement time per session use different denominators. 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, subsequent pages and task completion together, then add the missing specification, condition, example or next step instead of adding headings by quota.
7. Indexing: start from the canonical pages you want indexed
Sites contain login pages, duplicate parameter URLs and material deliberately kept out of Search, so indexing every discoverable URL is not the goal. Maintain a defined set of canonical pages intended for indexing and prioritise important pages within it. Group Page indexing report entries by their reasons and inspect representative URLs. The inspection tool distinguishes the stored indexed copy from the current live test. Requesting indexing does not force acceptance. Fix evidenced blocks found on the checked path, such as accidental noindex directives, blocking, wrong canonical targets, unavailable pages and missing rendered content. A “Crawled — currently not indexed” notice alone does not diagnose short text, and a correctly consolidated duplicate is not automatically a deletion task. Use canonical only for duplicate or highly similar content.
8. Backlinks and referring domains: keep delivery apart from later movement
Link count and referring-domain count are different dimensions. Search Console and third-party crawlers have different discovery coverage, update schedules and deduplication rules, so 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, reconcile source URL, target URL, anchor, link attributes, availability and observation time against the delivery list, then review agreed indexing checks and subsequent search performance. Published, indexed and improved target-page rankings are separate milestones. Guangsuan's combinations keep distinct roles for GPB independent-site links, GNB natural links and large-scale construction, with quantities, attributes, maintenance and indexing terms checked against the selected product.
9. Authority scores: compare within the same tool
Moz Domain Authority is Moz's predictive metric, not a public score assigned by Google. DA, Ahrefs DR and other tools' metrics come from different models and are not interchangeable units of link equity. Compare a relevant peer set within the same tool and time period, while inspecting actual links, target pages and search outcomes. Do not optimise a third-party score apart from technical work, content and qualified enquiries.
What to verify in GA4 and Search Console before changing pages
Work in this order on one finished range: capture, eligibility, message, then enquiry handling. Open Pages to locate the address that moved, then open its query list with impressions, clicks and position together.
| Observation | First checks | Useful next action |
|---|---|---|
| Console stable, GA4 near zero | Tags, consent, data stream and report filters | Restore reliable capture before judging demand |
| Impressions up, blended rate down, clicks up | Query and position mix | Compare similar segments before rewriting titles |
| Clicks up, qualified leads flat | Intent, market, mobile forms and lead qualification | Walk the product-page journey and read actual enquiry records |
| Important canonical page not indexed | Access, indexing signals, content and discovery path on the exact URL | Fix the evidenced block and log date, filters, owner and recheck |
For message changes, change a title or snippet-relevant passage only when the same narrow slice shows many impressions with few clicks and the shown wording misstates the page answer. If the query asks for model, delivery, price or compatibility but the ranking page only explains ideas, add product or comparison material and an enquiry entry before wording tweaks.
When to fix measurement instead of pages
Fix measurement first when Console holds data but analytics is near empty, when event definitions are unclear, or when duplicated events inflate engagement. Confirm tags fired, consent handling, stream selection and filter scope before judging demand. Name the ratio in use and keep tests, repeats and spam apart from qualified contacts. Fix eligibility first when a key canonical is outside the index: check the exact robots rule path with user-agent, canonical target, availability and rendered material, then request a recheck and record what remains unverified. Keep missing data marked as missing instead of filling it with another benchmark.
What to bring for follow-up help
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 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.
FAQ
Do flat impressions require a rewrite? No. Flat impressions 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 reading time prove the page worked? No. Longer time can mean useful study or confusion. Add the missing condition or next step and check whether the task was completed.