publish-seo-batch
Use when publishing SEO blog articles to qaskills.sh, e.g. "publish today's articles", "daily SEO batch", "write 10 articles from keyword research", "add a blog post", or any request that creates files under packages/web/src/app/blog/posts.
PramodDutta · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add PramodDutta/qaskills --skill publish-seo-batch技能说明
name: publish-seo-batch description: Use when publishing SEO blog articles to qaskills.sh, e.g. "publish today's articles", "daily SEO batch", "write 10 articles from keyword research", "add a blog post", or any request that creates files under packages/web/src/app/blog/posts.
Publish SEO Batch
The daily content pipeline: source topics -> dedup slugs -> write posts -> register -> build -> commit -> deploy -> prove live -> ping IndexNow. Default batch size is 10 unless the user says otherwise. Every step has a check; a batch is not "published" until step 8 passes, then step 9 nudges the search engines.
Step 0: State check
git -C /Users/promode/qaskills status --short # note pre-existing WIP; you will NOT stage it
date +%F # today's date, used in every post and the commit message
Pre-existing modified/untracked files are the user's WIP. Leave them alone.
Step 1: Source topics
Saved GSC reports in docs/seo/KEYWORD-OPPORTUNITIES-*.md are historical and fully published; do not source topics from them. Instead:
- If the user supplied topics or keywords, use those.
- Otherwise WebSearch for net-new opportunities in the site's clusters: Playwright (releases, features, integrations), LLM evaluation (DeepEval, Ragas, promptfoo, Langfuse), API testing, load testing, AI test generation, agentic testing, CI/CD. Favor high-intent long-tail: "X vs Y 2026", "how to X", tool + new-version guides, fresh industry reports.
- Cross-check each candidate against existing coverage (step 2). Prefer gaps over rewrites.
- If the research produced a reusable keyword dataset, save it as
docs/seo/KEYWORD-OPPORTUNITIES-YYYY-MM.mdand include it in the commit.
Step 2: Dedup every slug (MANDATORY before writing any file)
Batch arrays are spread into the registries LAST, so a colliding slug silently replaces a real article. This has shipped a stub over a full article before.
cd /Users/promode/qaskills
for s in slug-one slug-two; do
hits=$(grep -rn "$s" packages/web/src/app/blog/posts/ | grep -v "$s-something-longer" | wc -l)
echo "$s: $hits hits"
done
Any hit (filename, posts map key, postList entry, batch array entry): choose a different slug or drop the topic. Also scan titles in posts/index.ts for near-duplicate topics; a second article on the same query cannibalizes the first.
Step 3: Write each post
File: packages/web/src/app/blog/posts/<slug>.ts
import type { BlogPost } from './index';
export const post: BlogPost = {
title: 'Primary Keyword In Natural Title',
description: 'Meta description, 140-170 chars, contains the keyword, states the payoff.',
date: 'YYYY-MM-DD', // today
category: 'Guide', // Guide | Reference | Tutorial | Comparison | AI Testing | API Testing | Migration | BDD | Performance
content: `
# Same Title As Above
Opening paragraphs that answer the query directly...
`,
};
Per-article bar (all required):
- Content >= 1200 words; H1 equals
title - At least one markdown table (comparison, metrics, or reference)
- Code blocks for technical topics; ESCAPE backticks inside the template literal (\`\`\`)
- At least 2 internal links to existing posts (
/blog/<existing-slug>); verify each target exists inposts/index.tsbefore linking - No em dashes anywhere; no invented statistics (attribute figures or mark them approximate)
- No
${in prose unless intentionally interpolating; escape as \${ if literal - End with a
## Frequently Asked Questionssection (3-4### Question?H3s with short answers) as the LAST H2. It counts toward the word bar andsrc/lib/extract-faqs.tsturns it into FAQPage JSON-LD for AI-search citation. Without it, articles tend to land short of 1200 words.
Step 4: Register in BOTH registries
packages/web/src/app/blog/posts/index.ts needs three edits per post:
- Import:
import { post as camelCaseName } from './<slug>';(with the other imports) postsmap entry:'<slug>': camelCaseName,placed BEFORE the batch...Object.fromEntriesspreadspostListentry:{ slug: '<slug>', ...camelCaseName },placed before the batch spreads at the end
Missing 1 or 2 = the page 404s. Missing 3 = invisible on /blog and absent from the sitemap. Do not touch sitemap.ts; it derives from postList.
Step 5: Verify locally (do not skip)
cd /Users/promode/qaskills
# exactly 2 quoted occurrences per slug in index.ts (map key + postList)
for s in slug-one slug-two; do
c=$(grep -c "'$s'" packages/web/src/app/blog/posts/index.ts)
[ "$c" -eq 2 ] || echo "REGISTRATION WRONG: $s count=$c"
done
# no em dashes in the new files
grep -l '—' packages/web/src/app/blog/posts/<each-new-slug>.ts && echo "EM DASH FOUND"
# build must pass
pnpm --filter @qaskills/shared build && pnpm --filter @qaskills/web build
Fix and re-run until all three are clean. Build failure in a post file is almost always an unescaped backtick or ${ in the template literal.
Step 6: Commit
git -C /Users/promode/qaskills add \
packages/web/src/app/blog/posts/<slug-one>.ts \
packages/web/src/app/blog/posts/<slug-two>.ts \
packages/web/src/app/blog/posts/index.ts
git -C /Users/promode/qaskills diff --cached --stat # only your files
git -C /Users/promode/qaskills commit -m "feat: publish 10 SEO articles (YYYY-MM-DD) from keyword research"
git -C /Users/promode/qaskills push origin main
Explicit paths only. No trailers, no footers, no em dash in the message.
Step 7: Deploy
REQUIRED SUB-SKILL: ship-prod. Follow it exactly (worktree if the tree is dirty, explicit project IDs, its verification checklist).
Step 8: Prove it live
for s in slug-one slug-two; do
code=$(curl -s -o /dev/null -w '%{http_code}' "https://qaskills.sh/blog/$s")
echo "$s: $code"
done
curl -s https://qaskills.sh/sitemap.xml | grep -c '<one-new-slug>' # >= 1
Every slug must return 200 and appear in the sitem
阅读完整来源 ↗