Business Listing Checker

# Business Listing Checker

Compare a local merchant's public website with its public Google Maps and Yelp listings, one physical location at a time. Produce an evidence-based report, a prioritized optimization plan, and concrete work for the merchant or agency. A storefront account is not required.

## Loadout capabilities

Use <action-tag>composio:firecrawl_tools:firecrawl_scrape</action-tag> to read each public location page and its linked contact or service page. Use <action-tag>composio:serpapi_tools:serpapi_google_maps_search</action-tag> to find the corresponding public Google Maps listing. Where Yelp has coverage, use <action-tag>composio:yelp_tools:yelp_search_businesses</action-tag> to identify the listing, then <action-tag>composio:yelp_tools:yelp_get_business_details</action-tag> with the returned business ID or alias to compare details. Use <integration-tag>api:wordpress_api</integration-tag> when mapping recommended website corrections to a WordPress follow-up: its current Action reads connection-bound published posts, not static pages or edits, so this Skill keeps WordPress changes as a reviewable action plan. Call each research Action separately through `capabilities_execute`, after `capabilities_preflight` and normal authorization. These read facts; the Skill grants no permission to edit listings or the website.

## Inputs and boundaries

Ask for the merchant's public website and the physical locations in scope. If the site has several locations, identify each location from its own public page and run a separate comparison. An optional merchant-supplied canonical name, address, phone, booking URL, and opening hours helps resolve ambiguous results. Never assume public website data is correct merely because the merchant owns it.

Default to one site page fetch, one Google Maps query, one Yelp search, and one Yelp detail call per location. Preflight paid calls and state the estimated spend before execution. Do not expand a search, paginate, or run other paid calls without a reason tied to a missing fact. Yelp coverage varies by country; an empty result is unknown coverage, not proof that the business is unlisted. If an Action needs a merchant connection or fails, note the gap and continue with the available public evidence.

This workflow is read-only. Do not claim, edit, or verify ownership of profiles; do not respond to reviews, post content, upload media, or change a CMS. A merchant can connect an account later to apply approved corrections.

## Workflow

1. Fetch the location page. Record the retrieval date, page URL, location name, full address, phone, displayed hours, primary category or services, reservation or order destination, and visible site links. Mark missing values as missing, not inferred. Follow a relevant linked page only if the first page lacks a key field.
2. Search Google Maps with the business name plus street or town. Match by at least two independent identifiers, such as address, website, and phone. Distinguish two similarly named branches. Record the result URL or place ID, displayed name, address, phone, hours, category, website, and review count or rating if returned. Do not call a result position a stable search ranking; it is specific to the query, location, and viewport.
3. Where Yelp is available, search by name and town with a small limit. Confirm a candidate using address and another identifier, then fetch details with its returned ID or alias. Record the listing URL and fields actually returned. Yelp's `url` is the Yelp page, not the merchant website; missing phone or website is an unknown field. If several plausible listings remain, flag ambiguous identity and stop before asserting a conflict.
4. Compare normalized phone digits, street address and unit, business name, primary category, public hours including holiday caveats, website and booking destination. Preserve each raw value beside its source. Distinguish a confirmed conflict from a source omission, a platform formatting difference, a temporary-hours exception, or a stale/unverified observation. Never derive missing hours from opening status.
5. Optionally compare another public directory, such as Foursquare, only when an available read capability or user-provided public URL can be verified; label its source separately. Do not imply that Google Maps, Yelp, or another directory is a merchant-owned profile without account evidence.
6. For a WordPress merchant, map each site recommendation to the public page URL and exact visible field or section, such as Hartsdale page footer address, Contact page hours, or the Reservation and Order Now links. Identify the editor owner and needed canonical copy. Label this a manual or future connected WordPress edit; do not imply that the current WordPress integration can read or write those static pages.

## Required output

Return an **evidence-based report** with a dated source table by location: website URL, Google Maps listing identifier or URL, Yelp listing URL or coverage gap, observed values, and confidence. Include the exact field-level comparison and explicit unresolved identity or freshness flags. Link to the public pages wherever possible.

Then provide **specific prioritized optimization strategies**. Prioritize high-impact confirmed name, address, phone, hours, or destination conflicts; then missing or inconsistent services, categories, menu or booking links; then weaker presentation opportunities. For each recommendation, state the observed evidence, expected customer/search effect as a hypothesis, and what must be verified with the merchant. Do not promise rankings or cite review counts as proof of conversion.

Finish with **operable actions** in a table: priority, exact field and location, proposed correction or verification step, owner (merchant or agency), account or material required, a check after the change, and expected observable result. For a WordPress site, include the affected public URL and the specific editor field, block, or menu link to review; mark platform access as required for later application. Draft exact copy only from verified facts. Profile or site edits require merchant access and approval in a later workflow. If evidence is too thin, return a short verification queue instead of fabricating changes.