agentleFS
ahmedaminsaahmedaminsa/aljazeera360-mcp-server/.claude/skills/seo-maps/SKILL.md

seo-maps

Skill0 starsChanged 3 months agoMITView on GitHub

Maps intelligence for local SEO: geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification, competitor radius mapping, and LocalBusiness schema generation. Three tiers: free (Overpass + Geoapify), DataForSEO, and DataForSEO + Google. Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", or "SoLV".

20 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, blog-brand and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 4 projects that use this

  • gaznilmuzammil12-progSkill

    blog-brand

    Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

    Also in 3 projects that use this

  • gaznilmuzammil12-progSkill

    blog-cannibalization

    Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports local-only mode (grep-based) and DataForSEO API mode (Page Intersection endpoint at ~$0.01/call). Outputs severity-scored report with merge or differentiate recommendations. Use when user says "cannibalization", "keyword overlap", "competing pages", "duplicate keywords", "cannibalize".

    Also in 3 projects that use this

  • megastepSkill

    blog-calendar

    Generate editorial calendars for blogs with topic clusters, publishing schedules, content decay detection, freshness update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars optimized for SEO topic authority and AI citation freshness requirements (30-day update cycles). Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".

    Also in 3 projects that use this

  • megastepSkill

    blog-chart

    Generate dark-mode-compatible inline SVG data visualization charts for blog posts. Supports horizontal bar, grouped bar, donut, line, lollipop, area, and radar charts with automatic platform detection (HTML vs JSX/MDX). Enforces chart type diversity, accessible markup (role=img, aria-label), source attribution, and transparent backgrounds. Use when user says "blog chart", "generate chart", "data visualization", "svg chart", "blog graph", "visualize data", or when the blog-write workflow identifies chart-worthy data points (3+ comparable metrics, trends, before/after data).

    Also in 3 projects that use this

  • +6 more from gaznilmuzammil12-prog
  • +1 more from megastep

The file

We split this skill into the rules it gives an agent

10 rules. 6 are common, 0 are distinctive, and 4 are very specific to this project.

  • 6

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not duplicate seo-local on-page analysis.

    line 28
  2. Common:

    Before any analysis, detect the available capability tier:

    line 49
  3. Common:

    Before every geo-grid scan, display:

    line 90
  4. Common:

    Check 18-day rule (Sterling Sky): any 3-week gap = ranking risk

    line 143
  5. Common:

    Use Maps SERP API with business keyword + location

    line 176
  6. Common:

    Check business listing consistency across Google, Bing Places, Apple, and OSM.

    line 185
  7. Common:

    Search for business name on each platform:

    line 189
  8. Very specific:

    Add recommended properties: telephone, url, geo, openingHoursSpecification, priceRange

    line 211
  9. Very specific:

    Add strategic properties for multi-location: branchOf, areaServed, sameAs

    line 212
  10. Very specific:

    Add aggregateRating if review data available

    line 213

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Maps Intelligence (March 2026)

Maps platform analysis for local businesses. Works with external APIs to assess how a business appears on Google Maps, Bing Places, Apple Maps, and OpenStreetMap.

Boundary with seo-local: This skill analyzes the business on maps PLATFORMS (via APIs). seo-local analyzes local SEO signals on the WEBSITE (via HTML fetch). Do not duplicate seo-local on-page analysis. Recommend /seo local <url> for website-level checks.


Quick Reference

CommandWhat it doesTier
/seo maps <url>Full maps presence audit (auto-selects tier)0+
/seo maps grid <keyword> <location>Geo-grid rank scan (7x7, 1 keyword default)1+
/seo maps reviews <business> <location>Cross-platform review intelligence1+
/seo maps competitors <keyword> <location>Competitor radius mapping0+
/seo maps nap <business-name>Cross-platform NAP verification0+
/seo maps schema <business-name>Generate LocalBusiness JSON-LD from data0+
/seo maps gbp <business> <location>GBP completeness audit1+

Three-Tier Capability Detection

Before any analysis, detect the available capability tier:

Tier 0 (Free)

Detection: DataForSEO MCP tools NOT available. Capabilities: Overpass API competitor discovery, Geoapify POI search, Nominatim geocoding, static GBP checklist, schema generation, cross-platform NAP guidance. Load: ../seo/references/maps-free-apis.md

Tier 1 (DataForSEO)

Detection: business_data_business_listings_search MCP tool IS available. Capabilities: Everything in Tier 0 PLUS geo-grid rank tracking, live GBP profile audit, review intelligence (velocity, sentiment, distribution), GBP post activity, Q&A data, Tripadvisor/Trustpilot reviews. Load: ../seo/references/maps-api-endpoints.md

Tier 2 (DataForSEO + Google Maps Platform)

Detection: Tier 1 available AND Google Maps API key in environment. Capabilities: Everything in Tier 1 PLUS Google Places details, real-time business status, AI-powered place summaries, photo analysis. Note: Google ToS restricts storage to place_id only. Lat/lng cached 30 days max.

Always communicate the detected tier to the user at the start of analysis.


Geo-Grid Rank Tracking (Tier 1+)

Simulates Google Maps searches from multiple GPS coordinates to show ranking variation across a geographic area. Requires DataForSEO.

Load: ../seo/references/maps-geo-grid.md for algorithm, SoLV formula, heatmap format. Load: ../seo/references/maps-api-endpoints.md for Maps SERP endpoint details.

Workflow

  1. Geocode business address to get center lat/lng
  2. Generate grid points (default: 7x7, 5km radius) using Haversine offset formula
  3. Display cost estimate and ask for confirmation before proceeding
  4. Fire DataForSEO Maps SERP API calls with location_coordinate per grid point
  5. Find target business rank at each point
  6. Calculate SoLV: (top_3_count / total_points) * 100
  7. Render ASCII heatmap in output

Cost Warning (REQUIRED)

Before every geo-grid scan, display:

Geo-Grid Scan: [keyword] at [location]
Grid: 7x7 (49 points) | Keywords: [N] | Est. cost: $[amount]
DataForSEO credits will be consumed. Proceed?

GBP Profile Audit (Tier 1 preferred, Tier 0 manual)

Audits the 25 fields that affect Google Business Profile quality and ranking.

Load: ../seo/references/maps-gbp-checklist.md for full checklist and scoring.

AI & 2026 context (third-party reported): Ask Maps, reported by AP News as a Gemini conversational Maps feature launched 2026-03-12 (iOS/Android, US + India). AI Mode (1B+ MAU, reported from Google I/O 2026 keynote coverage; not confirmed on a Google-owned source) increasingly surfaces 1-2 business local AI interfaces in third-party terminology, and agentic booking/calling for local services (home repair, beauty, pet care) rolls out to all US users summer 2026 (Google can call businesses on the user's behalf). New 2026 GBP API additions: review media URLs, recurring local-post scheduling, review reply-state/moderation, and invitation Place ID. Source: blog.google/products-and-platforms/products/search/search-io-2026/ · developers.google.com/my-business/content/latest-updates

Tier 1 Workflow

  1. Fetch business profile via DataForSEO My Business Info API (keyword or CID)
  2. Map API response fields to 25-field checklist
  3. Score each field: Present + Optimized = 2pts, Present = 1pt, Missing = 0pts
  4. Apply industry-specific weight multipliers
  5. Normalize to 0-100 scale

Tier 0 Workflow

  1. Fetch the business website via WebFetch
  2. Extract any visible GBP signals (Maps embed, place references, review widgets)
  3. Apply static checklist based on detectable signals
  4. Mark undetectable fields as "Unknown (requires DataForSEO for live data)"

Review Intelligence (Tier 1+)

Cross-platform review analysis: velocity, sentiment, rating distribution, fake detection.

Reference: ../seo/references/local-seo-signals.md for benchmarks (shared with seo-local).

Workflow

  1. Fetch Google reviews via DataForSEO Reviews API (sort by newest)
  2. Calculate review velocity: reviews per month over last 6 months
  3. Check 18-day rule (Sterling Sky): any 3-week gap = ranking risk
  4. Analyze rating distribution: healthy = bell curve skewed to 5-star
  5. Calculate owner response rate: responses / total reviews
  6. Fetch Tripadvisor and Trustpilot reviews (if available)
  7. Cross-platform comparison table

Fake Review Detection Signals

Flag reviews matching 2+ of these patterns:

  • Uniform timing (multiple reviews same day/hour)
  • Reviewer accounts with limited history or single review
  • Geographic inconsistencies (reviewer location vs business location)
  • Exclusively 5-star velocity spike (vs historical baseline)
  • Identical or near-identical text across reviews
  • Sudden volume spike without corresponding marketing activity

Competitor Radius Mapping (Tier 0+)

Identify and analyze competitors within a defined radius.

Tier 0 (Overpass API)

Load: ../seo/references/maps-free-apis.md for query templates.

  1. Geocode business address
  2. Query Overpass API for businesses with same OSM tag within radius
  3. Parse results: name, address, phone, website, distance from center
  4. Sort by distance, present as competitor landscape table

Tier 1 (DataForSEO)

  1. Use Maps SERP API with business keyword + location
  2. Extract top 20 competitors with full profile data
  3. Compare: rating, review count, categories, photos, attributes
  4. Calculate competitive density score: competitors per km^2

Cross-Platform NAP Verification (Tier 0+)

Check business listing consistency across Google, Bing Places, Apple, and OSM.

Workflow

  1. Search for business name on each platform:
    • Google: infer from GBP data or Maps SERP result
    • Bing: WebFetch https://www.bing.com/maps?q=BUSINESS+NAME+LOCATION
    • Apple: manual check (no public API -- verify/claim Apple business listing presence; treat Apple Business launch/rename claims as TechRadar-sourced until confirmed by Apple primary)
    • OSM: Overpass or Nominatim search
  2. Extract NAP (Name, Address, Phone) from each source
  3. Compare for consistency: exact match, partial match, missing, or conflicting
  4. Flag discrepancies as Critical (name mismatch), High (address mismatch), Medium (phone mismatch)
  5. Recommend claiming unclaimed profiles

Schema Generation (Tier 0+)

Generate LocalBusiness JSON-LD markup from collected data.

Reference: ../seo/references/local-schema-types.md for industry subtypes (shared with seo-local).

Workflow

  1. Determine most specific schema subtype for the industry
  2. Populate required properties: @type, name, address, image
  3. Add recommended properties: telephone, url, geo, openingHoursSpecification, priceRange
  4. Add strategic properties for multi-location: branchOf, areaServed, sameAs
  5. Add aggregateRating if review data available
  6. Output valid JSON-LD block ready for implementation

Do NOT generate self-serving review markup -- Google ignores LocalBusiness review markup from the business itself. Only mark up third-party reviews visible on the page.


Reference Files

Load on-demand as needed (do NOT load all at startup):

  • ../seo/references/maps-api-endpoints.md: DataForSEO endpoint details, params, costs
  • ../seo/references/maps-free-apis.md: Overpass, Geoapify, Nominatim query templates
  • ../seo/references/maps-geo-grid.md: Grid algorithm, SoLV formula, heatmap rendering
  • ../seo/references/maps-gbp-checklist.md: 25-field GBP audit with industry weights
  • ../seo/references/local-seo-signals.md: Ranking factors, review benchmarks (shared)
  • ../seo/references/local-schema-types.md: LocalBusiness subtypes by industry (shared)

Output

Generate MAPS-ANALYSIS-{domain}.md with:

  1. Maps Health Score: XX/100 with dimension breakdown table
  2. Capability tier detected (Tier 0 or Tier 1) with explanation of what's available
  3. Geo-grid heatmap (Tier 1): ASCII grid with SoLV percentage and average rank
  4. GBP profile audit: field-by-field scoring with industry-specific weights
  5. Review intelligence: velocity chart, rating distribution, response rate, cross-platform comparison
  6. Competitor landscape: count in radius, top 5 by rating/reviews, competitive density
  7. Cross-platform presence: Google/Bing/Apple/OSM listing status
  8. Schema recommendation: generated LocalBusiness JSON-LD (if missing or incomplete)
  9. Top 10 prioritized actions (Critical > High > Medium > Low)
  10. Cost report: DataForSEO credits consumed during analysis (Tier 1 only)
  11. Limitations disclaimer: what could not be assessed at current tier

Cross-Skill Delegation

  • Website on-page local signals: recommend /seo local <url>
  • Full AI search visibility: recommend /seo geo <url>
  • Schema validation and fixes: recommend /seo schema <url>
  • Live SERP and keyword data: recommend /seo dataforseo [command]

Error Handling

ScenarioAction
DataForSEO MCP not availableDrop to Tier 0. Inform user: "DataForSEO not detected. Running free-tier analysis. For geo-grid tracking and review intelligence, install the DataForSEO extension."
Business not found in Maps SERPTry My Business Info with keyword. If still not found, report "Business not found in Google Maps for this location."
Geocoding fails (Nominatim)Ask user to provide coordinates or a more specific address.
API rate limit hitReport the limit. Suggest waiting or using standard (queued) method instead of live.
No reviews foundReport zero review state. Recommend review generation strategy with 18-day cadence target.
Multi-location detectedAsk user which location to analyze, or offer batch mode with per-location cost estimate.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.