CiteFoundry Docs
Open dashboard

Google Search Console

Connect GSC to ingest real organic queries into your prompt list. Setup, scopes, troubleshooting.

The Google Search Console (GSC) integration pulls real organic search queries from a verified property into the prompt-ingestion flow. It’s the single fastest way to seed a project with prompts that match what your customers actually search.

What it unlocks

  • Ingest GSC queries with impressions, clicks, average position, and date range filters.
  • Filter to a single country or aggregate globally.
  • A “strict” toggle to drop branded queries (so you don’t end up with a prompt list full of your own name).
  • Pin a default country per project so subsequent pulls stay consistent.

The integration is read-only — we never write to your GSC property.

Prerequisites

  • A Google account with Owner or Full access to the GSC property you want to pull from. Restricted users can authorize but won’t see queries.
  • Access to your project’s Settings → Integrations page.

Connecting

  1. Open Settings → Integrations in the dashboard.
  2. Find Google Search Console in the integration list and click Connect.
  3. You’ll be redirected to Google to authorize. The scope requested is https://www.googleapis.com/auth/webmasters.readonly — read-only access to your search properties.
  4. Approve and you’ll be redirected back to the dashboard. The integration card now shows Connected with the connected Google account.

Pulling queries

Once connected:

  1. Go to Prompts → Ingest → Google Search Console.
  2. Pick a property from the dropdown (we list every property the authorizing account has access to).
  3. Optionally pick a country, a date range, and a minimum impressions threshold.
  4. Toggle Strict on if you want to drop queries that contain your brand name (recommended for first imports).
  5. Pull kicks off an ingestion job. You’ll see candidate queries appear as the job runs.

Review the candidates, accept the good ones, and discard the rest. Accepted candidates become live prompts on the next save.

Pinning a country

Once you’ve found the country/property combination that works for your project, you can pin it as the default. Subsequent pulls (and the Pull again action on the drafts page) will use the pinned filters unless overridden.

Refresh, disconnect, expiry

  • Tokens are refreshed automatically before each pull. You don’t need to do anything.
  • Disconnect at any time from Settings → Integrations. The token is revoked at Google’s end immediately.
  • If you change Google passwords or revoke CiteFoundry from your Google account directly, the next pull will fail with a clear reconnect prompt.

Troubleshooting

  • “Property not found” — the authorizing account doesn’t have access. Make sure you’re authorizing with an account that has Owner or Full access to the property in GSC’s user settings.
  • “No queries returned” — check that the date range overlaps with a period that has impressions, and that your minimum-impressions threshold isn’t filtering everything out.
  • Country dropdown is empty — the property has no snapshot data yet for the chosen date range. Try a wider range or omit the country filter.
  • “This app is blocked” during consent — Workspace admin needs to allow-list CiteFoundry.

API

  • POST /v1/integrations/google-search-console/authorize — returns a Google OAuth URL.
  • GET /v1/integrations/google-search-console/properties — list properties accessible to the connected account.
  • POST /v1/projects/{projectId}/prompt-sources/gsc/start — start an ingestion job.
  • DELETE /v1/integrations/google-search-console — disconnect.