SerpAPI Skill — Live SERP Data for Local Search Verification

LocalSEOData gives you structured local SEO data: parsed GBP profiles, geogrid rankings, citation records. But sometimes you need the raw SERP — what does the actual search results page look like right now for this query in this location? Which features appear? Is there an AI Overview? A local pack? A featured snippet? What are the organic results?

The serpapi-tool skill connects Claude to SerpAPI’s real-time search result scraping. When a strategy skill needs to verify what is actually appearing on the SERP — not structured data about it, but the actual page — dispatch routes to SerpAPI. It also serves as the fallback data source when LocalSEOData is not connected, and it is the only tool in the stack that covers non-Google engines.

What This Skill Does

The serpapi-tool skill enables Claude to pull live search results for any query and location, capturing the full SERP layout: local pack presence and contents, organic results, featured snippets, knowledge panels, AI Overviews, People Also Ask boxes, and paid ad positions.

Prompt: "What does the actual SERP look like for 'emergency plumber near me'
searched from downtown Denver right now?"

Skills fired: dispatch → local-seo-audit + serpapi-tool
Data pulled: Live SERP for query at specified location

Output:
Live SERP — "emergency plumber near me" (Denver, CO)

SERP Features Present:
  - Local Services Ads: 3 (Mile High Plumbing, Denver Drain, ProPlumb)
  - Local Pack: 3 results (with map)
  - AI Overview: Yes — summarizes top-rated plumbers with 24/7 availability
  - People Also Ask: 4 questions
  - Organic results: 10
  - Featured snippet: No

Local Pack:
  1. Ace Plumbing (4.8, 234 reviews) — "Emergency Plumber"
  2. Denver Emergency Plumbing (4.7, 189 reviews) — "Plumber"
  3. Rocky Mountain Plumbing (4.9, 312 reviews) — "Plumber"

AI Overview mentions: Ace Plumbing, Rocky Mountain Plumbing, 24/7 Plumb Co
Organic #1: yelp.com/search?find_desc=emergency+plumber
Organic #2: homeadvisor.com/...

When Dispatch Routes Here vs LocalSEOData

Dispatch uses serpapi-tool in three situations:

  1. Real-time verification requests — When the prompt includes “live,” “right now,” “verify,” “current,” or any language suggesting the user wants to see what search results look like at this moment rather than from stored data.

  2. Non-Google engine requests — When the prompt mentions Bing, DuckDuckGo, Yahoo, or asks for cross-engine comparison. LocalSEOData covers Google. SerpAPI covers everything.

  3. LocalSEOData unavailable — If LocalSEOData is not connected or credits are depleted, serpapi-tool serves as the fallback for Google SERP data, ensuring that LocalSEOSkills workflows do not break due to data source unavailability.

For standard local pack analysis, competitive research, and audit workflows, localseodata-tool is the default. SerpAPI activates when timeliness or engine coverage demands it.

SERP Feature Verification and Competitive Analysis

The primary use case is SERP verification — confirming what actually appears for your target queries. Structured data from LocalSEOData tells you your ranking position. Live SERP data tells you what the searcher actually sees, including features that may push your listing below the fold or change how searchers interact with results.

This matters because SERP layouts vary significantly by query intent. A query like “plumber near me” might show LSAs, a local pack, and an AI Overview — pushing the first organic result far down the page. A query like “how to fix a leaky faucet” might show a featured snippet, a video carousel, and People Also Ask — with no local pack at all. Understanding the actual SERP layout for your target queries changes your optimization strategy.

Prompt: "Compare the SERP layout for 'dentist Austin' vs 'best cosmetic dentist Austin'.
What features appear for each and what does that mean for our strategy?"

Skills fired: dispatch → local-seo-audit + serpapi-tool

Output:
SERP Comparison:

"dentist Austin":
  LSAs: Yes (4), Local Pack: Yes, AI Overview: No
  Organic dominated by: Yelp, Healthgrades, ZocDoc
  Strategy: Local pack is the primary target. LSA opportunity exists.

"best cosmetic dentist Austin":
  LSAs: No, Local Pack: Yes (different 3 businesses), AI Overview: Yes
  AI Overview cites: 2 local practices, 1 directory
  Strategy: AI Overview captures significant clicks. Cosmetic-specific
  GBP categories and content needed. Different competitive set than
  generic "dentist" query.

Post-Optimization Verification

After making GBP changes, updating a website, or completing a technical fix, verify that changes have propagated to live results.

Prompt: "We updated our GBP categories and hours yesterday. Pull the live SERP
for 'AC repair Scottsdale' and verify the changes are reflected."

Skills fired: dispatch → serpapi-tool

Output:
VERIFICATION: "AC repair Scottsdale"
Scraped: March 30, 2026 at 3:08 PM UTC

LOCAL PACK STATUS:
#3: Cool Air Scottsdale — Categories now showing "HVAC contractor,
Air conditioning repair service" (previously only "HVAC contractor")
Hours: Mon-Sat 7AM-7PM (updated, previously showed Mon-Fri 8-5)

VERIFICATION RESULT: Category update propagated. Hours update propagated.
Both changes are live in search results.

Ranking Discrepancy Investigation

When rank tracking tools show one thing but manual searches show another, SerpAPI provides the neutral third-party verification.

Prompt: "Our tracking tool says we rank #1 for 'dentist Portland' but the client
says they see us at #4. Pull a neutral live result."

Skills fired: dispatch → serpapi-tool

Output:
NEUTRAL SERP VERIFICATION: "dentist Portland"
Scraped from: Data center IP (no personalization, no search history)
Location: Portland, OR

Local Pack:
#1: Pearl District Dental — 4.9 (423 reviews)
#2: Portland Family Dentistry — 4.8 (287 reviews)
#3: Rose City Dental — 4.7 (198 reviews)

Your business (Mountain View Dental): Not in visible 3-pack.
Local Finder position: #4

EXPLANATION: Your tracking tool may be measuring a different geographic
point or reflecting cached data. From a neutral Portland location, you
are position #4 in Local Finder, not visible in the default 3-pack.
The client's observation is correct.

Multi-Engine Local Visibility

SerpAPI is the only tool in the LocalSEOSkills stack that covers non-Google engines. This supports specific strategic use cases.

Bing Local Results for ChatGPT Context

ChatGPT with Browse uses Bing’s index. Understanding how your business appears in Bing local results provides context for ChatGPT visibility.

Prompt: "Pull Bing local results for 'plumber Phoenix' — I want to understand
why we're not showing up in ChatGPT recommendations."

Skills fired: dispatch → serpapi-tool (Bing engine)

Output:
BING LOCAL RESULTS: "plumber Phoenix"

Bing Local Pack:
#1: Arizona Plumbing Masters
#2: Phoenix Plumbing Pros
#3: Desert Pipeline Services

Your business (Valley Plumbing): Not in Bing local pack.
Bing organic: Not ranking page 1.

ANALYSIS: Your absence from Bing local results correlates with
limited ChatGPT visibility. ChatGPT Browse relies on Bing's index.

RECOMMENDED ACTIONS:
1. Verify and optimize Bing Places listing (bing-places skill)
2. Ensure website is indexed in Bing Webmaster Tools
3. Check Bing-specific local ranking factors

Cross-Engine Comparison

Full visibility picture across search engines.

Prompt: "Compare our local visibility for 'personal injury lawyer Dallas'
across Google, Bing, and DuckDuckGo."

Skills fired: dispatch → serpapi-tool (3 engine calls)

Output:
CROSS-ENGINE LOCAL VISIBILITY

             | Google    | Bing      | DuckDuckGo
-------------|-----------|-----------|------------
Local pack   | #2        | #5        | #4
Organic      | #4        | #11       | #8
SERP features| AI Overview, PAA | None | None

KEY FINDING: Strong Google presence does not translate to Bing/DDG.
Bing weakness likely affects ChatGPT Browse recommendations.

ACTION PRIORITY: Optimize Bing Places listing. A single improvement
affects both Bing and DuckDuckGo visibility, plus ChatGPT Browse context.

SERP Feature Mapping Across Keywords

Monitoring which SERP features appear across a keyword set informs where to focus optimization effort.

Prompt: "What SERP features are showing for our top 5 keywords in the
Denver HVAC market?"

Skills fired: dispatch → serpapi-tool (5 queries)

Output:
SERP FEATURE MAP: Denver HVAC Keywords

Keyword                    | LP | LSA | AIO | PAA | FS | KP
---------------------------|----|----|-----|-----|----|----
"HVAC repair Denver"       | Y  | Y  | Y   | Y   | N  | N
"AC installation Denver"   | Y  | Y  | N   | Y   | Y  | N
"furnace repair Denver"    | Y  | N  | Y   | Y   | N  | N
"heating and cooling Denver"| Y | Y  | N   | Y   | N  | N
"emergency HVAC Denver"    | Y  | Y  | Y   | Y   | N  | N

LP=Local Pack, LSA=Local Services Ads, AIO=AI Overview,
PAA=People Also Ask, FS=Featured Snippet, KP=Knowledge Panel

STRATEGIC NOTES:
- AI Overviews present for 3/5 keywords — ai-local-search strategy relevant
- LSA present for 4/5 keywords — LSA campaign opportunity
- Featured snippet only for "AC installation" — content opportunity

When to Use SerpAPI vs LocalSEOData

Use localseodata-tool (default) when:

  • Running audits with structured local SEO data
  • Analyzing local pack composition for competitive research
  • Pulling keyword data, citation data, review data, or AI visibility metrics
  • Standard workflows where you need organized, endpoint-specific data

Use serpapi-tool when:

  • Verifying live SERP state after changes (real-time confirmation)
  • Investigating ranking discrepancies between tools and reality
  • Analyzing Bing, DuckDuckGo, or Yahoo local results
  • Checking SERP feature presence across queries
  • LocalSEOData is not connected or credits are depleted
  • You need to see exactly what a searcher sees right now

LocalSEOData is the analytical foundation. SerpAPI is the live verification layer and the multi-engine specialist. Most workflows use LocalSEOData. SerpAPI activates when you need ground truth about what is actually happening in search results at this moment or when you need non-Google data.

Connecting SerpAPI to LocalSEOSkills

  1. SerpAPI account from serpapi.com (free tier available for testing, paid plans for production)
  2. API key from SerpAPI dashboard
  3. In Claude Code, add the MCP server:
{
  "mcpServers": {
    "serpapi": {
      "url": "https://serpapi.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
  1. Restart Claude Code
  2. Verify connection:
Run a live Google local pack query for "plumber Phoenix" through SerpAPI.

Each SerpAPI call consumes one search credit regardless of engine. Multi-engine comparisons across 3 engines consume 3 credits per query.

Get Started

Pull the live SERP for [keyword] in [city] and show me everything:
local pack, organic results, SERP features, and any AI Overview content.

This returns the complete SERP layout as it appears right now. Real-time data, no caching, no personalization. If you see a complete SERP breakdown with features, positions, and business names, the integration is working.

Learn More

To learn what this skill can do for your local SEO workflow, see the skill overview.