> Portal Navigation: > > - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version. > - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages). > - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`). > - Top-level index of all portals: https://dev.wix.com/docs/llms.txt > - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt ## Resource: Sample Flows ## Article: Sample Flows ## Article Link: https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/sample-flows.md ## Article Content: # GSC Site Readiness: Sample Flows This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation. ## Set up a site in Google Search Console A site owner wants their site verified, added to Google Search Console, submitting its sitemap, and indexed. Your app clears the readiness blockers first, then walks the site through the remaining setup steps. > **Prerequisite:** Connect a Google account to the site with the [GSC Connection API](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/connection-v1/introduction.md), and wait until the connection's status is `VALID`. To set up a site: 1. Call [Get Site Readiness](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/get-site-readiness.md). If `status` is `READY`, the site's connection and ownership verification are in place, so continue from step 4. 1. If `status` is `NOT_READY`, act on the returned `blockingReason`: - `SITE_OWNER_NOT_VERIFIED`: call [Verify Site](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/verify-site.md). Verification runs synchronously against Google, so allow up to a minute. If the call fails with `FAILED_PRECONDITION`, resolve the reported problem first: publish the site, connect a domain, or allow search-engine indexing. - `TOKEN_INVALID`: the stored Google credentials stopped working. Reconnect the Google account with the [GSC Connection API](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/connection-v1/introduction.md). - `DOMAIN_MISSING`: Google Search Console setup needs a connected domain. Have the site owner connect one before continuing. - `SITE_NOT_CREATED`: the site doesn't exist yet. Have the site owner create and publish it before continuing. - Any other value: treat the site as not ready, and don't assume a next action. New blocking reasons can be added over time. 1. Call [Get Site Readiness](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/get-site-readiness.md) again after each successful action, and repeat until `status` is `READY`. Read the current `blockingReason` each time instead of reusing an earlier one, because a response reports only the first step that's still blocking. 1. Call [Add Site](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/add-site.md) to add the site as a property in the connected account's Search Console, then call [Submit Sitemap](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/submit-sitemap.md). Wix generates and hosts the sitemap and submits its URL to the property. Google processes sitemaps asynchronously, so check the processing state later with [List Sitemaps](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/list-sitemaps.md). 1. Call [Request Site Indexing](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/request-site-indexing.md) to ask Google to crawl the site. A successful call means Google accepted the request into its crawl queue, not that the site is indexed. Readiness reports the site's Google connection and ownership verification. It doesn't track the property steps in steps 4 and 5, so call those in order yourself. ## Show the site's search performance Your app has a dashboard that shows how the site performs in Google Search: total clicks and impressions over time, and the top search queries. To show search performance: 1. Call [Get Search Analytics](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/get-search-analytics.md) with `?startDate=2026-08-01&endDate=2026-08-31&dimensions=date` to get a daily row for the period. Each row's `keys` holds the date, alongside its `clicks`, `impressions`, `ctr`, and `position`. 1. Call it again with `dimensions=query` and a `rowLimit` to get the top search terms for the same period. 1. Render the daily rows as a chart and the query rows as a table. Page through large result sets with `startRow` and `rowLimit`. ## Inspect the site's pages A site owner wants to know which of their pages are indexed by Google and which have issues. Your app runs Google URL inspection on the site's pages and presents the results. To inspect pages: 1. Call [Inspect URLs](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/inspect-urls.md) with the IDs of the pages to inspect. The response contains the results of the first batch of pages. 1. If the returned `status` is `ONGOING`, Wix is still inspecting the remaining pages server-side. Poll [Get Inspection](https://dev.wix.com/docs/api-reference/business-management/seo/google-search-console/site-readiness-v1/get-inspection.md) every few seconds until `status` is `COMPLETE` or `ERROR`. Large inspections can take several minutes. 1. Check `remainingPageCount` in the final response. A value above zero means the connected account's Google inspection quota ran out before every page was inspected, so the missing pages can be inspected after the quota resets, using `updateResults: true` to merge the new results into the stored ones. 1. Present each result. The `page` object identifies the inspected page, and `data` carries Google's raw URL-inspection payload, including the index status verdict and any issues Google reports.