---

name: google-search-console-url-inspector description: "Inspect a URL in Google Search Console and explain its current indexing status and blockers."

Google Search Console URL Inspector

Inspect a URL in Google Search Console and explain its current indexing status and blockers.

Required Aident Actions

• <action-tag>composio:google_search_console_tools:google_search_console_inspect_url</action-tag> (required inputs: site_url, inspection_url): Inspects a URL for indexing issues and status in Google Search Console.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete planAction · Inspect Urled effect directly advances the requested outcome. Do not invoke every listed Action by default.
3. Inspect the current schema and prepare the minimum valid input for each selected Action.
4. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
5. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Collect the verified Search Console property and exact canonical URL to inspect.
• Use composio:google_search_console_tools:google_search_console_inspect_url with the reviewed property and URL.
• Report coverage state, crawl information, canonical selection, mobile usability, and detected blockers when returned.
• Distinguish current inspection evidence from recommendations and do not claim that the Action submits indexing requests.
• Return prioritized corrective steps and the evidence needed for a later reinspection.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.