Initial release: 14 marketing skills for Claude Code
A collection of AI agent skills for technical marketers and founders: CRO Skills: - page-cro: Conversion optimization for marketing pages - signup-flow-cro: Signup/registration flow optimization - onboarding-cro: Post-signup activation and onboarding - form-cro: Lead capture and contact form optimization - popup-cro: Popup and modal optimization - paywall-upgrade-cro: In-app paywalls and upgrade screens Content Skills: - page-copywriting: Marketing page copy - email-sequence: Drip campaigns and email automation SEO Skills: - seo-audit: Technical and on-page SEO audits - programmatic-seo: Building SEO pages at scale - schema-markup: Structured data implementation Measurement Skills: - analytics-tracking: GA4, GTM, and event tracking - ab-test-setup: A/B test planning and analysis Growth Engineering: - free-tool-strategy: Engineering-as-marketing tools Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Corey Haines
508
skills/ab-test-setup.md
Normal file
508
skills/ab-test-setup.md
Normal file
@@ -0,0 +1,508 @@
|
||||
---
|
||||
name: ab-test-setup
|
||||
description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
|
||||
---
|
||||
|
||||
# A/B Test Setup
|
||||
|
||||
You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before designing a test, understand:
|
||||
|
||||
1. **Test Context**
|
||||
- What are you trying to improve?
|
||||
- What change are you considering?
|
||||
- What made you want to test this?
|
||||
|
||||
2. **Current State**
|
||||
- Baseline conversion rate?
|
||||
- Current traffic volume?
|
||||
- Any historical test data?
|
||||
|
||||
3. **Constraints**
|
||||
- Technical implementation complexity?
|
||||
- Timeline requirements?
|
||||
- Tools available?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Start with a Hypothesis
|
||||
- Not just "let's see what happens"
|
||||
- Specific prediction of outcome
|
||||
- Based on reasoning or data
|
||||
|
||||
### 2. Test One Thing
|
||||
- Single variable per test
|
||||
- Otherwise you don't know what worked
|
||||
- Save MVT for later
|
||||
|
||||
### 3. Statistical Rigor
|
||||
- Pre-determine sample size
|
||||
- Don't peek and stop early
|
||||
- Commit to the methodology
|
||||
|
||||
### 4. Measure What Matters
|
||||
- Primary metric tied to business value
|
||||
- Secondary metrics for context
|
||||
- Guardrail metrics to prevent harm
|
||||
|
||||
---
|
||||
|
||||
## Hypothesis Framework
|
||||
|
||||
### Structure
|
||||
|
||||
```
|
||||
Because [observation/data],
|
||||
we believe [change]
|
||||
will cause [expected outcome]
|
||||
for [audience].
|
||||
We'll know this is true when [metrics].
|
||||
```
|
||||
|
||||
### Examples
|
||||
|
||||
**Weak hypothesis:**
|
||||
"Changing the button color might increase clicks."
|
||||
|
||||
**Strong hypothesis:**
|
||||
"Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start."
|
||||
|
||||
### Good Hypotheses Include
|
||||
|
||||
- **Observation**: What prompted this idea
|
||||
- **Change**: Specific modification
|
||||
- **Effect**: Expected outcome and direction
|
||||
- **Audience**: Who this applies to
|
||||
- **Metric**: How you'll measure success
|
||||
|
||||
---
|
||||
|
||||
## Test Types
|
||||
|
||||
### A/B Test (Split Test)
|
||||
- Two versions: Control (A) vs. Variant (B)
|
||||
- Single change between versions
|
||||
- Most common, easiest to analyze
|
||||
|
||||
### A/B/n Test
|
||||
- Multiple variants (A vs. B vs. C...)
|
||||
- Requires more traffic
|
||||
- Good for testing several options
|
||||
|
||||
### Multivariate Test (MVT)
|
||||
- Multiple changes in combinations
|
||||
- Tests interactions between changes
|
||||
- Requires significantly more traffic
|
||||
- Complex analysis
|
||||
|
||||
### Split URL Test
|
||||
- Different URLs for variants
|
||||
- Good for major page changes
|
||||
- Easier implementation sometimes
|
||||
|
||||
---
|
||||
|
||||
## Sample Size Calculation
|
||||
|
||||
### Inputs Needed
|
||||
|
||||
1. **Baseline conversion rate**: Your current rate
|
||||
2. **Minimum detectable effect (MDE)**: Smallest change worth detecting
|
||||
3. **Statistical significance level**: Usually 95%
|
||||
4. **Statistical power**: Usually 80%
|
||||
|
||||
### Quick Reference
|
||||
|
||||
| Baseline Rate | 10% Lift | 20% Lift | 50% Lift |
|
||||
|---------------|----------|----------|----------|
|
||||
| 1% | 150k/variant | 39k/variant | 6k/variant |
|
||||
| 3% | 47k/variant | 12k/variant | 2k/variant |
|
||||
| 5% | 27k/variant | 7k/variant | 1.2k/variant |
|
||||
| 10% | 12k/variant | 3k/variant | 550/variant |
|
||||
|
||||
### Formula Resources
|
||||
- Evan Miller's calculator: https://www.evanmiller.org/ab-testing/sample-size.html
|
||||
- Optimizely's calculator: https://www.optimizely.com/sample-size-calculator/
|
||||
|
||||
### Test Duration
|
||||
|
||||
```
|
||||
Duration = Sample size needed per variant × Number of variants
|
||||
───────────────────────────────────────────────────
|
||||
Daily traffic to test page × Conversion rate
|
||||
```
|
||||
|
||||
Minimum: 1-2 business cycles (usually 1-2 weeks)
|
||||
Maximum: Avoid running too long (novelty effects, external factors)
|
||||
|
||||
---
|
||||
|
||||
## Metrics Selection
|
||||
|
||||
### Primary Metric
|
||||
- Single metric that matters most
|
||||
- Directly tied to hypothesis
|
||||
- What you'll use to call the test
|
||||
|
||||
### Secondary Metrics
|
||||
- Support primary metric interpretation
|
||||
- Explain why/how the change worked
|
||||
- Help understand user behavior
|
||||
|
||||
### Guardrail Metrics
|
||||
- Things that shouldn't get worse
|
||||
- Revenue, retention, satisfaction
|
||||
- Stop test if significantly negative
|
||||
|
||||
### Metric Examples by Test Type
|
||||
|
||||
**Homepage CTA test:**
|
||||
- Primary: CTA click-through rate
|
||||
- Secondary: Time to click, scroll depth
|
||||
- Guardrail: Bounce rate, downstream conversion
|
||||
|
||||
**Pricing page test:**
|
||||
- Primary: Plan selection rate
|
||||
- Secondary: Time on page, plan distribution
|
||||
- Guardrail: Support tickets, refund rate
|
||||
|
||||
**Signup flow test:**
|
||||
- Primary: Signup completion rate
|
||||
- Secondary: Field-level completion, time to complete
|
||||
- Guardrail: User activation rate (post-signup quality)
|
||||
|
||||
---
|
||||
|
||||
## Designing Variants
|
||||
|
||||
### Control (A)
|
||||
- Current experience, unchanged
|
||||
- Don't modify during test
|
||||
|
||||
### Variant (B+)
|
||||
|
||||
**Best practices:**
|
||||
- Single, meaningful change
|
||||
- Bold enough to make a difference
|
||||
- True to the hypothesis
|
||||
|
||||
**What to vary:**
|
||||
|
||||
Headlines/Copy:
|
||||
- Message angle
|
||||
- Value proposition
|
||||
- Specificity level
|
||||
- Tone/voice
|
||||
|
||||
Visual Design:
|
||||
- Layout structure
|
||||
- Color and contrast
|
||||
- Image selection
|
||||
- Visual hierarchy
|
||||
|
||||
CTA:
|
||||
- Button copy
|
||||
- Size/prominence
|
||||
- Placement
|
||||
- Number of CTAs
|
||||
|
||||
Content:
|
||||
- Information included
|
||||
- Order of information
|
||||
- Amount of content
|
||||
- Social proof type
|
||||
|
||||
### Documenting Variants
|
||||
|
||||
```
|
||||
Control (A):
|
||||
- Screenshot
|
||||
- Description of current state
|
||||
|
||||
Variant (B):
|
||||
- Screenshot or mockup
|
||||
- Specific changes made
|
||||
- Hypothesis for why this will win
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Traffic Allocation
|
||||
|
||||
### Standard Split
|
||||
- 50/50 for A/B test
|
||||
- Equal split for multiple variants
|
||||
|
||||
### Conservative Rollout
|
||||
- 90/10 or 80/20 initially
|
||||
- Limits risk of bad variant
|
||||
- Longer to reach significance
|
||||
|
||||
### Ramping
|
||||
- Start small, increase over time
|
||||
- Good for technical risk mitigation
|
||||
- Most tools support this
|
||||
|
||||
### Considerations
|
||||
- Consistency: Users see same variant on return
|
||||
- Segment sizes: Ensure segments are large enough
|
||||
- Time of day/week: Balanced exposure
|
||||
|
||||
---
|
||||
|
||||
## Implementation Approaches
|
||||
|
||||
### Client-Side Testing
|
||||
|
||||
**Tools**: Optimizely, VWO, Google Optimize (sunset), custom
|
||||
|
||||
**How it works**:
|
||||
- JavaScript modifies page after load
|
||||
- Quick to implement
|
||||
- Can cause flicker
|
||||
|
||||
**Best for**:
|
||||
- Marketing pages
|
||||
- Copy/visual changes
|
||||
- Quick iteration
|
||||
|
||||
### Server-Side Testing
|
||||
|
||||
**Tools**: LaunchDarkly, Split, custom
|
||||
|
||||
**How it works**:
|
||||
- Variant determined before page renders
|
||||
- No flicker
|
||||
- Requires development work
|
||||
|
||||
**Best for**:
|
||||
- Product features
|
||||
- Complex changes
|
||||
- Performance-sensitive pages
|
||||
|
||||
### Feature Flags
|
||||
|
||||
- Binary on/off (not true A/B)
|
||||
- Good for rollouts
|
||||
- Can convert to A/B with percentage split
|
||||
|
||||
---
|
||||
|
||||
## Running the Test
|
||||
|
||||
### Pre-Launch Checklist
|
||||
|
||||
- [ ] Hypothesis documented
|
||||
- [ ] Primary metric defined
|
||||
- [ ] Sample size calculated
|
||||
- [ ] Test duration estimated
|
||||
- [ ] Variants implemented correctly
|
||||
- [ ] Tracking verified
|
||||
- [ ] QA completed on all variants
|
||||
- [ ] Stakeholders informed
|
||||
|
||||
### During the Test
|
||||
|
||||
**DO:**
|
||||
- Monitor for technical issues
|
||||
- Check segment quality
|
||||
- Document any external factors
|
||||
|
||||
**DON'T:**
|
||||
- Peek at results and stop early
|
||||
- Make changes to variants
|
||||
- Add traffic from new sources
|
||||
- End early because you "know" the answer
|
||||
|
||||
### Peeking Problem
|
||||
|
||||
Looking at results before reaching sample size and stopping when you see significance leads to:
|
||||
- False positives
|
||||
- Inflated effect sizes
|
||||
- Wrong decisions
|
||||
|
||||
**Solutions:**
|
||||
- Pre-commit to sample size and stick to it
|
||||
- Use sequential testing if you must peek
|
||||
- Trust the process
|
||||
|
||||
---
|
||||
|
||||
## Analyzing Results
|
||||
|
||||
### Statistical Significance
|
||||
|
||||
- 95% confidence = p-value < 0.05
|
||||
- Means: <5% chance result is random
|
||||
- Not a guarantee—just a threshold
|
||||
|
||||
### Practical Significance
|
||||
|
||||
Statistical ≠ Practical
|
||||
|
||||
- Is the effect size meaningful for business?
|
||||
- Is it worth the implementation cost?
|
||||
- Is it sustainable over time?
|
||||
|
||||
### What to Look At
|
||||
|
||||
1. **Did you reach sample size?**
|
||||
- If not, result is preliminary
|
||||
|
||||
2. **Is it statistically significant?**
|
||||
- Check confidence intervals
|
||||
- Check p-value
|
||||
|
||||
3. **Is the effect size meaningful?**
|
||||
- Compare to your MDE
|
||||
- Project business impact
|
||||
|
||||
4. **Are secondary metrics consistent?**
|
||||
- Do they support the primary?
|
||||
- Any unexpected effects?
|
||||
|
||||
5. **Any guardrail concerns?**
|
||||
- Did anything get worse?
|
||||
- Long-term risks?
|
||||
|
||||
6. **Segment differences?**
|
||||
- Mobile vs. desktop?
|
||||
- New vs. returning?
|
||||
- Traffic source?
|
||||
|
||||
### Interpreting Results
|
||||
|
||||
| Result | Conclusion |
|
||||
|--------|------------|
|
||||
| Significant winner | Implement variant |
|
||||
| Significant loser | Keep control, learn why |
|
||||
| No significant difference | Need more traffic or bolder test |
|
||||
| Mixed signals | Dig deeper, maybe segment |
|
||||
|
||||
---
|
||||
|
||||
## Documenting and Learning
|
||||
|
||||
### Test Documentation
|
||||
|
||||
```
|
||||
Test Name: [Name]
|
||||
Test ID: [ID in testing tool]
|
||||
Dates: [Start] - [End]
|
||||
Owner: [Name]
|
||||
|
||||
Hypothesis:
|
||||
[Full hypothesis statement]
|
||||
|
||||
Variants:
|
||||
- Control: [Description + screenshot]
|
||||
- Variant: [Description + screenshot]
|
||||
|
||||
Results:
|
||||
- Sample size: [achieved vs. target]
|
||||
- Primary metric: [control] vs. [variant] ([% change], [confidence])
|
||||
- Secondary metrics: [summary]
|
||||
- Segment insights: [notable differences]
|
||||
|
||||
Decision: [Winner/Loser/Inconclusive]
|
||||
Action: [What we're doing]
|
||||
|
||||
Learnings:
|
||||
[What we learned, what to test next]
|
||||
```
|
||||
|
||||
### Building a Learning Repository
|
||||
|
||||
- Central location for all tests
|
||||
- Searchable by page, element, outcome
|
||||
- Prevents re-running failed tests
|
||||
- Builds institutional knowledge
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Test Plan Document
|
||||
|
||||
```
|
||||
# A/B Test: [Name]
|
||||
|
||||
## Hypothesis
|
||||
[Full hypothesis using framework]
|
||||
|
||||
## Test Design
|
||||
- Type: A/B / A/B/n / MVT
|
||||
- Duration: X weeks
|
||||
- Sample size: X per variant
|
||||
- Traffic allocation: 50/50
|
||||
|
||||
## Variants
|
||||
[Control and variant descriptions with visuals]
|
||||
|
||||
## Metrics
|
||||
- Primary: [metric and definition]
|
||||
- Secondary: [list]
|
||||
- Guardrails: [list]
|
||||
|
||||
## Implementation
|
||||
- Method: Client-side / Server-side
|
||||
- Tool: [Tool name]
|
||||
- Dev requirements: [If any]
|
||||
|
||||
## Analysis Plan
|
||||
- Success criteria: [What constitutes a win]
|
||||
- Segment analysis: [Planned segments]
|
||||
```
|
||||
|
||||
### Results Summary
|
||||
When test is complete
|
||||
|
||||
### Recommendations
|
||||
Next steps based on results
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
### Test Design
|
||||
- Testing too small a change (undetectable)
|
||||
- Testing too many things (can't isolate)
|
||||
- No clear hypothesis
|
||||
- Wrong audience
|
||||
|
||||
### Execution
|
||||
- Stopping early
|
||||
- Changing things mid-test
|
||||
- Not checking implementation
|
||||
- Uneven traffic allocation
|
||||
|
||||
### Analysis
|
||||
- Ignoring confidence intervals
|
||||
- Cherry-picking segments
|
||||
- Over-interpreting inconclusive results
|
||||
- Not considering practical significance
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's your current conversion rate?
|
||||
2. How much traffic does this page get?
|
||||
3. What change are you considering and why?
|
||||
4. What's the smallest improvement worth detecting?
|
||||
5. What tools do you have for testing?
|
||||
6. Have you tested this area before?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: For generating test ideas based on CRO principles
|
||||
- **analytics-tracking**: For setting up test measurement
|
||||
- **page-copywriting**: For creating variant copy
|
||||
539
skills/analytics-tracking.md
Normal file
539
skills/analytics-tracking.md
Normal file
@@ -0,0 +1,539 @@
|
||||
---
|
||||
name: analytics-tracking
|
||||
description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
|
||||
---
|
||||
|
||||
# Analytics Tracking
|
||||
|
||||
You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before implementing tracking, understand:
|
||||
|
||||
1. **Business Context**
|
||||
- What decisions will this data inform?
|
||||
- What are the key conversion actions?
|
||||
- What questions need answering?
|
||||
|
||||
2. **Current State**
|
||||
- What tracking exists?
|
||||
- What tools are in use (GA4, Mixpanel, Amplitude, etc.)?
|
||||
- What's working/not working?
|
||||
|
||||
3. **Technical Context**
|
||||
- What's the tech stack?
|
||||
- Who will implement and maintain?
|
||||
- Any privacy/compliance requirements?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Track for Decisions, Not Data
|
||||
- Every event should inform a decision
|
||||
- Avoid vanity metrics
|
||||
- Quality > quantity of events
|
||||
|
||||
### 2. Start with the Questions
|
||||
- What do you need to know?
|
||||
- What actions will you take based on this data?
|
||||
- Work backwards to what you need to track
|
||||
|
||||
### 3. Name Things Consistently
|
||||
- Naming conventions matter
|
||||
- Establish patterns before implementing
|
||||
- Document everything
|
||||
|
||||
### 4. Maintain Data Quality
|
||||
- Validate implementation
|
||||
- Monitor for issues
|
||||
- Clean data > more data
|
||||
|
||||
---
|
||||
|
||||
## Tracking Plan Framework
|
||||
|
||||
### Structure
|
||||
|
||||
```
|
||||
Event Name | Event Category | Properties | Trigger | Notes
|
||||
---------- | ------------- | ---------- | ------- | -----
|
||||
```
|
||||
|
||||
### Event Types
|
||||
|
||||
**Pageviews**
|
||||
- Automatic in most tools
|
||||
- Enhanced with page metadata
|
||||
|
||||
**User Actions**
|
||||
- Button clicks
|
||||
- Form submissions
|
||||
- Feature usage
|
||||
- Content interactions
|
||||
|
||||
**System Events**
|
||||
- Signup completed
|
||||
- Purchase completed
|
||||
- Subscription changed
|
||||
- Errors occurred
|
||||
|
||||
**Custom Conversions**
|
||||
- Goal completions
|
||||
- Funnel stages
|
||||
- Business-specific milestones
|
||||
|
||||
---
|
||||
|
||||
## Event Naming Conventions
|
||||
|
||||
### Format Options
|
||||
|
||||
**Object-Action (Recommended)**
|
||||
```
|
||||
signup_completed
|
||||
button_clicked
|
||||
form_submitted
|
||||
article_read
|
||||
```
|
||||
|
||||
**Action-Object**
|
||||
```
|
||||
click_button
|
||||
submit_form
|
||||
complete_signup
|
||||
```
|
||||
|
||||
**Category_Object_Action**
|
||||
```
|
||||
checkout_payment_completed
|
||||
blog_article_viewed
|
||||
onboarding_step_completed
|
||||
```
|
||||
|
||||
### Best Practices
|
||||
|
||||
- Lowercase with underscores
|
||||
- Be specific: `cta_hero_clicked` vs. `button_clicked`
|
||||
- Include context in properties, not event name
|
||||
- Avoid spaces and special characters
|
||||
- Document decisions
|
||||
|
||||
---
|
||||
|
||||
## Essential Events to Track
|
||||
|
||||
### Marketing Site
|
||||
|
||||
**Navigation**
|
||||
- page_view (enhanced)
|
||||
- outbound_link_clicked
|
||||
- scroll_depth (25%, 50%, 75%, 100%)
|
||||
|
||||
**Engagement**
|
||||
- cta_clicked (button_text, location)
|
||||
- video_played (video_id, duration)
|
||||
- form_started
|
||||
- form_submitted (form_type)
|
||||
- resource_downloaded (resource_name)
|
||||
|
||||
**Conversion**
|
||||
- signup_started
|
||||
- signup_completed
|
||||
- demo_requested
|
||||
- contact_submitted
|
||||
|
||||
### Product/App
|
||||
|
||||
**Onboarding**
|
||||
- signup_completed
|
||||
- onboarding_step_completed (step_number, step_name)
|
||||
- onboarding_completed
|
||||
- first_key_action_completed
|
||||
|
||||
**Core Usage**
|
||||
- feature_used (feature_name)
|
||||
- action_completed (action_type)
|
||||
- session_started
|
||||
- session_ended
|
||||
|
||||
**Monetization**
|
||||
- trial_started
|
||||
- pricing_viewed
|
||||
- checkout_started
|
||||
- purchase_completed (plan, value)
|
||||
- subscription_cancelled
|
||||
|
||||
### E-commerce
|
||||
|
||||
**Browsing**
|
||||
- product_viewed (product_id, category, price)
|
||||
- product_list_viewed (list_name, products)
|
||||
- product_searched (query, results_count)
|
||||
|
||||
**Cart**
|
||||
- product_added_to_cart
|
||||
- product_removed_from_cart
|
||||
- cart_viewed
|
||||
|
||||
**Checkout**
|
||||
- checkout_started
|
||||
- checkout_step_completed (step)
|
||||
- payment_info_entered
|
||||
- purchase_completed (order_id, value, products)
|
||||
|
||||
---
|
||||
|
||||
## Event Properties (Parameters)
|
||||
|
||||
### Standard Properties to Consider
|
||||
|
||||
**Page/Screen**
|
||||
- page_title
|
||||
- page_location (URL)
|
||||
- page_referrer
|
||||
- content_group
|
||||
|
||||
**User**
|
||||
- user_id (if logged in)
|
||||
- user_type (free, paid, admin)
|
||||
- account_id (B2B)
|
||||
- plan_type
|
||||
|
||||
**Campaign**
|
||||
- source
|
||||
- medium
|
||||
- campaign
|
||||
- content
|
||||
- term
|
||||
|
||||
**Product** (e-commerce)
|
||||
- product_id
|
||||
- product_name
|
||||
- category
|
||||
- price
|
||||
- quantity
|
||||
- currency
|
||||
|
||||
**Timing**
|
||||
- timestamp
|
||||
- session_duration
|
||||
- time_on_page
|
||||
|
||||
### Best Practices
|
||||
|
||||
- Use consistent property names
|
||||
- Include relevant context
|
||||
- Don't duplicate GA4 automatic properties
|
||||
- Avoid PII in properties
|
||||
- Document expected values
|
||||
|
||||
---
|
||||
|
||||
## GA4 Implementation
|
||||
|
||||
### Configuration
|
||||
|
||||
**Data Streams**
|
||||
- One stream per platform (web, iOS, Android)
|
||||
- Enable enhanced measurement
|
||||
|
||||
**Enhanced Measurement Events**
|
||||
- page_view (automatic)
|
||||
- scroll (90% depth)
|
||||
- outbound_click
|
||||
- site_search
|
||||
- video_engagement
|
||||
- file_download
|
||||
|
||||
**Recommended Events**
|
||||
- Use Google's predefined events when possible
|
||||
- Correct naming for enhanced reporting
|
||||
- See: https://support.google.com/analytics/answer/9267735
|
||||
|
||||
### Custom Events (GA4)
|
||||
|
||||
```javascript
|
||||
// gtag.js
|
||||
gtag('event', 'signup_completed', {
|
||||
'method': 'email',
|
||||
'plan': 'free'
|
||||
});
|
||||
|
||||
// Google Tag Manager (dataLayer)
|
||||
dataLayer.push({
|
||||
'event': 'signup_completed',
|
||||
'method': 'email',
|
||||
'plan': 'free'
|
||||
});
|
||||
```
|
||||
|
||||
### Conversions Setup
|
||||
|
||||
1. Collect event in GA4
|
||||
2. Mark as conversion in Admin > Events
|
||||
3. Set conversion counting (once per session or every time)
|
||||
4. Import to Google Ads if needed
|
||||
|
||||
### Custom Dimensions and Metrics
|
||||
|
||||
**When to use:**
|
||||
- Properties you want to segment by
|
||||
- Metrics you want to aggregate
|
||||
- Beyond standard parameters
|
||||
|
||||
**Setup:**
|
||||
1. Create in Admin > Custom definitions
|
||||
2. Scope: Event, User, or Item
|
||||
3. Parameter name must match
|
||||
|
||||
---
|
||||
|
||||
## Google Tag Manager Implementation
|
||||
|
||||
### Container Structure
|
||||
|
||||
**Tags**
|
||||
- GA4 Configuration (base)
|
||||
- GA4 Event tags (one per event or grouped)
|
||||
- Conversion pixels (Facebook, LinkedIn, etc.)
|
||||
|
||||
**Triggers**
|
||||
- Page View (DOM Ready, Window Loaded)
|
||||
- Click - All Elements / Just Links
|
||||
- Form Submission
|
||||
- Custom Events
|
||||
|
||||
**Variables**
|
||||
- Built-in: Click Text, Click URL, Page Path, etc.
|
||||
- Data Layer variables
|
||||
- JavaScript variables
|
||||
- Lookup tables
|
||||
|
||||
### Best Practices
|
||||
|
||||
- Use folders to organize
|
||||
- Consistent naming (Tag_Type_Description)
|
||||
- Version notes on every publish
|
||||
- Preview mode for testing
|
||||
- Workspaces for team collaboration
|
||||
|
||||
### Data Layer Pattern
|
||||
|
||||
```javascript
|
||||
// Push custom event
|
||||
dataLayer.push({
|
||||
'event': 'form_submitted',
|
||||
'form_name': 'contact',
|
||||
'form_location': 'footer'
|
||||
});
|
||||
|
||||
// Set user properties
|
||||
dataLayer.push({
|
||||
'user_id': '12345',
|
||||
'user_type': 'premium'
|
||||
});
|
||||
|
||||
// E-commerce event
|
||||
dataLayer.push({
|
||||
'event': 'purchase',
|
||||
'ecommerce': {
|
||||
'transaction_id': 'T12345',
|
||||
'value': 99.99,
|
||||
'currency': 'USD',
|
||||
'items': [{
|
||||
'item_id': 'SKU123',
|
||||
'item_name': 'Product Name',
|
||||
'price': 99.99
|
||||
}]
|
||||
}
|
||||
});
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## UTM Parameter Strategy
|
||||
|
||||
### Standard Parameters
|
||||
|
||||
| Parameter | Purpose | Example |
|
||||
|-----------|---------|---------|
|
||||
| utm_source | Where traffic comes from | google, facebook, newsletter |
|
||||
| utm_medium | Marketing medium | cpc, email, social, referral |
|
||||
| utm_campaign | Campaign name | spring_sale, product_launch |
|
||||
| utm_content | Differentiate versions | hero_cta, sidebar_link |
|
||||
| utm_term | Paid search keywords | running+shoes |
|
||||
|
||||
### Naming Conventions
|
||||
|
||||
**Lowercase everything**
|
||||
- google, not Google
|
||||
- email, not Email
|
||||
|
||||
**Use underscores or hyphens consistently**
|
||||
- product_launch or product-launch
|
||||
- Pick one, stick with it
|
||||
|
||||
**Be specific but concise**
|
||||
- blog_footer_cta, not cta1
|
||||
- 2024_q1_promo, not promo
|
||||
|
||||
### UTM Documentation
|
||||
|
||||
Track all UTMs in a spreadsheet or tool:
|
||||
|
||||
| Campaign | Source | Medium | Content | Full URL | Owner | Date |
|
||||
|----------|--------|--------|---------|----------|-------|------|
|
||||
| ... | ... | ... | ... | ... | ... | ... |
|
||||
|
||||
### UTM Builder
|
||||
|
||||
Provide a consistent UTM builder link to team:
|
||||
- Google's URL builder
|
||||
- Internal tool
|
||||
- Spreadsheet formula
|
||||
|
||||
---
|
||||
|
||||
## Debugging and Validation
|
||||
|
||||
### Testing Tools
|
||||
|
||||
**GA4 DebugView**
|
||||
- Real-time event monitoring
|
||||
- Enable with ?debug_mode=true
|
||||
- Or via Chrome extension
|
||||
|
||||
**GTM Preview Mode**
|
||||
- Test triggers and tags
|
||||
- See data layer state
|
||||
- Validate before publish
|
||||
|
||||
**Browser Extensions**
|
||||
- GA Debugger
|
||||
- Tag Assistant
|
||||
- dataLayer Inspector
|
||||
|
||||
### Validation Checklist
|
||||
|
||||
- [ ] Events firing on correct triggers
|
||||
- [ ] Property values populating correctly
|
||||
- [ ] No duplicate events
|
||||
- [ ] Works across browsers
|
||||
- [ ] Works on mobile
|
||||
- [ ] Conversions recorded correctly
|
||||
- [ ] User ID passing when logged in
|
||||
- [ ] No PII leaking
|
||||
|
||||
### Common Issues
|
||||
|
||||
**Events not firing**
|
||||
- Trigger misconfigured
|
||||
- Tag paused
|
||||
- GTM not loaded on page
|
||||
|
||||
**Wrong values**
|
||||
- Variable not configured
|
||||
- Data layer not pushing correctly
|
||||
- Timing issues (fire before data ready)
|
||||
|
||||
**Duplicate events**
|
||||
- Multiple GTM containers
|
||||
- Multiple tag instances
|
||||
- Trigger firing multiple times
|
||||
|
||||
---
|
||||
|
||||
## Privacy and Compliance
|
||||
|
||||
### Considerations
|
||||
|
||||
- Cookie consent required in EU/UK/CA
|
||||
- No PII in analytics properties
|
||||
- Data retention settings
|
||||
- User deletion capabilities
|
||||
- Cross-device tracking consent
|
||||
|
||||
### Implementation
|
||||
|
||||
**Consent Mode (GA4)**
|
||||
- Wait for consent before tracking
|
||||
- Use consent mode for partial tracking
|
||||
- Integrate with consent management platform
|
||||
|
||||
**Data Minimization**
|
||||
- Only collect what you need
|
||||
- IP anonymization
|
||||
- No PII in custom dimensions
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Tracking Plan Document
|
||||
|
||||
```
|
||||
# [Site/Product] Tracking Plan
|
||||
|
||||
## Overview
|
||||
- Tools: GA4, GTM
|
||||
- Last updated: [Date]
|
||||
- Owner: [Name]
|
||||
|
||||
## Events
|
||||
|
||||
### Marketing Events
|
||||
|
||||
| Event Name | Description | Properties | Trigger |
|
||||
|------------|-------------|------------|---------|
|
||||
| signup_started | User initiates signup | source, page | Click signup CTA |
|
||||
| signup_completed | User completes signup | method, plan | Signup success page |
|
||||
|
||||
### Product Events
|
||||
[Similar table]
|
||||
|
||||
## Custom Dimensions
|
||||
|
||||
| Name | Scope | Parameter | Description |
|
||||
|------|-------|-----------|-------------|
|
||||
| user_type | User | user_type | Free, trial, paid |
|
||||
|
||||
## Conversions
|
||||
|
||||
| Conversion | Event | Counting | Google Ads |
|
||||
|------------|-------|----------|------------|
|
||||
| Signup | signup_completed | Once per session | Yes |
|
||||
|
||||
## UTM Convention
|
||||
|
||||
[Guidelines]
|
||||
```
|
||||
|
||||
### Implementation Code
|
||||
|
||||
Provide ready-to-use code snippets
|
||||
|
||||
### Testing Checklist
|
||||
|
||||
Specific validation steps
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What tools are you using (GA4, Mixpanel, etc.)?
|
||||
2. What key actions do you want to track?
|
||||
3. What decisions will this data inform?
|
||||
4. Who implements - dev team or marketing?
|
||||
5. Are there privacy/consent requirements?
|
||||
6. What's already tracked?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **ab-test-setup**: For experiment tracking
|
||||
- **seo-audit**: For organic traffic analysis
|
||||
- **page-cro**: For conversion optimization (uses this data)
|
||||
416
skills/email-sequence.md
Normal file
416
skills/email-sequence.md
Normal file
@@ -0,0 +1,416 @@
|
||||
---
|
||||
name: email-sequence
|
||||
description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
|
||||
---
|
||||
|
||||
# Email Sequence Design
|
||||
|
||||
You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before creating a sequence, understand:
|
||||
|
||||
1. **Sequence Type**
|
||||
- Welcome/onboarding sequence
|
||||
- Lead nurture sequence
|
||||
- Re-engagement sequence
|
||||
- Post-purchase sequence
|
||||
- Event-based sequence
|
||||
- Educational sequence
|
||||
- Sales sequence
|
||||
|
||||
2. **Audience Context**
|
||||
- Who are they?
|
||||
- What triggered them into this sequence?
|
||||
- What do they already know/believe?
|
||||
- What's their current relationship with you?
|
||||
|
||||
3. **Goals**
|
||||
- Primary conversion goal
|
||||
- Relationship-building goals
|
||||
- Segmentation goals
|
||||
- What defines success?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. One Email, One Job
|
||||
- Each email has one primary purpose
|
||||
- One main CTA per email
|
||||
- Don't try to do everything
|
||||
|
||||
### 2. Value Before Ask
|
||||
- Lead with usefulness
|
||||
- Build trust through content
|
||||
- Earn the right to sell
|
||||
|
||||
### 3. Relevance Over Volume
|
||||
- Fewer, better emails win
|
||||
- Segment for relevance
|
||||
- Quality > frequency
|
||||
|
||||
### 4. Clear Path Forward
|
||||
- Every email moves them somewhere
|
||||
- Links should do something useful
|
||||
- Make next steps obvious
|
||||
|
||||
---
|
||||
|
||||
## Email Sequence Strategy
|
||||
|
||||
### Sequence Length
|
||||
- Welcome: 3-7 emails
|
||||
- Lead nurture: 5-10 emails
|
||||
- Onboarding: 5-10 emails
|
||||
- Re-engagement: 3-5 emails
|
||||
|
||||
Depends on:
|
||||
- Sales cycle length
|
||||
- Product complexity
|
||||
- Relationship stage
|
||||
|
||||
### Timing/Delays
|
||||
- Welcome email: Immediately
|
||||
- Early sequence: 1-2 days apart
|
||||
- Nurture: 2-4 days apart
|
||||
- Long-term: Weekly or bi-weekly
|
||||
|
||||
Consider:
|
||||
- B2B: Avoid weekends
|
||||
- B2C: Test weekends
|
||||
- Time zones: Send at local time
|
||||
|
||||
### Subject Line Strategy
|
||||
- Clear > Clever
|
||||
- Specific > Vague
|
||||
- Benefit or curiosity-driven
|
||||
- 40-60 characters ideal
|
||||
- Test emoji (they're polarizing)
|
||||
|
||||
**Patterns that work:**
|
||||
- Question: "Still struggling with X?"
|
||||
- How-to: "How to [achieve outcome] in [timeframe]"
|
||||
- Number: "3 ways to [benefit]"
|
||||
- Direct: "[First name], your [thing] is ready"
|
||||
- Story tease: "The mistake I made with [topic]"
|
||||
|
||||
### Preview Text
|
||||
- Extends the subject line
|
||||
- ~90-140 characters
|
||||
- Don't repeat subject line
|
||||
- Complete the thought or add intrigue
|
||||
|
||||
---
|
||||
|
||||
## Sequence Templates
|
||||
|
||||
### Welcome Sequence (Post-Signup)
|
||||
|
||||
**Email 1: Welcome (Immediate)**
|
||||
- Subject: Welcome to [Product] — here's your first step
|
||||
- Deliver what was promised (lead magnet, access, etc.)
|
||||
- Single next action
|
||||
- Set expectations for future emails
|
||||
|
||||
**Email 2: Quick Win (Day 1-2)**
|
||||
- Subject: Get your first [result] in 10 minutes
|
||||
- Enable small success
|
||||
- Build confidence
|
||||
- Link to helpful resource
|
||||
|
||||
**Email 3: Story/Why (Day 3-4)**
|
||||
- Subject: Why we built [Product]
|
||||
- Origin story or mission
|
||||
- Connect emotionally
|
||||
- Show you understand their problem
|
||||
|
||||
**Email 4: Social Proof (Day 5-6)**
|
||||
- Subject: How [Customer] achieved [Result]
|
||||
- Case study or testimonial
|
||||
- Relatable to their situation
|
||||
- Soft CTA to explore
|
||||
|
||||
**Email 5: Overcome Objection (Day 7-8)**
|
||||
- Subject: "I don't have time for X" — sound familiar?
|
||||
- Address common hesitation
|
||||
- Reframe the obstacle
|
||||
- Show easy path forward
|
||||
|
||||
**Email 6: Core Feature (Day 9-11)**
|
||||
- Subject: Have you tried [Feature] yet?
|
||||
- Highlight underused capability
|
||||
- Show clear benefit
|
||||
- Direct CTA to try it
|
||||
|
||||
**Email 7: Conversion (Day 12-14)**
|
||||
- Subject: Ready to [upgrade/buy/commit]?
|
||||
- Summarize value
|
||||
- Clear offer
|
||||
- Urgency if appropriate
|
||||
- Risk reversal (guarantee, trial)
|
||||
|
||||
---
|
||||
|
||||
### Lead Nurture Sequence (Pre-Sale)
|
||||
|
||||
**Email 1: Deliver + Introduce (Immediate)**
|
||||
- Deliver the lead magnet
|
||||
- Brief intro to who you are
|
||||
- Preview what's coming
|
||||
|
||||
**Email 2: Expand on Topic (Day 2-3)**
|
||||
- Related insight to lead magnet
|
||||
- Establish expertise
|
||||
- Light CTA to content
|
||||
|
||||
**Email 3: Problem Deep-Dive (Day 4-5)**
|
||||
- Articulate their problem deeply
|
||||
- Show you understand
|
||||
- Hint at solution
|
||||
|
||||
**Email 4: Solution Framework (Day 6-8)**
|
||||
- Your approach/methodology
|
||||
- Educational, not salesy
|
||||
- Builds toward your product
|
||||
|
||||
**Email 5: Case Study (Day 9-11)**
|
||||
- Real results from real customer
|
||||
- Specific and relatable
|
||||
- Soft CTA
|
||||
|
||||
**Email 6: Differentiation (Day 12-14)**
|
||||
- Why your approach is different
|
||||
- Address alternatives
|
||||
- Build preference
|
||||
|
||||
**Email 7: Objection Handler (Day 15-18)**
|
||||
- Common concern addressed
|
||||
- FAQ or myth-busting
|
||||
- Reduce friction
|
||||
|
||||
**Email 8: Direct Offer (Day 19-21)**
|
||||
- Clear pitch
|
||||
- Strong value proposition
|
||||
- Specific CTA
|
||||
- Urgency if available
|
||||
|
||||
---
|
||||
|
||||
### Re-Engagement Sequence
|
||||
|
||||
**Email 1: Check-In (Day 30-60 of inactivity)**
|
||||
- Subject: Is everything okay, [Name]?
|
||||
- Genuine concern
|
||||
- Ask what happened
|
||||
- Easy win to re-engage
|
||||
|
||||
**Email 2: Value Reminder (Day 2-3 after)**
|
||||
- Subject: Remember when you [achieved X]?
|
||||
- Remind of past value
|
||||
- What's new since they left
|
||||
- Quick CTA
|
||||
|
||||
**Email 3: Incentive (Day 5-7 after)**
|
||||
- Subject: We miss you — here's something special
|
||||
- Offer if appropriate
|
||||
- Limited time
|
||||
- Clear CTA
|
||||
|
||||
**Email 4: Last Chance (Day 10-14 after)**
|
||||
- Subject: Should we stop emailing you?
|
||||
- Honest and direct
|
||||
- One-click to stay or go
|
||||
- Clean the list if no response
|
||||
|
||||
---
|
||||
|
||||
### Onboarding Sequence (Product Users)
|
||||
|
||||
Coordinate with in-app onboarding. Email supports, doesn't duplicate.
|
||||
|
||||
**Email 1: Welcome + First Step (Immediate)**
|
||||
- Confirm signup
|
||||
- One critical action
|
||||
- Link directly to that action
|
||||
|
||||
**Email 2: Getting Started Help (Day 1)**
|
||||
- If they haven't completed step 1
|
||||
- Quick tip or video
|
||||
- Support option
|
||||
|
||||
**Email 3: Feature Highlight (Day 2-3)**
|
||||
- Key feature they should know
|
||||
- Specific use case
|
||||
- In-app link
|
||||
|
||||
**Email 4: Success Story (Day 4-5)**
|
||||
- Customer who succeeded
|
||||
- Relatable journey
|
||||
- Motivational
|
||||
|
||||
**Email 5: Check-In (Day 7)**
|
||||
- How's it going?
|
||||
- Ask for feedback
|
||||
- Offer help
|
||||
|
||||
**Email 6: Advanced Tip (Day 10-12)**
|
||||
- Power feature
|
||||
- For engaged users
|
||||
- Level-up content
|
||||
|
||||
**Email 7: Upgrade/Expand (Day 14+)**
|
||||
- For trial users: conversion push
|
||||
- For free users: upgrade prompt
|
||||
- For paid: expansion opportunity
|
||||
|
||||
---
|
||||
|
||||
## Email Copy Guidelines
|
||||
|
||||
### Structure
|
||||
1. **Hook**: First line grabs attention
|
||||
2. **Context**: Why this matters to them
|
||||
3. **Value**: The useful content
|
||||
4. **CTA**: What to do next
|
||||
5. **Sign-off**: Human, warm close
|
||||
|
||||
### Formatting
|
||||
- Short paragraphs (1-3 sentences)
|
||||
- White space between sections
|
||||
- Bullet points for scanability
|
||||
- Bold for emphasis (sparingly)
|
||||
- Mobile-first (most read on phone)
|
||||
|
||||
### Tone
|
||||
- Conversational, not formal
|
||||
- First-person (I/we) and second-person (you)
|
||||
- Active voice
|
||||
- Match your brand but lean friendly
|
||||
- Read it out loud—does it sound human?
|
||||
|
||||
### Length
|
||||
- Shorter is usually better
|
||||
- 50-125 words for transactional
|
||||
- 150-300 words for educational
|
||||
- 300-500 words for story-driven
|
||||
- If it's long, it better be good
|
||||
|
||||
### CTA Buttons vs. Links
|
||||
- Buttons: Primary actions, high-visibility
|
||||
- Links: Secondary actions, in-text
|
||||
- One clear primary CTA per email
|
||||
- Button text: Action + outcome
|
||||
|
||||
---
|
||||
|
||||
## Personalization
|
||||
|
||||
### Merge Fields
|
||||
- First name (fallback to "there" or "friend")
|
||||
- Company name (B2B)
|
||||
- Relevant data (usage, plan, etc.)
|
||||
|
||||
### Dynamic Content
|
||||
- Based on segment
|
||||
- Based on behavior
|
||||
- Based on stage
|
||||
|
||||
### Triggered Emails
|
||||
- Action-based sends
|
||||
- More relevant than time-based
|
||||
- Examples: Feature used, milestone hit, inactivity
|
||||
|
||||
---
|
||||
|
||||
## Segmentation Strategies
|
||||
|
||||
### By Behavior
|
||||
- Openers vs. non-openers
|
||||
- Clickers vs. non-clickers
|
||||
- Active vs. inactive
|
||||
|
||||
### By Stage
|
||||
- Trial vs. paid
|
||||
- New vs. long-term
|
||||
- Engaged vs. at-risk
|
||||
|
||||
### By Profile
|
||||
- Industry/role (B2B)
|
||||
- Use case / goal
|
||||
- Company size
|
||||
|
||||
---
|
||||
|
||||
## Testing and Optimization
|
||||
|
||||
### What to Test
|
||||
- Subject lines (highest impact)
|
||||
- Send times
|
||||
- Email length
|
||||
- CTA placement and copy
|
||||
- Personalization level
|
||||
- Sequence timing
|
||||
|
||||
### How to Test
|
||||
- A/B test one variable at a time
|
||||
- Sufficient sample size
|
||||
- Statistical significance
|
||||
- Document learnings
|
||||
|
||||
### Metrics to Track
|
||||
- Open rate (benchmark: 20-40%)
|
||||
- Click rate (benchmark: 2-5%)
|
||||
- Unsubscribe rate (keep under 0.5%)
|
||||
- Conversion rate (specific to sequence goal)
|
||||
- Revenue per email (if applicable)
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Sequence Overview
|
||||
```
|
||||
Sequence Name: [Name]
|
||||
Trigger: [What starts the sequence]
|
||||
Goal: [Primary conversion goal]
|
||||
Length: [Number of emails]
|
||||
Timing: [Delay between emails]
|
||||
Exit Conditions: [When they leave the sequence]
|
||||
```
|
||||
|
||||
### For Each Email
|
||||
```
|
||||
Email [#]: [Name/Purpose]
|
||||
Send: [Timing]
|
||||
Subject: [Subject line]
|
||||
Preview: [Preview text]
|
||||
Body: [Full copy]
|
||||
CTA: [Button text] → [Link destination]
|
||||
Segment/Conditions: [If applicable]
|
||||
```
|
||||
|
||||
### Metrics Plan
|
||||
What to measure and benchmarks
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What triggers entry to this sequence?
|
||||
2. What's the primary goal/conversion action?
|
||||
3. Who is the audience?
|
||||
4. What do they already know about you?
|
||||
5. What other emails are they receiving?
|
||||
6. What's your current email performance?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **onboarding-cro**: For in-app onboarding (email supports this)
|
||||
- **page-copywriting**: For landing pages emails link to
|
||||
- **ab-test-setup**: For testing email elements
|
||||
- **popup-cro**: For email capture popups
|
||||
345
skills/form-cro.md
Normal file
345
skills/form-cro.md
Normal file
@@ -0,0 +1,345 @@
|
||||
---
|
||||
name: form-cro
|
||||
description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
|
||||
---
|
||||
|
||||
# Form CRO
|
||||
|
||||
You are an expert in form optimization. Your goal is to maximize form completion rates while capturing the data that matters.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, identify:
|
||||
|
||||
1. **Form Type**
|
||||
- Lead capture (gated content, newsletter)
|
||||
- Contact form
|
||||
- Demo/sales request
|
||||
- Application form
|
||||
- Survey/feedback
|
||||
- Checkout form
|
||||
- Quote request
|
||||
|
||||
2. **Current State**
|
||||
- How many fields?
|
||||
- What's the current completion rate?
|
||||
- Mobile vs. desktop split?
|
||||
- Where do users abandon?
|
||||
|
||||
3. **Business Context**
|
||||
- What happens with form submissions?
|
||||
- Which fields are actually used in follow-up?
|
||||
- Are there compliance/legal requirements?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Every Field Has a Cost
|
||||
Each field reduces completion rate. Rule of thumb:
|
||||
- 3 fields: Baseline
|
||||
- 4-6 fields: 10-25% reduction
|
||||
- 7+ fields: 25-50%+ reduction
|
||||
|
||||
For each field, ask:
|
||||
- Is this absolutely necessary before we can help them?
|
||||
- Can we get this information another way?
|
||||
- Can we ask this later?
|
||||
|
||||
### 2. Value Must Exceed Effort
|
||||
- Clear value proposition above form
|
||||
- Make what they get obvious
|
||||
- Reduce perceived effort (field count, labels)
|
||||
|
||||
### 3. Reduce Cognitive Load
|
||||
- One question per field
|
||||
- Clear, conversational labels
|
||||
- Logical grouping and order
|
||||
- Smart defaults where possible
|
||||
|
||||
---
|
||||
|
||||
## Field-by-Field Optimization
|
||||
|
||||
### Email Field
|
||||
- Single field, no confirmation
|
||||
- Inline validation
|
||||
- Typo detection (did you mean gmail.com?)
|
||||
- Proper mobile keyboard
|
||||
|
||||
### Name Fields
|
||||
- Single "Name" vs. First/Last — test this
|
||||
- Single field reduces friction
|
||||
- Split needed only if personalization requires it
|
||||
|
||||
### Phone Number
|
||||
- Make optional if possible
|
||||
- If required, explain why
|
||||
- Auto-format as they type
|
||||
- Country code handling
|
||||
|
||||
### Company/Organization
|
||||
- Auto-suggest for faster entry
|
||||
- Enrichment after submission (Clearbit, etc.)
|
||||
- Consider inferring from email domain
|
||||
|
||||
### Job Title/Role
|
||||
- Dropdown if categories matter
|
||||
- Free text if wide variation
|
||||
- Consider making optional
|
||||
|
||||
### Message/Comments (Free Text)
|
||||
- Make optional
|
||||
- Reasonable character guidance
|
||||
- Expand on focus
|
||||
|
||||
### Dropdown Selects
|
||||
- "Select one..." placeholder
|
||||
- Searchable if many options
|
||||
- Consider radio buttons if < 5 options
|
||||
- "Other" option with text field
|
||||
|
||||
### Checkboxes (Multi-select)
|
||||
- Clear, parallel labels
|
||||
- Reasonable number of options
|
||||
- Consider "Select all that apply" instruction
|
||||
|
||||
---
|
||||
|
||||
## Form Layout Optimization
|
||||
|
||||
### Field Order
|
||||
1. Start with easiest fields (name, email)
|
||||
2. Build commitment before asking more
|
||||
3. Sensitive fields last (phone, company size)
|
||||
4. Logical grouping if many fields
|
||||
|
||||
### Labels and Placeholders
|
||||
- Labels: Always visible (not just placeholder)
|
||||
- Placeholders: Examples, not labels
|
||||
- Help text: Only when genuinely helpful
|
||||
|
||||
**Good:**
|
||||
```
|
||||
Email
|
||||
[name@company.com]
|
||||
```
|
||||
|
||||
**Bad:**
|
||||
```
|
||||
[Enter your email address] ← Disappears on focus
|
||||
```
|
||||
|
||||
### Visual Design
|
||||
- Sufficient spacing between fields
|
||||
- Clear visual hierarchy
|
||||
- CTA button stands out
|
||||
- Mobile-friendly tap targets (44px+)
|
||||
|
||||
### Single Column vs. Multi-Column
|
||||
- Single column: Higher completion, mobile-friendly
|
||||
- Multi-column: Only for short related fields (First/Last name)
|
||||
- When in doubt, single column
|
||||
|
||||
---
|
||||
|
||||
## Multi-Step Forms
|
||||
|
||||
### When to Use Multi-Step
|
||||
- More than 5-6 fields
|
||||
- Logically distinct sections
|
||||
- Conditional paths based on answers
|
||||
- Complex forms (applications, quotes)
|
||||
|
||||
### Multi-Step Best Practices
|
||||
- Progress indicator (step X of Y)
|
||||
- Start with easy, end with sensitive
|
||||
- One topic per step
|
||||
- Allow back navigation
|
||||
- Save progress (don't lose data on refresh)
|
||||
- Clear indication of required vs. optional
|
||||
|
||||
### Progressive Commitment Pattern
|
||||
1. Low-friction start (just email)
|
||||
2. More detail (name, company)
|
||||
3. Qualifying questions
|
||||
4. Contact preferences
|
||||
|
||||
---
|
||||
|
||||
## Error Handling
|
||||
|
||||
### Inline Validation
|
||||
- Validate as they move to next field
|
||||
- Don't validate too aggressively while typing
|
||||
- Clear visual indicators (green check, red border)
|
||||
|
||||
### Error Messages
|
||||
- Specific to the problem
|
||||
- Suggest how to fix
|
||||
- Positioned near the field
|
||||
- Don't clear their input
|
||||
|
||||
**Good:** "Please enter a valid email address (e.g., name@company.com)"
|
||||
**Bad:** "Invalid input"
|
||||
|
||||
### On Submit
|
||||
- Focus on first error field
|
||||
- Summarize errors if multiple
|
||||
- Preserve all entered data
|
||||
- Don't clear form on error
|
||||
|
||||
---
|
||||
|
||||
## Submit Button Optimization
|
||||
|
||||
### Button Copy
|
||||
Weak: "Submit" | "Send"
|
||||
Strong: "[Action] + [What they get]"
|
||||
|
||||
Examples:
|
||||
- "Get My Free Quote"
|
||||
- "Download the Guide"
|
||||
- "Request Demo"
|
||||
- "Send Message"
|
||||
- "Start Free Trial"
|
||||
|
||||
### Button Placement
|
||||
- Immediately after last field
|
||||
- Left-aligned with fields
|
||||
- Sufficient size and contrast
|
||||
- Mobile: Sticky or clearly visible
|
||||
|
||||
### Post-Submit States
|
||||
- Loading state (disable button, show spinner)
|
||||
- Success confirmation (clear next steps)
|
||||
- Error handling (clear message, focus on issue)
|
||||
|
||||
---
|
||||
|
||||
## Trust and Friction Reduction
|
||||
|
||||
### Near the Form
|
||||
- Privacy statement: "We'll never share your info"
|
||||
- Security badges if collecting sensitive data
|
||||
- Testimonial or social proof
|
||||
- Expected response time
|
||||
|
||||
### Reducing Perceived Effort
|
||||
- "Takes 30 seconds"
|
||||
- Field count indicator
|
||||
- Remove visual clutter
|
||||
- Generous white space
|
||||
|
||||
### Addressing Objections
|
||||
- "No spam, unsubscribe anytime"
|
||||
- "We won't share your number"
|
||||
- "No credit card required"
|
||||
|
||||
---
|
||||
|
||||
## Form Types: Specific Guidance
|
||||
|
||||
### Lead Capture (Gated Content)
|
||||
- Minimum viable fields (often just email)
|
||||
- Clear value proposition for what they get
|
||||
- Consider asking enrichment questions post-download
|
||||
- Test email-only vs. email + name
|
||||
|
||||
### Contact Form
|
||||
- Essential: Email/Name + Message
|
||||
- Phone optional
|
||||
- Set response time expectations
|
||||
- Offer alternatives (chat, phone)
|
||||
|
||||
### Demo Request
|
||||
- Name, Email, Company required
|
||||
- Phone: Optional with "preferred contact" choice
|
||||
- Use case/goal question helps personalize
|
||||
- Calendar embed can increase show rate
|
||||
|
||||
### Quote/Estimate Request
|
||||
- Multi-step often works well
|
||||
- Start with easy questions
|
||||
- Technical details later
|
||||
- Save progress for complex forms
|
||||
|
||||
### Survey Forms
|
||||
- Progress bar essential
|
||||
- One question per screen for engagement
|
||||
- Skip logic for relevance
|
||||
- Consider incentive for completion
|
||||
|
||||
---
|
||||
|
||||
## Mobile Optimization
|
||||
|
||||
- Larger touch targets (44px minimum height)
|
||||
- Appropriate keyboard types (email, tel, number)
|
||||
- Autofill support
|
||||
- Single column only
|
||||
- Sticky submit button
|
||||
- Minimal typing (dropdowns, buttons)
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
### Key Metrics
|
||||
- **Form start rate**: Page views → Started form
|
||||
- **Completion rate**: Started → Submitted
|
||||
- **Field drop-off**: Which fields lose people
|
||||
- **Error rate**: By field
|
||||
- **Time to complete**: Total and by field
|
||||
- **Mobile vs. desktop**: Completion by device
|
||||
|
||||
### What to Track
|
||||
- Form views
|
||||
- First field focus
|
||||
- Each field completion
|
||||
- Errors by field
|
||||
- Submit attempts
|
||||
- Successful submissions
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Form Audit
|
||||
For each issue:
|
||||
- **Issue**: What's wrong
|
||||
- **Impact**: Estimated effect on conversions
|
||||
- **Fix**: Specific recommendation
|
||||
- **Priority**: High/Medium/Low
|
||||
|
||||
### Recommended Form Design
|
||||
- **Required fields**: Justified list
|
||||
- **Optional fields**: With rationale
|
||||
- **Field order**: Recommended sequence
|
||||
- **Copy**: Labels, placeholders, button
|
||||
- **Error messages**: For each field
|
||||
- **Layout**: Visual guidance
|
||||
|
||||
### Test Hypotheses
|
||||
Ideas to A/B test with expected outcomes
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's your current form completion rate?
|
||||
2. Do you have field-level analytics?
|
||||
3. What happens with the data after submission?
|
||||
4. Which fields are actually used in follow-up?
|
||||
5. Are there compliance/legal requirements?
|
||||
6. What's the mobile vs. desktop split?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **signup-flow-cro**: For account creation forms
|
||||
- **popup-cro**: For forms inside popups/modals
|
||||
- **page-cro**: For the page containing the form
|
||||
- **ab-test-setup**: For testing form changes
|
||||
576
skills/free-tool-strategy.md
Normal file
576
skills/free-tool-strategy.md
Normal file
@@ -0,0 +1,576 @@
|
||||
---
|
||||
name: free-tool-strategy
|
||||
description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
|
||||
---
|
||||
|
||||
# Free Tool Strategy (Engineering as Marketing)
|
||||
|
||||
You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before designing a tool strategy, understand:
|
||||
|
||||
1. **Business Context**
|
||||
- What's the core product/service?
|
||||
- Who is the target audience?
|
||||
- What problems do they have?
|
||||
|
||||
2. **Goals**
|
||||
- Lead generation primary goal?
|
||||
- SEO/traffic acquisition?
|
||||
- Brand awareness?
|
||||
- Product education?
|
||||
|
||||
3. **Resources**
|
||||
- Technical capacity to build?
|
||||
- Ongoing maintenance bandwidth?
|
||||
- Budget for promotion?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Solve a Real Problem
|
||||
- Tool must provide genuine value
|
||||
- Solves a problem your audience actually has
|
||||
- Useful even without your main product
|
||||
|
||||
### 2. Adjacent to Core Product
|
||||
- Related to what you sell
|
||||
- Natural path from tool to product
|
||||
- Educates on problem you solve
|
||||
|
||||
### 3. Simple and Focused
|
||||
- Does one thing well
|
||||
- Low friction to use
|
||||
- Immediate value
|
||||
|
||||
### 4. Worth the Investment
|
||||
- Lead value × expected leads > build cost + maintenance
|
||||
- Consider SEO value
|
||||
- Consider brand halo effect
|
||||
|
||||
---
|
||||
|
||||
## Tool Types
|
||||
|
||||
### Calculators
|
||||
|
||||
**Best for**: Decisions involving numbers, comparisons, estimates
|
||||
|
||||
**Examples**:
|
||||
- ROI calculator
|
||||
- Savings calculator
|
||||
- Cost comparison tool
|
||||
- Salary calculator
|
||||
- Tax estimator
|
||||
|
||||
**Why they work**:
|
||||
- Personalized output
|
||||
- High perceived value
|
||||
- Share-worthy results
|
||||
- Clear problem → solution
|
||||
|
||||
### Generators
|
||||
|
||||
**Best for**: Creating something useful quickly
|
||||
|
||||
**Examples**:
|
||||
- Policy generator
|
||||
- Template generator
|
||||
- Name/tagline generator
|
||||
- Email subject line generator
|
||||
- Resume builder
|
||||
|
||||
**Why they work**:
|
||||
- Tangible output
|
||||
- Saves time
|
||||
- Easily shared
|
||||
- Repeat usage
|
||||
|
||||
### Analyzers/Auditors
|
||||
|
||||
**Best for**: Evaluating existing work or assets
|
||||
|
||||
**Examples**:
|
||||
- Website grader
|
||||
- SEO analyzer
|
||||
- Email subject tester
|
||||
- Headline analyzer
|
||||
- Security checker
|
||||
|
||||
**Why they work**:
|
||||
- Curiosity-driven
|
||||
- Personalized insights
|
||||
- Creates awareness of problems
|
||||
- Natural lead to solution
|
||||
|
||||
### Testers/Validators
|
||||
|
||||
**Best for**: Checking if something works
|
||||
|
||||
**Examples**:
|
||||
- Meta tag preview
|
||||
- Email rendering test
|
||||
- Accessibility checker
|
||||
- Mobile-friendly test
|
||||
- Speed test
|
||||
|
||||
**Why they work**:
|
||||
- Immediate utility
|
||||
- Bookmark-worthy
|
||||
- Repeat usage
|
||||
- Professional necessity
|
||||
|
||||
### Libraries/Resources
|
||||
|
||||
**Best for**: Reference material
|
||||
|
||||
**Examples**:
|
||||
- Icon library
|
||||
- Template library
|
||||
- Code snippet library
|
||||
- Example gallery
|
||||
- Directory
|
||||
|
||||
**Why they work**:
|
||||
- High SEO value
|
||||
- Ongoing traffic
|
||||
- Establishes authority
|
||||
- Linkable asset
|
||||
|
||||
### Interactive Educational
|
||||
|
||||
**Best for**: Learning/understanding
|
||||
|
||||
**Examples**:
|
||||
- Interactive tutorials
|
||||
- Code playgrounds
|
||||
- Visual explainers
|
||||
- Quizzes/assessments
|
||||
- Simulators
|
||||
|
||||
**Why they work**:
|
||||
- Engages deeply
|
||||
- Demonstrates expertise
|
||||
- Shareable
|
||||
- Memory-creating
|
||||
|
||||
---
|
||||
|
||||
## Ideation Framework
|
||||
|
||||
### Start with Pain Points
|
||||
|
||||
1. **What problems does your audience Google?**
|
||||
- Search query research
|
||||
- Common questions
|
||||
- "How to" searches
|
||||
|
||||
2. **What manual processes are tedious?**
|
||||
- Tasks done in spreadsheets
|
||||
- Repetitive calculations
|
||||
- Copy-paste workflows
|
||||
|
||||
3. **What do they need before buying your product?**
|
||||
- Assessments of current state
|
||||
- Planning/scoping
|
||||
- Comparisons
|
||||
|
||||
4. **What information do they wish they had?**
|
||||
- Data they can't easily access
|
||||
- Personalized insights
|
||||
- Industry benchmarks
|
||||
|
||||
### Validate the Idea
|
||||
|
||||
**Search demand:**
|
||||
- Is there search volume for this problem?
|
||||
- What keywords would rank?
|
||||
- How competitive?
|
||||
|
||||
**Uniqueness:**
|
||||
- What exists already?
|
||||
- How can you be 10x better or different?
|
||||
- What's your unique angle?
|
||||
|
||||
**Lead quality:**
|
||||
- Does this problem-audience match buyers?
|
||||
- Will users be your target customers?
|
||||
- Is there a natural path to your product?
|
||||
|
||||
**Build feasibility:**
|
||||
- How complex to build?
|
||||
- Can you scope an MVP?
|
||||
- Ongoing maintenance burden?
|
||||
|
||||
---
|
||||
|
||||
## SEO Considerations
|
||||
|
||||
### Keyword Strategy
|
||||
|
||||
**Tool landing page:**
|
||||
- "[thing] calculator"
|
||||
- "[thing] generator"
|
||||
- "free [tool type]"
|
||||
- "[industry] [tool type]"
|
||||
|
||||
**Supporting content:**
|
||||
- "How to [use case]"
|
||||
- "What is [concept tool helps with]"
|
||||
- Blog posts that link to tool
|
||||
|
||||
### Link Building
|
||||
|
||||
Free tools attract links because:
|
||||
- Genuinely useful (people reference them)
|
||||
- Unique (can't link to just any page)
|
||||
- Shareable (social amplification)
|
||||
|
||||
**Outreach opportunities:**
|
||||
- Roundup posts ("best free tools for X")
|
||||
- Resource pages
|
||||
- Industry publications
|
||||
- Blogs writing about the problem
|
||||
|
||||
### Technical SEO
|
||||
|
||||
- Fast load time critical
|
||||
- Mobile-friendly essential
|
||||
- Crawlable content (not just JS app)
|
||||
- Proper meta tags
|
||||
- Schema markup if applicable
|
||||
|
||||
---
|
||||
|
||||
## Lead Capture Strategy
|
||||
|
||||
### When to Gate
|
||||
|
||||
**Fully gated (email required to use):**
|
||||
- High-value, unique tools
|
||||
- Personalized reports
|
||||
- Risk: Lower usage
|
||||
|
||||
**Partially gated (email for full results):**
|
||||
- Show preview, gate details
|
||||
- Better balance
|
||||
- Most common pattern
|
||||
|
||||
**Ungated with optional capture:**
|
||||
- Tool is free to use
|
||||
- Email to save/share results
|
||||
- Highest usage, lower capture
|
||||
|
||||
**Ungated entirely:**
|
||||
- Pure SEO/brand play
|
||||
- No direct leads
|
||||
- Maximum reach
|
||||
|
||||
### Lead Capture Best Practices
|
||||
|
||||
- Value exchange clear: "Get your full report"
|
||||
- Minimal friction: Email only
|
||||
- Show preview of what they'll get
|
||||
- Optional: Segment by asking one qualifying question
|
||||
|
||||
### Post-Capture
|
||||
|
||||
- Immediate email with results/link
|
||||
- Nurture sequence relevant to tool topic
|
||||
- Clear path to main product
|
||||
- Don't spam—provide value
|
||||
|
||||
---
|
||||
|
||||
## Build vs. Buy vs. Embed
|
||||
|
||||
### Build Custom
|
||||
|
||||
**When:**
|
||||
- Unique concept, nothing exists
|
||||
- Core to brand/product
|
||||
- High strategic value
|
||||
- Have development capacity
|
||||
|
||||
**Consider:**
|
||||
- Development time
|
||||
- Ongoing maintenance
|
||||
- Hosting costs
|
||||
- Bug fixes
|
||||
|
||||
### Use No-Code Tools
|
||||
|
||||
**Options:**
|
||||
- Outgrow, Involve.me (calculators/quizzes)
|
||||
- Typeform, Tally (forms/quizzes)
|
||||
- Notion, Coda (databases)
|
||||
- Bubble, Webflow (apps)
|
||||
|
||||
**When:**
|
||||
- Speed to market
|
||||
- Limited dev resources
|
||||
- Testing concept viability
|
||||
|
||||
### Embed Existing
|
||||
|
||||
**When:**
|
||||
- Something good already exists
|
||||
- White-label options available
|
||||
- Not core differentiator
|
||||
|
||||
**Consider:**
|
||||
- Branding limitations
|
||||
- Dependency on third party
|
||||
- Cost vs. build
|
||||
|
||||
---
|
||||
|
||||
## MVP Scope
|
||||
|
||||
### Minimum Viable Tool
|
||||
|
||||
1. **Core functionality only**
|
||||
- Does the one thing
|
||||
- No bells and whistles
|
||||
- Works reliably
|
||||
|
||||
2. **Essential UX**
|
||||
- Clear input
|
||||
- Obvious output
|
||||
- Mobile works
|
||||
|
||||
3. **Basic lead capture**
|
||||
- Email collection works
|
||||
- Leads go somewhere useful
|
||||
- Follow-up exists
|
||||
|
||||
### What to Skip Initially
|
||||
|
||||
- Account creation
|
||||
- Saving results
|
||||
- Advanced features
|
||||
- Perfect design
|
||||
- Every edge case
|
||||
|
||||
### Iterate Based on Use
|
||||
|
||||
- Track where users drop off
|
||||
- See what questions they have
|
||||
- Add features that get requested
|
||||
- Improve based on data
|
||||
|
||||
---
|
||||
|
||||
## Promotion Strategy
|
||||
|
||||
### Launch
|
||||
|
||||
**Owned channels:**
|
||||
- Email list announcement
|
||||
- Blog post / landing page
|
||||
- Social media
|
||||
- Product hunt (if applicable)
|
||||
|
||||
**Outreach:**
|
||||
- Relevant newsletters
|
||||
- Industry publications
|
||||
- Bloggers in space
|
||||
- Social influencers
|
||||
|
||||
### Ongoing
|
||||
|
||||
**SEO:**
|
||||
- Target tool-related keywords
|
||||
- Supporting content
|
||||
- Link building
|
||||
|
||||
**Social:**
|
||||
- Share interesting results (anonymized)
|
||||
- Use case examples
|
||||
- Tips for using the tool
|
||||
|
||||
**Product integration:**
|
||||
- Mention in sales process
|
||||
- Link from related product features
|
||||
- Include in email sequences
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
### Metrics to Track
|
||||
|
||||
**Acquisition:**
|
||||
- Traffic to tool
|
||||
- Traffic sources
|
||||
- Keyword rankings
|
||||
- Backlinks acquired
|
||||
|
||||
**Engagement:**
|
||||
- Tool usage/completions
|
||||
- Time spent
|
||||
- Return visitors
|
||||
- Shares
|
||||
|
||||
**Conversion:**
|
||||
- Email captures
|
||||
- Lead quality score
|
||||
- MQLs generated
|
||||
- Pipeline influenced
|
||||
- Customers attributed
|
||||
|
||||
### Attribution
|
||||
|
||||
- UTM parameters for paid promotion
|
||||
- Separate landing page for organic
|
||||
- Track lead source through funnel
|
||||
- Survey new customers
|
||||
|
||||
---
|
||||
|
||||
## Evaluation Framework
|
||||
|
||||
### Tool Idea Scorecard
|
||||
|
||||
Rate each factor 1-5:
|
||||
|
||||
| Factor | Score |
|
||||
|--------|-------|
|
||||
| Search demand exists | ___ |
|
||||
| Audience match to buyers | ___ |
|
||||
| Uniqueness vs. existing tools | ___ |
|
||||
| Natural path to product | ___ |
|
||||
| Build feasibility | ___ |
|
||||
| Maintenance burden (inverse) | ___ |
|
||||
| Link-building potential | ___ |
|
||||
| Share-worthiness | ___ |
|
||||
|
||||
**25+**: Strong candidate
|
||||
**15-24**: Promising, needs refinement
|
||||
**<15**: Reconsider or scope differently
|
||||
|
||||
### ROI Projection
|
||||
|
||||
```
|
||||
Estimated monthly leads: [X]
|
||||
Lead-to-customer rate: [Y%]
|
||||
Average customer value: [$Z]
|
||||
|
||||
Monthly value: X × Y% × $Z = $___
|
||||
|
||||
Build cost: $___
|
||||
Monthly maintenance: $___
|
||||
|
||||
Payback period: Build cost / (Monthly value - Monthly maintenance)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Tool Strategy Document
|
||||
|
||||
```
|
||||
# Free Tool Strategy: [Tool Name]
|
||||
|
||||
## Concept
|
||||
[What it does in one paragraph]
|
||||
|
||||
## Target Audience
|
||||
[Who uses it, what problem it solves]
|
||||
|
||||
## Lead Generation Fit
|
||||
[How this connects to your product/sales]
|
||||
|
||||
## SEO Opportunity
|
||||
- Target keywords: [list]
|
||||
- Search volume: [estimate]
|
||||
- Competition: [assessment]
|
||||
|
||||
## Build Approach
|
||||
- Custom / No-code / Embed
|
||||
- MVP scope: [core features]
|
||||
- Estimated effort: [time/cost]
|
||||
|
||||
## Lead Capture Strategy
|
||||
- Gating approach: [Full/Partial/Ungated]
|
||||
- Capture mechanism: [description]
|
||||
- Follow-up sequence: [outline]
|
||||
|
||||
## Success Metrics
|
||||
- [Metric 1]: [Target]
|
||||
- [Metric 2]: [Target]
|
||||
|
||||
## Promotion Plan
|
||||
- Launch: [channels]
|
||||
- Ongoing: [strategy]
|
||||
|
||||
## Timeline
|
||||
- Phase 1: [scope] - [timeframe]
|
||||
- Phase 2: [scope] - [timeframe]
|
||||
```
|
||||
|
||||
### Implementation Spec
|
||||
If moving forward with build
|
||||
|
||||
### Promotion Plan
|
||||
Detailed launch and ongoing strategy
|
||||
|
||||
---
|
||||
|
||||
## Example Tool Concepts by Business Type
|
||||
|
||||
### SaaS Product
|
||||
- Product ROI calculator
|
||||
- Competitor comparison tool
|
||||
- Readiness assessment quiz
|
||||
- Template library for use case
|
||||
|
||||
### Agency/Services
|
||||
- Industry benchmark tool
|
||||
- Project scoping calculator
|
||||
- Portfolio review tool
|
||||
- Cost estimator
|
||||
|
||||
### E-commerce
|
||||
- Product finder quiz
|
||||
- Comparison tool
|
||||
- Size/fit calculator
|
||||
- Savings calculator
|
||||
|
||||
### Developer Tools
|
||||
- Code snippet library
|
||||
- Testing/preview tool
|
||||
- Documentation generator
|
||||
- Interactive tutorials
|
||||
|
||||
### Finance
|
||||
- Financial calculators
|
||||
- Investment comparison
|
||||
- Budget planner
|
||||
- Tax estimator
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's your core product/service?
|
||||
2. What problems does your audience commonly face?
|
||||
3. What existing tools do they use for workarounds?
|
||||
4. How do you currently generate leads?
|
||||
5. What technical resources are available?
|
||||
6. What's the timeline and budget?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: For optimizing the tool's landing page
|
||||
- **seo-audit**: For SEO-optimizing the tool
|
||||
- **analytics-tracking**: For measuring tool usage
|
||||
- **email-sequence**: For nurturing leads from the tool
|
||||
- **programmatic-seo**: For building tool-based pages at scale
|
||||
346
skills/onboarding-cro.md
Normal file
346
skills/onboarding-cro.md
Normal file
@@ -0,0 +1,346 @@
|
||||
---
|
||||
name: onboarding-cro
|
||||
description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
|
||||
---
|
||||
|
||||
# Onboarding CRO
|
||||
|
||||
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, understand:
|
||||
|
||||
1. **Product Context**
|
||||
- What type of product? (SaaS tool, marketplace, app, etc.)
|
||||
- B2B or B2C?
|
||||
- What's the core value proposition?
|
||||
|
||||
2. **Activation Definition**
|
||||
- What's the "aha moment" for your product?
|
||||
- What action indicates a user "gets it"?
|
||||
- What's your current activation rate?
|
||||
|
||||
3. **Current State**
|
||||
- What happens immediately after signup?
|
||||
- Is there an existing onboarding flow?
|
||||
- Where do users currently drop off?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Time-to-Value Is Everything
|
||||
- How quickly can someone experience the core value?
|
||||
- Remove every step between signup and that moment
|
||||
- Consider: Can they experience value BEFORE signup?
|
||||
|
||||
### 2. One Goal Per Session
|
||||
- Don't try to teach everything at once
|
||||
- Focus first session on one successful outcome
|
||||
- Save advanced features for later
|
||||
|
||||
### 3. Do, Don't Show
|
||||
- Interactive > Tutorial
|
||||
- Doing the thing > Learning about the thing
|
||||
- Show UI in context of real tasks
|
||||
|
||||
### 4. Progress Creates Motivation
|
||||
- Show advancement
|
||||
- Celebrate completions
|
||||
- Make the path visible
|
||||
|
||||
---
|
||||
|
||||
## Defining Activation
|
||||
|
||||
### Find Your Aha Moment
|
||||
The action that correlates most strongly with retention:
|
||||
- What do retained users do that churned users don't?
|
||||
- What's the earliest indicator of future engagement?
|
||||
- What action demonstrates they "got it"?
|
||||
|
||||
**Examples by product type:**
|
||||
- Project management: Create first project + add team member
|
||||
- Analytics: Install tracking + see first report
|
||||
- Design tool: Create first design + export/share
|
||||
- Collaboration: Invite first teammate
|
||||
- Marketplace: Complete first transaction
|
||||
|
||||
### Activation Metrics
|
||||
- % of signups who reach activation
|
||||
- Time to activation
|
||||
- Steps to activation
|
||||
- Activation by cohort/source
|
||||
|
||||
---
|
||||
|
||||
## Onboarding Flow Design
|
||||
|
||||
### Immediate Post-Signup (First 30 Seconds)
|
||||
|
||||
**Options:**
|
||||
1. **Product-first**: Drop directly into product
|
||||
- Best for: Simple products, B2C, mobile apps
|
||||
- Risk: Blank slate overwhelm
|
||||
|
||||
2. **Guided setup**: Short wizard to configure
|
||||
- Best for: Products needing personalization
|
||||
- Risk: Adds friction before value
|
||||
|
||||
3. **Value-first**: Show outcome immediately
|
||||
- Best for: Products with demo data or samples
|
||||
- Risk: May not feel "real"
|
||||
|
||||
**Whatever you choose:**
|
||||
- Clear single next action
|
||||
- No dead ends
|
||||
- Progress indication if multi-step
|
||||
|
||||
### Onboarding Checklist Pattern
|
||||
|
||||
**When to use:**
|
||||
- Multiple setup steps required
|
||||
- Product has several features to discover
|
||||
- Self-serve B2B products
|
||||
|
||||
**Best practices:**
|
||||
- 3-7 items (not overwhelming)
|
||||
- Order by value (most impactful first)
|
||||
- Start with quick wins
|
||||
- Progress bar/completion %
|
||||
- Celebration on completion
|
||||
- Dismiss option (don't trap users)
|
||||
|
||||
**Checklist item structure:**
|
||||
- Clear action verb
|
||||
- Benefit hint
|
||||
- Estimated time
|
||||
- Quick-start capability
|
||||
|
||||
Example:
|
||||
```
|
||||
☐ Connect your first data source (2 min)
|
||||
Get real-time insights from your existing tools
|
||||
[Connect Now]
|
||||
```
|
||||
|
||||
### Empty States
|
||||
|
||||
Empty states are onboarding opportunities, not dead ends.
|
||||
|
||||
**Good empty state:**
|
||||
- Explains what this area is for
|
||||
- Shows what it looks like with data
|
||||
- Clear primary action to add first item
|
||||
- Optional: Pre-populate with example data
|
||||
|
||||
**Structure:**
|
||||
1. Illustration or preview
|
||||
2. Brief explanation of value
|
||||
3. Primary CTA to add first item
|
||||
4. Optional: Secondary action (import, template)
|
||||
|
||||
### Tooltips and Guided Tours
|
||||
|
||||
**When to use:**
|
||||
- Complex UI that benefits from orientation
|
||||
- Features that aren't self-evident
|
||||
- Power features users might miss
|
||||
|
||||
**When to avoid:**
|
||||
- Simple, intuitive interfaces
|
||||
- Mobile apps (limited screen space)
|
||||
- When they interrupt important flows
|
||||
|
||||
**Best practices:**
|
||||
- Max 3-5 steps per tour
|
||||
- Point to actual UI elements
|
||||
- Dismissable at any time
|
||||
- Don't repeat for returning users
|
||||
- Consider user-initiated tours
|
||||
|
||||
### Progress Indicators
|
||||
|
||||
**Types:**
|
||||
- Checklist (discrete tasks)
|
||||
- Progress bar (% complete)
|
||||
- Level/stage indicator
|
||||
- Profile completeness
|
||||
|
||||
**Best practices:**
|
||||
- Show early progress (start at 20%, not 0%)
|
||||
- Quick early wins (first items easy to complete)
|
||||
- Clear benefit of completing
|
||||
- Don't block features behind completion
|
||||
|
||||
---
|
||||
|
||||
## Multi-Channel Onboarding
|
||||
|
||||
### Email + In-App Coordination
|
||||
|
||||
**Trigger-based emails:**
|
||||
- Welcome email (immediate)
|
||||
- Incomplete onboarding (24h, 72h)
|
||||
- Activation achieved (celebration + next step)
|
||||
- Feature discovery (days 3, 7, 14)
|
||||
- Stalled user re-engagement
|
||||
|
||||
**Email should:**
|
||||
- Reinforce in-app actions
|
||||
- Not duplicate in-app messaging
|
||||
- Drive back to product with specific CTA
|
||||
- Be personalized based on actions taken
|
||||
|
||||
### Push Notifications (Mobile)
|
||||
|
||||
- Permission timing is critical (not immediately)
|
||||
- Clear value proposition for enabling
|
||||
- Reserve for genuine value moments
|
||||
- Re-engagement for stalled users
|
||||
|
||||
---
|
||||
|
||||
## Engagement Loops
|
||||
|
||||
### Building Habits
|
||||
- What regular action should users take?
|
||||
- What trigger can prompt return?
|
||||
- What reward reinforces the behavior?
|
||||
|
||||
**Loop structure:**
|
||||
Trigger → Action → Variable Reward → Investment
|
||||
|
||||
**Examples:**
|
||||
- Trigger: Email digest of activity
|
||||
- Action: Log in to respond
|
||||
- Reward: Social engagement, progress, achievement
|
||||
- Investment: Add more data, connections, content
|
||||
|
||||
### Milestone Celebrations
|
||||
- Acknowledge meaningful achievements
|
||||
- Show progress relative to journey
|
||||
- Suggest next milestone
|
||||
- Shareable moments (social proof generation)
|
||||
|
||||
---
|
||||
|
||||
## Handling Stalled Users
|
||||
|
||||
### Detection
|
||||
- Define "stalled" criteria (X days inactive, incomplete setup)
|
||||
- Monitor at cohort level
|
||||
- Track recovery rate
|
||||
|
||||
### Re-engagement Tactics
|
||||
1. **Email sequence for incomplete onboarding**
|
||||
- Reminder of value proposition
|
||||
- Address common blockers
|
||||
- Offer help/demo/call
|
||||
- Deadline/urgency if appropriate
|
||||
|
||||
2. **In-app recovery**
|
||||
- Welcome back message
|
||||
- Pick up where they left off
|
||||
- Simplified path to activation
|
||||
|
||||
3. **Human touch**
|
||||
- For high-value accounts: personal outreach
|
||||
- Offer live walkthrough
|
||||
- Ask what's blocking them
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
### Key Metrics
|
||||
- **Activation rate**: % reaching activation event
|
||||
- **Time to activation**: How long to first value
|
||||
- **Onboarding completion**: % completing setup
|
||||
- **Day 1/7/30 retention**: Return rate by timeframe
|
||||
- **Feature adoption**: Which features get used
|
||||
|
||||
### Funnel Analysis
|
||||
Track drop-off at each step:
|
||||
```
|
||||
Signup → Step 1 → Step 2 → Activation → Retention
|
||||
100% 80% 60% 40% 25%
|
||||
```
|
||||
|
||||
Identify biggest drops and focus there.
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Onboarding Audit
|
||||
For each issue:
|
||||
- **Finding**: What's happening
|
||||
- **Impact**: Why it matters
|
||||
- **Recommendation**: Specific fix
|
||||
- **Priority**: High/Medium/Low
|
||||
|
||||
### Onboarding Flow Design
|
||||
- **Activation goal**: What they should achieve
|
||||
- **Step-by-step flow**: Each screen/state
|
||||
- **Checklist items**: If applicable
|
||||
- **Empty states**: Copy and CTA
|
||||
- **Email sequence**: Triggers and content
|
||||
- **Metrics plan**: What to measure
|
||||
|
||||
### Copy Deliverables
|
||||
- Welcome screen copy
|
||||
- Checklist items with microcopy
|
||||
- Empty state copy
|
||||
- Tooltip content
|
||||
- Email sequence copy
|
||||
- Milestone celebration copy
|
||||
|
||||
---
|
||||
|
||||
## Common Patterns by Product Type
|
||||
|
||||
### B2B SaaS Tool
|
||||
1. Short setup wizard (use case selection)
|
||||
2. First value-generating action
|
||||
3. Team invitation prompt
|
||||
4. Checklist for deeper setup
|
||||
|
||||
### Marketplace/Platform
|
||||
1. Complete profile
|
||||
2. First search/browse
|
||||
3. First transaction
|
||||
4. Repeat engagement loop
|
||||
|
||||
### Mobile App
|
||||
1. Permission requests (strategic timing)
|
||||
2. Quick win in first session
|
||||
3. Push notification setup
|
||||
4. Habit loop establishment
|
||||
|
||||
### Content/Social Platform
|
||||
1. Follow/customize feed
|
||||
2. First content consumption
|
||||
3. First content creation
|
||||
4. Social connection/engagement
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What action most correlates with retention?
|
||||
2. What happens immediately after signup?
|
||||
3. Where do users currently drop off?
|
||||
4. What's your activation rate target?
|
||||
5. Do you have cohort analysis on successful vs. churned users?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **signup-flow-cro**: For optimizing the signup before onboarding
|
||||
- **email-sequence**: For onboarding email series
|
||||
- **paywall-upgrade-cro**: For converting to paid during/after onboarding
|
||||
- **ab-test-setup**: For testing onboarding changes
|
||||
290
skills/page-copywriting.md
Normal file
290
skills/page-copywriting.md
Normal file
@@ -0,0 +1,290 @@
|
||||
---
|
||||
name: page-copywriting
|
||||
description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
|
||||
---
|
||||
|
||||
# Page Copywriting
|
||||
|
||||
You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
|
||||
|
||||
## Before Writing
|
||||
|
||||
Gather this context (ask if not provided):
|
||||
|
||||
### 1. Page Purpose
|
||||
- What type of page is this? (homepage, landing page, pricing, feature, about)
|
||||
- What is the ONE primary action you want visitors to take?
|
||||
- What's the secondary action (if any)?
|
||||
|
||||
### 2. Audience
|
||||
- Who is the ideal customer for this page?
|
||||
- What problem are they trying to solve?
|
||||
- What have they already tried?
|
||||
- What objections or hesitations do they have?
|
||||
- What language do they use to describe their problem?
|
||||
|
||||
### 3. Product/Offer
|
||||
- What are you selling or offering?
|
||||
- What makes it different from alternatives?
|
||||
- What's the key transformation or outcome?
|
||||
- Any proof points (numbers, testimonials, case studies)?
|
||||
|
||||
### 4. Context
|
||||
- Where is traffic coming from? (ads, organic, email)
|
||||
- What do visitors already know before arriving?
|
||||
- What messaging are they seeing before this page?
|
||||
|
||||
---
|
||||
|
||||
## Copywriting Principles
|
||||
|
||||
### Clarity Over Cleverness
|
||||
- If you have to choose between clear and creative, choose clear
|
||||
- Every sentence should have one job
|
||||
- Remove words that don't add meaning
|
||||
|
||||
### Benefits Over Features
|
||||
- Features: What it does
|
||||
- Benefits: What that means for the customer
|
||||
- Always connect features to outcomes
|
||||
|
||||
### Specificity Over Vagueness
|
||||
- Vague: "Save time on your workflow"
|
||||
- Specific: "Cut your weekly reporting from 4 hours to 15 minutes"
|
||||
|
||||
### Customer Language Over Company Language
|
||||
- Use words your customers use
|
||||
- Avoid jargon unless your audience uses it
|
||||
- Mirror voice-of-customer from reviews, interviews, support tickets
|
||||
|
||||
### One Idea Per Section
|
||||
- Don't try to say everything everywhere
|
||||
- Each section should advance one argument
|
||||
- Build a logical flow down the page
|
||||
|
||||
---
|
||||
|
||||
## Page Structure Framework
|
||||
|
||||
### Above the Fold (First Screen)
|
||||
|
||||
**Headline**
|
||||
- Your single most important message
|
||||
- Should communicate core value proposition
|
||||
- Specific > generic
|
||||
|
||||
Formulas that work:
|
||||
- "[Achieve outcome] without [pain point]"
|
||||
- "[Achieve outcome] in [timeframe]"
|
||||
- "The [category] that [key differentiator]"
|
||||
- "Stop [pain]. Start [pleasure]."
|
||||
- "[Number] [people] use [product] to [outcome]"
|
||||
|
||||
**Subheadline**
|
||||
- Expands on the headline
|
||||
- Adds specificity or addresses secondary concern
|
||||
- 1-2 sentences max
|
||||
|
||||
**Primary CTA**
|
||||
- Action-oriented button text
|
||||
- Communicate what they get, not what they do
|
||||
- "Start Free Trial" > "Sign Up"
|
||||
- "Get Your Report" > "Submit"
|
||||
|
||||
**Supporting Visual**
|
||||
- Product screenshot, demo, or hero image
|
||||
- Should reinforce the message, not distract
|
||||
|
||||
### Social Proof Section
|
||||
|
||||
Options (use 1-2):
|
||||
- Customer logos (recognizable > many)
|
||||
- Key metric ("10,000+ teams")
|
||||
- Short testimonial with attribution
|
||||
- Star rating with review count
|
||||
|
||||
### Problem/Pain Section
|
||||
|
||||
- Articulate the problem better than they can
|
||||
- Show you understand their situation
|
||||
- Create recognition ("that's exactly my problem")
|
||||
|
||||
Structure:
|
||||
- "You know the feeling..." or "If you're like most [role]..."
|
||||
- Describe the specific frustrations
|
||||
- Hint at the cost of not solving it
|
||||
|
||||
### Solution/Benefits Section
|
||||
|
||||
- Bridge from problem to your solution
|
||||
- Focus on 3-5 key benefits (not 10)
|
||||
- Each benefit: headline + short explanation + proof point if available
|
||||
|
||||
Format options:
|
||||
- Benefit blocks with icons
|
||||
- Before/after comparison
|
||||
- Feature → Benefit → Proof structure
|
||||
|
||||
### How It Works Section
|
||||
|
||||
- Reduce perceived complexity
|
||||
- 3-4 step process
|
||||
- Each step: simple action + outcome
|
||||
|
||||
Example:
|
||||
1. "Connect your tools (2 minutes)"
|
||||
2. "Set your preferences"
|
||||
3. "Get automated reports every Monday"
|
||||
|
||||
### Social Proof (Detailed)
|
||||
|
||||
- Full testimonials with:
|
||||
- Specific results
|
||||
- Customer name, role, company
|
||||
- Photo if possible
|
||||
- Case study snippets
|
||||
- Logos section (if not above)
|
||||
|
||||
### Objection Handling
|
||||
|
||||
Common objections to address:
|
||||
- "Is this right for my situation?"
|
||||
- "What if it doesn't work?"
|
||||
- "Is it hard to set up?"
|
||||
- "How is this different from X?"
|
||||
|
||||
Formats:
|
||||
- FAQ section
|
||||
- Comparison table
|
||||
- Guarantee/promise section
|
||||
- "Built for [specific audience]" section
|
||||
|
||||
### Final CTA Section
|
||||
|
||||
- Recap the value proposition
|
||||
- Repeat the primary CTA
|
||||
- Add urgency if genuine (deadline, limited availability)
|
||||
- Risk reversal (guarantee, free trial, no credit card)
|
||||
|
||||
---
|
||||
|
||||
## CTA Copy Guidelines
|
||||
|
||||
**Weak CTAs (avoid):**
|
||||
- Submit
|
||||
- Sign Up
|
||||
- Learn More
|
||||
- Click Here
|
||||
- Get Started
|
||||
|
||||
**Strong CTAs (use):**
|
||||
- Start Free Trial
|
||||
- Get [Specific Thing]
|
||||
- See [Product] in Action
|
||||
- Create Your First [Thing]
|
||||
- Book My Demo
|
||||
- Download the Guide
|
||||
- Try It Free
|
||||
|
||||
**CTA formula:**
|
||||
[Action Verb] + [What They Get] + [Qualifier if needed]
|
||||
|
||||
Examples:
|
||||
- "Start My Free Trial"
|
||||
- "Get the Complete Checklist"
|
||||
- "See Pricing for My Team"
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
When writing copy, provide:
|
||||
|
||||
### Page Copy
|
||||
Organized by section with clear labels:
|
||||
- Headline
|
||||
- Subheadline
|
||||
- CTA
|
||||
- Section headers
|
||||
- Body copy
|
||||
- Secondary CTAs
|
||||
|
||||
### Annotations
|
||||
For key elements, explain:
|
||||
- Why you made this choice
|
||||
- What principle it applies
|
||||
- Alternatives considered
|
||||
|
||||
### Alternatives
|
||||
For headlines and CTAs, provide 2-3 options:
|
||||
- Option A: [copy] — [rationale]
|
||||
- Option B: [copy] — [rationale]
|
||||
- Option C: [copy] — [rationale]
|
||||
|
||||
### Meta Content (if relevant)
|
||||
- Page title (for SEO)
|
||||
- Meta description
|
||||
|
||||
---
|
||||
|
||||
## Page-Specific Guidance
|
||||
|
||||
### Homepage Copy
|
||||
- Serve multiple audiences without being generic
|
||||
- Lead with broadest value proposition
|
||||
- Provide clear paths for different visitor intents
|
||||
- Balance "ready to buy" and "still researching"
|
||||
|
||||
### Landing Page Copy
|
||||
- Single message, single CTA
|
||||
- Match headline to ad/traffic source
|
||||
- Complete argument on one page
|
||||
- Remove distractions (often no nav)
|
||||
|
||||
### Pricing Page Copy
|
||||
- Help visitors choose the right plan
|
||||
- Clarify what's included at each level
|
||||
- Address "which is right for me?" anxiety
|
||||
- Make recommended plan obvious
|
||||
|
||||
### Feature Page Copy
|
||||
- Connect feature to benefit to outcome
|
||||
- Show use cases and examples
|
||||
- Differentiate from competitors' versions
|
||||
- Clear path to try or buy
|
||||
|
||||
### About Page Copy
|
||||
- Tell the story of why you exist
|
||||
- Connect company mission to customer benefit
|
||||
- Build trust through transparency
|
||||
- Still include a CTA (it's still a marketing page)
|
||||
|
||||
---
|
||||
|
||||
## Voice and Tone Considerations
|
||||
|
||||
Before writing, establish:
|
||||
|
||||
**Formality level:**
|
||||
- Casual/conversational
|
||||
- Professional but friendly
|
||||
- Formal/enterprise
|
||||
|
||||
**Brand personality:**
|
||||
- Playful or serious?
|
||||
- Bold or understated?
|
||||
- Technical or accessible?
|
||||
|
||||
Maintain consistency throughout, but adjust intensity:
|
||||
- Headlines can be bolder
|
||||
- Body copy should be clearer
|
||||
- CTAs should be action-oriented
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: If the page structure/strategy needs work, not just copy
|
||||
- **email-sequence**: For email copywriting
|
||||
- **popup-cro**: For popup and modal copy
|
||||
- **ab-test-setup**: To test copy variations properly
|
||||
228
skills/page-cro.md
Normal file
228
skills/page-cro.md
Normal file
@@ -0,0 +1,228 @@
|
||||
---
|
||||
name: page-cro
|
||||
description: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
|
||||
---
|
||||
|
||||
# Page Conversion Rate Optimization (CRO)
|
||||
|
||||
You are a conversion rate optimization expert. Your goal is to analyze marketing pages and provide actionable recommendations to improve conversion rates.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, identify:
|
||||
|
||||
1. **Page Type**: What kind of page is this?
|
||||
- Homepage
|
||||
- Landing page (paid traffic, specific campaign)
|
||||
- Pricing page
|
||||
- Feature/product page
|
||||
- Blog post with CTA
|
||||
- About page
|
||||
- Other
|
||||
|
||||
2. **Primary Conversion Goal**: What's the one thing this page should get visitors to do?
|
||||
- Sign up / Start trial
|
||||
- Request demo
|
||||
- Purchase
|
||||
- Subscribe to newsletter
|
||||
- Download resource
|
||||
- Contact sales
|
||||
- Other
|
||||
|
||||
3. **Traffic Context**: If known, where are visitors coming from?
|
||||
- Organic search (what intent?)
|
||||
- Paid ads (what messaging?)
|
||||
- Social media
|
||||
- Email
|
||||
- Referral
|
||||
- Direct
|
||||
|
||||
## CRO Analysis Framework
|
||||
|
||||
Analyze the page across these dimensions, in order of impact:
|
||||
|
||||
### 1. Value Proposition Clarity (Highest Impact)
|
||||
|
||||
**Check for:**
|
||||
- Can a visitor understand what this is and why they should care within 5 seconds?
|
||||
- Is the primary benefit clear, specific, and differentiated?
|
||||
- Does it address a real pain point or desire?
|
||||
- Is it written in the customer's language (not company jargon)?
|
||||
|
||||
**Common issues:**
|
||||
- Feature-focused instead of benefit-focused
|
||||
- Too vague ("The best solution for your needs")
|
||||
- Too clever (sacrificing clarity for creativity)
|
||||
- Trying to say everything instead of the one most important thing
|
||||
|
||||
### 2. Headline Effectiveness
|
||||
|
||||
**Evaluate:**
|
||||
- Does it communicate the core value proposition?
|
||||
- Is it specific enough to be meaningful?
|
||||
- Does it create curiosity or urgency without being clickbait?
|
||||
- Does it match the traffic source's messaging (ad → landing page consistency)?
|
||||
|
||||
**Strong headline patterns:**
|
||||
- Outcome-focused: "Get [desired outcome] without [pain point]"
|
||||
- Specificity: Include numbers, timeframes, or concrete details
|
||||
- Social proof baked in: "Join 10,000+ teams who..."
|
||||
- Direct address of pain: "Tired of [specific problem]?"
|
||||
|
||||
### 3. CTA Placement, Copy, and Hierarchy
|
||||
|
||||
**Primary CTA assessment:**
|
||||
- Is there one clear primary action?
|
||||
- Is it visible without scrolling (above the fold)?
|
||||
- Does the button copy communicate value, not just action?
|
||||
- Weak: "Submit," "Sign Up," "Learn More"
|
||||
- Strong: "Start Free Trial," "Get My Report," "See Pricing"
|
||||
- Is there sufficient contrast and visual weight?
|
||||
|
||||
**CTA hierarchy:**
|
||||
- Is there a logical primary vs. secondary CTA structure?
|
||||
- Are CTAs repeated at key decision points (after benefits, after social proof, etc.)?
|
||||
- Is the commitment level appropriate for the page stage?
|
||||
|
||||
### 4. Visual Hierarchy and Scannability
|
||||
|
||||
**Check:**
|
||||
- Can someone scanning get the main message?
|
||||
- Are the most important elements visually prominent?
|
||||
- Is there clear information hierarchy (H1 → H2 → body)?
|
||||
- Is there enough white space to let elements breathe?
|
||||
- Do images support or distract from the message?
|
||||
|
||||
**Common issues:**
|
||||
- Wall of text with no visual breaks
|
||||
- Competing elements fighting for attention
|
||||
- Important information buried below the fold
|
||||
- Stock photos that add nothing
|
||||
|
||||
### 5. Trust Signals and Social Proof
|
||||
|
||||
**Types to look for:**
|
||||
- Customer logos (especially recognizable ones)
|
||||
- Testimonials (specific, attributed, with photos)
|
||||
- Case study snippets with real numbers
|
||||
- Review scores and counts
|
||||
- Security badges (where relevant)
|
||||
- "As seen in" media mentions
|
||||
- Team/founder credibility
|
||||
|
||||
**Placement:**
|
||||
- Near CTAs (to reduce friction at decision point)
|
||||
- After benefit claims (to validate them)
|
||||
- Throughout the page at natural break points
|
||||
|
||||
### 6. Objection Handling
|
||||
|
||||
**Identify likely objections for this page type:**
|
||||
- Price/value concerns
|
||||
- "Will this work for my situation?"
|
||||
- Implementation difficulty
|
||||
- Time to value
|
||||
- Switching costs
|
||||
- Trust/legitimacy concerns
|
||||
- "What if it doesn't work?"
|
||||
|
||||
**Check if the page addresses these through:**
|
||||
- FAQ sections
|
||||
- Guarantee/refund policies
|
||||
- Comparison content
|
||||
- Feature explanations
|
||||
- Process transparency
|
||||
|
||||
### 7. Friction Points
|
||||
|
||||
**Look for unnecessary friction:**
|
||||
- Too many form fields
|
||||
- Unclear next steps
|
||||
- Confusing navigation
|
||||
- Required information that shouldn't be required
|
||||
- Broken or slow elements
|
||||
- Mobile experience issues
|
||||
- Long load times
|
||||
|
||||
## Output Format
|
||||
|
||||
Structure your recommendations as:
|
||||
|
||||
### Quick Wins (Implement Now)
|
||||
Changes that are easy to make and likely to have immediate impact.
|
||||
|
||||
### High-Impact Changes (Prioritize)
|
||||
Bigger changes that require more effort but will significantly improve conversions.
|
||||
|
||||
### Test Ideas
|
||||
Hypotheses worth A/B testing rather than assuming.
|
||||
|
||||
### Copy Alternatives
|
||||
For key elements (headlines, CTAs, value props), provide 2-3 alternative versions with rationale.
|
||||
|
||||
---
|
||||
|
||||
## Page-Specific Frameworks
|
||||
|
||||
### Homepage CRO
|
||||
|
||||
Homepages serve multiple audiences. Focus on:
|
||||
- Clear positioning statement that works for cold visitors
|
||||
- Quick path to most common conversion action
|
||||
- Navigation that helps visitors self-select
|
||||
- Handling both "ready to buy" and "still researching" visitors
|
||||
|
||||
### Landing Page CRO
|
||||
|
||||
Single-purpose pages. Focus on:
|
||||
- Message match with traffic source
|
||||
- Single CTA (remove navigation if possible)
|
||||
- Complete argument on one page (minimize clicks to convert)
|
||||
- Urgency/scarcity if genuine
|
||||
|
||||
### Pricing Page CRO
|
||||
|
||||
High-intent visitors. Focus on:
|
||||
- Clear plan comparison
|
||||
- Recommended plan indication
|
||||
- Feature clarity (what's included/excluded)
|
||||
- Addressing "which plan is right for me?" anxiety
|
||||
- Easy path from pricing to checkout
|
||||
|
||||
### Feature Page CRO
|
||||
|
||||
Visitors researching specifics. Focus on:
|
||||
- Connecting feature to benefit
|
||||
- Use cases and examples
|
||||
- Comparison to alternatives
|
||||
- Clear CTA to try/buy
|
||||
|
||||
### Blog Post CRO
|
||||
|
||||
Content-to-conversion. Focus on:
|
||||
- Contextual CTAs that match content topic
|
||||
- Lead magnets related to article subject
|
||||
- Inline CTAs at natural stopping points
|
||||
- Exit-intent as backup
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask the User
|
||||
|
||||
If you need more context, ask:
|
||||
|
||||
1. What's your current conversion rate and goal?
|
||||
2. Where is traffic coming from?
|
||||
3. What does your signup/purchase flow look like after this page?
|
||||
4. Do you have any user research, heatmaps, or session recordings?
|
||||
5. What have you already tried?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **signup-flow-cro**: If the issue is in the signup process itself, not the page leading to it
|
||||
- **form-cro**: If forms on the page need optimization
|
||||
- **popup-cro**: If considering popups as part of the conversion strategy
|
||||
- **page-copywriting**: If the page needs a complete copy rewrite rather than CRO tweaks
|
||||
- **ab-test-setup**: To properly test recommended changes
|
||||
414
skills/paywall-upgrade-cro.md
Normal file
414
skills/paywall-upgrade-cro.md
Normal file
@@ -0,0 +1,414 @@
|
||||
---
|
||||
name: paywall-upgrade-cro
|
||||
description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
|
||||
---
|
||||
|
||||
# Paywall and Upgrade Screen CRO
|
||||
|
||||
You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, understand:
|
||||
|
||||
1. **Upgrade Context**
|
||||
- Freemium → Paid conversion
|
||||
- Trial → Paid conversion
|
||||
- Tier upgrade (Basic → Pro)
|
||||
- Feature-specific upsell
|
||||
- Usage limit upsell
|
||||
|
||||
2. **Product Model**
|
||||
- What's free forever?
|
||||
- What's behind the paywall?
|
||||
- What triggers upgrade prompts?
|
||||
- What's the current conversion rate?
|
||||
|
||||
3. **User Journey**
|
||||
- At what point does this appear?
|
||||
- What have they experienced already?
|
||||
- What are they trying to do when blocked?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Value Before Ask
|
||||
- User should have experienced real value first
|
||||
- The upgrade should feel like a natural next step
|
||||
- Timing: After "aha moment," not before
|
||||
|
||||
### 2. Show, Don't Just Tell
|
||||
- Demonstrate the value of paid features
|
||||
- Preview what they're missing
|
||||
- Make the upgrade feel tangible
|
||||
|
||||
### 3. Friction-Free Path
|
||||
- Easy to upgrade when ready
|
||||
- Don't make them hunt for pricing
|
||||
- Remove barriers to conversion
|
||||
|
||||
### 4. Respect the No
|
||||
- Don't trap or pressure
|
||||
- Make it easy to continue free
|
||||
- Maintain trust for future conversion
|
||||
|
||||
---
|
||||
|
||||
## Paywall Trigger Points
|
||||
|
||||
### Feature Gates
|
||||
When user clicks a paid-only feature:
|
||||
- Clear explanation of why it's paid
|
||||
- Show what the feature does
|
||||
- Quick path to unlock
|
||||
- Option to continue without
|
||||
|
||||
### Usage Limits
|
||||
When user hits a limit:
|
||||
- Clear indication of what limit was reached
|
||||
- Show what upgrading provides
|
||||
- Option to buy more without full upgrade
|
||||
- Don't block abruptly
|
||||
|
||||
### Trial Expiration
|
||||
When trial is ending:
|
||||
- Early warnings (7 days, 3 days, 1 day)
|
||||
- Clear "what happens" on expiration
|
||||
- Easy re-activation if expired
|
||||
- Summarize value received
|
||||
|
||||
### Time-Based Prompts
|
||||
After X days/sessions of free use:
|
||||
- Gentle upgrade reminder
|
||||
- Highlight unused paid features
|
||||
- Not intrusive—banner or subtle modal
|
||||
- Easy to dismiss
|
||||
|
||||
### Context-Triggered
|
||||
When behavior indicates upgrade fit:
|
||||
- Power users who'd benefit
|
||||
- Teams using solo features
|
||||
- Heavy usage approaching limits
|
||||
- Inviting teammates
|
||||
|
||||
---
|
||||
|
||||
## Paywall Screen Components
|
||||
|
||||
### 1. Headline
|
||||
Focus on what they get, not what they pay:
|
||||
- "Unlock [Feature] to [Benefit]"
|
||||
- "Get more [value] with [Plan]"
|
||||
- Not: "Upgrade to Pro for $X/month"
|
||||
|
||||
### 2. Value Demonstration
|
||||
Show what they're missing:
|
||||
- Preview of the feature in action
|
||||
- Before/after comparison
|
||||
- "With Pro, you could..." examples
|
||||
- Specific to their use case if possible
|
||||
|
||||
### 3. Feature Comparison
|
||||
If showing tiers:
|
||||
- Highlight key differences
|
||||
- Current plan clearly marked
|
||||
- Recommended plan emphasized
|
||||
- Focus on outcomes, not feature lists
|
||||
|
||||
### 4. Pricing
|
||||
- Clear, simple pricing
|
||||
- Annual vs. monthly options
|
||||
- Per-seat clarity if applicable
|
||||
- Any trials or guarantees
|
||||
|
||||
### 5. Social Proof (Optional)
|
||||
- Customer quotes about the upgrade
|
||||
- "X teams use this feature"
|
||||
- Success metrics from upgraded users
|
||||
|
||||
### 6. CTA
|
||||
- Specific: "Upgrade to Pro" not "Upgrade"
|
||||
- Value-oriented: "Start Getting [Benefit]"
|
||||
- If trial: "Start Free Trial"
|
||||
|
||||
### 7. Escape Hatch
|
||||
- Clear "Not now" or "Continue with Free"
|
||||
- Don't make them feel bad
|
||||
- "Maybe later" vs. "No, I'll stay limited"
|
||||
|
||||
---
|
||||
|
||||
## Specific Paywall Types
|
||||
|
||||
### Feature Lock Paywall
|
||||
When clicking a paid feature:
|
||||
|
||||
```
|
||||
[Lock Icon]
|
||||
This feature is available on Pro
|
||||
|
||||
[Feature preview/screenshot]
|
||||
|
||||
[Feature name] helps you [benefit]:
|
||||
• [Specific capability]
|
||||
• [Specific capability]
|
||||
• [Specific capability]
|
||||
|
||||
[Upgrade to Pro - $X/mo]
|
||||
[Maybe Later]
|
||||
```
|
||||
|
||||
### Usage Limit Paywall
|
||||
When hitting a limit:
|
||||
|
||||
```
|
||||
You've reached your free limit
|
||||
|
||||
[Visual: Progress bar at 100%]
|
||||
|
||||
Free plan: 3 projects
|
||||
Pro plan: Unlimited projects
|
||||
|
||||
You're active! Upgrade to keep building.
|
||||
|
||||
[Upgrade to Pro] [Delete a project]
|
||||
```
|
||||
|
||||
### Trial Expiration Paywall
|
||||
When trial is ending:
|
||||
|
||||
```
|
||||
Your trial ends in 3 days
|
||||
|
||||
What you'll lose:
|
||||
• [Feature they've used]
|
||||
• [Feature they've used]
|
||||
• [Data/work they've created]
|
||||
|
||||
What you've accomplished:
|
||||
• Created X projects
|
||||
• [Specific value metric]
|
||||
|
||||
[Continue with Pro - $X/mo]
|
||||
[Remind me later] [Downgrade to Free]
|
||||
```
|
||||
|
||||
### Soft Upgrade Prompt
|
||||
Non-blocking suggestion:
|
||||
|
||||
```
|
||||
[Banner or subtle modal]
|
||||
|
||||
You've been using [Product] for 2 weeks!
|
||||
Teams like yours get X% more [value] with Pro.
|
||||
|
||||
[See Pro Features] [Dismiss]
|
||||
```
|
||||
|
||||
### Team/Seat Upgrade
|
||||
When adding users:
|
||||
|
||||
```
|
||||
Invite your team
|
||||
|
||||
Your plan: Solo (1 user)
|
||||
Team plans start at $X/user
|
||||
|
||||
• Shared projects
|
||||
• Collaboration features
|
||||
• Admin controls
|
||||
|
||||
[Upgrade to Team] [Continue Solo]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mobile Paywall Patterns
|
||||
|
||||
### iOS/Android Conventions
|
||||
- System-like styling builds trust
|
||||
- Standard paywall patterns users recognize
|
||||
- Free trial emphasis common
|
||||
- Subscription terminology they expect
|
||||
|
||||
### Mobile-Specific UX
|
||||
- Full-screen often acceptable
|
||||
- Swipe to dismiss
|
||||
- Large tap targets
|
||||
- Plan selection with clear visual state
|
||||
|
||||
### App Store Considerations
|
||||
- Clear pricing display
|
||||
- Subscription terms visible
|
||||
- Restore purchases option
|
||||
- Meet review guidelines
|
||||
|
||||
---
|
||||
|
||||
## Timing and Frequency
|
||||
|
||||
### When to Show
|
||||
- **Best**: After value moment, before frustration
|
||||
- After activation/aha moment
|
||||
- When hitting genuine limits
|
||||
- When using adjacent-to-paid features
|
||||
|
||||
### When NOT to Show
|
||||
- During onboarding (too early)
|
||||
- When they're in a flow
|
||||
- Repeatedly after dismissal
|
||||
- Before they understand the product
|
||||
|
||||
### Frequency Rules
|
||||
- Limit to X per session
|
||||
- Cool-down after dismiss (days, not hours)
|
||||
- Escalate urgency appropriately (trial end)
|
||||
- Track annoyance signals (rage clicks, churn)
|
||||
|
||||
---
|
||||
|
||||
## Upgrade Flow Optimization
|
||||
|
||||
### From Paywall to Payment
|
||||
- Minimize steps
|
||||
- Keep them in-context if possible
|
||||
- Pre-fill known information
|
||||
- Show security signals
|
||||
|
||||
### Plan Selection
|
||||
- Default to recommended plan
|
||||
- Annual vs. monthly clear trade-off
|
||||
- Feature comparison if helpful
|
||||
- FAQ or objection handling nearby
|
||||
|
||||
### Checkout
|
||||
- Minimal fields
|
||||
- Multiple payment methods
|
||||
- Trial terms clear
|
||||
- Easy cancellation visible (builds trust)
|
||||
|
||||
### Post-Upgrade
|
||||
- Immediate access to features
|
||||
- Confirmation and receipt
|
||||
- Guide to new features
|
||||
- Celebrate the upgrade
|
||||
|
||||
---
|
||||
|
||||
## A/B Testing Paywalls
|
||||
|
||||
### What to Test
|
||||
- Trigger timing (earlier vs. later)
|
||||
- Trigger type (feature gate vs. soft prompt)
|
||||
- Headline/copy variations
|
||||
- Price presentation
|
||||
- Trial length
|
||||
- Feature emphasis
|
||||
- Social proof presence
|
||||
- Design/layout
|
||||
|
||||
### Metrics to Track
|
||||
- Paywall impression rate
|
||||
- Click-through to upgrade
|
||||
- Upgrade completion rate
|
||||
- Revenue per user
|
||||
- Churn rate post-upgrade
|
||||
- Time to upgrade
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Paywall Design
|
||||
For each paywall:
|
||||
- **Trigger**: When it appears
|
||||
- **Context**: What user was doing
|
||||
- **Type**: Feature gate, limit, trial, etc.
|
||||
- **Copy**: Full copy with headline, body, CTA
|
||||
- **Design notes**: Layout, visual elements
|
||||
- **Mobile**: Mobile-specific considerations
|
||||
- **Frequency**: How often shown
|
||||
- **Exit path**: How to dismiss
|
||||
|
||||
### Upgrade Flow
|
||||
- Step-by-step screens
|
||||
- Copy for each step
|
||||
- Decision points
|
||||
- Success state
|
||||
|
||||
### Metrics Plan
|
||||
What to measure and expected benchmarks
|
||||
|
||||
---
|
||||
|
||||
## Common Patterns by Business Model
|
||||
|
||||
### Freemium SaaS
|
||||
- Generous free tier to build habit
|
||||
- Feature gates for power features
|
||||
- Usage limits for volume
|
||||
- Soft prompts for heavy free users
|
||||
|
||||
### Free Trial
|
||||
- Trial countdown prominent
|
||||
- Value summary at expiration
|
||||
- Grace period or easy restart
|
||||
- Win-back for expired trials
|
||||
|
||||
### Usage-Based
|
||||
- Clear usage tracking
|
||||
- Alerts at thresholds (75%, 100%)
|
||||
- Easy to add more without plan change
|
||||
- Volume discounts visible
|
||||
|
||||
### Per-Seat
|
||||
- Friction at invitation
|
||||
- Team feature highlights
|
||||
- Volume pricing clear
|
||||
- Admin value proposition
|
||||
|
||||
---
|
||||
|
||||
## Anti-Patterns to Avoid
|
||||
|
||||
### Dark Patterns
|
||||
- Hiding the close button
|
||||
- Confusing plan selection
|
||||
- Buried downgrade option
|
||||
- Misleading urgency
|
||||
- Guilt-trip copy
|
||||
|
||||
### Conversion Killers
|
||||
- Asking before value delivered
|
||||
- Too frequent prompts
|
||||
- Blocking critical flows
|
||||
- Unclear pricing
|
||||
- Complicated upgrade process
|
||||
|
||||
### Trust Destroyers
|
||||
- Surprise charges
|
||||
- Hard-to-cancel subscriptions
|
||||
- Bait and switch
|
||||
- Data hostage tactics
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's your current free → paid conversion rate?
|
||||
2. What triggers upgrade prompts today?
|
||||
3. What features are behind the paywall?
|
||||
4. What's your "aha moment" for users?
|
||||
5. What pricing model? (per seat, usage, flat)
|
||||
6. Mobile app, web app, or both?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **page-cro**: For public pricing page optimization
|
||||
- **onboarding-cro**: For driving to aha moment before upgrade
|
||||
- **ab-test-setup**: For testing paywall variations
|
||||
- **analytics-tracking**: For measuring upgrade funnel
|
||||
358
skills/popup-cro.md
Normal file
358
skills/popup-cro.md
Normal file
@@ -0,0 +1,358 @@
|
||||
---
|
||||
name: popup-cro
|
||||
description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
|
||||
---
|
||||
|
||||
# Popup CRO
|
||||
|
||||
You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, understand:
|
||||
|
||||
1. **Popup Purpose**
|
||||
- Email/newsletter capture
|
||||
- Lead magnet delivery
|
||||
- Discount/promotion
|
||||
- Announcement
|
||||
- Exit intent save
|
||||
- Feature promotion
|
||||
- Feedback/survey
|
||||
|
||||
2. **Current State**
|
||||
- Existing popup performance?
|
||||
- What triggers are used?
|
||||
- User complaints or feedback?
|
||||
- Mobile experience?
|
||||
|
||||
3. **Traffic Context**
|
||||
- Traffic sources (paid, organic, direct)
|
||||
- New vs. returning visitors
|
||||
- Page types where shown
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Timing Is Everything
|
||||
- Too early = annoying interruption
|
||||
- Too late = missed opportunity
|
||||
- Right time = helpful offer at moment of need
|
||||
|
||||
### 2. Value Must Be Obvious
|
||||
- Clear, immediate benefit
|
||||
- Relevant to page context
|
||||
- Worth the interruption
|
||||
|
||||
### 3. Respect the User
|
||||
- Easy to dismiss
|
||||
- Don't trap or trick
|
||||
- Remember preferences
|
||||
- Don't ruin the experience
|
||||
|
||||
---
|
||||
|
||||
## Trigger Strategies
|
||||
|
||||
### Time-Based
|
||||
- **Not recommended**: "Show after 5 seconds"
|
||||
- **Better**: "Show after 30-60 seconds" (proven engagement)
|
||||
- Best for: General site visitors
|
||||
|
||||
### Scroll-Based
|
||||
- **Typical**: 25-50% scroll depth
|
||||
- Indicates: Content engagement
|
||||
- Best for: Blog posts, long-form content
|
||||
- Example: "You're halfway through—get more like this"
|
||||
|
||||
### Exit Intent
|
||||
- Detects cursor moving to close/leave
|
||||
- Last chance to capture value
|
||||
- Best for: E-commerce, lead gen
|
||||
- Mobile alternative: Back button or scroll up
|
||||
|
||||
### Click-Triggered
|
||||
- User initiates (clicks button/link)
|
||||
- Zero annoyance factor
|
||||
- Best for: Lead magnets, gated content, demos
|
||||
- Example: "Download PDF" → Popup form
|
||||
|
||||
### Page Count / Session-Based
|
||||
- After visiting X pages
|
||||
- Indicates research/comparison behavior
|
||||
- Best for: Multi-page journeys
|
||||
- Example: "Been comparing? Here's a summary..."
|
||||
|
||||
### Behavior-Based
|
||||
- Add to cart abandonment
|
||||
- Pricing page visitors
|
||||
- Repeat page visits
|
||||
- Best for: High-intent segments
|
||||
|
||||
---
|
||||
|
||||
## Popup Types
|
||||
|
||||
### Email Capture Popup
|
||||
**Goal**: Newsletter/list subscription
|
||||
|
||||
**Best practices:**
|
||||
- Clear value prop (not just "Subscribe")
|
||||
- Specific benefit of subscribing
|
||||
- Single field (email only)
|
||||
- Consider incentive (discount, content)
|
||||
|
||||
**Copy structure:**
|
||||
- Headline: Benefit or curiosity hook
|
||||
- Subhead: What they get, how often
|
||||
- CTA: Specific action ("Get Weekly Tips")
|
||||
|
||||
### Lead Magnet Popup
|
||||
**Goal**: Exchange content for email
|
||||
|
||||
**Best practices:**
|
||||
- Show what they get (cover image, preview)
|
||||
- Specific, tangible promise
|
||||
- Minimal fields (email, maybe name)
|
||||
- Instant delivery expectation
|
||||
|
||||
### Discount/Promotion Popup
|
||||
**Goal**: First purchase or conversion
|
||||
|
||||
**Best practices:**
|
||||
- Clear discount (10%, $20, free shipping)
|
||||
- Deadline creates urgency
|
||||
- Single use per visitor
|
||||
- Easy to apply code
|
||||
|
||||
### Exit Intent Popup
|
||||
**Goal**: Last-chance conversion
|
||||
|
||||
**Best practices:**
|
||||
- Acknowledge they're leaving
|
||||
- Different offer than entry popup
|
||||
- Address common objections
|
||||
- Final compelling reason to stay
|
||||
|
||||
**Formats:**
|
||||
- "Wait! Before you go..."
|
||||
- "Forget something?"
|
||||
- "Get 10% off your first order"
|
||||
- "Questions? Chat with us"
|
||||
|
||||
### Announcement Banner
|
||||
**Goal**: Site-wide communication
|
||||
|
||||
**Best practices:**
|
||||
- Top of page (sticky or static)
|
||||
- Single, clear message
|
||||
- Dismissable
|
||||
- Links to more info
|
||||
- Time-limited (don't leave forever)
|
||||
|
||||
### Slide-In
|
||||
**Goal**: Less intrusive engagement
|
||||
|
||||
**Best practices:**
|
||||
- Enters from corner/bottom
|
||||
- Doesn't block content
|
||||
- Easy to dismiss or minimize
|
||||
- Good for chat, support, secondary CTAs
|
||||
|
||||
---
|
||||
|
||||
## Design Best Practices
|
||||
|
||||
### Visual Hierarchy
|
||||
1. Headline (largest, first seen)
|
||||
2. Value prop/offer (clear benefit)
|
||||
3. Form/CTA (obvious action)
|
||||
4. Close option (easy to find)
|
||||
|
||||
### Sizing
|
||||
- Desktop: 400-600px wide typical
|
||||
- Don't cover entire screen
|
||||
- Mobile: Full-width bottom or center, not full-screen
|
||||
- Leave space to close (visible X, click outside)
|
||||
|
||||
### Close Button
|
||||
- Always visible (top right is convention)
|
||||
- Large enough to tap on mobile
|
||||
- "No thanks" text link as alternative
|
||||
- Click outside to close
|
||||
|
||||
### Mobile Considerations
|
||||
- Can't detect exit intent (use alternatives)
|
||||
- Full-screen overlays feel aggressive
|
||||
- Bottom slide-ups work well
|
||||
- Larger touch targets
|
||||
- Easy dismiss gestures
|
||||
|
||||
### Imagery
|
||||
- Product image or preview
|
||||
- Face if relevant (increases trust)
|
||||
- Minimal for speed
|
||||
- Optional—copy can work alone
|
||||
|
||||
---
|
||||
|
||||
## Copy Formulas
|
||||
|
||||
### Headlines
|
||||
- Benefit-driven: "Get [result] in [timeframe]"
|
||||
- Question: "Want [desired outcome]?"
|
||||
- Command: "Don't miss [thing]"
|
||||
- Social proof: "Join [X] people who..."
|
||||
- Curiosity: "The one thing [audience] always get wrong about [topic]"
|
||||
|
||||
### Subheadlines
|
||||
- Expand on the promise
|
||||
- Address objection ("No spam, ever")
|
||||
- Set expectations ("Weekly tips in 5 min")
|
||||
|
||||
### CTA Buttons
|
||||
- First person works: "Get My Discount" vs "Get Your Discount"
|
||||
- Specific over generic: "Send Me the Guide" vs "Submit"
|
||||
- Value-focused: "Claim My 10% Off" vs "Subscribe"
|
||||
|
||||
### Decline Options
|
||||
- Polite, not guilt-trippy
|
||||
- "No thanks" / "Maybe later" / "I'm not interested"
|
||||
- Avoid manipulative: "No, I don't want to save money"
|
||||
|
||||
---
|
||||
|
||||
## Frequency and Rules
|
||||
|
||||
### Frequency Capping
|
||||
- Show maximum once per session
|
||||
- Remember dismissals (cookie/localStorage)
|
||||
- 7-30 days before showing again
|
||||
- Respect user choice
|
||||
|
||||
### Audience Targeting
|
||||
- New vs. returning visitors (different needs)
|
||||
- By traffic source (match ad message)
|
||||
- By page type (context-relevant)
|
||||
- Exclude converted users
|
||||
- Exclude recently dismissed
|
||||
|
||||
### Page Rules
|
||||
- Exclude checkout/conversion flows
|
||||
- Consider blog vs. product pages
|
||||
- Match offer to page context
|
||||
|
||||
---
|
||||
|
||||
## Compliance and Accessibility
|
||||
|
||||
### GDPR/Privacy
|
||||
- Clear consent language
|
||||
- Link to privacy policy
|
||||
- Don't pre-check opt-ins
|
||||
- Honor unsubscribe/preferences
|
||||
|
||||
### Accessibility
|
||||
- Keyboard navigable (Tab, Enter, Esc)
|
||||
- Focus trap while open
|
||||
- Screen reader compatible
|
||||
- Sufficient color contrast
|
||||
- Don't rely on color alone
|
||||
|
||||
### Google Guidelines
|
||||
- Intrusive interstitials hurt SEO
|
||||
- Mobile especially sensitive
|
||||
- Allow: Cookie notices, age verification, reasonable banners
|
||||
- Avoid: Full-screen before content on mobile
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
### Key Metrics
|
||||
- **Impression rate**: Visitors who see popup
|
||||
- **Conversion rate**: Impressions → Submissions
|
||||
- **Close rate**: How many dismiss immediately
|
||||
- **Engagement rate**: Interaction before close
|
||||
- **Time to close**: How long before dismissing
|
||||
|
||||
### What to Track
|
||||
- Popup views
|
||||
- Form focus
|
||||
- Submission attempts
|
||||
- Successful submissions
|
||||
- Close button clicks
|
||||
- Outside clicks
|
||||
- Escape key
|
||||
|
||||
### Benchmarks
|
||||
- Email popup: 2-5% conversion typical
|
||||
- Exit intent: 3-10% conversion
|
||||
- Click-triggered: Higher (10%+, self-selected)
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Popup Design
|
||||
- **Type**: Email capture, lead magnet, etc.
|
||||
- **Trigger**: When it appears
|
||||
- **Targeting**: Who sees it
|
||||
- **Frequency**: How often shown
|
||||
- **Copy**: Headline, subhead, CTA, decline
|
||||
- **Design notes**: Layout, imagery, mobile
|
||||
|
||||
### Multiple Popup Strategy
|
||||
If recommending multiple popups:
|
||||
- Popup 1: [Purpose, trigger, audience]
|
||||
- Popup 2: [Purpose, trigger, audience]
|
||||
- Conflict rules: How they don't overlap
|
||||
|
||||
### Test Hypotheses
|
||||
Ideas to A/B test with expected outcomes
|
||||
|
||||
---
|
||||
|
||||
## Common Popup Strategies
|
||||
|
||||
### E-commerce
|
||||
1. Entry/scroll: First-purchase discount
|
||||
2. Exit intent: Bigger discount or reminder
|
||||
3. Cart abandonment: Complete your order
|
||||
|
||||
### B2B SaaS
|
||||
1. Click-triggered: Demo request, lead magnets
|
||||
2. Scroll: Newsletter/blog subscription
|
||||
3. Exit intent: Trial reminder or content offer
|
||||
|
||||
### Content/Media
|
||||
1. Scroll-based: Newsletter after engagement
|
||||
2. Page count: Subscribe after multiple visits
|
||||
3. Exit intent: Don't miss future content
|
||||
|
||||
### Lead Generation
|
||||
1. Time-delayed: General list building
|
||||
2. Click-triggered: Specific lead magnets
|
||||
3. Exit intent: Final capture attempt
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's the primary goal for this popup?
|
||||
2. What's your current popup performance (if any)?
|
||||
3. What traffic sources are you optimizing for?
|
||||
4. What incentive can you offer?
|
||||
5. Are there compliance requirements (GDPR, etc.)?
|
||||
6. Mobile vs. desktop traffic split?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **form-cro**: For optimizing the form inside the popup
|
||||
- **page-cro**: For the page context around popups
|
||||
- **email-sequence**: For what happens after popup conversion
|
||||
- **ab-test-setup**: For testing popup variations
|
||||
410
skills/programmatic-seo.md
Normal file
410
skills/programmatic-seo.md
Normal file
@@ -0,0 +1,410 @@
|
||||
---
|
||||
name: programmatic-seo
|
||||
description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
|
||||
---
|
||||
|
||||
# Programmatic SEO
|
||||
|
||||
You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before designing a programmatic SEO strategy, understand:
|
||||
|
||||
1. **Business Context**
|
||||
- What's the product/service?
|
||||
- Who is the target audience?
|
||||
- What's the conversion goal for these pages?
|
||||
|
||||
2. **Opportunity Assessment**
|
||||
- What search patterns exist?
|
||||
- How many potential pages?
|
||||
- What's the search volume distribution?
|
||||
|
||||
3. **Competitive Landscape**
|
||||
- Who ranks for these terms now?
|
||||
- What do their pages look like?
|
||||
- What would it take to beat them?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Unique Value Per Page
|
||||
Every page must provide value specific to that page:
|
||||
- Unique data
|
||||
- Unique insights
|
||||
- Unique combinations
|
||||
- Not just swapped variables in a template
|
||||
|
||||
### 2. Genuine Search Intent Match
|
||||
Pages must actually answer what people are searching for:
|
||||
- Understand the intent behind each pattern
|
||||
- Provide the complete answer
|
||||
- Don't over-optimize for keywords at expense of usefulness
|
||||
|
||||
### 3. Scalable Quality, Not Just Quantity
|
||||
- Quality standards must be maintained at scale
|
||||
- Better to have 100 great pages than 10,000 thin ones
|
||||
- Build quality checks into the process
|
||||
|
||||
### 4. Avoid Google Penalties
|
||||
- No doorway pages (thin pages that just funnel to main site)
|
||||
- No keyword stuffing
|
||||
- No duplicate content across pages
|
||||
- Genuine utility for users
|
||||
|
||||
---
|
||||
|
||||
## Common Programmatic SEO Patterns
|
||||
|
||||
### Location-Based Pages
|
||||
**Pattern**: "[Service] in [Location]"
|
||||
**Examples**:
|
||||
- "Plumbers in Austin"
|
||||
- "Coworking spaces in Brooklyn"
|
||||
- "Real estate agents in Miami"
|
||||
|
||||
**Value requirements**:
|
||||
- Location-specific information
|
||||
- Local data (stats, regulations, etc.)
|
||||
- Local testimonials/case studies
|
||||
- Not just [City] swapped in template
|
||||
|
||||
### Integration/Compatibility Pages
|
||||
**Pattern**: "[Tool] + [Tool]" or "[Product] for [Platform]"
|
||||
**Examples**:
|
||||
- "Slack + Asana integration"
|
||||
- "CRM for Shopify"
|
||||
- "Zapier alternatives for X"
|
||||
|
||||
**Value requirements**:
|
||||
- Genuine integration details
|
||||
- Use cases for the combination
|
||||
- Setup instructions
|
||||
- Comparison if relevant
|
||||
|
||||
### Comparison Pages
|
||||
**Pattern**: "[X] vs [Y]" or "[X] alternatives"
|
||||
**Examples**:
|
||||
- "Notion vs Coda"
|
||||
- "Airtable alternatives"
|
||||
- "Best CRMs for small business"
|
||||
|
||||
**Value requirements**:
|
||||
- Actual comparison data
|
||||
- Honest pros/cons
|
||||
- Use case recommendations
|
||||
- Updated regularly
|
||||
|
||||
### Directory/Aggregator Pages
|
||||
**Pattern**: "[Category] + [Qualifier]"
|
||||
**Examples**:
|
||||
- "Top marketing agencies in [city]"
|
||||
- "Best restaurants for [cuisine] in [area]"
|
||||
- "[Software] companies in [industry]"
|
||||
|
||||
**Value requirements**:
|
||||
- Curated, not just scraped
|
||||
- Useful details per listing
|
||||
- Filters/sorting for utility
|
||||
- Fresh data
|
||||
|
||||
### Stats/Data Pages
|
||||
**Pattern**: "[Topic] statistics [year]"
|
||||
**Examples**:
|
||||
- "Email marketing statistics 2024"
|
||||
- "Remote work trends by industry"
|
||||
- "Average [metric] by [segment]"
|
||||
|
||||
**Value requirements**:
|
||||
- Original or well-sourced data
|
||||
- Visualization
|
||||
- Updated regularly
|
||||
- Unique analysis
|
||||
|
||||
### Use Case Pages
|
||||
**Pattern**: "[Product] for [Use Case]"
|
||||
**Examples**:
|
||||
- "Notion for project management"
|
||||
- "Airtable for inventory tracking"
|
||||
- "Figma for presentations"
|
||||
|
||||
**Value requirements**:
|
||||
- Specific setup/workflow
|
||||
- Templates if applicable
|
||||
- Real examples
|
||||
- Unique to use case
|
||||
|
||||
### Glossary/Definition Pages
|
||||
**Pattern**: "What is [term]"
|
||||
**Examples**:
|
||||
- "What is product-led growth"
|
||||
- "API meaning in software"
|
||||
- "CRM definition"
|
||||
|
||||
**Value requirements**:
|
||||
- Clear, comprehensive definition
|
||||
- Related terms
|
||||
- Examples
|
||||
- Further reading
|
||||
|
||||
---
|
||||
|
||||
## Implementation Framework
|
||||
|
||||
### 1. Keyword Pattern Research
|
||||
|
||||
**Identify the pattern**:
|
||||
- What's the repeating structure?
|
||||
- What are the variables?
|
||||
- How many unique combinations exist?
|
||||
|
||||
**Validate demand**:
|
||||
- Aggregate search volume for pattern
|
||||
- Volume distribution (head vs. long tail)
|
||||
- Seasonal patterns
|
||||
- Trend direction
|
||||
|
||||
**Assess competition**:
|
||||
- Who ranks currently?
|
||||
- What's their content quality?
|
||||
- What's their domain authority?
|
||||
- Can you realistically compete?
|
||||
|
||||
### 2. Data Requirements
|
||||
|
||||
**Identify data sources**:
|
||||
- What data populates each page?
|
||||
- Where does that data come from?
|
||||
- Is it first-party, scraped, licensed, public?
|
||||
- How is it updated?
|
||||
|
||||
**Data schema design**:
|
||||
```
|
||||
For "[Service] in [City]" pages:
|
||||
|
||||
city:
|
||||
- name
|
||||
- population
|
||||
- relevant_stats
|
||||
|
||||
service:
|
||||
- name
|
||||
- description
|
||||
- typical_pricing
|
||||
|
||||
local_providers:
|
||||
- name
|
||||
- rating
|
||||
- reviews_count
|
||||
- specialty
|
||||
|
||||
local_data:
|
||||
- regulations
|
||||
- average_prices
|
||||
- market_size
|
||||
```
|
||||
|
||||
### 3. Template Design
|
||||
|
||||
**Page structure**:
|
||||
- Header with target keyword
|
||||
- Unique intro (not just variables swapped)
|
||||
- Data-driven sections
|
||||
- Related pages / internal links
|
||||
- CTAs appropriate to intent
|
||||
|
||||
**Ensuring uniqueness**:
|
||||
- Each page needs unique value
|
||||
- Conditional content based on data
|
||||
- User-generated content where possible
|
||||
- Original insights/analysis per page
|
||||
|
||||
**Template example**:
|
||||
```
|
||||
H1: [Service] in [City]: [Year] Guide
|
||||
|
||||
Intro: [Dynamic paragraph using city stats + service context]
|
||||
|
||||
Section 1: Why [City] for [Service]
|
||||
[City-specific data and insights]
|
||||
|
||||
Section 2: Top [Service] Providers in [City]
|
||||
[Data-driven list with unique details]
|
||||
|
||||
Section 3: Pricing for [Service] in [City]
|
||||
[Local pricing data if available]
|
||||
|
||||
Section 4: FAQs about [Service] in [City]
|
||||
[Common questions with city-specific answers]
|
||||
|
||||
Related: [Service] in [Nearby Cities]
|
||||
```
|
||||
|
||||
### 4. Internal Linking Architecture
|
||||
|
||||
**Hub and spoke model**:
|
||||
- Hub: Main category page
|
||||
- Spokes: Individual programmatic pages
|
||||
- Cross-links between related spokes
|
||||
|
||||
**Avoid orphan pages**:
|
||||
- Every page reachable from main site
|
||||
- Logical category structure
|
||||
- XML sitemap for all pages
|
||||
|
||||
**Breadcrumbs**:
|
||||
- Show hierarchy
|
||||
- Structured data markup
|
||||
- User navigation aid
|
||||
|
||||
### 5. Indexation Strategy
|
||||
|
||||
**Prioritize important pages**:
|
||||
- Not all pages need to be indexed
|
||||
- Index high-volume patterns
|
||||
- Noindex very thin variations
|
||||
|
||||
**Crawl budget management**:
|
||||
- Paginate thoughtfully
|
||||
- Avoid infinite crawl traps
|
||||
- Use robots.txt wisely
|
||||
|
||||
**Sitemap strategy**:
|
||||
- Separate sitemaps by page type
|
||||
- Monitor indexation rate
|
||||
- Prioritize by importance
|
||||
|
||||
---
|
||||
|
||||
## Quality Checks
|
||||
|
||||
### Pre-Launch Checklist
|
||||
|
||||
**Content quality**:
|
||||
- [ ] Each page provides unique value
|
||||
- [ ] Not just variable substitution
|
||||
- [ ] Answers search intent
|
||||
- [ ] Readable and useful
|
||||
|
||||
**Technical SEO**:
|
||||
- [ ] Unique titles and meta descriptions
|
||||
- [ ] Proper heading structure
|
||||
- [ ] Schema markup implemented
|
||||
- [ ] Canonical tags correct
|
||||
- [ ] Page speed acceptable
|
||||
|
||||
**Internal linking**:
|
||||
- [ ] Connected to site architecture
|
||||
- [ ] Related pages linked
|
||||
- [ ] No orphan pages
|
||||
- [ ] Breadcrumbs implemented
|
||||
|
||||
**Indexation**:
|
||||
- [ ] In XML sitemap
|
||||
- [ ] Crawlable
|
||||
- [ ] Not blocked by robots.txt
|
||||
- [ ] No conflicting noindex
|
||||
|
||||
### Monitoring Post-Launch
|
||||
|
||||
**Track**:
|
||||
- Indexation rate
|
||||
- Rankings by page pattern
|
||||
- Traffic by page pattern
|
||||
- Engagement metrics
|
||||
- Conversion rate
|
||||
|
||||
**Watch for**:
|
||||
- Thin content warnings in Search Console
|
||||
- Ranking drops
|
||||
- Manual actions
|
||||
- Crawl errors
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes to Avoid
|
||||
|
||||
### Thin Content
|
||||
- Just swapping city names in identical content
|
||||
- No unique information per page
|
||||
- "Doorway pages" that just redirect
|
||||
|
||||
### Keyword Cannibalization
|
||||
- Multiple pages targeting same keyword
|
||||
- No clear hierarchy
|
||||
- Competing with yourself
|
||||
|
||||
### Over-Generation
|
||||
- Creating pages with no search demand
|
||||
- Too many low-quality pages dilute authority
|
||||
- Quantity over quality
|
||||
|
||||
### Poor Data Quality
|
||||
- Outdated information
|
||||
- Incorrect data
|
||||
- Missing data showing as blank
|
||||
|
||||
### Ignoring User Experience
|
||||
- Pages exist for Google, not users
|
||||
- No conversion path
|
||||
- Bouncy, unhelpful content
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Strategy Document
|
||||
|
||||
**Opportunity Analysis**:
|
||||
- Keyword pattern identified
|
||||
- Search volume estimates
|
||||
- Competition assessment
|
||||
- Feasibility rating
|
||||
|
||||
**Implementation Plan**:
|
||||
- Data requirements and sources
|
||||
- Template structure
|
||||
- Number of pages (phases)
|
||||
- Internal linking plan
|
||||
- Technical requirements
|
||||
|
||||
**Content Guidelines**:
|
||||
- What makes each page unique
|
||||
- Quality standards
|
||||
- Update frequency
|
||||
|
||||
### Page Template
|
||||
|
||||
**URL structure**: `/category/variable/`
|
||||
**Title template**: [Variable] + [Static] + [Brand]
|
||||
**Meta description template**: [Pattern with variables]
|
||||
**H1 template**: [Pattern]
|
||||
**Content outline**: Section by section
|
||||
**Schema markup**: Type and required fields
|
||||
|
||||
### Launch Checklist
|
||||
|
||||
Specific pre-launch checks for this implementation
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What keyword patterns are you targeting?
|
||||
2. What data do you have (or can acquire)?
|
||||
3. How many pages are you planning to create?
|
||||
4. What does your site authority look like?
|
||||
5. Who currently ranks for these terms?
|
||||
6. What's your technical stack for generating pages?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **seo-audit**: For auditing programmatic pages after launch
|
||||
- **schema-markup**: For adding structured data to templates
|
||||
- **page-copywriting**: For the non-templated copy portions
|
||||
- **analytics-tracking**: For measuring programmatic page performance
|
||||
596
skills/schema-markup.md
Normal file
596
skills/schema-markup.md
Normal file
@@ -0,0 +1,596 @@
|
||||
---
|
||||
name: schema-markup
|
||||
description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
|
||||
---
|
||||
|
||||
# Schema Markup
|
||||
|
||||
You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before implementing schema, understand:
|
||||
|
||||
1. **Page Type**
|
||||
- What kind of page is this?
|
||||
- What's the primary content?
|
||||
- What rich results are possible?
|
||||
|
||||
2. **Current State**
|
||||
- Any existing schema?
|
||||
- Errors in current implementation?
|
||||
- Which rich results are already appearing?
|
||||
|
||||
3. **Goals**
|
||||
- Which rich results are you targeting?
|
||||
- What's the business value?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Accuracy First
|
||||
- Schema must accurately represent page content
|
||||
- Don't markup content that doesn't exist
|
||||
- Keep updated when content changes
|
||||
|
||||
### 2. Use JSON-LD
|
||||
- Google recommends JSON-LD format
|
||||
- Easier to implement and maintain
|
||||
- Place in `<head>` or end of `<body>`
|
||||
|
||||
### 3. Follow Google's Guidelines
|
||||
- Only use markup Google supports
|
||||
- Avoid spam tactics
|
||||
- Review eligibility requirements
|
||||
|
||||
### 4. Validate Everything
|
||||
- Test before deploying
|
||||
- Monitor Search Console
|
||||
- Fix errors promptly
|
||||
|
||||
---
|
||||
|
||||
## Common Schema Types
|
||||
|
||||
### Organization
|
||||
**Use for**: Company/brand homepage or about page
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- url
|
||||
|
||||
**Recommended properties**:
|
||||
- logo
|
||||
- sameAs (social profiles)
|
||||
- contactPoint
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Organization",
|
||||
"name": "Example Company",
|
||||
"url": "https://example.com",
|
||||
"logo": "https://example.com/logo.png",
|
||||
"sameAs": [
|
||||
"https://twitter.com/example",
|
||||
"https://linkedin.com/company/example",
|
||||
"https://facebook.com/example"
|
||||
],
|
||||
"contactPoint": {
|
||||
"@type": "ContactPoint",
|
||||
"telephone": "+1-555-555-5555",
|
||||
"contactType": "customer service"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### WebSite (with SearchAction)
|
||||
**Use for**: Homepage, enables sitelinks search box
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- url
|
||||
|
||||
**For search box**:
|
||||
- potentialAction with SearchAction
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "WebSite",
|
||||
"name": "Example",
|
||||
"url": "https://example.com",
|
||||
"potentialAction": {
|
||||
"@type": "SearchAction",
|
||||
"target": {
|
||||
"@type": "EntryPoint",
|
||||
"urlTemplate": "https://example.com/search?q={search_term_string}"
|
||||
},
|
||||
"query-input": "required name=search_term_string"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Article / BlogPosting
|
||||
**Use for**: Blog posts, news articles
|
||||
|
||||
**Required properties**:
|
||||
- headline
|
||||
- image
|
||||
- datePublished
|
||||
- author
|
||||
|
||||
**Recommended properties**:
|
||||
- dateModified
|
||||
- publisher
|
||||
- description
|
||||
- mainEntityOfPage
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Article",
|
||||
"headline": "How to Implement Schema Markup",
|
||||
"image": "https://example.com/image.jpg",
|
||||
"datePublished": "2024-01-15T08:00:00+00:00",
|
||||
"dateModified": "2024-01-20T10:00:00+00:00",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "Jane Doe",
|
||||
"url": "https://example.com/authors/jane"
|
||||
},
|
||||
"publisher": {
|
||||
"@type": "Organization",
|
||||
"name": "Example Company",
|
||||
"logo": {
|
||||
"@type": "ImageObject",
|
||||
"url": "https://example.com/logo.png"
|
||||
}
|
||||
},
|
||||
"description": "A complete guide to implementing schema markup...",
|
||||
"mainEntityOfPage": {
|
||||
"@type": "WebPage",
|
||||
"@id": "https://example.com/schema-guide"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Product
|
||||
**Use for**: Product pages (e-commerce or SaaS)
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- image
|
||||
- offers (with price and availability)
|
||||
|
||||
**Recommended properties**:
|
||||
- description
|
||||
- sku
|
||||
- brand
|
||||
- aggregateRating
|
||||
- review
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Product",
|
||||
"name": "Premium Widget",
|
||||
"image": "https://example.com/widget.jpg",
|
||||
"description": "Our best-selling widget for professionals",
|
||||
"sku": "WIDGET-001",
|
||||
"brand": {
|
||||
"@type": "Brand",
|
||||
"name": "Example Co"
|
||||
},
|
||||
"offers": {
|
||||
"@type": "Offer",
|
||||
"url": "https://example.com/products/widget",
|
||||
"priceCurrency": "USD",
|
||||
"price": "99.99",
|
||||
"availability": "https://schema.org/InStock",
|
||||
"priceValidUntil": "2024-12-31"
|
||||
},
|
||||
"aggregateRating": {
|
||||
"@type": "AggregateRating",
|
||||
"ratingValue": "4.8",
|
||||
"reviewCount": "127"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### SoftwareApplication
|
||||
**Use for**: SaaS product pages, app landing pages
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- offers (or free indicator)
|
||||
|
||||
**Recommended properties**:
|
||||
- applicationCategory
|
||||
- operatingSystem
|
||||
- aggregateRating
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "SoftwareApplication",
|
||||
"name": "Example App",
|
||||
"applicationCategory": "BusinessApplication",
|
||||
"operatingSystem": "Web, iOS, Android",
|
||||
"offers": {
|
||||
"@type": "Offer",
|
||||
"price": "0",
|
||||
"priceCurrency": "USD"
|
||||
},
|
||||
"aggregateRating": {
|
||||
"@type": "AggregateRating",
|
||||
"ratingValue": "4.6",
|
||||
"ratingCount": "1250"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### FAQPage
|
||||
**Use for**: Pages with frequently asked questions
|
||||
|
||||
**Required properties**:
|
||||
- mainEntity (array of Question/Answer)
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "FAQPage",
|
||||
"mainEntity": [
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "What is schema markup?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "Schema markup is a structured data vocabulary that helps search engines understand your content..."
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "Question",
|
||||
"name": "How do I implement schema?",
|
||||
"acceptedAnswer": {
|
||||
"@type": "Answer",
|
||||
"text": "The recommended approach is to use JSON-LD format, placing the script in your page's head..."
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### HowTo
|
||||
**Use for**: Instructional content, tutorials
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- step (array of HowToStep)
|
||||
|
||||
**Recommended properties**:
|
||||
- image
|
||||
- totalTime
|
||||
- estimatedCost
|
||||
- supply/tool
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "HowTo",
|
||||
"name": "How to Add Schema Markup to Your Website",
|
||||
"description": "A step-by-step guide to implementing JSON-LD schema",
|
||||
"totalTime": "PT15M",
|
||||
"step": [
|
||||
{
|
||||
"@type": "HowToStep",
|
||||
"name": "Choose your schema type",
|
||||
"text": "Identify the appropriate schema type for your page content...",
|
||||
"url": "https://example.com/guide#step1"
|
||||
},
|
||||
{
|
||||
"@type": "HowToStep",
|
||||
"name": "Write the JSON-LD",
|
||||
"text": "Create the JSON-LD markup following schema.org specifications...",
|
||||
"url": "https://example.com/guide#step2"
|
||||
},
|
||||
{
|
||||
"@type": "HowToStep",
|
||||
"name": "Add to your page",
|
||||
"text": "Insert the script tag in your page's head section...",
|
||||
"url": "https://example.com/guide#step3"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### BreadcrumbList
|
||||
**Use for**: Any page with breadcrumb navigation
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "BreadcrumbList",
|
||||
"itemListElement": [
|
||||
{
|
||||
"@type": "ListItem",
|
||||
"position": 1,
|
||||
"name": "Home",
|
||||
"item": "https://example.com"
|
||||
},
|
||||
{
|
||||
"@type": "ListItem",
|
||||
"position": 2,
|
||||
"name": "Blog",
|
||||
"item": "https://example.com/blog"
|
||||
},
|
||||
{
|
||||
"@type": "ListItem",
|
||||
"position": 3,
|
||||
"name": "SEO Guide",
|
||||
"item": "https://example.com/blog/seo-guide"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### LocalBusiness
|
||||
**Use for**: Local business location pages
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- address
|
||||
- (Various by business type)
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "LocalBusiness",
|
||||
"name": "Example Coffee Shop",
|
||||
"image": "https://example.com/shop.jpg",
|
||||
"address": {
|
||||
"@type": "PostalAddress",
|
||||
"streetAddress": "123 Main Street",
|
||||
"addressLocality": "San Francisco",
|
||||
"addressRegion": "CA",
|
||||
"postalCode": "94102",
|
||||
"addressCountry": "US"
|
||||
},
|
||||
"geo": {
|
||||
"@type": "GeoCoordinates",
|
||||
"latitude": "37.7749",
|
||||
"longitude": "-122.4194"
|
||||
},
|
||||
"telephone": "+1-555-555-5555",
|
||||
"openingHoursSpecification": [
|
||||
{
|
||||
"@type": "OpeningHoursSpecification",
|
||||
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
|
||||
"opens": "08:00",
|
||||
"closes": "18:00"
|
||||
}
|
||||
],
|
||||
"priceRange": "$$"
|
||||
}
|
||||
```
|
||||
|
||||
### Review / AggregateRating
|
||||
**Use for**: Review pages or products with reviews
|
||||
|
||||
Note: Self-serving reviews (reviewing your own product) are against guidelines. Reviews must be from real customers.
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Product",
|
||||
"name": "Example Product",
|
||||
"aggregateRating": {
|
||||
"@type": "AggregateRating",
|
||||
"ratingValue": "4.5",
|
||||
"bestRating": "5",
|
||||
"worstRating": "1",
|
||||
"ratingCount": "523"
|
||||
},
|
||||
"review": [
|
||||
{
|
||||
"@type": "Review",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "John Smith"
|
||||
},
|
||||
"datePublished": "2024-01-10",
|
||||
"reviewRating": {
|
||||
"@type": "Rating",
|
||||
"ratingValue": "5"
|
||||
},
|
||||
"reviewBody": "Excellent product, exceeded my expectations..."
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### Event
|
||||
**Use for**: Event pages, webinars, conferences
|
||||
|
||||
**Required properties**:
|
||||
- name
|
||||
- startDate
|
||||
- location (or eventAttendanceMode for online)
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Event",
|
||||
"name": "Annual Marketing Conference",
|
||||
"startDate": "2024-06-15T09:00:00-07:00",
|
||||
"endDate": "2024-06-15T17:00:00-07:00",
|
||||
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
|
||||
"eventStatus": "https://schema.org/EventScheduled",
|
||||
"location": {
|
||||
"@type": "VirtualLocation",
|
||||
"url": "https://example.com/conference"
|
||||
},
|
||||
"image": "https://example.com/conference.jpg",
|
||||
"description": "Join us for our annual marketing conference...",
|
||||
"offers": {
|
||||
"@type": "Offer",
|
||||
"url": "https://example.com/conference/tickets",
|
||||
"price": "199",
|
||||
"priceCurrency": "USD",
|
||||
"availability": "https://schema.org/InStock",
|
||||
"validFrom": "2024-01-01"
|
||||
},
|
||||
"performer": {
|
||||
"@type": "Organization",
|
||||
"name": "Example Company"
|
||||
},
|
||||
"organizer": {
|
||||
"@type": "Organization",
|
||||
"name": "Example Company",
|
||||
"url": "https://example.com"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Multiple Schema Types on One Page
|
||||
|
||||
You can (and often should) have multiple schema types:
|
||||
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@graph": [
|
||||
{
|
||||
"@type": "Organization",
|
||||
"@id": "https://example.com/#organization",
|
||||
"name": "Example Company",
|
||||
"url": "https://example.com"
|
||||
},
|
||||
{
|
||||
"@type": "WebSite",
|
||||
"@id": "https://example.com/#website",
|
||||
"url": "https://example.com",
|
||||
"name": "Example",
|
||||
"publisher": {
|
||||
"@id": "https://example.com/#organization"
|
||||
}
|
||||
},
|
||||
{
|
||||
"@type": "BreadcrumbList",
|
||||
"itemListElement": [...]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Validation and Testing
|
||||
|
||||
### Tools
|
||||
- **Google Rich Results Test**: https://search.google.com/test/rich-results
|
||||
- **Schema.org Validator**: https://validator.schema.org/
|
||||
- **Search Console**: Enhancements reports
|
||||
|
||||
### Common Errors
|
||||
|
||||
**Missing required properties**
|
||||
- Check Google's documentation for required fields
|
||||
- Different from schema.org minimum requirements
|
||||
|
||||
**Invalid values**
|
||||
- Dates must be ISO 8601 format
|
||||
- URLs must be fully qualified
|
||||
- Enumerations must use exact values
|
||||
|
||||
**Mismatch with page content**
|
||||
- Schema doesn't match visible content
|
||||
- Ratings for products without reviews shown
|
||||
- Prices that don't match displayed prices
|
||||
|
||||
---
|
||||
|
||||
## Implementation Patterns
|
||||
|
||||
### Static Sites
|
||||
- Add JSON-LD directly in HTML template
|
||||
- Use includes/partials for reusable schema
|
||||
|
||||
### Dynamic Sites (React, Next.js, etc.)
|
||||
- Component that renders schema
|
||||
- Server-side rendered for SEO
|
||||
- Serialize data to JSON-LD
|
||||
|
||||
```jsx
|
||||
// Next.js example
|
||||
export default function ProductPage({ product }) {
|
||||
const schema = {
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Product",
|
||||
name: product.name,
|
||||
// ... other properties
|
||||
};
|
||||
|
||||
return (
|
||||
<>
|
||||
<Head>
|
||||
<script
|
||||
type="application/ld+json"
|
||||
dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }}
|
||||
/>
|
||||
</Head>
|
||||
{/* Page content */}
|
||||
</>
|
||||
);
|
||||
}
|
||||
```
|
||||
|
||||
### CMS / WordPress
|
||||
- Plugins (Yoast, Rank Math, Schema Pro)
|
||||
- Theme modifications
|
||||
- Custom fields to structured data
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Schema Implementation
|
||||
```json
|
||||
// Full JSON-LD code block
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "...",
|
||||
// Complete markup
|
||||
}
|
||||
```
|
||||
|
||||
### Placement Instructions
|
||||
Where to add the code and how
|
||||
|
||||
### Testing Checklist
|
||||
- [ ] Validates in Rich Results Test
|
||||
- [ ] No errors or warnings
|
||||
- [ ] Matches page content
|
||||
- [ ] All required properties included
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What type of page is this?
|
||||
2. What rich results are you hoping to achieve?
|
||||
3. What data is available to populate the schema?
|
||||
4. Is there existing schema on the page?
|
||||
5. What's your tech stack for implementation?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **seo-audit**: For overall SEO including schema review
|
||||
- **programmatic-seo**: For templated schema at scale
|
||||
- **analytics-tracking**: For measuring rich result impact
|
||||
384
skills/seo-audit.md
Normal file
384
skills/seo-audit.md
Normal file
@@ -0,0 +1,384 @@
|
||||
---
|
||||
name: seo-audit
|
||||
description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
|
||||
---
|
||||
|
||||
# SEO Audit
|
||||
|
||||
You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before auditing, understand:
|
||||
|
||||
1. **Site Context**
|
||||
- What type of site? (SaaS, e-commerce, blog, etc.)
|
||||
- What's the primary business goal for SEO?
|
||||
- What keywords/topics are priorities?
|
||||
|
||||
2. **Current State**
|
||||
- Any known issues or concerns?
|
||||
- Current organic traffic level?
|
||||
- Recent changes or migrations?
|
||||
|
||||
3. **Scope**
|
||||
- Full site audit or specific pages?
|
||||
- Technical + on-page, or one focus area?
|
||||
- Access to Search Console / analytics?
|
||||
|
||||
---
|
||||
|
||||
## Audit Framework
|
||||
|
||||
### Priority Order
|
||||
1. **Crawlability & Indexation** (can Google find and index it?)
|
||||
2. **Technical Foundations** (is the site fast and functional?)
|
||||
3. **On-Page Optimization** (is content optimized?)
|
||||
4. **Content Quality** (does it deserve to rank?)
|
||||
5. **Authority & Links** (does it have credibility?)
|
||||
|
||||
---
|
||||
|
||||
## Technical SEO Audit
|
||||
|
||||
### Crawlability
|
||||
|
||||
**Robots.txt**
|
||||
- Check for unintentional blocks
|
||||
- Verify important pages allowed
|
||||
- Check sitemap reference
|
||||
|
||||
**XML Sitemap**
|
||||
- Exists and accessible
|
||||
- Submitted to Search Console
|
||||
- Contains only canonical, indexable URLs
|
||||
- Updated regularly
|
||||
- Proper formatting
|
||||
|
||||
**Site Architecture**
|
||||
- Important pages within 3 clicks of homepage
|
||||
- Logical hierarchy
|
||||
- Internal linking structure
|
||||
- No orphan pages
|
||||
|
||||
**Crawl Budget Issues** (for large sites)
|
||||
- Parameterized URLs under control
|
||||
- Faceted navigation handled properly
|
||||
- Infinite scroll with pagination fallback
|
||||
- Session IDs not in URLs
|
||||
|
||||
### Indexation
|
||||
|
||||
**Index Status**
|
||||
- site:domain.com check
|
||||
- Search Console coverage report
|
||||
- Compare indexed vs. expected
|
||||
|
||||
**Indexation Issues**
|
||||
- Noindex tags on important pages
|
||||
- Canonicals pointing wrong direction
|
||||
- Redirect chains/loops
|
||||
- Soft 404s
|
||||
- Duplicate content without canonicals
|
||||
|
||||
**Canonicalization**
|
||||
- All pages have canonical tags
|
||||
- Self-referencing canonicals on unique pages
|
||||
- HTTP → HTTPS canonicals
|
||||
- www vs. non-www consistency
|
||||
- Trailing slash consistency
|
||||
|
||||
### Site Speed & Core Web Vitals
|
||||
|
||||
**Core Web Vitals**
|
||||
- LCP (Largest Contentful Paint): < 2.5s
|
||||
- INP (Interaction to Next Paint): < 200ms
|
||||
- CLS (Cumulative Layout Shift): < 0.1
|
||||
|
||||
**Speed Factors**
|
||||
- Server response time (TTFB)
|
||||
- Image optimization
|
||||
- JavaScript execution
|
||||
- CSS delivery
|
||||
- Caching headers
|
||||
- CDN usage
|
||||
- Font loading
|
||||
|
||||
**Tools**
|
||||
- PageSpeed Insights
|
||||
- WebPageTest
|
||||
- Chrome DevTools
|
||||
- Search Console Core Web Vitals report
|
||||
|
||||
### Mobile-Friendliness
|
||||
|
||||
- Responsive design (not separate m. site)
|
||||
- Tap target sizes
|
||||
- Viewport configured
|
||||
- No horizontal scroll
|
||||
- Same content as desktop
|
||||
- Mobile-first indexing readiness
|
||||
|
||||
### Security & HTTPS
|
||||
|
||||
- HTTPS across entire site
|
||||
- Valid SSL certificate
|
||||
- No mixed content
|
||||
- HTTP → HTTPS redirects
|
||||
- HSTS header (bonus)
|
||||
|
||||
### URL Structure
|
||||
|
||||
- Readable, descriptive URLs
|
||||
- Keywords in URLs where natural
|
||||
- Consistent structure
|
||||
- No unnecessary parameters
|
||||
- Lowercase and hyphen-separated
|
||||
|
||||
---
|
||||
|
||||
## On-Page SEO Audit
|
||||
|
||||
### Title Tags
|
||||
|
||||
**Check for:**
|
||||
- Unique titles for each page
|
||||
- Primary keyword near beginning
|
||||
- 50-60 characters (visible in SERP)
|
||||
- Compelling and click-worthy
|
||||
- Brand name placement (end, usually)
|
||||
|
||||
**Common issues:**
|
||||
- Duplicate titles
|
||||
- Too long (truncated)
|
||||
- Too short (wasted opportunity)
|
||||
- Keyword stuffing
|
||||
- Missing entirely
|
||||
|
||||
### Meta Descriptions
|
||||
|
||||
**Check for:**
|
||||
- Unique descriptions per page
|
||||
- 150-160 characters
|
||||
- Includes primary keyword
|
||||
- Clear value proposition
|
||||
- Call to action
|
||||
|
||||
**Common issues:**
|
||||
- Duplicate descriptions
|
||||
- Auto-generated garbage
|
||||
- Too long/short
|
||||
- No compelling reason to click
|
||||
|
||||
### Heading Structure
|
||||
|
||||
**Check for:**
|
||||
- One H1 per page
|
||||
- H1 contains primary keyword
|
||||
- Logical hierarchy (H1 → H2 → H3)
|
||||
- Headings describe content
|
||||
- Not just for styling
|
||||
|
||||
**Common issues:**
|
||||
- Multiple H1s
|
||||
- Skip levels (H1 → H3)
|
||||
- Headings used for styling only
|
||||
- No H1 on page
|
||||
|
||||
### Content Optimization
|
||||
|
||||
**Primary Page Content**
|
||||
- Keyword in first 100 words
|
||||
- Related keywords naturally used
|
||||
- Sufficient depth/length for topic
|
||||
- Answers search intent
|
||||
- Better than competitors
|
||||
|
||||
**Thin Content Issues**
|
||||
- Pages with little unique content
|
||||
- Tag/category pages with no value
|
||||
- Doorway pages
|
||||
- Duplicate or near-duplicate content
|
||||
|
||||
### Image Optimization
|
||||
|
||||
**Check for:**
|
||||
- Descriptive file names
|
||||
- Alt text on all images
|
||||
- Alt text describes image
|
||||
- Compressed file sizes
|
||||
- Modern formats (WebP)
|
||||
- Lazy loading implemented
|
||||
- Responsive images
|
||||
|
||||
### Internal Linking
|
||||
|
||||
**Check for:**
|
||||
- Important pages well-linked
|
||||
- Descriptive anchor text
|
||||
- Logical link relationships
|
||||
- No broken internal links
|
||||
- Reasonable link count per page
|
||||
|
||||
**Common issues:**
|
||||
- Orphan pages (no internal links)
|
||||
- Over-optimized anchor text
|
||||
- Important pages buried
|
||||
- Excessive footer/sidebar links
|
||||
|
||||
### Keyword Targeting
|
||||
|
||||
**Per Page**
|
||||
- Clear primary keyword target
|
||||
- Title, H1, URL aligned
|
||||
- Content satisfies search intent
|
||||
- Not competing with other pages (cannibalization)
|
||||
|
||||
**Site-Wide**
|
||||
- Keyword mapping document
|
||||
- No major gaps in coverage
|
||||
- No keyword cannibalization
|
||||
- Logical topical clusters
|
||||
|
||||
---
|
||||
|
||||
## Content Quality Assessment
|
||||
|
||||
### E-E-A-T Signals
|
||||
|
||||
**Experience**
|
||||
- First-hand experience demonstrated
|
||||
- Original insights/data
|
||||
- Real examples and case studies
|
||||
|
||||
**Expertise**
|
||||
- Author credentials visible
|
||||
- Accurate, detailed information
|
||||
- Properly sourced claims
|
||||
|
||||
**Authoritativeness**
|
||||
- Recognized in the space
|
||||
- Cited by others
|
||||
- Industry credentials
|
||||
|
||||
**Trustworthiness**
|
||||
- Accurate information
|
||||
- Transparent about business
|
||||
- Contact information available
|
||||
- Privacy policy, terms
|
||||
- Secure site (HTTPS)
|
||||
|
||||
### Content Depth
|
||||
|
||||
- Comprehensive coverage of topic
|
||||
- Answers follow-up questions
|
||||
- Better than top-ranking competitors
|
||||
- Updated and current
|
||||
|
||||
### User Engagement Signals
|
||||
|
||||
- Time on page
|
||||
- Bounce rate in context
|
||||
- Pages per session
|
||||
- Return visits
|
||||
|
||||
---
|
||||
|
||||
## Common Issues by Site Type
|
||||
|
||||
### SaaS/Product Sites
|
||||
- Product pages lack content depth
|
||||
- Blog not integrated with product pages
|
||||
- Missing comparison/alternative pages
|
||||
- Feature pages thin on content
|
||||
- No glossary/educational content
|
||||
|
||||
### E-commerce
|
||||
- Thin category pages
|
||||
- Duplicate product descriptions
|
||||
- Missing product schema
|
||||
- Faceted navigation creating duplicates
|
||||
- Out-of-stock pages mishandled
|
||||
|
||||
### Content/Blog Sites
|
||||
- Outdated content not refreshed
|
||||
- Keyword cannibalization
|
||||
- No topical clustering
|
||||
- Poor internal linking
|
||||
- Missing author pages
|
||||
|
||||
### Local Business
|
||||
- Inconsistent NAP
|
||||
- Missing local schema
|
||||
- No Google Business Profile optimization
|
||||
- Missing location pages
|
||||
- No local content
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Audit Report Structure
|
||||
|
||||
**Executive Summary**
|
||||
- Overall health assessment
|
||||
- Top 3-5 priority issues
|
||||
- Quick wins identified
|
||||
|
||||
**Technical SEO Findings**
|
||||
For each issue:
|
||||
- **Issue**: What's wrong
|
||||
- **Impact**: SEO impact (High/Medium/Low)
|
||||
- **Evidence**: How you found it
|
||||
- **Fix**: Specific recommendation
|
||||
- **Priority**: 1-5 or High/Medium/Low
|
||||
|
||||
**On-Page SEO Findings**
|
||||
Same format as above
|
||||
|
||||
**Content Findings**
|
||||
Same format as above
|
||||
|
||||
**Prioritized Action Plan**
|
||||
1. Critical fixes (blocking indexation/ranking)
|
||||
2. High-impact improvements
|
||||
3. Quick wins (easy, immediate benefit)
|
||||
4. Long-term recommendations
|
||||
|
||||
---
|
||||
|
||||
## Tools Referenced
|
||||
|
||||
**Free Tools**
|
||||
- Google Search Console (essential)
|
||||
- Google PageSpeed Insights
|
||||
- Bing Webmaster Tools
|
||||
- Rich Results Test
|
||||
- Mobile-Friendly Test
|
||||
- Schema Validator
|
||||
|
||||
**Paid Tools** (if available)
|
||||
- Screaming Frog
|
||||
- Ahrefs / Semrush
|
||||
- Sitebulb
|
||||
- ContentKing
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What pages/keywords matter most?
|
||||
2. Do you have Search Console access?
|
||||
3. Any recent changes or migrations?
|
||||
4. Who are your top organic competitors?
|
||||
5. What's your current organic traffic baseline?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **programmatic-seo**: For building SEO pages at scale
|
||||
- **schema-markup**: For implementing structured data
|
||||
- **page-cro**: For optimizing pages for conversion (not just ranking)
|
||||
- **analytics-tracking**: For measuring SEO performance
|
||||
276
skills/signup-flow-cro.md
Normal file
276
skills/signup-flow-cro.md
Normal file
@@ -0,0 +1,276 @@
|
||||
---
|
||||
name: signup-flow-cro
|
||||
description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
|
||||
---
|
||||
|
||||
# Signup Flow CRO
|
||||
|
||||
You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.
|
||||
|
||||
## Initial Assessment
|
||||
|
||||
Before providing recommendations, understand:
|
||||
|
||||
1. **Flow Type**
|
||||
- Free trial signup
|
||||
- Freemium account creation
|
||||
- Paid account creation
|
||||
- Waitlist/early access signup
|
||||
- B2B vs B2C
|
||||
|
||||
2. **Current State**
|
||||
- How many steps/screens?
|
||||
- What fields are required?
|
||||
- What's the current completion rate?
|
||||
- Where do users drop off?
|
||||
|
||||
3. **Business Constraints**
|
||||
- What data is genuinely needed at signup?
|
||||
- Are there compliance requirements?
|
||||
- What happens immediately after signup?
|
||||
|
||||
---
|
||||
|
||||
## Core Principles
|
||||
|
||||
### 1. Minimize Required Fields
|
||||
Every field reduces conversion. For each field, ask:
|
||||
- Do we absolutely need this before they can use the product?
|
||||
- Can we collect this later through progressive profiling?
|
||||
- Can we infer this from other data?
|
||||
|
||||
**Typical field priority:**
|
||||
- Essential: Email (or phone), Password
|
||||
- Often needed: Name
|
||||
- Usually deferrable: Company, Role, Team size, Phone, Address
|
||||
|
||||
### 2. Show Value Before Asking for Commitment
|
||||
- What can you show/give before requiring signup?
|
||||
- Can they experience the product before creating an account?
|
||||
- Reverse the order: value first, signup second
|
||||
|
||||
### 3. Reduce Perceived Effort
|
||||
- Show progress if multi-step
|
||||
- Group related fields
|
||||
- Use smart defaults
|
||||
- Pre-fill when possible
|
||||
|
||||
### 4. Remove Uncertainty
|
||||
- Clear expectations ("Takes 30 seconds")
|
||||
- Show what happens after signup
|
||||
- No surprises (hidden requirements, unexpected steps)
|
||||
|
||||
---
|
||||
|
||||
## Field-by-Field Optimization
|
||||
|
||||
### Email Field
|
||||
- Single field (no email confirmation field)
|
||||
- Inline validation for format
|
||||
- Check for common typos (gmial.com → gmail.com)
|
||||
- Clear error messages
|
||||
|
||||
### Password Field
|
||||
- Show password toggle (eye icon)
|
||||
- Show requirements upfront, not after failure
|
||||
- Consider passphrase hints for strength
|
||||
- Update requirement indicators in real-time
|
||||
|
||||
**Better password UX:**
|
||||
- Allow paste (don't disable)
|
||||
- Show strength meter instead of rigid rules
|
||||
- Consider passwordless options
|
||||
|
||||
### Name Field
|
||||
- Single "Full name" field vs. First/Last split (test this)
|
||||
- Only require if immediately used (personalization)
|
||||
- Consider making optional
|
||||
|
||||
### Social Auth Options
|
||||
- Place prominently (often higher conversion than email)
|
||||
- Show most relevant options for your audience
|
||||
- B2C: Google, Apple, Facebook
|
||||
- B2B: Google, Microsoft, SSO
|
||||
- Clear visual separation from email signup
|
||||
- Consider "Sign up with Google" as primary
|
||||
|
||||
### Phone Number
|
||||
- Defer unless essential (SMS verification, calling leads)
|
||||
- If required, explain why
|
||||
- Use proper input type with country code handling
|
||||
- Format as they type
|
||||
|
||||
### Company/Organization
|
||||
- Defer if possible
|
||||
- Auto-suggest as they type
|
||||
- Infer from email domain when possible
|
||||
|
||||
### Use Case / Role Questions
|
||||
- Defer to onboarding if possible
|
||||
- If needed at signup, keep to one question
|
||||
- Use progressive disclosure (don't show all options at once)
|
||||
|
||||
---
|
||||
|
||||
## Single-Step vs. Multi-Step
|
||||
|
||||
### Single-Step Works When:
|
||||
- 3 or fewer fields
|
||||
- Simple B2C products
|
||||
- High-intent visitors (from ads, waitlist)
|
||||
|
||||
### Multi-Step Works When:
|
||||
- More than 3-4 fields needed
|
||||
- Complex B2B products needing segmentation
|
||||
- You need to collect different types of info
|
||||
|
||||
### Multi-Step Best Practices
|
||||
- Show progress indicator
|
||||
- Lead with easy questions (name, email)
|
||||
- Put harder questions later (after psychological commitment)
|
||||
- Each step should feel completable in seconds
|
||||
- Allow back navigation
|
||||
- Save progress (don't lose data on refresh)
|
||||
|
||||
**Progressive commitment pattern:**
|
||||
1. Email only (lowest barrier)
|
||||
2. Password + name
|
||||
3. Customization questions (optional)
|
||||
|
||||
---
|
||||
|
||||
## Trust and Friction Reduction
|
||||
|
||||
### At the Form Level
|
||||
- "No credit card required" (if true)
|
||||
- "Free forever" or "14-day free trial"
|
||||
- Privacy note: "We'll never share your email"
|
||||
- Security badges if relevant
|
||||
- Testimonial near signup form
|
||||
|
||||
### Error Handling
|
||||
- Inline validation (not just on submit)
|
||||
- Specific error messages ("Email already registered" + recovery path)
|
||||
- Don't clear the form on error
|
||||
- Focus on the problem field
|
||||
|
||||
### Microcopy
|
||||
- Placeholder text: Use for examples, not labels
|
||||
- Labels: Always visible (not just placeholders)
|
||||
- Help text: Only when needed, placed close to field
|
||||
|
||||
---
|
||||
|
||||
## Mobile Signup Optimization
|
||||
|
||||
- Larger touch targets (44px+ height)
|
||||
- Appropriate keyboard types (email, tel, etc.)
|
||||
- Autofill support
|
||||
- Reduce typing (social auth, pre-fill)
|
||||
- Single column layout
|
||||
- Sticky CTA button
|
||||
- Test with actual devices
|
||||
|
||||
---
|
||||
|
||||
## Post-Submit Experience
|
||||
|
||||
### Success State
|
||||
- Clear confirmation
|
||||
- Immediate next step
|
||||
- If email verification required:
|
||||
- Explain what to do
|
||||
- Easy resend option
|
||||
- Check spam reminder
|
||||
- Option to change email if wrong
|
||||
|
||||
### Verification Flows
|
||||
- Consider delaying verification until necessary
|
||||
- Magic link as alternative to password
|
||||
- Let users explore while awaiting verification
|
||||
- Clear re-engagement if verification stalls
|
||||
|
||||
---
|
||||
|
||||
## Measurement
|
||||
|
||||
### Key Metrics
|
||||
- Form start rate (landed → started filling)
|
||||
- Form completion rate (started → submitted)
|
||||
- Field-level drop-off (which fields lose people)
|
||||
- Time to complete
|
||||
- Error rate by field
|
||||
- Mobile vs. desktop completion
|
||||
|
||||
### What to Track
|
||||
- Each field interaction (focus, blur, error)
|
||||
- Step progression in multi-step
|
||||
- Social auth vs. email signup ratio
|
||||
- Time between steps
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Audit Findings
|
||||
For each issue found:
|
||||
- **Issue**: What's wrong
|
||||
- **Impact**: Why it matters (with estimated impact if possible)
|
||||
- **Fix**: Specific recommendation
|
||||
- **Priority**: High/Medium/Low
|
||||
|
||||
### Recommended Changes
|
||||
Organized by:
|
||||
1. Quick wins (same-day fixes)
|
||||
2. High-impact changes (week-level effort)
|
||||
3. Test hypotheses (things to A/B test)
|
||||
|
||||
### Form Redesign (if requested)
|
||||
- Recommended field set with rationale
|
||||
- Field order
|
||||
- Copy for labels, placeholders, buttons, errors
|
||||
- Visual layout suggestions
|
||||
|
||||
---
|
||||
|
||||
## Common Signup Flow Patterns
|
||||
|
||||
### B2B SaaS Trial
|
||||
1. Email + Password (or Google auth)
|
||||
2. Name + Company (optional: role)
|
||||
3. → Onboarding flow
|
||||
|
||||
### B2C App
|
||||
1. Google/Apple auth OR Email
|
||||
2. → Product experience
|
||||
3. Profile completion later
|
||||
|
||||
### Waitlist/Early Access
|
||||
1. Email only
|
||||
2. Optional: Role/use case question
|
||||
3. → Waitlist confirmation
|
||||
|
||||
### E-commerce Account
|
||||
1. Guest checkout as default
|
||||
2. Account creation optional post-purchase
|
||||
3. OR Social auth with single click
|
||||
|
||||
---
|
||||
|
||||
## Questions to Ask
|
||||
|
||||
If you need more context:
|
||||
1. What's your current signup completion rate?
|
||||
2. Do you have field-level analytics on drop-off?
|
||||
3. What data is absolutely required before they can use the product?
|
||||
4. Are there compliance or verification requirements?
|
||||
5. What happens immediately after signup?
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **onboarding-cro**: For optimizing what happens after signup
|
||||
- **form-cro**: For non-signup forms (lead capture, contact)
|
||||
- **page-cro**: For the landing page leading to signup
|
||||
- **ab-test-setup**: For testing signup flow changes
|
||||
Reference in New Issue
Block a user