Specify the reporting question and authorization
Choose the property, date range, dimensions, filters, and search type needed for the decision. Confirm the executing account has access and that the project’s authorization is appropriate. Keep property identifiers and configuration separate from report output. Never ask a visitor to paste account passwords or private tokens into a public sheet.
- ✓ Document the reporting scope before requesting access.
- ✓ Check current official API and Apps Script setup instructions during implementation.
Make imports repeatable and traceable
Retrieve data in supported batches, handle pagination where applicable, and respect current service limits. Use a clear rule for replacing or appending a date range so retries do not double-count rows. Record query configuration and collection time. Search Console reporting has aggregation and coverage limitations; it should not be presented as a complete raw event log.
- ✓ Validate totals, date boundaries, and duplicate keys.
- ✓ Checkpoint long jobs and surface failures rather than writing partial success silently.
Connect the report to an action
Join exported evidence to page identifiers carefully, preserving canonical and redirect context. Use the result to investigate a specific change in discovery or performance. SearchGraph may support report-based workflows, but an Apps Script import and a native product integration are separate capabilities. Keep account ownership, trigger maintenance, and deletion procedures in the handoff.
- ✓ Preserve the raw import alongside transformed reporting tables.
- ✓ Test a small sample before scheduling repeated runs.