AgriciDaniel/claude-blog / skills/blog
blog
VerifiedFull-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.
references/cta-placement.md
View on GitHub# CTA Placement Guide
## Core Testing Hypotheses
The figures below are vendor-reported directional benchmarks. Use them as A/B
test hypotheses, not universal rules, unless the source URL, date, methodology,
and audience fit are loaded for the project.
- Personalized/contextual CTAs often outperform generic CTAs
- A focused primary CTA often outperforms competing conversion goals
- Inline CTAs often outperform disconnected sidebar CTAs
- CTA alignment and first-person copy should be tested against the page design
## Placement Rules by Content Type
| Content Type | CTA Position | Rationale |
|-------------|-------------|-----------|
| How-to guide | After first completed step sequence | Value already demonstrated |
| Listicle | After item #3-4 (mid-list) | Reader engaged but not finished |
| Comparison | After recommendation section | Decision point reached |
| Case study | After results section | Proof delivered |
| Pillar page | 2-3 natural section breaks | Avoid CTA fatigue on long pages |
| Tutorial | After first working example | Success moment |
| Product review | After verdict/rating | Purchase intent peaks |
| Thought leadership | At natural conclusion | Reflection complete |
| Data research | After key finding visualization | Impact moment |
| FAQ | After the 3rd answer | Pattern established |
## CTA Design Principles
- Place CTAs AFTER value delivery, not at arbitrary positions
- Above-fold CTAs only work when preceding content conveys value proposition
- Moving a CTA below long-form value content won one reported A/B test on a long sales page (Michael Aagaard, ContentVerve, reported as +304%; original write-up not verified here). Treat it as a reason to test placement, not an expected lift
- Maximum 2-3 CTAs per long-form post (intro contextual, mid-content, end summary)
## Accessible HTML
- Use `<a>` for navigation CTAs, `<button>` for action CTAs
- Never use `<div>` as a clickable CTA
- Minimum 44x44px touch targets
- CTA text: 4.5:1 contrast ratio minimum
- Focus indicators, borders, and icons: 3:1 contrast ratio minimum
- Visible focus indicators
- Descriptive link text (not "click here")
- `aria-labelledby` pointing to CTA heading when context is needed
## CTA Copy Formula
- Lead with first-person: "Start My..." not "Start Your..."
- Include benefit: "Get My Free Guide" not just "Download"
- Create urgency without being pushy: "Join 10,000+ readers" not "Act now!!!"
- Match surrounding content topic (contextual, not generic)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |