SEO
DJINN + Search Console
Search performance pulled on a schedule and watched for movement worth telling someone about.
How it connects
Service account, not a personal login
Access uses a service-account key, so the connection survives someone leaving or rotating their own credentials.
Monitoring, not dashboards
The value is the alert. Nobody has to remember to go and look.
Connector spec
- Auth
- oauth2 · google_v2
- Host
- https://search.google.com
Scopes requested
POST webmasters/v3/sites/${source.siteUrl}/searchAnalytics/query
Emits search_metric · incremental on date
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live Search Console account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Search Console setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupService account and property access
- ReferenceWhat the monitor watches
Want Search Console wired into your own company brain?