# SEO Data Sources

> Choose and document SEO data sources and MCP/provider boundaries for audits. Use when Codex needs to decide between local scripts, Firecrawl, Google Search Console, PageSpeed Insights, CrUX, DataForSEO, SE Ranking, Ahrefs, browser checks, or paid/live integrations; or when SEO findings require explicit source, cost, account, API-key, and confidence boundaries.

- Skill: `majiayu000/seo-data-sources` (Agent Skill)
- Install (CLI): `npx skillmds@latest add majiayu000/seo-data-sources`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/seo-data-sources/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/majiayu000/seo-data-sources

---


# SEO Data Sources

Use this skill before relying on external SEO data. Read `references/data-sources.md` (resolved from the suite/plugin root) first.

## Workflow

1. State the claim that needs proof.
2. Pick the smallest source that can prove it.
3. Verify whether the provider is installed/authenticated in the current environment.
4. If unavailable, mark it as a blocker or hypothesis, not a confirmed finding.
5. Attach the data source to each SEO claim.

## Provider Roles

- Local scripts: repo/package/site metadata and crawlability baseline.
- Firecrawl: rendered crawl and competitor page extraction.
- Google Search Console: owned-site indexing, queries, impressions, sitemap submission.
- PageSpeed/CrUX: lab and field performance evidence.
- DataForSEO: keyword, SERP, and competitor data via API.
- SE Ranking: packaged SEO/GEO workflows and share-of-voice style reporting.
- Ahrefs: backlinks, content gap, competing pages, and authority estimates.

## Output

A short data-source decision record: the claim, the chosen source, why the
smaller sources were insufficient, access status (installed / needs auth /
unavailable), and cost boundary. Attach it to the audit report or issue.

## Failure Handling

- If no available source can prove the claim, report it as `Hypothesis` with
  the missing provider named as a blocker. Do not downgrade silently to a
  weaker source without recording the substitution.

## Rules

- Do not present optional MCPs as installed without current proof.
- Do not use crawl data as ranking data.
- Do not use Search Console without explicit account/browser/API access.
- Do not put API keys in repo files, reports, prompts, or screenshots.