Review Desk Consult Pack: 9 SEO Counts to Confirm Before You Touch a Review
For Filmxa-style review editors: how to read 9 SEO metric groups in Search Console and GA4, separate counting problems from page problems, and pack a consult note before changing a review or asking for help.
Brand promotion: this article introduces Guangsuan's SEO guides and services for film editors.
You keep a weekly review slate live, then a title underperforms. The desk has two different jobs to choose between: amend the page, or repair how the reading was taken. This consult pack helps you tell those jobs apart and write down a note that a colleague or an outside team can repeat. For definitions, see Guangsuan's 9 SEO metrics guide.
What this pack is for and what Guangsuan does
This note fits an editor who maintains an archive of reviews, interviews and festival dispatches and must decide whether to edit copy, fix tracking, or request indexing work. It does not fit a decision about Filmxa's own business, and it makes no claim about this site's audience size or awards.
Guangsuan publishes method notes on measurement, indexing and links, and offers whole-site work across technical repair, content supply and outside resources. If you later ask for help, you will be asked for the same pack described below: address, market, affected pages, one finished export with filters, what changed and when, who can approve code or copy, and how your team recognises a genuine enquiry.
Write down one comparable frame before you open reports
Pick one site view, one search type, and one closed span, then keep that choice for every pull. Read handheld and desktop apart. Keep brand demand apart from non-brand demand. Note tongue, nation, device and the affected address on each file. Leave the still-running day outside the comparison and leave a blank row marked as blank instead of borrowing another site's figure.
When totals shift, first locate the address, nation and device behind the shift. A blended move often comes from a wider mix rather than worse copy, so narrow the slice before you judge a headline.
Counting lines: arrivals, queries, picks and contacts
Arrivals shown in Search versus visits seen on site
Console describes how often a page surfaced and was chosen inside Google Search. Analytics describes what could be observed after arrival. Clock zones, view scope, consent handling, tag firing and canonical assignment can pull those two totals apart, so do not force them to agree. If Console holds data while analytics sits near empty, restore tags, consent handling, data stream and report filters before you judge reader interest. A smaller organic share can also follow heavier paid spend.
Queries and mean position under fixed filters
Mean position summarises the view you picked on an impression basis. It is not one live rank seen by every searcher. Outside keyword totals rest on their own lists, markets and collection dates. Sort queries by film, director, festival and reader question, then ask whether the live result favours a review, an interview, a guide, video or another answer type. A page that answers another task will not win this task by headline tweaks alone.
Pick share read only inside close slices
Compare only matched intent, position band, device, market and page before you judge a headline. Added low-position shows can drag a blended share down while total picks still climb. As a hypothetical teaching illustration with invented numbers only, 20 picks from 1,000 shows shows the division. That line shows the arithmetic and sets no target for brand, information or buying tasks. State the genuine page answer and describe only real page material. Do not add an unverified certificate or performance figure to win picks.
Contacts with both sides named
A chat tap, finished form, newsletter signup, download and paid order are separate outcomes. Try the live event, then keep tests, repeats, spam and genuine contacts on separate lines in your own log. 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. For a review desk, keep review-page visits, signups from that review and membership records apart.
Behaviour and eligibility read without guessing
Bounce read with your own GA4 setting
In GA4, bounce means the share of visits without engagement, the reverse of engagement share for the same slice. 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. Verify capture first.
Focus time judged by task completion
Focus time records time with the page in front. Longer time can reflect careful study or confusion. Finding a detail on one page is not worse than needing four pages. Read time, later pages and task completion together, then add the missing condition, example or next step that unblocks the task rather than adding headings by quota.
Eligibility from a list you intend to keep
Keep a defined set of canonical addresses you intend to hold in the index and rank important ones inside it. Login areas, parameter copies and material held out by choice stay outside that aim, so covering every discoverable address is not useful. Group indexing entries by reason and open samples. Asking for indexing starts a process without forcing entry. A crawled-but-not-indexed note alone does not prove thin copy. Use canonical only for duplicate or highly similar material. Fix only the proven block on the checked path, such as accidental noindex, blocking, wrong canonical target, unavailable page or absent rendered material.
Outside counts: delivery 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. A Links report cannot stand in for a live indexing check of each source address. 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 are separate stages.
Moz's score is the vendor's own prediction, not Google's public grade. Scores from different vendors come from different models and are not interchangeable. 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.
Pack to send before you ask for help
Bring facts another person can repeat: site address, target nation and tongue stated separately, affected review 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 handling where analytics sits near empty while Console holds data. Record dates, filters, what changed, owner and what stays unverified. For whole-site scope across technical repair, content supply and links, see the Guangsuan Google SEO service, where counts and terms are checked against the chosen plan. For people-first checks, see Google guidance on creating helpful, reliable, people-first content.
Short checks before you act
Shows flat, should you rewrite? No. Flat shows mean the page is seldom offered for that query. Confirm eligibility, entry links and whether the page type fits what results favour first.
Blended share down, should you retitle? Not alone. Check whether new low-position queries widened the mix, then compare narrow slices before editing.
Longer reading, does it prove success? No. Longer time can reflect study or confusion. Add the missing condition or next step and check whether the task was completed.