Search Console turns “is Google seeing the site?” into URL, sitemap, query, page, and indexing evidence—but it still needs the correct production property.
Verify the domain or exact production URL property, ensure all preferred host variants are understood, submit the canonical sitemap, inspect representative URLs, and record the indexed and live-test states separately. Use Page Indexing to diagnose excluded groups and Performance to compare queries, pages, countries, devices, impressions, clicks, CTR, and average position. Annotate every release. Search Console does not report every AI appearance or non-Google crawler.
This guide connects AI-builder publication and custom-domain changes to Search Console setup, indexing diagnosis, performance analysis, and post-release monitoring without treating impressions, position, crawler visits, or AI citations as the same signal.
Main Explanation
Choose the property carefully. A Domain property can aggregate protocol and subdomain variants after DNS verification, while a URL-prefix property covers its exact prefix. Confirm that the canonical custom domain—not only the builder or preview domain—is verified. Preserve verification tokens in server-visible output or DNS as appropriate and recheck them after template or domain changes.
Submit the sitemap served by the preferred host and inspect its fetch status. Compare listed URLs with the real public inventory, not with every route in the codebase. Search Console notes that sitemaps support discovery; they do not guarantee indexing. Use URL Inspection for a small representative set and distinguish the last indexed version from the live test.
Diagnose groups before requesting more crawls. Filter Page Indexing states by sitemap and inspect examples for redirects, alternate canonicals, noindex, blocked access, soft 404s, duplicates, discovered-not-crawled, and crawled-not-indexed. Match each state to a production test and the owning platform layer before giving a coding agent a task.
Use Performance for trends, not promises. Compare dates and annotate launches, domain migrations, content releases, outages, and large template changes. Separate branded from nonbranded queries and evaluate pages by intent. Search Console impressions and clicks are Google Search evidence; AI crawler logs, assistant citations, referrals, and conversions need separate datasets.
Keep the public acquisition layer separate from the private application. Marketing, use-case, comparison, documentation, support, and policy pages may be discovery targets when they serve visitors. Account, dashboard, billing, checkout, API, webhook, admin, preview, staging, test, and user-data routes should remain protected and outside public sitemaps. A crawler directive is not a substitute for authentication or authorization.
Turn each finding into a bounded implementation task. Record the production URL, observed response or element, affected route scope, owning layer, files or settings allowed to change, routes that must remain private, and the acceptance test. After the smallest safe correction, run project checks, publish, and repeat the exact anonymous request. A builder preview or local success does not prove the production response changed.
Measure the stages separately. A successful fetch is crawl evidence, Search Console reports Google discovery and performance, infrastructure logs record requests, analytics records attributed visits, and controlled observations or provider reports can record AI appearances. Technical readiness can remove blockers, but no builder, prompt, sitemap, schema block, scan, or indexing request guarantees ranking, citation, recommendation, traffic, or conversion.
Practical Steps
- Verify the canonical production property.
- Confirm preferred host redirects.
- Submit the canonical sitemap.
- Inspect representative priority URLs.
- Group Page Indexing exclusions.
- Export query and page baselines.
- Annotate production releases.
- Rescan and compare each evidence layer separately.
FAQ
Should I verify the builder subdomain?
The controlled custom domain is the priority. A builder subdomain can be useful for diagnosis but should not become a competing canonical surface.
Does URL Inspection show the live page?
The indexed result reflects Google’s stored version; use Test Live URL for a current fetch, while noting that it cannot predict every indexing decision.
Can Search Console measure ChatGPT traffic?
No. Use analytics and referral or crawler evidence separately; Search Console reports Google Search data.
Sources and methodology
Reviewed on 2026-08-26 against current first-party platform documentation and Google Search Central guidance. The workflow evaluates the public production response and keeps crawlability, indexing, search performance, AI visibility, referrals, and business outcomes separate.
These references support the changeable facts and study findings discussed above. Results depend on each source's sample, date, market, query set, and measurement method.