Google Search Console sitemap submission

Owner-only Search Console steps

1. Open the Search Console sitemap page for the URL-prefix property.
2. Sign in with the Google account that owns or can verify https://qihaze123.github.io/billing-webhook-kit/.
3. If the property is not verified, complete Google's ownership verification in the account UI.
4. Submit sitemap.xml in the sitemap field for that verified property.
5. Confirm that Google reports the submitted sitemap as discovered or success.

Latest browser check

On 2026-06-18, the direct Search Console sitemap URL redirected to Google's not-verified/no-access page while signed in as qihaze99@gmail.com. The visible Google action was 验证您的所有权, so the blocker is account/property verification, not sitemap reachability.

Browser assistance can open the exact Search Console URL, check whether the property is verified, fill sitemap.xml, submit it after explicit owner authorization, and confirm the visible submitted/fetched state. Google login, permission grants, and ownership verification must still be performed by the owner in the browser.

Live crawl files already in place

The site exposes the discovery files that Search Console expects before manual submission: public homepage, robots.txt with a sitemap directive, sitemap.xml with 104 URLs, sitemap.html, RSS feed, llms.txt, Google indexing priority queue, free Lemon Squeezy webhook test tools, webhook endpoint smoke test, status page, guide index, tool index, free sample, Pro Kit preview, launch evidence pack, and Pro sample report.

Automation boundary and owner actions

I can use the browser for navigation, visible-state checks, sitemap field entry, explicit owner-authorized sitemap submission, and post-submit verification. I should not operate Google login, ownership verification, or permission grants because those are account and ownership side effects.