More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsSeo Article Architect
Build search-intent-driven SEO content briefs, keyword clusters, heading hierarchies, and complete authoritative articles that rank and convert.
Free
seo-article-architect
Example session with this skill installed
Write an SEO article brief and full post for the primary keyword "headless cms for ecommerce" targeting mid-market developers. Use first-principles as I have no proprietary data.
- Read your context and instructions
- Compiled the seo-article-architect
I have mapped the primary keyword to a
Commercial Investigation intent for practitioner-level readers. Since no proprietary data was provided, I have utilized a first-principles mechanism fallback focusing on microservices architecture.
SEO Strategy & Metadata
| Metric | Specification |
|---|---|
| Primary Keyword | headless cms for ecommerce |
| Search Intent | Commercial Investigation |
| JSON-LD Schema | SoftwareApplication |
| Title Tag | Best Headless CMS for Ecommerce: A Developer's Guide [54 chars] |
| Meta Description | Compare top headless CMS options for ecommerce. Learn how to decouple your frontend for better performance, scalability, and API-driven commerce. [152 chars] |
| URL Slug | headless-cms-ecommerce |
Headless CMS for Ecommerce: Architecture and Selection
TL;DR: A headless CMS for ecommerce decouples the content management layer from the storefront presentation. This allows developers to deliver product data via APIs to any frontend, improving site speed and omnichannel flexibility. Unlike traditional platforms, it enables a best-of-breed stack by separating commerce logic from content delivery. [58 words]
Key Technical Trade-offs
| Criteria | Traditional CMS | Headless CMS |
|---|---|---|
| Frontend | Coupled / Templates | Agnostic / API-first |
| Scaling | Monolithic Scaling | Independent Service Scaling |
| Dev Overhead | Low (Themes) | High (Custom Frontend) |
| Data Flow | Server-side Render | JSON/GraphQL API |
Common Mistakes to Avoid
Do not choose a headless provider that lacks a native GraphQL API. High-latency REST endpoints can bottleneck your checkout flow. Ensure the CMS supports preview URLs for non-technical editors, or your marketing team will lose visibility into drafted changes.
People Also Ask
Is a headless CMS better for SEO?
Yes, it allows for granular control over metadata, faster page load speeds through static site generation, and cleaner HTML structures. However, you must manually manage routing and canonical tags within your frontend framework to ensure search engines crawl the decoupled site correctly. [48 words]
Publication Readiness Verdict: NEEDS INPUT
The technical framework is complete, but you should replace {{insert_verified_metric_or_source}} in the performance section with your specific Lighthouse speed benchmarks.
Next steps
- Insert internal links for
{{internal_slug_1}}. - Add your specific API latency data to the performance section.
- Validate the JSON-LD FAQ schema for the PAA section.
Connects securely to your tools. The creator never sees your data.
About this skill
Search-Intent SEO Content & Authority Articles Without the AI Fluff
Standard AI blog posts fail in search because they open with generic filler ("In today's fast-paced digital world..."), miss searcher intent, and invent fake statistics.
SEO Article Architect structures every piece of content around real search intent, Featured Snippet / AI Overview formatting, and strict factual grounding.
What It Delivers (Complete 7-Part SEO Blueprint)
- SEO Strategy & Keyword Card: Maps Primary Keyword, Search Intent (
Informational,Commercial,Transactional,Comparison), Reader Stage, 5–8 Semantic Secondary Keywords, and JSON-LD Schema type (Article,HowTo,FAQPage). - Exact-Length Metadata Block: Title Tag strictly between 50 and 60 characters, Meta Description between 145 and 158 characters (with exact character counts reported), plus clean 3–5 word URL slug and image alt-text.
- Semantic Heading Map (
H1->H2->H3): Takeaway-driven headings paired with target searcher questions (zero generic "Introduction" or "Conclusion" headers). - 40–60 Word Direct-Answer Lead (TL;DR): Placed immediately below the
H1to capture Featured Snippets and AI search summaries within the first 60 words. - Authoritative Article Body: Scannable paragraphs (<3 sentences), step-by-step methodology, a structured Markdown Comparison Table / Decision Matrix, and a
Common Mistakes to Avoidsection. - People-Also-Ask (FAQ) Block: 4 to 5 long-tail questions answered concisely in 30 to 55 words each.
- Internal Linking & CTA Plan: 3 contextual anchor-text recommendations with
{{internal_slug}}placeholders and an intent-matched closing CTA.
Strict E-E-A-T & Anti-Hallucination Guardrails
- Zero Fabricated Data: Never invents fake survey percentages, studies, or citations. When no user metrics are supplied, uses First-Principles Workflow Examples and clean
{{insert_verified_metric_or_source}}placeholders. - No Black-Hat Stuffing: Rejects unnatural keyword stuffing, hidden text, and unverifiable ranking guarantees.
- 3-Tier Readiness Verdict: Outputs
READY(all 7 parts and metadata counts verified),NEEDS INPUT(safe first-principles fallback used; optional metrics noted), orHOLD(flags black-hat or unverified claims).
Quick Start Prompt
"Use seo-article-architect to write a complete technical SEO guide on 'PostgreSQL connection pooling vs PgBouncer' for backend engineers."
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
7 people have installed this skill.
Trust & safety
Security scanned
Verified clean today
- Free to download with an account