
Seo Firecrawl
- 26 installs
- 548 repo stars
- Updated July 20, 2026
- agricidaniel/codex-seo
seo-firecrawl is a Claude Code SEO skill that uses the Firecrawl MCP to crawl, map, scrape, and search entire websites for site-wide SEO analysis.
About
seo-firecrawl is a Claude Code skill that drives the Firecrawl MCP server to crawl, map, scrape, and search entire websites for SEO analysis. A developer uses it to discover all pages, detect broken links and orphan pages, and extract page content (including JavaScript-rendered SPAs) at scale. It exists so site-wide SEO audits get real crawl data rather than single-page fetches.
- Wraps the Firecrawl MCP to crawl, map, scrape, and search whole sites for SEO audits
- Renders JavaScript so SPA/React/Vue pages can be inventoried and analyzed
- Feeds crawled content to sibling seo-technical, seo-content, and seo-schema skills
Seo Firecrawl by the numbers
- 26 all-time installs (skills.sh)
- Ranked #1,441 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
seo-firecrawl capabilities & compatibility
Free tier 500 Firecrawl credits/month (1 credit = 1 page); paid plans for larger crawls
- Capabilities
- site crawl · site map · broken link detection · orphan page detection · content inventory · seo audit
- Use cases
- web scraping · seo · web search
- Pricing
- Freemium
What seo-firecrawl says it does
Full-site crawling, scraping, and site mapping via Firecrawl MCP.
SPA/JS-rendered sites**: Firecrawl renders JavaScript, solving the Issue #11 problem
Free tier: 500 credits/month
npx skills add https://github.com/agricidaniel/codex-seo --skill seo-firecrawlAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 26 |
|---|---|
| repo stars | ★ 548 |
| Last updated | July 20, 2026 |
| Repository | agricidaniel/codex-seo ↗ |
What it does
Crawl and map a full website to find broken links, orphan pages, and thin content before an SEO audit.
Who is it for?
Site-wide SEO crawls, broken-link and orphan-page detection, and inventorying JS-rendered pages
Skip if: Single static-page checks where fetch_page.py works with no API cost
When should I use this skill?
user says crawl site, map site, full crawl, find all pages, broken links, or site structure
What you get
A full inventory of a site's URLs, structure, broken links, and rendered page content ready to feed into SEO sub-skills.
- Full-site crawl output
- Site URL map with pattern breakdown
- Broken-link and orphan-page findings
By the numbers
- Free tier: 500 credits/month
- Crawl limit default 100, max 500 pages
- Map default limit 5000 URLs
Files
Firecrawl Extension for Codex SEO
Shared Data Cache
Step 0 -- Check shared data cache:
Before gathering, check .seo-cache/ for reusable context from related SEO skills. Reference: ../seo/references/shared-data-cache.md for schemas and dependency map.
Check these cache files when present:
.seo-cache/site-meta.jsonfor domain, business type, industry, and crawl context.seo-cache/audit-scores.jsonfor prior full-audit priorities.seo-cache/pages/{url-slug}/page-analysis.jsonfor page-level context when a URL is provided
- If found: parse and use clearly valid fields (note "Using cached [X] from [date]")
- If missing, corrupt, or irrelevant: continue with fresh evidence
- If the user says "refresh" or "re-run": ignore cache reads and overwrite on write
This skill requires the Firecrawl extension to be installed:
./extensions/firecrawl/install.shCheck availability: Before using any Firecrawl tool, verify the MCP server is connected by checking if firecrawl_scrape or any Firecrawl tool is available. If tools are not available, inform the user the extension is not installed and provide install instructions.
Quick Reference
| Command | Purpose |
|---|---|
/seo firecrawl crawl <url> | Full-site crawl with content extraction |
/seo firecrawl map <url> | Discover site structure (URLs only, fast) |
/seo firecrawl scrape <url> | Single-page scrape with JS rendering |
/seo firecrawl search <query> <url> | Search within a crawled site |
Commands
crawl -- Full-Site Crawl
Crawl an entire website starting from the given URL. Returns page content, metadata, and links for all discovered pages.
MCP Tool: firecrawl_crawl
Parameters:
url(required): Starting URL to crawllimit: Max pages to crawl (default: 100, max: 500)maxDepth: Max link depth from start URL (default: 3)includePaths: Array of glob patterns to include (e.g.,["/blog/*"])excludePaths: Array of glob patterns to exclude (e.g.,["/admin/*", "/api/*"])scrapeOptions.formats: Output formats --["markdown", "html", "links"]
SEO Usage Patterns: 1. Comprehensive audit crawl: Crawl full site, extract all pages for subagent analysis 2. Section-focused crawl: Use includePaths to audit only /blog/* or /products/* 3. Broken link detection: Crawl with ["links"] format, check all hrefs for 404s 4. Content inventory: Extract all page titles, meta descriptions, H1s at scale 5. SPA/JS-rendered sites: Firecrawl renders JavaScript, solving the Issue #11 problem
Example orchestration for `/seo audit`:
1. firecrawl_map(url) -> get all URLs (fast, no content)
2. Filter to top 50 most important pages (homepage, key sections)
3. firecrawl_crawl(url, limit=50) -> get full content
4. Feed content to seo-technical, seo-content, seo-schema agentsCost awareness:
- Free tier: 500 credits/month
- 1 credit = 1 page crawled or scraped
- Map operations are cheaper (0.5 credits per URL discovered)
- Always inform user of estimated credit usage before large crawls
map -- Site Structure Discovery
Discover all URLs on a website without fetching content. Fast and credit-efficient.
MCP Tool: firecrawl_map
Parameters:
url(required): Website URL to maplimit: Max URLs to discover (default: 5000)search: Optional search term to filter URLs
SEO Usage Patterns: 1. Sitemap comparison: Map site, compare discovered URLs vs XML sitemap 2. Orphan page detection: URLs in sitemap but not linked from any page 3. Crawl budget analysis: Total indexable pages vs pages linked from homepage 4. URL pattern analysis: Identify URL structure patterns, duplicates, parameter bloat 5. Pre-audit discovery: Run map first, then targeted crawl on key sections
Output: Array of URLs. Present as:
Site: example.com
Pages discovered: 342
URL Pattern Breakdown:
/blog/* - 128 pages (37%)
/products/* - 89 pages (26%)
/category/* - 45 pages (13%)
/pages/* - 32 pages (9%)
/ (root pages) - 48 pages (14%)scrape -- Single-Page Deep Scrape
Scrape a single page with full JavaScript rendering. More thorough than fetch_page.py because it executes JS and waits for dynamic content.
MCP Tool: firecrawl_scrape
Parameters:
url(required): Page URL to scrapeformats: Output formats --["markdown", "html", "links", "screenshot"]onlyMainContent: Strip nav/footer/sidebar (default: true)waitFor: CSS selector or milliseconds to wait for contenttimeout: Request timeout in ms (default: 30000)actions: Browser actions before scraping (click, scroll, wait)
SEO Usage Patterns: 1. SPA content extraction: Scrape JS-rendered React/Vue/Angular pages 2. Dynamic content audit: Pages with lazy-loaded content below the fold 3. Paywall/login detection: Identify content behind authentication walls 4. Main content extraction: Use onlyMainContent for clean E-E-A-T analysis 5. Screenshot capture: Use screenshot format for visual analysis
When to use scrape vs fetch_page.py:
| Scenario | Use |
|---|---|
| Static HTML page | fetch_page.py (no API cost) |
| JS-rendered SPA | firecrawl_scrape (renders JS) |
| Need response headers | fetch_page.py (returns headers) |
| Need clean markdown | firecrawl_scrape (better extraction) |
| Rate-limited/blocked | firecrawl_scrape (handles anti-bot) |
search -- Site-Scoped Search
Search within a website for specific content. Useful for finding pages related to a topic without crawling everything.
MCP Tool: firecrawl_search
Parameters:
query(required): Search queryurl(required): Website to search withinlimit: Max results (default: 10)scrapeOptions.formats: Output format for matched pages
SEO Usage Patterns: 1. Content gap validation: Search for a keyword on the site to check if content exists 2. Internal linking opportunities: Find pages mentioning a topic that could link to each other 3. Duplicate content detection: Search for key phrases to find near-duplicates 4. Competitor content research: Search competitor site for specific topics
Cross-Skill Integration
With seo-audit (full audit)
When Firecrawl is available during /seo audit: 1. Use firecrawl_map to discover all site URLs 2. Compare with XML sitemap (seo-sitemap) to find orphan/missing pages 3. Select top pages for deep analysis 4. Feed crawled content to all subagents (technical, content, schema, geo) 5. Report total crawlable pages, URL patterns, and crawl depth
With seo-technical
- Broken link detection: crawl all internal links, check for 404s
- Redirect chain mapping: follow all redirects, flag chains > 2 hops
- Mixed content detection: check HTTP resources on HTTPS pages
- Canonical verification: compare canonical URLs with actual URLs
With seo-sitemap
- Sitemap coverage: % of crawled pages present in sitemap
- Orphan pages: pages found by crawl but missing from sitemap
- Stale sitemap entries: URLs in sitemap that return 404/410
With seo-content
- Content extraction: feed clean markdown to E-E-A-T analysis
- Thin content detection: identify pages with < 300 words at scale
- Duplicate content: compare content across pages for near-duplicates
With seo-schema
- Schema extraction: pull JSON-LD from all crawled pages
- Schema coverage: % of pages with structured data
- Schema validation: batch-validate extracted schemas
Error Handling
| Error | Cause | Resolution |
|---|---|---|
FIRECRAWL_API_KEY not set | MCP not configured | Run ./extensions/firecrawl/install.sh |
402 Payment Required | Credits exhausted | Check usage at firecrawl.dev/app, upgrade plan |
429 Too Many Requests | Rate limited | Wait 60s, reduce crawl concurrency |
408 Timeout | Page too slow to render | Increase timeout, try without JS rendering |
403 Forbidden | Site blocks crawling | Check robots.txt, may need to skip this site |
Graceful fallback: If Firecrawl is unavailable, inform the user and suggest: 1. Use fetch_page.py for single-page analysis (no API cost) 2. Use WebFetch tool for basic HTML retrieval 3. Install Firecrawl: ./extensions/firecrawl/install.sh
Write to shared data cache
After completing all work, write a concise JSON summary to .seo-cache/ when the workflow produced durable findings. Use the schemas and naming rules in ../seo/references/shared-data-cache.md; include at least cache_type, analyzed_at, source URL/domain, key findings, issues, recommendations, and tool limitations. Add .seo-cache/ to .gitignore if it is missing.
MIT License - see repository root LICENSE file for complete terms.
Copyright (c) 2026 AgriciDaniel
https://github.com/AgriciDaniel/codex-seo
Related skills
FAQ
Does seo-firecrawl need a separate service?
Yes. It requires the Firecrawl MCP server and a FIRECRAWL_API_KEY; the free tier gives 500 credits/month where 1 credit equals 1 page crawled or scraped.
Can it handle JavaScript-rendered pages?
Yes. Firecrawl renders JavaScript, so React, Vue, and Angular SPAs can be scraped and inventoried, unlike a plain HTML fetch.