More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    SchemaParity — Local Business Structured Data Audit

    1

    Compare local-business structured data to the visible page and authoritative business details.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SchemaParity — Local Business Structured Data Audit

    SchemaParity — Local Business Structured Data Audit

    Example session with this skill installed

    Run SchemaParity — Local Business Structured Data Audit as an evidence-first preflight. This is a representative, hypothetical test case: A restaurant page displays Saturday 11–22 but JSON-LD says closed all Saturday. The materials I have available are: public business page URL or HTML; JSON-LD or microdata; confirmed NAP and opening hours. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.

    • Read your context and instructions
    • Compiled the schemaparity

    REPRESENTATIVE EXAMPLE — NOT A LIVE RUN

    PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Compare local-business structured data to the visible page and authoritative business details.
    Scenario supplied by buyer: A restaurant page displays Saturday 11–22 but JSON-LD says closed all Saturday.

    1. MATERIAL FINDING (HIGH): Opening-hour inconsistency is directly observable from the supplied HTML and markup. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.

    2. TRACEABILITY MATRIX

    • Claimed behavior: A restaurant page displays Saturday 11–22 but JSON-LD says closed all Saturday.
    • Critical evidence sources: public business page URL or HTML, JSON-LD or microdata, confirmed NAP and opening hours.
    • Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
    1. CHECKS THE SKILL WILL RUN
    • Extract the actual schema type and property values; do not invent missing locality details.
    • Cross-check business name, address, phone and opening hours against visible content.
    • Identify invalid URLs, duplicate entities, conflicting addresses and unsupported review claims.
    • Verify JSON-LD syntax separately from search-engine eligibility and rich-result availability.
    • Generate minimal correction snippets, uncertainty labels and steps using official validators.
    1. CORRECTION TO PROPOSE
      Correct only the Saturday hours after confirming them with the operator; keep the authoritative source in the report. Do not present this as implemented until the seller/developer actually applies the change and reviews the result.

    2. REPRODUCTION / ACCEPTANCE TEST
      Validate the changed JSON-LD syntax and visually inspect the actual page after deployment. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS.

    3. SCOPE LIMIT
      Does not guarantee rich results or independently verify ownership of business details.

    Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.

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

    About this skill

    SchemaParity — Local Business Structured Data Audit

    Compare local-business structured data to the visible page and authoritative business details.

    What you receive

    • A ready-to-install skill with a repeatable, evidence-first procedure.
    • A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
    • A clearly separated verification checklist and unknowns register.
    • A representative worked example; it is not passed off as a live customer run.

    Example issue

    A restaurant page displays Saturday 11–22 but JSON-LD says closed all Saturday.

    Trust boundary

    Does not guarantee rich results or independently verify ownership of business details.

    No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.

    Does not guarantee rich results or independently verify ownership of business details.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    Permissions

    File Scopes

    Buyer-provided
    local
    files
    (read-only)

    No production changes or account access without owner authorization.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    No. Supply files or authorize a suitable read-only connection. Missing evidence is marked unverified.

    No, they illustrate a representative workflow; the delivered skill uses your actual materials.