Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Search Change Proof — On-Page SEO QA

    1

    Close one on-page SEO ticket with exact before and after values. See which local, live and search checks are complete.

    Free

    1 useSecurity scanned
    Search Change Proof — On-Page SEO QA

    Search Change Proof — On-Page SEO QA

    Example session with this skill installed

    Synthetic local example. example.test is an illustrative domain; these original HTML files are not a deployed site.

    For the supplied static pricing page, change only the canonical from https://example.test/old-pricing to https://example.test/pricing. Keep the title, meta description and robots directive unchanged. Check the local source and rendered preview, and do not deploy. Return the values observed at each stage and name any remaining check.

    • Read your context and instructions
    • Compiled the search change proof

    Canonical source corrected; preview not verified

    Actual synthetic source check, 21 October 2026 at 05:09:28 UTC. Only the local HTML fixture changed. example.test was not contacted.

    CheckBeforeAfterObserved status
    Source canonicalhttps://example.test/old-pricinghttps://example.test/pricingVerified in the local files
    Canonical declarations11Verified in the local files
    Other page fieldsTitle, description and robots baseline retainedUnchangedVerified in the local files
    Rendered browser DOMNot observedNot observedLocal preview access unavailable in this demonstration
    Deployed pageNot observedNot observedDeployment excluded
    Search-engine index and selected canonicalNot observedNot observedNo indexed-view evidence
    Rankings or trafficNot measuredNot measuredNo performance claim

    The retained patch changes only the canonical href in the synthetic pricing HTML. The source assertions passed; this is not yet a local-render or deployment result.

    Next step: inspect the rendered canonical in an accessible preview before treating the local change as fully verified. After a separately authorized release, inspect the live page and then the search engine's indexed view.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    You changed a canonical tag or robots directive. The ticket still needs an answer: what does the page expose now, and which checks are still outstanding?

    Search Change Proof carries one specific on-page correction from its baseline to the stages you can actually inspect. It works with a known URL and a named finding: title, description, canonical, robots or relevant structured data.

    Your agent records the current value, makes the scoped change when authorized, checks the rendered preview when browser access is available, and inspects the deployed page when release access is available. A verification-only request stays read-only.

    A ticket you can hand back

    The result names the changed file or CMS entry and shows the exact baseline, local and deployed values with dates and sources. Unobserved layers stay visible, with a concrete next check. That gives the next person a clear place to continue.

    Bring the URL, audit finding and relevant project/page access. This free package contains workflow instructions and uses your agent's available project, browser and HTTP tools. Deployment and Search Console access are optional and require their own authorization.

    A live page check cannot establish indexing or a ranking gain. Those require later search-engine evidence and measured results.

    Send one URL and the exact value you want to verify.

    Covers one known URL and a specific on-page recommendation per run.
    Source, rendered preview, deployed page, indexed result and measured performance are separate observations.
    Unavailable browser, deployment or Search Console access leaves that layer unobserved.
    A declared canonical does not prove the search engine selected it; indexing, ranking, traffic, snippet and rich-result outcomes are not guaranteed.
    The package includes no credentials, MCP server, analytics feed or automatic deployment action.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Permissions

    Read Files
    Write Files
    Terminal / Shell
    Browser
    Network Access

    Read project files and pages; write project files only for requested implementation. Live URL reads need network access. Deployment, CMS updates, and Search Console account actions require the user's authorization.

    Listed1 month ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    One URL, a specific audit recommendation or desired value, and the project or CMS entry involved. State whether the task is to implement, verify or both.

    Local and deployed page checks can proceed with the relevant tools and access. Without an authorized indexed-view result, index status and the search engine’s selected canonical remain unobserved.

    Only when the task includes that action and the relevant authorization. A verification-only request stays read-only.

    New in Marketing & SEO