Integrations

Google Search Console

Connect Search Console to see Google index coverage on AI Readiness, seed prompts from your search queries, and let CiteCue submit its answer-page sitemap.

6 min read

Connecting Google Search Console lets CiteCue read how Google sees your site. This page covers what the connection adds, how to set it up, what it syncs, and how to fix it when it stops.

What connecting gives you

  • Google index coverage on AI Readiness, the SEO health tab under AI readiness: how many of your sitemap pages Google has indexed, and why the rest weren't, grouped by cause. Each cause becomes a fix listing the affected URLs. It shows up after your next scan.
  • Import from Search Console on the Prompts page: queries your site appeared for in Google, as prompt seeds (see below).
  • Answer-page sitemap submission: CiteCue submits https://example.com/citecue-sitemap.xml (on your own domain) to your property, so Google can find the answer pages AI Auto-Fix publishes.

The sitemap is submitted only when the connection has write access, Help AI and search engines find your answer pages is on, a check in the last 30 days (Verify in the CDN modal, or Check installation on a plugin card) confirmed your delivery layer serves that sitemap, at least one answer page is published, and the list of answer pages has changed since the last submission. CiteCue tries at most once every 24 hours. The card says where it stands, for example "Waiting for installation verification." or "Search Console reported: …" with Google's reason.

Who can connect

A project admin or the organization owner. Connecting, choosing a property, Sync now, Disconnect and importing queries as prompts all need that role.

Connect Search Console

  1. Open Integrations in your project. Under Connectors, find the Search Console card and click Connect.
  2. On Google's consent screen, choose a Google account with access to your site's property, and approve.
  3. Back on Integrations, pick your property under Search Console site and click Save.
  4. The first sync starts straight away. The card then links to See index issues on AI Readiness.

The picker only lists properties that cover your project's domain: Domain properties (sc-domain:example.com) for your domain or a parent of it, and URL-prefix properties on your domain or a subdomain. Each option shows the permission level Google reports for your account.

What CiteCue asks Google for

One consent grants both scopes, with offline access so syncs run without you:

Scope Used for
webmasters.readonly (read) URL Inspection results and the search query report.
webmasters (read and write) Submitting CiteCue's answer-page sitemap, nothing else.

Connections made before the write scope existed are read-only. Their card says "Reconnect Search Console to let Citecue submit this sitemap." with a Reconnect link that adds it.

What syncs, and how often

Each project syncs once a day, and Sync now starts one immediately. The card shows "Last synced … · next …".

  • Index status. Each sync asks Google's URL Inspection about up to 50 pages: your homepage every time, then the sitemap pages inspected longest ago, never-inspected ones first. CiteCue reads up to 200 page URLs from your sitemap, so coverage builds over several days, then refreshes oldest-first. A sync stops inspecting after 90 seconds; skipped pages go first next time.
  • Search queries. The report covers 28 days, ending 3 days before the sync because Google keeps revising recent days. CiteCue reads up to 5,000 rows and keeps the 500 queries with the most impressions, replacing the previous set.

Import from Search Console

On the Prompts page, open New Prompt → Import from Search Console. The menu is shown to project admins only.

The table lists Query, Impressions, Clicks and Avg position, and a Question badge marks queries already phrased as questions. CiteCue drops navigational searches (your brand name alone, or with words like "login"), merges similar phrasings and adds up their impressions, and hides queries under 10 impressions and queries you already track. Up to 40 candidates are shown.

Select queries, choose Target platforms, then:

  • Import {n} as-is keeps the exact wording, with no AI involved. A query needs at least 3 characters to stand as a prompt.
  • Rewrite {n} with AI turns keyword phrasing into a natural question.

Both open a review where you can edit each prompt, its topic and tags, turn on Import as disabled, and save. Imported prompts show Search in the Source column.

Empty state Meaning
Search Console isn't connected Connect it first (Go to Integrations).
No query data yet No sync has stored queries yet. Wait for the daily sync or use Sync now.
You've imported every usable query Every candidate is already a prompt.
No usable queries in this window Every query was a brand search or had too few impressions.
Search Console prompt seeding is turned off Switched off platform-wide. Other ways of adding prompts still work.

Card states

Badge What the card shows What to do
Not connected Connect Connect it.
Not connected A Search Console site picker Choose a property and Save.
Connected Property, Google account, sync times, Sync now, Disconnect Nothing.
Needs reconnect "Google access expired or was revoked — reconnect to resume syncing." Reconnect and approve again.

Use your own Google OAuth client

By default the connection uses CiteCue's shared Google app, as the row under the connector cards says. Click Use your own OAuth client to open the Google OAuth client modal, then Use your own credentials. Register the Callback URL to register as a redirect URI on an OAuth client in Google Cloud console, enable the Search Console API, enter the Client ID and Client secret, click Save, then reconnect.

Disconnect

Disconnect appears on a connected card only; a card that needs reconnecting has to be reconnected first. Disconnecting deletes the index status and query data CiteCue synced. Prompts you already imported stay. When nothing else in the project uses the Google connection, CiteCue also asks Google to revoke its access. Your own saved OAuth client is kept.

Troubleshooting

Message What to do
You need admin access to connect Google. Ask a project admin or the owner.
You cancelled the Google consent screen. Click Connect again and approve.
No Search Console site covering example.com found for this Google account. Verify a property for your domain in Search Console, or connect a Google account that has one.
This Google account no longer has permission for the selected property. Check its access in Google, then sync again. Restore the account's access, then Sync now.
The selected property no longer exists in this Google account. Pick a different one. Disconnect, then connect again and pick a current property.
Still running — it'll finish in the background. Click Check again later.

A message ending "The next sync will retry automatically." clears on its own.

Next steps

Search Console supplies indexing evidence; connecting it does not enable publishing fixes. Publishing connection messages in the fix queue refer to a supported site plugin or delivery connection separately.