Google Search Console and indexing

Search Console brings your Google Search Console reports into the selected Project environment. It shows your own search impressions, clicks, click-through rate and average position, separately from third-party research estimates. Its tabs are Performance, Pages & queries, Indexing, All pages, Sitemaps and Settings; the header shows the connected property and how recent its search data is.

Connect the right property

1. Confirm the website URL for the intended Project environment.
2. Open Search Console and start setup in Settings. An Organization owner or administrator can connect a Google account or reuse the Organization's existing Google access.
3. Choose a Search Console property that covers this website and save the connection.
4. Check the connection state and report freshness before reading the results.

Signing in to SiteOS with Google does not grant Search Console access. The connection needs separate consent and access to the selected property. If a property is missing, check the Google account's permissions and refresh the available properties. A reconnect prompt or mismatched website needs attention before reports can update.

Each environment has its own property binding. Changing a website or connecting another property does not make an old report current for the new target.

After connection, SiteOS syncs finalized Search Console data in the background every day. Settings → Sync now requests an update sooner, and Change property selects another property. A failed sync keeps the last successful report visible.

Read search performance

In Performance, choose a date range and, when useful, a comparison period. Explore Queries, Pages, Countries and Devices; use filters to narrow the question. Open a row for more detail.

Pages & queries compares the latest 28 days with the previous 28 days for your pages and queries. Show pages With findings from your latest site audit, or pages whose Clicks declined, and sort by clicks, click decline or impressions. A finding next to a decline does not prove that it caused the decline. Opportunities lists pages that lost a significant number of clicks, ranked with your other next steps. Page details in Site Audit also show each page's Google clicks, impressions and position.

The report shows its saved date selection and freshness. Google data has its own reporting delay, and date ranges use Pacific Time. Missing rows are not automatically measured zeros. Average position and click-through rate describe the selected Google Search evidence, not conversions or revenue.

Saved reports and their exports do not consume SEO research credits. For visits, events and conversions, use Analytics, which also supports a separate Google Analytics connection. Saved Google queries can also become monitored questions in AI Visibility.

Check Google indexing

Open Search Console → Indexing, All pages, or Site Audit → Pages → All known pages, and choose Discover & check pages. SiteOS collects known public URLs from sitemaps, saved crawls and Search Console search reports, then requests inspection evidence from Google. Progress continues in background activity if you leave the page.

Inspect the result for a page: indexed, not indexed, not checked and unavailable remain different states. Details include Google's reason, available crawl and canonical information, and when SiteOS last checked it. HTML noindex findings and Google indexing verdicts are separate evidence.

Indexing opens with an overview: indexed and not indexed pages, a daily history and Why pages aren't indexed. Google's reasons are grouped into issues to fix on your site, Google's own choices (crawled or discovered but not indexed) and expected exclusions such as redirects. For each reason, On your site now compares Google's last crawl with your latest SiteOS audit, for example a page Google saw as 404 that now redirects. When every audited page of a reason is fixed, Validate opens the Page indexing report in Search Console: Google lets you start validation only there.

After you press Validate fix in Search Console, open the reason in SiteOS and choose I started validation. SiteOS then re-inspects the reason's pages every day and shows Google's verdict for each one: Confirmed once Google recrawled it without the problem, Waiting for recrawl, or Still failing. Validation in progress summarizes each tracked reason until every page is confirmed; Stop tracking ends it. This follows Google's per-page verdicts; Search Console's own validation status remains in Search Console.

All pages lists every known page with the same groups: filter to pages to fix, Google's choices or expected exclusions, or to one Google reason.

The inventory covers known URLs within discovery limits; it is not a list of every URL Google knows. A page with no search clicks can still be indexed, and a missing inspection is not a negative verdict. The Project's Sitemap can highlight the same Google index status for each page.

Refresh or submit a sitemap

Use Refresh statuses for new inspection evidence, or enable Settings → Refresh daily when you want recurring checks. Google allows 2,000 inspections per property each day, so daily checks follow Inspection priority: pages in a validation every day, pages with search clicks every three days and other pages weekly. Settings shows how many pages each tier has and how many inspections SiteOS used in the last 24 hours. Google quotas can defer work; progress shows checked and pending pages rather than claiming completion early. A failed refresh preserves the last successful result with its date.

Sitemaps lists the sitemaps Google reads and the known pages missing from all of them; adding those pages is the quickest way to get them discovered. Submit sitemap is a separate explicit action and may request additional Google consent. An accepted sitemap helps discovery; it does not prove that any URL was indexed. For an individual indexing request, use Open in Search Console and request it there. SiteOS does not automatically submit ordinary pages for indexing.

For a technical check of your page's robots, canonical or sitemap signals, use Site Audit.