Search visibility after deployment

Merging into beta does not publish the website. Follow deployment to release the main site and docs before submitting their new URLs to search engines.

In Google Search Console, use the verified toolzerhub.com domain property (which covers its subdomains), or verify both HTTPS URL-prefix properties: https://toolzerhub.com/ and https://docs.toolzerhub.com/.

1. Submit https://toolzerhub.com/sitemap.xml in Sitemaps after it and its children return XML with HTTP 200. The generated index lists the main site's URL-set shards and the validated docs URL set at /sitemap-docs.xml. The docs site's robots.txt names the latter, which authorizes Google's cross-site submission without assuming shared Search Console ownership. Keep https://docs.toolzerhub.com/sitemap.xml available as the docs site's local source and independently submit it when both hosts are verified.
2. Inspect the homepage, one /apis/ platform page, one docs guide, and one /reference/ endpoint with URL Inspection → Test live URL. Check that Google can fetch the page, indexing is allowed, and the declared canonical matches the page's public URL. Request indexing for these representative pages.
3. In Page indexing, distinguish undiscovered pages from crawled-but-not-indexed pages, duplicate canonical selections, redirects, and server errors. If the live inspection receives a challenge or 403, check Cloudflare security events for that request before changing any bot protections.
4. In Performance, filter by /apis/ and the docs hostname. Compare impressions, clicks, and queries over time; keep the unrelated /tools/ traffic separate.

A successful build, sitemap submission, or live inspection does not prove indexing or guarantee a ranking. Record Search Console's actual status rather than treating an empty site: search as a complete inventory.

References: Google sitemap guidance, Sitemaps protocol, URL Inspection.