seo-content
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: seo-content
description: 2026 SEO content writing for marketing sites — search intent, on-page structure, keyword researc…
category: writing
runtime: no special runtime
---
# seo-content output preview
## PART A: Task fit
- Use case: 2026 SEO content writing for marketing sites — search intent, on-page structure, keyword research, E-E-A-T, internal linking, and AI Overview optimization. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Search Intent Classification — Do This First / Title, H1, and Meta Description / Keyword Research Workflow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “2026 SEO content writing for marketing sites — search intent, on-page structure, keyword research, E-E-A-T, internal linking, and AI Overview optimization. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Search Intent Classification — Do This First / Title, H1, and Meta Description / Keyword Research Workflow” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Search Intent Classification — Do This First / Title, H1, and Meta Description / Keyword Research Workflow”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: seo-content
description: 2026 SEO content writing for marketing sites — search intent, on-page structure, keyword researc…
category: writing
source: tomevault-io/skills-registry
---
# seo-content
## When to use
- 2026 SEO content writing for marketing sites — search intent, on-page structure, keyword research, E-E-A-T, internal l…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Search Intent Classification — Do This First / Title, H1, and Meta Description / Keyword Research Workflow” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "seo-content" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Search Intent Classification — Do This First / Title, H1, and Meta Description / Keyword Research Workflow
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}SEO Content — 2026 Marketing Site Writing
Search Intent Classification — Do This First
Before writing a single word, classify the intent of the target query. Getting this wrong means the page will not rank regardless of quality.
| Intent | What the user wants | Content format |
|---|---|---|
| Informational | Learn something | Long-form guide, tutorial, comparison |
| Navigational | Find a specific site/page | Not a content play — fix your brand SERP |
| Commercial investigation | Evaluate options before buying | Comparison, listicle, review |
| Transactional | Buy or sign up now | Landing page, product page |
To verify intent: Google the keyword. Look at the top 5 results. Match their format and depth. If the SERP is all listicles, write a listicle. If it is all tutorials, write a tutorial.
Title, H1, and Meta Description
Title tag:
- 50–60 characters max (Google truncates at ~580px).
- Primary keyword near the front.
- Differentiation signal: year, number, modifier ("Best", "Complete Guide", "For [ICP]").
- Example:
B2B Cold Email Templates That Actually Book Meetings (2026)
H1:
- Can differ from the title tag — use the keyword naturally, not stuffed.
- One H1 per page only.
Meta description:
- 120–158 characters.
- Not a ranking factor but directly affects CTR.
- Include primary keyword, a benefit, and an implicit CTA.
- Example:
Skip the generic templates. These cold email frameworks generated 3,000+ replies for SaaS teams in 2025. Copy and adapt.
Keyword Research Workflow
Paid tools: Ahrefs Keywords Explorer, Semrush Keyword Magic.
Free stack (in order):
- Google Search Console — find queries where you rank 8–20 and optimize for them (fastest wins).
- Bing Keyword Research Tool — free, underused, shows volume and CPC.
- AlsoAsked.com — maps the "People Also Ask" tree; reveals the sub-questions to answer in the article.
- Google autocomplete + related searches — primary keyword in the search bar, scrape suggestions.
Targeting signal: primary keyword + 3–5 secondary/LSI keywords woven naturally into H2s and body copy. Do not stuff. Google detects unnatural density.
Difficulty vs. opportunity heuristic: target keywords with KD < 30 for new sites, KD 30–60 for established domains. Above 60 requires serious authority and backlinks — a content play alone will not rank.
E-E-A-T Signals (Experience, Expertise, Authoritativeness, Trustworthiness)
Google's quality rater guidelines penalize thin, anonymous, unverifiable content. Countermeasures:
- Author byline with real name, photo, credentials, and LinkedIn link.
- First-person experience. "I tested X" or "Our team ran Y" signals real experience.
- Citations and sources. Link to primary research, studies, and authoritative domains.
- Publication date + last-updated date. Keep evergreen content updated annually at minimum.
- About page and author bio pages. Must exist and be detailed.
- Expert quotes. Pull quotes from named practitioners (with permission).
For YMYL (Your Money or Your Life) topics — finance, health, legal — E-E-A-T requirements are significantly stricter. Anonymous content will not rank.
Internal Linking
Internal links distribute PageRank and signal topical authority. Do both:
- Hub-and-spoke. Create a pillar page for a broad topic; link to it from all related cluster posts. Pillar links back to clusters.
- Contextual links. Link from body copy using descriptive anchor text (not "click here"). Anchor text should describe the destination page's topic.
- Rule of thumb: 3–5 internal links per 1,000 words.
- Audit broken internal links quarterly.
AI Overview / SGE Optimization
Google's AI Overviews (formerly SGE) cite specific sources. To be citation-worthy:
- Answer the question in the first 100 words. The model favors content that answers directly before elaborating.
- Use structured formats. Numbered steps, definition-first paragraphs, comparison tables — all easier for LLMs to parse and cite.
- Claim specificity. "Reduces churn by 18%" is citable. "Reduces churn significantly" is not.
- FAQ schema. Marks up questions and answers explicitly for AI parsing (see snippet below).
- Structured data. Article, BreadcrumbList, and FAQPage schemas increase the signal-to-noise ratio for crawlers.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is a good cold email open rate?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A good cold email open rate for B2B outreach is 40–60%. Below 30% usually signals deliverability problems or weak subject lines."
}
}
]
}Add this in a <script type="application/ld+json"> block in the page <head>.
On-Page Checklist Before Publishing
- Keyword in title, H1, first 100 words, at least one H2.
- Meta description written, under 158 characters.
- Images have descriptive alt text including keyword where natural.
- Internal links to 3+ relevant pages.
- External links to at least 2 authoritative sources (opens in new tab).
- Author byline with credentials.
- FAQ schema added if the post answers specific questions.
- Core Web Vitals pass (LCP < 2.5s, CLS < 0.1, INP < 200ms) — check via PageSpeed Insights.
- Mobile rendering verified.
What Not to Do
- Do not keyword-stuff. "Best CRM software best CRM best software for CRM" will trigger a manual or algorithmic penalty.
- Do not write for bots. Write for the user who typed that query — what do they need to know?
- Do not publish thin content (< 600 words) unless the intent is genuinely a short answer.
- Do not ignore cannibalization. Two pages targeting the same keyword split authority. Merge or redirect one.
- Do not chase volume alone. A keyword with 200 monthly searches and clear transactional intent often converts better than a 10,000-search informational keyword.
Source: Aldocooek/lukasdlouhy-claude-ecosystem — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review