Google Search Console

Your first report

Find a page worth improving.

Start with a page people already find in Google. Ask your agent to read its search data, then compare the queries with what the page actually helps a visitor do.

Connect the property you want to measure

1. Enable the Search Console API in the Google Cloud project used for your credentials. StackOS supports Google OAuth and service-account connections. Google's authorization guide covers the API setup.
2. In StackOS, choose Read only for reports or Read and submit sitemaps for submission access. These request the webmasters.readonly and webmasters scopes respectively. Changing an existing read-only connection needs fresh Google consent for OAuth, or a new token with the full scope for a service account. StackOS handles the service-account token.
3. Give the connected account access to the site in Search Console. Restricted users can read performance data; submitting a sitemap requires an owner or full user. For a service account, add the client_email from its JSON key under Settings → Users and permissions. Google's property permissions are separate from the connection's scope.
4. Add the account through your StackOS project's Connections page and ask your agent to confirm the available properties. Keep credentials in StackOS. If your AI client is not connected yet, follow the client setup guide first.

Ask for one bounded report

Replace the example property and dates with a property you can access and a complete reporting period.

For https://example.com/, show Web search performance from August 29 through September 25, 2026, inclusive, using final data. List pages with clicks, impressions, CTR and average position. Then show query rows for one page we could improve. State the filters and any limits on the returned rows. Read only; do not change the site.

Search Console reports these dates in Pacific Time. Its Search Analytics API returns top rows and may omit other data, so an absent row is not proof of zero traffic.

Four clicks from 200 impressions gives a 2% CTR. That alone does not tell you what to change. If the query rows concern connecting a client, read the page for a missing setup step or an unclear success check. Improve that gap if you find it. Keep the URL and useful content, then compare the same page and reporting scope after enough new data has accumulated.

The content refresh workflow can carry that diagnosis into reviewed changes and later measurement. A small report is a starting point for investigation; it does not establish a cause or promise better rankings.

Submit the sitemap after a site update

StackOS 2.1.31 can submit or resubmit an existing sitemap URL. First publish your changes and check that the sitemap includes the pages you want Google to discover. Then replace the property and sitemap URLs in this request:

For https://example.com/, submit https://example.com/sitemap.xml to Search Console. After submission succeeds, read its sitemap record and report when Google last downloaded it, plus any warnings or errors.

Sitemap submission tells Google where to find the sitemap; it does not edit the file. A successful result confirms submission. The follow-up sitemap record can show that Google fetched it. Neither result proves that Google indexed the listed pages.

Batch independent requests

When you have several checks, ask your agent to group property listings, performance queries, sitemap records or URL inspections into a read batch using one connected account. Sitemap submissions use a separate write batch. Each batch supports up to 1,000 requests.

Google counts each request against quota and may run them in any order. Keep dependent work separate, such as submitting a sitemap and then checking its new record. Ask for each item's result. If part of a batch fails, keep the successful results and inspect uncertain submissions before deciding what to retry.

Check what Google has indexed

Google's URL Inspection API reports on the indexed version of a URL. Use it to investigate Google's recorded status after an update. It does not test the live page or request indexing for an individual article.