How to use a Righthand with Google Search Console

Quick answer

Use Righthand to prepare a Search Console page-query review grounded in your verified property's reported performance. Keep indexing questions separate from search-click observations.

Start with a reviewable deliverable, keeping Google Search Console as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Google documents Search Console's Performance report, including clicks and query or page views. See the official Google Search Console reference. Provider capabilities and Righthand's available tools are separate checks.

Use the owner's verified property export with search type, date range, dimensions, and filters. Preserve query and page scope rather than assuming one report covers all traffic. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: property, page, query, dates, search type, country, device, clicks, impressions, CTR, position. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Search performance does not prove a page was indexed throughout the whole period or caused a sale. Preserve filters and reporting limitations.

Illustrative first-run brief

Use the owner-provided Google Search Console snapshot or approved read-only view. Compare the supplied weekly page and query exports for ten approved URLs. Flag changes and missing rows, and draft follow-up questions. Do not request indexing or change the site. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the SEO owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A page with fewer clicks but similar impressions prompts a title or query-mix review, not a certainty that its ranking collapsed.

Match property, period, and search type with the original report before checking one page row. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Page totals and query totals may not reconcile exactly because of reporting aggregation and omitted data. Explain the limitation instead of inventing missing queries.

If totals differ between filtered and unfiltered reports, retain the filter definitions and request the intended scope. Do not “correct” a valid filtered total.

FAQ

What should the reviewer verify first?

Verify property, search type, window, country or device filters, and query/page dimensions. Clicks, impressions, and position describe different aspects of search activity.

How should a repeat run be scoped?

Keep property and filters consistent across runs. Record the latest available date and compare matched windows; do not treat incomplete recent data as a confirmed decline.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.