Bulk Seo Guides From Keywords

Bulk SEO guides from keywords

What this is

This skill encodes a repeatable shipping loop that improved rankings in practice: research keywords → author many unique guides → register routes → update sitemap → list on resources/hub pages so Google and users can find them. It complements `gsc-ahrefs-browser-audit` (writes the brief) and `ctr-snippet-batch-optimize` (snippet fixes on existing URLs).

Input: seo-work-brief.md (preferred)

1. Read `seo-work-brief.md` at the site project root (default `./seo-work-brief.md`) unless the user gives another path. That file is produced by `gsc-ahrefs-browser-audit`; see references/brief-format.md for how to parse it. 2. Use the section `## New guide backlog (for bulk-seo-guides-from-keywords)` as the authoritative queue: process rows with Status `queued` or empty, in Priority order. 3. After each batch, edit the same `seo-work-brief.md` and set Status to shipped or skipped for finished rows. 4. If the brief is missing or the backlog table is empty, fall through to the research phase below and optionally create a new seo-work-brief.md with a populated backlog for the next run.

Research phase (fallback or top-up)

1. Build or extend a candidate list from Ahrefs Organic keywords, Opportunities (e.g. low-hanging fruit), or exported reports—prioritize volume × realistic difficulty × fit with the product. 2. If API/MCP hits limits, switch to browser automation with the user logged into Ahrefs (same rationale as the browser audit skill). 3. Optional: use web search (e.g. Exa or similar) to confirm SERP intent (informational vs tool vs mixed) before committing a template. 4. Dedupe against URLs that already exist in the repo (grep routes, sitemap, content folders). 5. When you used fallback research, append or merge new rows into `seo-work-brief.md` using the backlog table format from `gsc-ahrefs-browser-audit/references/seo-work-brief.md` so the queue stays the single source of truth.

Page quality bar (non-negotiable)

• Each page needs substantive, unique body content—not spun placeholders. Include sections, examples, tables, or lists where appropriate.
• Add internal links to closely related existing guides (and note neighbors for future cross-links).
• Align title and meta with the target query using the same CTR habits as the `ctr-snippet-batch-optimize` skill’s references/ctr-patterns.md (same repo).

Shipping phase (always complete the plumbing)

For every new URL, update whatever your stack uses—adapt names to the project:

Do not stop at “TSX created” if the user expects live URLs—confirm routes and sitemap are wired, or explicitly list remaining manual steps.

Scale and execution

• Batch size — Groups of ~5 pages per iteration reduce context loss and review fatigue (adjust if the user asks).
• Parallelism — If the agent supports subtasks/subagents, parallelize batches; merge conflicts are avoided by giving each batch distinct filenames/slugs up front.
• Slug consistency — One slug per keyword cluster; avoid near-duplicate paths (e.g. red-herring-examples vs red-herring-fallacy) unless intent truly differs—document the distinction in copy.

Handoff to the user

After a large batch, provide:

• Full list of new paths (domain-appended if they asked).
• Anything left manual (e.g. CDN cache, Search Console inspection).

Related

• Produce or refresh the queue with `gsc-ahrefs-browser-audit` → `seo-work-brief.md`.
• Refresh snippets on thin-performing winners with `ctr-snippet-batch-optimize` (uses Tier tables in the same brief, not the backlog section).
• Backlog parsing rules: references/brief-format.md
• Detailed checklist: references/shipping-checklist.md

Input: seo-work-brief.md

Default location

Read `./seo-work-brief.md` at the site project root first. If the user passes another path, use that.

Section to consume

Find the heading (exact text):

## New guide backlog (for bulk-seo-guides-from-keywords)

Parse the markdown table immediately below it.

Row selection

Process rows where Status is:

• queued, or
• empty / missing

Skip rows marked `shipped` or `skipped`.

Sort order

Sort by `Priority` ascending (1 before 2). Tie-break by row order in the file.

After shipping

Update the brief in place: set Status to shipped (or skipped with a short reason) for each completed row so future runs do not recreate the same URLs.

Full brief spec

The audit skill defines the complete file shape and column meanings: `gsc-ahrefs-browser-audit/references/seo-work-brief.md` (same repository as these skills).

If `seo-work-brief.md` is missing or the backlog table is empty, fall back to live Ahrefs (or browser) research and offer to create a new brief with a populated backlog for the next run.

Bulk guide shipping checklist

Use after each batch (or each page, if small).

Content

• [ ] Title and meta description match query intent and follow CTR patterns (numbers, specifics, no redundant phrasing).
• [ ] Body is not thin: multiple sections, examples, or structured data where relevant.
• [ ] At least 2–3 internal links to related existing pages where natural.
• [ ] No accidental duplicate slug or overlapping topic without clear differentiation.

Technical

• [ ] New page file added in the project’s content directory.
• [ ] Route registered (framework-specific).
• [ ] Sitemap source updated so the URL is discoverable by crawlers.
• [ ] Hub / resources / nav updated if the site uses a browse page or index.
• [ ] Images/assets referenced exist or use existing design system components.

Optional follow-ups

• [ ] Submit a sample of new URLs in Google Search Console URL Inspection if the user cares about fast feedback.
• [ ] Note keywords queued for a future batch if context ran out mid-run.