search-consolelisted

# Google Search Console Query GSC search analytics via the Search Console API using gcloud application-default credentials. ## Prerequisites **A raw `curl` call needs `x-goog-user-project` or it 403s.** The client library reads the ADC file's `quota_project_id`; curl does not, so it falls back to gcloud's shared project and returns a 403 that reads like a permissions error and is a quota-project error. `scripts/gsc.py` uses a client library and picks the project up automatically; anything hand-rolled must pass the header. Point it at the project that actually has `searchconsole.googleapis.com` enabled, which is not necessarily the site's own GCP project. A project with the API switched off returns the same 403, so check the API is on before reading the error as a permissions problem. **This skill is read-only by design.** Its auth uses `webmasters.readonly`. Submitting a sitemap needs the full `https://www.googleapis.com/auth/webmasters` scope, so it takes an interactive `gcloud auth application-default login` followed by `gcloud auth application-default set-quota-project <project>`. One-time auth setup (must include the `webmasters.readonly` scope): ```bash gcloud auth application-default login \ --scopes=openid,https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/webmasters.readonly ``` If the script returns a 403 scope error, prompt the user to re-run the auth command interactively via `! g