Integration guide
Google Search Console
Review owned-site search visibility.
Use this page to plan Google Search Console with NOGL. Confirm source coverage, customer authorisation and the delivery method before relying on a connection.
Start with a retail decision
Choose the review
Compare product-page visibility with the range under review.
Make the evidence comparable
Confirm property ownership, reporting lag and aggregation before interpreting a change.
Data scope to agree
These are planning fields, not a guarantee that every field is exposed or connected. Begin with the smallest useful sample.
| Proposed fields | Operation | Access boundary |
|---|---|---|
| Date · page or query grouping · country · device · aggregate impressions and clicks | Read an agreed sample | Confirm permissions and field availability before setup |
Before you begin
- Name the business owner and the person who can approve source access.
- Choose one market, a small sample and a concrete review question.
- Agree record IDs, date range, currency, privacy boundaries and retention.
From scope to a reviewed connection
01
Plan
Agree the fields, direction, delivery method and success criteria.
02
Authorise
Confirm the owner and permissions through the agreed secure setup process.
03
Validate
Compare a small sample with the source; check missing rows, duplicates and timestamps.
04
Review health
Agree a freshness threshold, failure contact and how to pause or revoke access.
Limits & support
Search visibility is not sales. Account data needs owner-approved access or an agreed export.
Do not send passwords, API keys or customer records through the contact form.