OpenClaw SEO Content Writer
Use this skill to run a full SEO blog production lane instead of treating “write a blog post” as only a drafting task.
Core model
Split ownership clearly:
- Tony owns draft generation, safe-template normalization, preflight, content-quality gating, source publish readiness, and artifact receipts.
- Peter owns deployment, live verification, indexability checks, Google Search Console submission, and indexing-status receipts.
Never collapse these into one fuzzy “content done” state.
Required workflow
- Gather same-day inputs
- keyword / topic target
- audience + search intent
- Hunter research / evidence / proof links
- brand positioning + CTA source
- Write the draft batch
- Use a stable SEO skeleton, not freeform prose.
- Ensure every draft answers the query directly and has enough structure to survive QA.
- Normalize through safe template
- Stamp template metadata.
- Ensure every draft contains a quick answer, TL;DR, scannable sections, FAQ, conclusion, CTA, and source/proof notes.
- Run publish gates
- structural preflight
- content-quality audit
- If not publishable, recover correctly
- Do not pad with filler.
- Call Hunter for bounded same-day recovery research first.
- Only downgrade or replace the topic if Hunter also cannot make it longform-worthy.
- Source publish
- Only after preflight + quality audit pass.
- Write a structured source-publish receipt.
- Peter closeout
- deploy production
- verify live URL and
/blog
- verify canonical / sitemap / noindex / discovery
- write deployment + indexability receipts
- Search Console follow-through
- submit only
INDEX_READY URLs
- write GSC submission receipt
- check indexing status later and write GSC status receipt
Non-negotiable rules
- No filler padding. If word count is thin, add real information or trigger research recovery.
- No publish without receipts. Preflight, quality audit, source publish, deploy, and indexability should all leave artifacts.
- No “live” claims without Peter verification. Code-ready is not live.
- No GSC submission before indexability passes. Live + self-canonical + sitemap +
/blog discovery must be true first.
Minimum draft contract
Every publish candidate should have:
- direct answer / quick answer
- TL;DR
- 4+ substantial H2 sections
- comparison table or clear scannable structure
- FAQ with at least 4 real questions
- conclusion
- CTA
- source / proof notes
- enough specificity, proof, and search-intent coverage to be publishable
Recovery logic
If a draft batch fails because it is thin, weakly evidenced, or not publishable:
- classify the problem
- call Hunter for more research
- rewrite once with stronger evidence / FAQ material / angles
- rerun gates
- only then downgrade or replace the topic if still too weak
Receipts to maintain
Use the same style of structured receipts for every lane:
- preflight receipt
- content-quality audit receipt
- source-publish receipt
- deployment receipt
- blog indexability receipt
- GSC submission receipt
- GSC index-status receipt
References
Read these files when needed:
references/tony-pipeline.md — drafting, gating, recovery, and source publish flow
references/peter-closeout.md — deploy, live verification, indexability, and closure rules
references/gsc-indexing.md — Search Console submission and indexing-status workflow
references/receipt-contracts.md — receipt expectations and truth states
Prerequisites
This skill is a workflow guide, not a standalone tool. It assumes you already have:
Deployment
- A deployment pipeline for your site (e.g. Vercel, Netlify, Cloudflare Pages, or a custom CI/CD setup)
- SSH or CLI access to trigger deploys
- A working sitemap generator (e.g. Next.js
sitemap.ts, or equivalent)
Google Search Console
- A verified GSC property for your domain (
sc-domain: or URL-prefix)
- Google Cloud project with the Indexing API and Search Console API enabled
- A service account JSON key with GSC permissions, or OAuth credentials
googleapis npm package or gcloud CLI available in your environment
Content pipeline
- A content source directory or CMS where drafts are stored
- A safe-template normalization script or convention (this skill describes the contract, not the implementation)
Optional but recommended
- Tavily or web search tool for Hunter research recovery
- A receipt/artifact directory convention (e.g.
mission-control/data/)
No credentials are bundled
This skill does not ship any API keys, service accounts, or deployment configs. All credentials must be configured in your own environment before use.
1---2name: openclaw-seo-content-writer3description: Write and ship SEO blog posts with Tony + Peter workflow, publish QA, deploy verification, and GSC indexing. SEO博客写作/发布/部署/谷歌收录4metadata:5 source: https://skillmd.com/skills/x-rayluan/openclaw-seo-content-writer6---78# OpenClaw SEO Content Writer910Use this skill to run a full SEO blog production lane instead of treating “write a blog post” as only a drafting task.1112## Core model1314Split ownership clearly:1516- **Tony** owns draft generation, safe-template normalization, preflight, content-quality gating, source publish readiness, and artifact receipts.17- **Peter** owns deployment, live verification, indexability checks, Google Search Console submission, and indexing-status receipts.1819Never collapse these into one fuzzy “content done” state.2021## Required workflow22231. **Gather same-day inputs**24 - keyword / topic target25 - audience + search intent26 - Hunter research / evidence / proof links27 - brand positioning + CTA source282. **Write the draft batch**29 - Use a stable SEO skeleton, not freeform prose.30 - Ensure every draft answers the query directly and has enough structure to survive QA.313. **Normalize through safe template**32 - Stamp template metadata.33 - Ensure every draft contains a quick answer, TL;DR, scannable sections, FAQ, conclusion, CTA, and source/proof notes.344. **Run publish gates**35 - structural preflight36 - content-quality audit375. **If not publishable, recover correctly**38 - Do not pad with filler.39 - Call Hunter for bounded same-day recovery research first.40 - Only downgrade or replace the topic if Hunter also cannot make it longform-worthy.416. **Source publish**42 - Only after preflight + quality audit pass.43 - Write a structured source-publish receipt.447. **Peter closeout**45 - deploy production46 - verify live URL and `/blog`47 - verify canonical / sitemap / noindex / discovery48 - write deployment + indexability receipts498. **Search Console follow-through**50 - submit only `INDEX_READY` URLs51 - write GSC submission receipt52 - check indexing status later and write GSC status receipt5354## Non-negotiable rules5556- **No filler padding.** If word count is thin, add real information or trigger research recovery.57- **No publish without receipts.** Preflight, quality audit, source publish, deploy, and indexability should all leave artifacts.58- **No “live” claims without Peter verification.** Code-ready is not live.59- **No GSC submission before indexability passes.** Live + self-canonical + sitemap + `/blog` discovery must be true first.6061## Minimum draft contract6263Every publish candidate should have:6465- direct answer / quick answer66- TL;DR67- 4+ substantial H2 sections68- comparison table or clear scannable structure69- FAQ with at least 4 real questions70- conclusion71- CTA72- source / proof notes73- enough specificity, proof, and search-intent coverage to be publishable7475## Recovery logic7677If a draft batch fails because it is thin, weakly evidenced, or not publishable:78791. classify the problem802. call Hunter for more research813. rewrite once with stronger evidence / FAQ material / angles824. rerun gates835. only then downgrade or replace the topic if still too weak8485## Receipts to maintain8687Use the same style of structured receipts for every lane:8889- preflight receipt90- content-quality audit receipt91- source-publish receipt92- deployment receipt93- blog indexability receipt94- GSC submission receipt95- GSC index-status receipt9697## References9899Read these files when needed:100101- `references/tony-pipeline.md` — drafting, gating, recovery, and source publish flow102- `references/peter-closeout.md` — deploy, live verification, indexability, and closure rules103- `references/gsc-indexing.md` — Search Console submission and indexing-status workflow104- `references/receipt-contracts.md` — receipt expectations and truth states105106## Prerequisites107108This skill is a workflow guide, not a standalone tool. It assumes you already have:109110### Deployment111- A deployment pipeline for your site (e.g. Vercel, Netlify, Cloudflare Pages, or a custom CI/CD setup)112- SSH or CLI access to trigger deploys113- A working sitemap generator (e.g. Next.js `sitemap.ts`, or equivalent)114115### Google Search Console116- A verified GSC property for your domain (`sc-domain:` or URL-prefix)117- Google Cloud project with the **Indexing API** and **Search Console API** enabled118- A service account JSON key with GSC permissions, or OAuth credentials119- `googleapis` npm package or `gcloud` CLI available in your environment120121### Content pipeline122- A content source directory or CMS where drafts are stored123- A safe-template normalization script or convention (this skill describes the contract, not the implementation)124125### Optional but recommended126- Tavily or web search tool for Hunter research recovery127- A receipt/artifact directory convention (e.g. `mission-control/data/`)128129### No credentials are bundled130This skill does not ship any API keys, service accounts, or deployment configs. All credentials must be configured in your own environment before use.