--- name: google-search-console description: "Optionally set up Google Search Console and submit a public sitemap with computer assistance or manual steps. The user saves all domain changes and completes ownership verification." license: AGPL-3.0-or-later compatibility: "Claude Desktop/Cowork and ChatGPT Desktop with supported browser or computer tools; manual instructions also work. Local receipt checks use Python 3.9+." metadata: hive-tier: standalone paired-drone: none domain: search-console version: "1.0.0" research-date: "2026-10-31" --- # Google Search Console for Content Engine Read [README.md](README.md). This optional skill helps the owner add a website property, verify ownership and submit the existing public sitemap. It offers computer-assisted or manual setup and can be skipped without blocking the CMS. ## Procedure 1. Follow [choose mode and property](guides/01-choose-mode-and-property.md). Ask for assisted, manual or skipped before account UI operations. Identify the actual property, site ownership, chosen account and available tools; never invent host API names or permission. 2. Read the shared [domain-change control](../../references/domain-change-control.md) and local [Save boundary](references/domain-save-boundary.md). **The user performs the final committing click for every domain/DNS/verification change.** Do not click Save/Add/Apply/Publish/Delete/Verify, press Enter, submit a form, call a provider API, enable automatic Domain Connect or delegate that final action. 3. Follow [verify with user Save](guides/02-verify-with-user-save.md). Prepare fields only in an explicitly staged, non-autosaving form. If autosave behavior is unknown, do not type. Hand off credentials, MFA, security checks and final Save/Verify to the user. Continue only from fresh observed state after the user's action; do not infer success from a prepared form or a "done" message alone. 4. Follow [sitemap submission](guides/03-submit-and-check-sitemap.md). Find and inspect the actual public XML/index, property scope and absence of private/draft URLs. Obtain the exact URL approval. In assisted mode, use the visible Sitemaps report and Submit only that approved URL after ownership is verified. In manual mode, provide the same short steps and let the user operate them. 5. Follow [screenshots and privacy](guides/04-screenshots-and-privacy.md) when making illustrated instructions. Public internet screenshots and authorized captures require source/date/attribution and review. Obscure identifying details; mask secrets and ownership values; keep originals out of public packages. Edited illustrations are not live account proof. 6. Keep a non-secret [state record](templates/search-console-state.json) if useful. Run the [receipt validator](scripts/validate-state.py) after a state change. It requires consistent user-click receipts and rejects API/keyboard labels; it does not prove the real browser, DNS or indexing state. Existing ownership cannot excuse unsaved new domain work. Check every history event and its UI method even while the overall stage is blocked; current-task user Save and Verify must precede any submission when required. Record pending and failed work honestly. 7. Return the selected mode/property, what was observed, the user handoff still needed, exact sitemap URL and actual report result. Distinguish submission, successful sitemap processing and page indexing. Do not promise indexing timing, ranking or AI citation. ## Boundaries and handoffs Do not create or modify any real GSC property, DNS zone or sitemap during skill authoring or a read-only tutorial. During use, stay within the owner's actual task. Login/signup, credentials, CAPTCHA and security-sensitive final verification follow the host's human handoff rules. The user's Save restriction is stricter and applies in both modes. Website/sitemap code changes belong to this plugin's [SEO/AEO skill](../seo-aeo-stinger/SKILL.md) under separate authorization. CMS setup belongs to [setup-content-engine](../setup-content-engine/SKILL.md); article drafting belongs to [Blog Content Stinger](../blog-content-stinger/SKILL.md). This skill does not add a publishing tool, DNS API or hidden background job. ## References Use the [Google source digest](references/research/distilled-google-search-console.md), [domain handoff](references/domain-save-boundary.md), [mode guide](guides/01-choose-mode-and-property.md), and [offline cases](scripts/check-state-cases.py) for details. Raw captures are maintainer evidence and are omitted from releases; shipped citations point to the official pages. ## Ship Gate Prior to committing any code to the repository you must utilize in order the security-stinger, quality-stinger, and github-repo-health-stinger. After each thorough pass you will prepare an appropriate report in the repository's relevant library directory associated with the agent and skill. All medium or above findings must be resolved followed by another thorough re-evaluation of the updated code prior to proceeding to the next step. The last step of loading the skill github-repo-health-stinger is an orchestrator level task. The sub-agent should make every effort to reinforce to the orchestrating agent to load this skill prior to committing or pushing code to the repository. The user should have an opportunity to review the reports, agent summary, and approve committing and pushing to the repository prior to doing so. ## Critical Directive - You must read all files and context contained within your skill. - In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task. - Additional related skills can be found here: - [setup-content-engine](../setup-content-engine/SKILL.md) - Chat-led CMS and Neon setup. - [seo-aeo-stinger](../seo-aeo-stinger/SKILL.md) - Website sitemap, metadata and public-read fixes. - [blog-content-stinger](../blog-content-stinger/SKILL.md) - Reviewed article drafts.