HVAC & Plumbing GEO Audit: Check Facts & Schema

    1

    Check up to 5 public pages for conflicting business facts, JSON-LD issues, indexing restrictions and service/city wording. Get URL-level evidence and a prioritized fix list.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    HVAC & Plumbing GEO Audit: Check Facts & Schema

    Example session with this skill installed

    Audit these four public Ranshaw Plumbing & Heating pages: https://ranshaw.com/, https://ranshaw.com/about/contact, https://ranshaw.com/plumbing/pipe-repair and https://ranshaw.com/about/service-area. Use website-observed reference values: name Ranshaw Plumbing & Heating, phone +1-718-767-0707, city Whitestone, services plumbing/heating/pipe repair. Treat these as provisional, not owner-confirmed facts. Show actual page coverage, evidence, manual review actions and limits. Do not change the website or claim an AI ranking score.

    • Read your context and instructions
    • Compiled the hvac & plumbing
    • Generated the document

    Executed public-site audit

    This was a fresh read-only run against four public pages on 2026-11-12. All four returned HTTP 200 and were inspected as initial HTML. The business reference values came from the same public website; they are not independently verified or owner-confirmed. This is an independent public test, not a client case study.

    PageHTTPJSON-LD observedLiteral coverage observed
    Homepage /200No application/ld+json blockWhitestone, plumbing, heating
    /about/contact200No application/ld+json blockWhitestone, plumbing, heating
    /plumbing/pipe-repair200No application/ld+json blockWhitestone, plumbing, heating, pipe repair
    /about/service-area200No application/ld+json blockWhitestone, plumbing, heating

    Findings and actions

    • Coverage: 4/4 pages retrieved. There were no failed page requests in this run.
    • The listed noindex/nosnippet/none restriction tokens were not observed in the checked meta/header sources. This does not prove Google indexing or crawler access.
    • Four pages lacked an observed initial-HTML JSON-LD local-business candidate. Review whether appropriate, accurate markup is already supplied through another format or JavaScript before adding anything.
    • Twelve business identity, telephone and opening-hours checks remained unverified because no JSON-LD business entity was selected. These are not twelve failed HTTP requests and do not prove incorrect business information.
    • Whitestone, plumbing and heating appeared across the captured pages. The exact phrase pipe repair appeared on the selected pipe-repair service page. Literal presence is not a service-quality or AI-visibility measure.
    • Confirm business identity, public-address applicability, main phone and hours with the owner before drafting changes. Never invent an address or emergency-service promise.

    The report recorded 13 pass observations, 4 review items and 12 unverified property checks. These counts are not a GEO score. Zero JSON-LD blocks means no JSON-LD syntax was exercised on that page, not that all possible markup was validated.

    Reproducibility and validation

    The delivered report.html, report.json, fix-plan.md and local fetched-snapshot.json contain URLs, timestamps, evidence and capture hashes. Replaying that snapshot produced identical per-page and cross-page evidence without new network requests.

    A separate set of ten synthetic local scenarios checked malformed JSON-LD, graph/address references, wrong business facts, ambiguous entities, HTTP 403, hidden phone numbers, HTML escaping, invalid inputs and independent script execution. The corrected synthetic fixture passed all eight observation categories. These fixtures do not represent changes made to the public website.

    Limits

    No site changes, forms, appointments, browser rendering, Search Console connection, real AI-citation measurement or ranking verification were performed. Missing JSON-LD in these four responses does not establish absence of microdata, RDFa or rendered schema. The audit is complete for the selected initial HTML pages; performance outcomes remain unmeasured.

    report.html

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Make your business facts easier to check

    Your website says one thing, its JSON-LD says another, or the main phone is hard to find. This small audit helps HVAC and plumbing businesses review those gaps before making changes.

    What you provide

    • A homepage and up to four contact or service page URLs.
    • A reference business name, main phone, city and service phrases.
    • Optional: a specific JSON-LD entity ID when several businesses appear.

    What you receive

    • An HTML report and machine-readable JSON with URLs, capture hashes and observed evidence.
    • A prioritized fix-plan.md that separates confirmed contradictions, review items and unverified coverage.
    • A local HTML snapshot for repeatable offline inspection.

    Eight check categories

    HTTP retrieval; observed meta/header indexing restrictions; JSON-LD syntax; local-business types; selected entity name/address coverage; reference/main-phone consistency; hours-field presence; and literal city/service wording across the selected pages.

    Designed for one location

    The tool selects a specific business entity before comparing its facts. It handles JSON-LD arrays and @graph, and keeps ambiguous entities for review. Different branches and department phone numbers must not be merged into a single business identity.

    Verified examples

    A fresh four-page public-site audit completed with HTTP 200 responses and matched its offline replay. Ten synthetic local scenarios also passed the expected parser and reporting checks. The public test found no initial-HTML JSON-LD blocks; it did not establish missing markup in other formats or any AI-visibility outcome.

    Scope you can verify

    This audits the initial HTML response and JSON-LD, not a rendered browser session, full-site crawl or comprehensive schema validation. A missing phrase means it was not observed in these pages. A field's presence does not prove factual accuracy. Failed fetches are unverified coverage.

    It does not connect to Search Console, measure actual AI citations, create a GEO ranking score, publish changes or promise traffic gains. Google does not require special AI schema or llms.txt for its AI features. Confirm facts with the owner before changing a name, phone, address, service promise or hours.

    Python 3.10+ and beautifulsoup4 are required. The runner uses terminal, network and local files; no paid API or hosted subscription is included. The price is a $1 one-time skill purchase.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Marketing & SEO.

    Initial HTML and JSON-LD only; no JavaScript rendering, robots.txt analysis, full-site crawl or full schema validation. Up to 5 explicit URLs for one location. Reference facts need owner confirmation. Phone comparison strips punctuation and normalizes North American +1. No AI-visibility, citation or ranking measurement.

    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 buying a skill.

    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 4 days ago

    Software
    Python 3.10+beautifulsoup4

    Agent needs terminal, network and local file access. Live checks read public pages only; offline snapshot replay does not need network.

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Reads the selected public URLs and operator reference profile, then writes local reports and a fetched HTML snapshot. No forms, booking, CMS edits or deployment. Snapshot replay is local. Do not publish captured HTML or use it as marketplace content.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    It reports observable website evidence and a fix list. It does not measure AI mentions, rankings or traffic, and makes no performance guarantee. Authorized Search Console data and separate search testing would be needed to assess actual outcomes.

    Public HVAC and plumbing pages for one business location. Select up to five pages. It parses the initial HTML and JSON-LD, so JavaScript-rendered markup, other schema formats and multiple branch identities require manual review.

    No. It generates reports and suggested actions only. Confirm names, phones, service areas, addresses and hours with the business before editing. Missing or ambiguous facts remain review items.

    The skill instructions, standalone audit script and profile example. Python and Beautiful Soup must be available in your agent environment. Hosted execution, paid APIs and publishing services are not included.

    New in Marketing & SEO