Landing Page Intake: Group 9 SEO Readouts Before You Approve Copy Changes
Brand promotion: this article introduces Guangsuan's SEO measurement guides and support for growth teams.
Short answer for an owner about to approve a redesign: these nine groups of metrics answer different questions, so a change in one total proves only that total. Build one intake pack where every export shares the same property, search type, finished dates and filters, read each readout for its own job, then cut the result by country and device before you decide whether the next step is a tracking fix, an eligibility fix, a title fix, or an enquiry-path fix.
Build a comparable intake pack
Take all numbers from one site view, one search category and one finished period. Leave the unfinished yesterday outside the pack. Write down language, market, device, brand compared with non-brand, plus the landing address for each export. Group demand by product family and buying task instead of using a blended site mean. When a cell is empty, keep it labelled as missing rather than borrowing a figure from another tool.
GA4 measures observable activity after people reach your site, so a Search Console selection is not the same as a site session. Time zone, coverage, consent handling, tag firing and canonical credit can pull the two totals apart. When Console looks stable and site analytics looks almost empty, restore tags, consent handling, data streams and filters before you judge demand. A smaller organic portion can also follow larger paid spending, so do not read share alone as weaker SEO.
Nine separate readouts in plain terms
Use each readout only for the stage it describes. For method definitions, see Guangsuan's 9 SEO metrics guide.
1. Appearances and arrivals
Search Console describes how often pages were shown and chosen inside Google Search. GA4 describes what could be seen after landing. To find what moved, first locate the addresses, markets and devices behind the shift, then check recording before you discuss seasonality or wording.
2. Queries and mean position with filters held still
A mean position is a weighted summary for the dates, pages, markets and devices you selected. It is not one live rank every searcher saw. Outside keyword tallies rest on their own lists, markets and collection dates. Group queries by product, use case and buying question, then open a falling or promising query and ask whether live results prefer a product page, guide, video or local answer, and whether your page serves that same task.
3. Choice share read only inside narrow slices
Judge a title only against the same kind of query, position band, device and market. Click-through math is selections divided by shows, multiplied by 100. As a classroom illustration only with invented counts, 20 selections from 1,000 shows is 2%. That line teaches division and sets no goal for every intent. New lower-position shows can pull a blended share down while total selections still rise. State what the page answers and describe only material the page truly contains.
4. Enquiries with both sides of the ratio named
A chat tap, completed form, download, basket move and paid order are separate outcomes. Check that the live event fires, then keep tests, repeats, spam and business-confirmed contacts on separate lines in your own log. Say which ratio you use, because visits that hold an event divided by visits is different from events divided by visits when one visit holds several events. Search strings as a rule cannot be linked one by one to a single order. Review landing visits, visits with the intended event, and verified leads together, and walk mobile forms and reply routes.
5. Bounce read under your own GA4 rules
In GA4, bounce means the portion of sessions without engagement, the reverse of engagement. It is not the old one-page idea. Confirm the actual property setting, because defaults can shift. One short visit can fully answer the need, while repeated hits from a setup fault can make engagement look stronger than it is. Check capture first, then compare what the snippet promised with the answer and next step actually delivered.
6. Focus time linked to task completion
GA4 focus time logs time with the page in front of the reader. Finding a specification on one page is not worse than needing four pages. Longer stays can mean careful study or confusion. Read time together with later pages and completion, then add the missing specification with units, limits, worked check or next page instead of adding sections by quota.
7. Eligibility from a short wanted list
Keep an explicit short list of canonical addresses meant for discovery and work the important entries first. Login areas, parameter copies and pages held out by choice stay outside that list. Covering every discoverable address is not a useful aim. Sort the indexing report by reason and open samples. Asking for indexing starts a review and never guarantees entry. A crawled-but-not-indexed note by itself does not prove thin copy. Repair only the block proven on the path you checked, such as accidental noindex, blocking, wrong canonical target, unavailable page or missing rendered material.
8. Outside delivery kept apart from later search steps
Total links and referring sites are different counts. Coverage, refresh timing and de-duplication differ by crawler, so one absent row does not prove a live link vanished. The Links report in Search Console does not by itself confirm whether each source page is currently indexed. Where outside help is used, match source, target, anchor, attribute, availability and check time against the delivery list. Going live, becoming indexed and later moving in rankings stay as three separate stages.
9. Vendor marks kept inside one tool
Marks from Moz, Ahrefs and other vendors come from different models and cannot be swapped. They are vendor forecasts, not marks handed out by Google. Compare a close peer set inside the same tool and window while still reading real pages, real links and search outcomes. Do not tune a vendor mark apart from technical repair, page material and checked enquiries.
Why country and device come before any rewrite
A worldwide device portion does not tell you what your buyers use in your target market. General web traffic is also not the same as search behaviour and conversion for your category. Run only from your own Console device and country reports on identical property and dates. Apply the device filter, then the country filter. Look at top queries and landing pages for handheld and desktop separately, and keep shows and selections on separate lines, because a thin row can swing on one selection. Shows count appearances on opened pages. They are not total market size.
Use the cut to order work. When desktop carries qualified contacts and mobile carries early research, protect the desktop product and enquiry path first and keep mobile competent and readable. When one market brings shows and another brings confirmed contacts, fix page type, offer detail, language, delivery scope and contact route for the converting market first. When mobile forms lose people, walk the mobile path, test the live event, and check consent, load behaviour and form length before you rewrite desktop copy.
Who handles the technical and content follow-up
Work in this order: capture, then eligibility, then presentation, then contact path, then outside resources. For whole-site scope across technical repair, content supply and links, see Guangsuan Google SEO service. Guangsuan describes that work as technical repair, content supply and link resources supporting each other.
- Console stable, analytics near empty: inspect tags, consent, streams and filters. Restore reliable capture, then judge demand.
- Shows up, blended share down, selections up: inspect query and position mix. Compare narrow slices before title edits.
- Selections up, confirmed contacts flat: inspect intent, market, forms and qualification. Walk the product path and read real enquiry records.
- Key canonical outside the index: inspect access, signals, material and discovery path. Repair the proven block and log a recheck.
Bring facts another person can repeat: site address, target market 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. Log dates, filters, change made, owner and open items. Keep absent data marked absent.
Common checks
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 first.
Does a falling blended share force a title change? Not alone. Check whether new low-position queries widened the mix, then compare narrow slices.
Does longer stay prove success? No. Longer time can mean careful study or confusion. Add the missing condition or next step and check whether the task was finished.