Connect Google Search Console
Let AXO read search reports for one Search Console property.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
search_console_site_url | Exact property string, such as sc-domain:example.com or https://www.example.com/. |
Connect
Open Integrations, find Google Search Console, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Save the exact property in the connector.
- Use Connect Google account and authorize a user who can read the selected property.
- Ask AXO for search queries or page performance for that property.
Verify the result
The check reads the selected property. It does not change Search Console.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
A URL-prefix property and a domain property are different bindings. Correct the property string or grant the Google user access, then reconnect.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Provider reference: Search Console authorization scopes. Reviewed October 2026.
Next: create an event-triggered action, or implement a webhook receiver.