# Seo Subdomain

> Mapa de propiedad de subdominios de un dominio: lista subdominios, cruza overview/keywords/competidores/backlinks y detecta qué subdominio domina cada tema, fragmentación y si conviene consolidar.

Fuente: https://skillsagentes.com/skills/seranking/seo-skills/seo-subdomain
Markdown: https://skillsagentes.com/skills/seranking/seo-skills/seo-subdomain.md

Repositorio: https://github.com/seranking/seo-skills
Autor: seranking
Licencia: MIT
Actualizado: hace 4 meses
Coste de contexto: 104 tok instalada, 2.1k tok al activarse, 2.1k tok con todos los archivos del bundle
Bundle: 1 archivo, 8 KB
Permisos que pide: ninguno declarado

## Instalación

Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina.

```bash
# Claude Code
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent claude-code
# Cursor
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent cursor
# Codex
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent codex
# Gemini CLI
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent gemini
# Windsurf
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent windsurf
# Cline
npx -y skills add seranking/seo-skills --skill seo-subdomain --agent cline
```

## Qué hace

- Descubre todos los subdominios de un dominio raíz vía DATA_getDomainSubdomains
- Analiza overview, keywords, competidores y backlinks por cada subdominio
- Detecta fragmentación y cannibalización entre subdominios para el mismo topic cluster
- Genera un mapa de propiedad de temas (topic ownership) y recomendaciones de consolidar/dividir/dejar igual
- Crea una carpeta con SUBDOMAINS.md, mapa de ownership, flags de fragmentación y evidencia cruda

## Cuándo usarla

- El usuario pide 'subdomain analysis', 'subdomain ownership' o 'subdomain SEO'
- Se pregunta 'blog vs main domain' o 'support vs docs subdomain'
- Se plantea si conviene consolidar subdominios

## Qué la activa

- "Analiza los subdominios de example.com y dime si hay cannibalización"
- "¿Debería consolidar blog.example.com con el dominio principal?"
- "Hazme un mapa de ownership de temas entre docs, blog y support de mi dominio"

## Antes de instalar

- Requiere el servidor MCP de SE Ranking conectado y un dominio raíz objetivo; opcionalmente se puede limitar el número de subdominios con --limit.

## Archivos

- SKILL.md — 8 KB

## SKILL.md

Reproducido tal cual desde seranking/seo-skills bajo MIT. Esta sección es el documento original y está en inglés.

> Example output: [examples/seo-subdomain-notion-so-20260514/SUBDOMAINS.md](../../examples/seo-subdomain-notion-so-20260514/SUBDOMAINS.md)

# Subdomain Analysis

Map a domain's subdomain ecosystem. Which subdomains exist, what each ranks for, where they overlap, and whether the structure is healthy or fragmented. Output: an ownership map (which topic is owned by which subdomain), a fragmentation report, and recommendations for consolidate / split / leave alone.

## Prerequisites

- SE Ranking MCP server connected.
- User provides: a target root domain (e.g. `example.com`). The skill discovers subdomains automatically.
- Optional: `--limit N` to cap the number of subdomains analysed (default: top 10 by ranked keyword count).

## Process

1. **Validate & preflight**
   - Normalise root domain (no protocol, no `www.`).
   - `DATA_getCreditBalance` — surface remaining credits. Subdomain analysis is N × ~5 calls; cost scales with subdomain count.

2. **Discover subdomains** `DATA_getDomainSubdomains`
   - List all subdomains of the root domain.
   - For each: keyword count, traffic estimate, backlinks count.
   - Sort by ranked-keyword count descending.
   - Apply `--limit` (default top 10).

3. **Per-subdomain overview** `DATA_getDomainOverviewWorldwide`
   - For each subdomain in scope: domain authority, traffic estimate, organic + paid keyword counts, top regions.
   - This establishes a baseline for cross-subdomain comparison.

4. **Per-subdomain top keywords** `DATA_getDomainKeywords`
   - For each subdomain: top 100 organic keywords with positions, intent, traffic.
   - Cluster keywords by topic. This skill's grouping is a lightweight per-subdomain ownership map, not a content plan — token-grouping by head term + intent is sufficient here. (For full content-cluster planning use `seo-keyword-cluster`, which now clusters by SERP overlap, not text similarity.)
   - Each subdomain gets a list of "owned topics" (clusters where it dominates) and "minor topics".

5. **Per-subdomain competitors** `DATA_getDomainCompetitors`
   - For each subdomain: top organic competitors by `common_keywords`.
   - Surface: do different subdomains have different competitor sets? (Sign of legitimately separate scopes.) Do they share competitors? (Sign of redundant scopes.)

6. **Per-subdomain backlinks** `DATA_getBacklinksSummary` and `DATA_getBacklinksRefDomains` (top 20)
   - Subdomains often have separate backlink profiles. Capture each.
   - Surface: do subdomains have meaningfully different referring-domain populations?

7. **Authority distribution** `DATA_getDistributionOfDomainAuthority`
   - For each subdomain, pull DA distribution of referring domains.

8. **Detect fragmentation**
   - For each topic-cluster, identify all subdomains ranking for keywords in that cluster.
   - **Fragmentation signal:** ≥ 2 subdomains rank in the top 50 for the same high-volume keyword (cannibalization).
   - **Healthy split:** distinct topic clusters per subdomain, minimal overlap.

9. **Make recommendations**
   - **Consolidate:** if `blog.example.com` and `example.com/blog/` both rank for the same topic cluster but neither dominates — pick one canonical home.
   - **Split:** if a subdomain is ranking for a topic completely off-mission for the root domain, that's a split worth keeping.
   - **Leave alone:** if subdomains have distinct topic ownership and don't cannibalize, don't disturb.
   - **Investigate:** ambiguous cases flagged for human review.

10. **Synthesise** `SUBDOMAINS.md`

## Output format

Create a folder `seo-subdomain-{target-slug}-{YYYYMMDD}/` with:

```
seo-subdomain-{target-slug}-{YYYYMMDD}/
├── SUBDOMAINS.md                       (synthesised report + recommendations — primary deliverable)
├── 06-topic-ownership-map.md           (cluster × subdomain matrix — load-bearing reference content teams brief from)
├── 07-fragmentation-flags.md           (cannibalization detected — load-bearing reference for consolidation decisions)
└── evidence/
    ├── 01-subdomains-list.md           (DATA_getDomainSubdomains — raw step output)
    ├── 02-overview-by-subdomain.md     (per-subdomain overview rows)
    ├── 03-keywords-by-subdomain/
    │   ├── blog-example-com.md
    │   ├── docs-example-com.md
    │   └── ...                          (one per subdomain)
    ├── 04-competitors-by-subdomain.md
    └── 05-backlinks-by-subdomain.md
```

Top-level: `SUBDOMAINS.md` + `06-topic-ownership-map.md` + `07-fragmentation-flags.md`. Content teams brief from the ownership map; consolidation decisions cite the fragmentation flags directly. The 01–05 step files preserve raw API outputs in `evidence/`.

`SUBDOMAINS.md` follows this shape:

```markdown
# Subdomain Analysis: {root domain}

> Snapshot dated {YYYY-MM-DD} · Subdomains analysed: {n} of {n discovered} (limit: top {limit} by keyword count)

## Subdomain inventory

| Subdomain | Keywords | Traffic est. | Backlinks | Domain authority | Top topics owned |
|---|---|---|---|---|---|
| {root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| blog.{root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| docs.{root} | {n} | {n}/mo | {n} | {DA} | {topics} |
| ... |

## Topic ownership map

| Topic cluster | Owned by | Also ranks (cannibalization?) |
|---|---|---|
| {topic 1} | blog.{root} (avg pos 3.2 across 47 keywords) | {root} (avg pos 12) — {⚠ cannibalization} |
| {topic 2} | docs.{root} | (none) |
| ... |

## Fragmentation flags

### {⚠ Cannibalization detected: topic = {topic X}}
- `blog.{root}` ranks {n} keywords for {topic X}, avg position {p}.
- `{root}` (root path) ranks {m} keywords for the same topic, avg position {p}.
- The two sets overlap on {k} exact keywords.
- **Recommendation:** consolidate to `blog.{root}` (the stronger ranker). 301 the root-path duplicates with intent preserved.

### ... (per fragmentation finding)

## Recommendations summary

- **Consolidate:** {n} subdomain pairs → see fragmentation flags above.
- **Split intentional and healthy:** {n} subdomains have distinct ownership; leave alone.
- **Investigate:** {n} edge cases flagged for human review.

## Risk notes

- Subdomain consolidation requires careful 301 redirect mapping; track via `seo-drift` after the migration.
- A subdomain with separate backlinks (per `evidence/05-backlinks-by-subdomain.md`) is harder to consolidate without losing link equity — plan accordingly.

## Raw data
- See per-subdomain files under `evidence/03-keywords-by-subdomain/`.
- Topic ownership matrix: `06-topic-ownership-map.md`.
```

## Tips

- Respect rate limit. The skill makes ~5 calls per subdomain. With `--limit 10`, that's ~50 calls; pace sequentially.
- Call `DATA_getCreditBalance` before running. Cost scales with subdomain count: ~20–60 credits typical for `--limit 10`; up to 150+ for unlimited.
- **`--limit` is your friend.** Sites with hundreds of subdomains (large platforms) don't need every subdomain analysed — top 10 by keyword count covers >90% of organic value usually.
- **Don't conflate "subdomain has lower DA" with "subdomain is bad."** Subdomains often have lower DA than the root because they accumulate links separately. The question is topic ownership and cannibalization, not DA per se.
- **Consolidation is risky.** A 301 from `blog.example.com` to `example.com/blog/` retains most link equity but can lose 5–15% in transition. Track post-migration with `seo-drift`.
- **Don't recommend consolidation when one subdomain is on a different platform.** If `blog.example.com` is on a different CMS, the engineering cost of consolidation may exceed the SEO benefit. Surface this as a constraint, not a recommendation.
- The topic-ownership matrix is the highest-leverage artifact. Use it to brief content teams on which subdomain should publish what.
- Pair with `seo-page` to deep-dive into specific URLs flagged in cannibalization.
- Pair with `seo-drift` to baseline subdomains before major restructures.

## Dónde encaja

- Categoría: [SEO y GEO](https://skillsagentes.com/categorias/seo-geo.md) — Keywords, auditorías on-page, datos estructurados y visibilidad en respuestas de IA.
- Creador: [seranking](https://skillsagentes.com/creators/seranking.md) — 32 skills en el directorio
- [Todas las skills](https://skillsagentes.com/skills.md)
- [Ranking de instalaciones](https://skillsagentes.com/ranking.md)

## Otras skills del mismo repositorio

- [Client Onboarding Proposal](https://skillsagentes.com/skills/seranking/seo-skills/client-onboarding-proposal.md): Construye una propuesta de onboarding de cliente basada en datos, combinando un audit SEO + búsqueda IA de SE Ranking con un análisis en Planable del rendimiento social actual del cliente.
- [Local Gmb Visibility](https://skillsagentes.com/skills/seranking/seo-skills/local-gmb-visibility.md): Combina el seguimiento de rankings por ciudad de SE Ranking con contenido social local en Planable, incluyendo publicaciones de Google Business Profile.
- [Ai Search Gaps To Social Campaign](https://skillsagentes.com/skills/seranking/seo-skills/ai-search-gaps-to-social-campaign.md): Encuentra los prompts y temas de búsqueda con IA donde una marca es invisible o pierde frente a competidores en SE Ranking, y convierte esos vacíos en una campaña social en Planable con seguimiento antes/después.
- [Site Audit To Social Distribution](https://skillsagentes.com/skills/seranking/seo-skills/site-audit-to-social-distribution.md): Detecta páginas débiles y brechas de contenido en SE Ranking, y coordina la corrección en Planable: redacta el copy reescrito para revisión y aprobación, y programa la distribución social.
- [Seo Ai Social Report](https://skillsagentes.com/skills/seranking/seo-skills/seo-ai-social-report.md): Genera un único reporte de rendimiento que une rankings SEO, visibilidad en búsquedas IA (SE Ranking) y engagement social (Planable): resumen en el chat más un informe HTML interactivo autónomo.

---

Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)