Tool Integration

Screaming Frog + Claude: Technical Audits for Location Pages

Internal technical issues that suppress local landing pages. Schema verification at scale. Duplicate content across locations. The crawl data layer.

Get on GitHub

Screaming Frog Tool Integration: Technical SEO for Location Pages

LocalSEOData analyzes the external SERP landscape. GSC measures organic performance. GA4 tracks conversions.

None of them see inside the website.

Screaming Frog crawls the site itself — finding technical issues that suppress local landing page rankings and are completely invisible to external tools.

Broken internal links between location pages. Redirect chains that bleed PageRank. Missing schema on 12 of 35 location pages. Duplicate content across location pages because someone copy-pasted and only changed the city name. Pages excluded from the sitemap that Google doesn’t know exist.

These issues don’t show up in rankings data until they’ve already cost you months of traffic.

What This Integration Unlocks

Location page technical audit — Not generic technical SEO. Issues that specifically affect local landing page performance.

Schema verification at scale — Check LocalBusiness schema implementation across 5, 50, or 500 location pages in one crawl.

Duplicate content detection — Identify location pages that are too similar to rank independently — before Google decides for you.

Internal linking analysis — Find orphaned location pages, broken location-to-location links, and internal link opportunities.

Dispatch Routing

Routes to screaming-frog-tool when:

  • Prompt involves technical site audit
  • Location pages are underperforming for technical (not content or GBP) reasons
  • Schema implementation needs verification across all location pages
  • Practitioner explicitly requests Screaming Frog

Works alongside local-schema and local-landing-pages skills for interpretation.

Three Workflows

Workflow 1 — Location Page Technical Audit:

Prompt: "Run a Screaming Frog audit on smithlaw.com focused on location pages.
What technical issues are suppressing their performance?"

Output:
LOCATION PAGE TECHNICAL AUDIT — smithlaw.com
Crawled: 47 pages matching /locations/* and /*-office/

CRITICAL ISSUES (Fix immediately):

Missing from XML Sitemap (3 pages):
- /locations/wheaton/ — not in sitemap.xml
- /locations/downers-grove/ — not in sitemap.xml
- /locations/aurora/ — not in sitemap.xml
Impact: Google may not crawl these pages regularly

Redirect Chains (2 pages):
- /chicago-office → /locations/chicago-office → /locations/chicago/
  3-hop redirect, PageRank dilution
- /naperville-office → /locations/naperville-office → /locations/naperville/
  Same issue

Broken Internal Links (4 instances):
- /locations/oak-park/ links to /chicago-office (404)
- /practice-areas/personal-injury/ links to /evanston-office (404)
- [2 more listed]

HIGH PRIORITY:

Missing H1 Tags (6 pages):
- /locations/skokie/
- /locations/evanston/
- [4 more listed]

Thin Content (5 pages under 300 words):
- /locations/lincolnwood/ — 187 words
- /locations/niles/ — 212 words
- [3 more listed]

Duplicate Title Tags (3 pairs):
- /locations/oak-park/ and /locations/forest-park/ — identical title
- [2 more pairs]

Workflow 2 — Schema Verification at Scale:

Prompt: "Use Screaming Frog's custom extraction to verify LocalBusiness schema
is correctly implemented on all 35 location pages of smithlaw.com."

Output:
SCHEMA VERIFICATION — smithlaw.com (35 Location Pages)

Schema Implementation Status:
- Correct implementation: 23 pages (66%)
- Missing schema entirely: 7 pages (20%)
- Schema errors: 5 pages (14%)

MISSING SCHEMA (7 pages):
/locations/wheaton/
/locations/downers-grove/
/locations/aurora/
/locations/lincolnwood/
/locations/niles/
/locations/morton-grove/
/locations/park-ridge/

SCHEMA ERRORS (5 pages):

/locations/evanston/:
- Missing: telephone
- Missing: openingHoursSpecification
- @type: "LegalService" (should be "Attorney" or "LegalService" with
  appropriate properties)

/locations/skokie/:
- Invalid: address.addressRegion = "Illinois" (should be "IL")
- Missing: geo coordinates

/locations/oak-park/:
- Duplicate @id values (conflicts with /locations/forest-park/)

[2 more pages with specific errors]

CORRECTED SCHEMA for Evanston:
{
  "@context": "https://schema.org",
  "@type": "Attorney",
  "@id": "https://smithlaw.com/locations/evanston/#organization",
  "name": "Smith Law - Evanston Office",
  "telephone": "+1-312-555-1234",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1847 Central Street",
    "addressLocality": "Evanston",
    "addressRegion": "IL",
    "postalCode": "60201"
  },
  "openingHoursSpecification": [...]
}

Workflow 3 — Multi-Location Duplicate Content Check:

Prompt: "Check smithlaw.com's location pages for duplicate content issues
using Screaming Frog. Which pages are too similar to rank independently?"

Output:
DUPLICATE CONTENT ANALYSIS — smithlaw.com Location Pages

Near-Duplicate Pairs (>80% similarity):

/locations/oak-park/ vs /locations/forest-park/
Similarity: 94%
Issue: Body content identical except city name
Risk: Google may consolidate or suppress both

/locations/lincolnwood/ vs /locations/niles/
Similarity: 91%
Issue: Same template, same testimonials, same attorney bio
Risk: Neither page has unique ranking signals

/locations/skokie/ vs /locations/evanston/
Similarity: 87%
Issue: Same practice area descriptions, same case results
Risk: Internal competition, neither ranks well

High-Similarity Clusters (70-80%):
- Aurora/Naperville/Wheaton cluster (73-78% similar)
- Morton Grove/Park Ridge/Niles cluster (71-76% similar)

DIFFERENTIATION REQUIREMENTS:

For Oak Park vs Forest Park (94% similar):
Currently identical:
- Practice area descriptions
- Attorney bios
- Testimonials
- Case results

Differentiation needed:
1. Unique local content: Oak Park courthouse info, Forest Park parking
2. Location-specific testimonials (or remove from one)
3. Neighborhood-specific service descriptions
4. Local landmark references
5. Different featured case results

Target: Below 70% similarity for independent ranking

Word count requirements:
- Current average: 340 words
- Recommended minimum: 800 words with 50%+ unique content per page

Setup

  1. Screaming Frog license (paid version required for API mode)
  2. Enable API mode in Screaming Frog preferences
  3. In Claude Code: Settings → MCP Servers → Add Server
    • Name: Screaming Frog
    • Endpoint: Local API endpoint from Screaming Frog
  4. Verify connection

First Prompt After Setup

"Initiate a test crawl of [single URL] via Screaming Frog to confirm connection.
Return page title, H1, word count, and schema presence."

Skill Documentation

For technical details on how this skill works, what data it pulls, and complete prompt reference, see the full skill documentation.

All 36 skills. Free. Open source. Get on GitHub →