Initial commit
This commit is contained in:
730
skills/content-brief-generator/references/seo_guidelines.md
Normal file
730
skills/content-brief-generator/references/seo_guidelines.md
Normal file
@@ -0,0 +1,730 @@
|
||||
|
||||
|
||||
# SEO Guidelines for Content Briefs
|
||||
|
||||
Comprehensive SEO best practices for content writers to rank higher and drive organic traffic.
|
||||
|
||||
---
|
||||
|
||||
## SEO Fundamentals
|
||||
|
||||
### What is SEO?
|
||||
|
||||
**Search Engine Optimization (SEO)** is the practice of optimizing content to rank higher in search engine results pages (SERPs) and drive organic (unpaid) traffic.
|
||||
|
||||
**Key components:**
|
||||
- **Technical SEO:** Site structure, performance, indexing
|
||||
- **On-page SEO:** Content optimization, keywords, meta tags
|
||||
- **Off-page SEO:** Backlinks, domain authority, social signals
|
||||
|
||||
**This guide focuses on on-page SEO for content creation.**
|
||||
|
||||
---
|
||||
|
||||
## Keyword Research
|
||||
|
||||
### Finding the Right Keywords
|
||||
|
||||
**1. Start with seed keywords**
|
||||
- Your main topic or product
|
||||
- What users search for
|
||||
- Industry terminology
|
||||
|
||||
**2. Expand with keyword tools**
|
||||
- **Google Keyword Planner** (free)
|
||||
- **Ahrefs** (paid, comprehensive)
|
||||
- **SEMrush** (paid, competitive analysis)
|
||||
- **Ubersuggest** (freemium)
|
||||
- **AnswerThePublic** (question-based keywords)
|
||||
|
||||
**3. Analyze keyword metrics**
|
||||
|
||||
| Metric | What It Means | Good Target |
|
||||
|--------|---------------|-------------|
|
||||
| Search Volume | Monthly searches | 500-10K for most content |
|
||||
| Keyword Difficulty | Competition (0-100) | < 40 for newer sites |
|
||||
| CPC | Paid ad cost | Higher = more commercial |
|
||||
| SERP Features | Rich snippets, featured boxes | Opportunity to capture |
|
||||
|
||||
**4. Evaluate search intent**
|
||||
|
||||
**Types of search intent:**
|
||||
- **Informational:** "how to", "what is", "guide to"
|
||||
- **Navigational:** Brand names, specific pages
|
||||
- **Commercial:** "best", "review", "comparison"
|
||||
- **Transactional:** "buy", "price", "discount"
|
||||
|
||||
**Match content type to intent:**
|
||||
- Informational → Blog posts, guides, tutorials
|
||||
- Commercial → Reviews, comparisons, listicles
|
||||
- Transactional → Product pages, landing pages
|
||||
|
||||
---
|
||||
|
||||
## Keyword Strategy
|
||||
|
||||
### Primary Keyword
|
||||
**One main target keyword per piece of content**
|
||||
|
||||
**Characteristics:**
|
||||
- Relevant to topic
|
||||
- Moderate search volume (500-10K typically)
|
||||
- Achievable difficulty
|
||||
- Matches search intent
|
||||
|
||||
**Example:**
|
||||
For a tutorial on JWT authentication:
|
||||
- Primary: "JWT authentication tutorial" (2,400/month, KD 35)
|
||||
|
||||
### Secondary Keywords
|
||||
**2-4 related keywords that support the primary**
|
||||
|
||||
**Types:**
|
||||
- Synonyms: "JSON web token tutorial"
|
||||
- Related terms: "JWT Node.js", "secure API authentication"
|
||||
- Long-tail variations: "how to implement JWT authentication"
|
||||
|
||||
**Example:**
|
||||
- Secondary: "JSON web token Node.js", "JWT implementation guide", "API authentication tutorial"
|
||||
|
||||
### LSI Keywords (Latent Semantic Indexing)
|
||||
**Related terms that provide context**
|
||||
|
||||
**How to find:**
|
||||
- Google "related searches" at bottom of SERP
|
||||
- "People also ask" boxes
|
||||
- LSIGraph tool
|
||||
- Ahrefs "Also rank for" section
|
||||
|
||||
**Example:**
|
||||
For JWT content: "access token", "refresh token", "bearer token", "authentication flow", "authorization header"
|
||||
|
||||
---
|
||||
|
||||
## On-Page SEO Elements
|
||||
|
||||
### Title Tag (H1)
|
||||
|
||||
**Requirements:**
|
||||
- Include primary keyword
|
||||
- 50-60 characters (to avoid truncation)
|
||||
- Compelling and click-worthy
|
||||
- Front-load important words
|
||||
|
||||
**Formula:**
|
||||
`[Primary Keyword]: [Benefit/Hook] | [Brand]`
|
||||
|
||||
**Examples:**
|
||||
|
||||
❌ Bad:
|
||||
- "Authentication" (too vague)
|
||||
- "The Complete, Comprehensive, Ultimate Guide to JSON Web Token Authentication in Node.js Applications" (too long)
|
||||
|
||||
✅ Good:
|
||||
- "JWT Authentication Tutorial: Secure Your Node.js API in 10 Minutes"
|
||||
- "How to Implement JWT Authentication | Complete Node.js Guide"
|
||||
|
||||
**Best practices:**
|
||||
- Use power words: "Complete", "Ultimate", "Essential", "Proven"
|
||||
- Include numbers: "10 Minutes", "5 Steps", "2024 Guide"
|
||||
- Address user intent: "How to", "Step-by-Step", "Quick Start"
|
||||
|
||||
---
|
||||
|
||||
### Meta Description
|
||||
|
||||
**Requirements:**
|
||||
- 150-160 characters
|
||||
- Include primary keyword
|
||||
- Compelling call-to-action
|
||||
- Accurate summary
|
||||
|
||||
**Not a ranking factor but affects CTR (click-through rate)**
|
||||
|
||||
**Formula:**
|
||||
`[Problem] + [Solution] + [Benefit/CTA]`
|
||||
|
||||
**Examples:**
|
||||
|
||||
❌ Bad:
|
||||
- "Learn about JWT authentication" (boring, no value)
|
||||
- "This article covers everything you need to know about JSON Web Tokens, including how they work, how to implement them, and best practices" (too long, truncated)
|
||||
|
||||
✅ Good:
|
||||
- "Learn JWT authentication with Node.js in 10 minutes. Step-by-step tutorial with code examples. Secure your API today."
|
||||
- "Implement JWT authentication in your Node.js app. Complete guide with Express.js examples and security best practices."
|
||||
|
||||
---
|
||||
|
||||
### Headers (H2, H3, H4)
|
||||
|
||||
**Purpose:**
|
||||
- Structure content for readability
|
||||
- Signal topic relevance to search engines
|
||||
- Improve featured snippet chances
|
||||
|
||||
**Best practices:**
|
||||
|
||||
**H2 (Main sections):**
|
||||
- Include keywords naturally
|
||||
- 3-7 H2s per article typically
|
||||
- Descriptive and scannable
|
||||
|
||||
**H3 (Subsections):**
|
||||
- Support H2 topics
|
||||
- Use long-tail keywords
|
||||
- Answer specific questions
|
||||
|
||||
**Examples:**
|
||||
|
||||
✅ Good header structure:
|
||||
```
|
||||
# JWT Authentication Tutorial [H1]
|
||||
|
||||
## What Is JWT Authentication? [H2 - keyword + question]
|
||||
|
||||
## How JWT Authentication Works [H2 - keyword + process]
|
||||
### The Authentication Flow [H3]
|
||||
### Access Tokens vs Refresh Tokens [H3]
|
||||
|
||||
## Implementing JWT in Node.js [H2 - keyword + action]
|
||||
### Installing Dependencies [H3]
|
||||
### Creating JWT Tokens [H3]
|
||||
### Verifying JWT Tokens [H3]
|
||||
|
||||
## JWT Security Best Practices [H2 - keyword + value]
|
||||
```
|
||||
|
||||
**Avoid:**
|
||||
- Generic headers: "Introduction", "Conclusion"
|
||||
- Keyword stuffing: "JWT JWT JWT Authentication"
|
||||
- Skipping heading levels (H2 → H4)
|
||||
|
||||
---
|
||||
|
||||
### Content Body
|
||||
|
||||
**Keyword usage:**
|
||||
|
||||
**Primary keyword placement:**
|
||||
- [ ] First 100 words (important!)
|
||||
- [ ] In H1 (title)
|
||||
- [ ] In at least one H2
|
||||
- [ ] In URL slug
|
||||
- [ ] 3-5 times throughout content (naturally)
|
||||
- [ ] In conclusion
|
||||
|
||||
**Secondary keywords:**
|
||||
- [ ] Sprinkle naturally throughout
|
||||
- [ ] In H2s and H3s where relevant
|
||||
- [ ] In image alt text
|
||||
- [ ] In anchor text for internal links
|
||||
|
||||
**Keyword density:**
|
||||
- **Target: 0.5-2.5%** of total words
|
||||
- Don't obsess over exact percentage
|
||||
- Prioritize natural writing
|
||||
- Use synonyms and variations
|
||||
|
||||
**Example:**
|
||||
|
||||
❌ Bad (keyword stuffing):
|
||||
"JWT authentication is important. JWT authentication secures your API. Implementing JWT authentication with JWT authentication libraries makes JWT authentication easier."
|
||||
|
||||
✅ Good (natural use):
|
||||
"JWT authentication provides a secure way to handle user sessions in modern APIs. This token-based approach offers several advantages over traditional session management..."
|
||||
|
||||
---
|
||||
|
||||
### Internal Linking
|
||||
|
||||
**Why it matters:**
|
||||
- Distributes page authority
|
||||
- Helps search engines discover pages
|
||||
- Improves user engagement
|
||||
- Reduces bounce rate
|
||||
|
||||
**Best practices:**
|
||||
- **3-5 internal links** per blog post
|
||||
- Link to relevant related content
|
||||
- Use descriptive anchor text (not "click here")
|
||||
- Link to authoritative pages
|
||||
- Create content clusters
|
||||
|
||||
**Anchor text examples:**
|
||||
|
||||
❌ Bad:
|
||||
- "Click here to learn more"
|
||||
- "Read this article"
|
||||
- Full URLs as anchor text
|
||||
|
||||
✅ Good:
|
||||
- "Learn about [secure API design patterns](link)"
|
||||
- "Our [Node.js security guide](link) covers..."
|
||||
- "For more on [authentication vs authorization](link)..."
|
||||
|
||||
**Content clustering:**
|
||||
```
|
||||
Pillar Page: "Complete Guide to API Authentication"
|
||||
├─ Cluster: "JWT Authentication Tutorial"
|
||||
├─ Cluster: "OAuth 2.0 Implementation Guide"
|
||||
├─ Cluster: "API Key Best Practices"
|
||||
└─ Cluster: "Session vs Token Authentication"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### External Linking
|
||||
|
||||
**Why link externally:**
|
||||
- Provides value to readers
|
||||
- Signals trust and authority
|
||||
- May earn reciprocal links
|
||||
- Shows you're not keyword-focused
|
||||
|
||||
**Best practices:**
|
||||
- **2-3 external links** to authoritative sources
|
||||
- Link to original research/data
|
||||
- Link to tools/resources mentioned
|
||||
- Open in new tab (user preference)
|
||||
- Use `rel="nofollow"` for untrusted sources
|
||||
|
||||
**Authority sources:**
|
||||
- Official documentation
|
||||
- Government sites (.gov)
|
||||
- Educational institutions (.edu)
|
||||
- Industry research firms
|
||||
- Reputable publications
|
||||
|
||||
---
|
||||
|
||||
### Images & Alt Text
|
||||
|
||||
**SEO value:**
|
||||
- Image search traffic
|
||||
- Featured snippets with images
|
||||
- Improved user engagement
|
||||
- Accessibility (screen readers)
|
||||
|
||||
**Image optimization:**
|
||||
|
||||
**File size:**
|
||||
- Compress images (< 200KB ideal)
|
||||
- Use WebP format when possible
|
||||
- Lazy loading for below-fold images
|
||||
|
||||
**File names:**
|
||||
- Descriptive, not "IMG_1234.jpg"
|
||||
- Include keyword: "jwt-authentication-flow.png"
|
||||
- Use hyphens, not underscores
|
||||
|
||||
**Alt text:**
|
||||
- Describe image content
|
||||
- Include keyword naturally
|
||||
- 10-15 words typical
|
||||
- Don't stuff keywords
|
||||
|
||||
**Examples:**
|
||||
|
||||
❌ Bad:
|
||||
- Alt: "image" or empty
|
||||
- File: "screenshot-2024.png"
|
||||
|
||||
✅ Good:
|
||||
- Alt: "JWT authentication flow diagram showing token generation and verification"
|
||||
- File: "jwt-authentication-flow-diagram.png"
|
||||
|
||||
---
|
||||
|
||||
## URL Structure
|
||||
|
||||
**SEO-friendly URLs:**
|
||||
|
||||
**Best practices:**
|
||||
- **Include primary keyword**
|
||||
- **Short and descriptive** (3-5 words)
|
||||
- **Use hyphens**, not underscores
|
||||
- **Lowercase only**
|
||||
- **Avoid parameters** (?id=123)
|
||||
|
||||
**Examples:**
|
||||
|
||||
❌ Bad:
|
||||
- `/blog/post?id=12345`
|
||||
- `/blog/2024/01/15/new-post`
|
||||
- `/JWT_Authentication_Tutorial_Complete_Guide`
|
||||
|
||||
✅ Good:
|
||||
- `/jwt-authentication-tutorial`
|
||||
- `/blog/jwt-authentication-nodejs`
|
||||
- `/guides/api-authentication`
|
||||
|
||||
---
|
||||
|
||||
## Content Length & Quality
|
||||
|
||||
### Optimal Length
|
||||
|
||||
**General guidelines:**
|
||||
|
||||
| Content Type | Optimal Length | Rationale |
|
||||
|--------------|----------------|-----------|
|
||||
| Blog post | 1,500-2,500 words | Comprehensive coverage |
|
||||
| Tutorial | 2,000-3,000 words | Detailed instructions |
|
||||
| Listicle | 1,000-2,000 words | Quick, scannable |
|
||||
| Landing page | 500-1,000 words | Concise, conversion-focused |
|
||||
| Product page | 300-500 words | Key info only |
|
||||
|
||||
**But length isn't everything:**
|
||||
- Match top-ranking content length
|
||||
- Cover topic comprehensively
|
||||
- Don't add fluff to hit word count
|
||||
- Value > length
|
||||
|
||||
### Content Quality Signals
|
||||
|
||||
**E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness):**
|
||||
|
||||
**Experience:**
|
||||
- First-hand knowledge
|
||||
- Personal insights
|
||||
- Real-world examples
|
||||
|
||||
**Expertise:**
|
||||
- Author credentials
|
||||
- Technical accuracy
|
||||
- Depth of coverage
|
||||
|
||||
**Authoritativeness:**
|
||||
- Backlinks from reputable sites
|
||||
- Author byline
|
||||
- Citations and references
|
||||
|
||||
**Trustworthiness:**
|
||||
- Accurate information
|
||||
- Proper citations
|
||||
- Clear sources
|
||||
- Privacy policy, contact info
|
||||
|
||||
---
|
||||
|
||||
## Technical SEO Checklist
|
||||
|
||||
### Page Speed
|
||||
- [ ] Page loads in < 3 seconds
|
||||
- [ ] Images optimized and compressed
|
||||
- [ ] Lazy loading implemented
|
||||
- [ ] Minified CSS/JS
|
||||
- [ ] Browser caching enabled
|
||||
|
||||
### Mobile-Friendly
|
||||
- [ ] Responsive design
|
||||
- [ ] Text readable without zooming
|
||||
- [ ] Touch targets 48x48px+
|
||||
- [ ] No horizontal scrolling
|
||||
|
||||
### Core Web Vitals
|
||||
- [ ] LCP (Largest Contentful Paint) < 2.5s
|
||||
- [ ] FID (First Input Delay) < 100ms
|
||||
- [ ] CLS (Cumulative Layout Shift) < 0.1
|
||||
|
||||
### Indexing
|
||||
- [ ] Pages not blocked by robots.txt
|
||||
- [ ] XML sitemap submitted
|
||||
- [ ] Canonical tags set correctly
|
||||
- [ ] No duplicate content
|
||||
|
||||
---
|
||||
|
||||
## Featured Snippets & Rich Results
|
||||
|
||||
### What Are Featured Snippets?
|
||||
|
||||
**"Position 0" results** that appear above organic listings
|
||||
|
||||
**Types:**
|
||||
- **Paragraph** (definitions, answers)
|
||||
- **List** (steps, rankings)
|
||||
- **Table** (comparisons, data)
|
||||
- **Video** (tutorials)
|
||||
|
||||
### How to Win Snippets
|
||||
|
||||
**1. Target question keywords**
|
||||
- "What is", "How to", "Why does"
|
||||
- "Best", "Top", "Checklist"
|
||||
|
||||
**2. Structure for snippets**
|
||||
|
||||
**Paragraph snippets:**
|
||||
- Answer question in 40-60 words
|
||||
- Place answer directly after H2
|
||||
- Define terms clearly
|
||||
|
||||
**List snippets:**
|
||||
- Use numbered lists (for steps)
|
||||
- Use bullet lists (for items)
|
||||
- 5-8 items optimal
|
||||
|
||||
**Table snippets:**
|
||||
- Use HTML tables
|
||||
- Clear headers
|
||||
- Comparison data
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
## What Is JWT Authentication?
|
||||
|
||||
JWT (JSON Web Token) authentication is a stateless authentication method that uses cryptographically signed tokens to verify user identity. Instead of storing session data on the server, JWT embeds user information in a secure token that clients include with each request.
|
||||
|
||||
### How JWT Authentication Works:
|
||||
|
||||
1. User logs in with credentials
|
||||
2. Server validates and creates JWT
|
||||
3. Token sent to client
|
||||
4. Client includes token in requests
|
||||
5. Server verifies token signature
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Schema Markup
|
||||
|
||||
**Structured data** that helps search engines understand content
|
||||
|
||||
**Common types for content:**
|
||||
- **Article:** Blog posts, news
|
||||
- **HowTo:** Step-by-step guides
|
||||
- **FAQPage:** FAQ sections
|
||||
- **VideoObject:** Embedded videos
|
||||
- **BreadcrumbList:** Navigation
|
||||
|
||||
**Example (JSON-LD):**
|
||||
```json
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Article",
|
||||
"headline": "JWT Authentication Tutorial",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "John Developer"
|
||||
},
|
||||
"datePublished": "2024-01-15",
|
||||
"image": "https://example.com/jwt-tutorial.jpg"
|
||||
}
|
||||
```
|
||||
|
||||
**Tools:**
|
||||
- [Google Rich Results Test](https://search.google.com/test/rich-results)
|
||||
- [Schema Markup Generator](https://technicalseo.com/tools/schema-markup-generator/)
|
||||
|
||||
---
|
||||
|
||||
## SEO Content Writing Process
|
||||
|
||||
### 1. Keyword Research (1-2 hours)
|
||||
- [ ] Identify primary keyword
|
||||
- [ ] Find secondary keywords
|
||||
- [ ] Analyze top 10 results
|
||||
- [ ] Determine search intent
|
||||
- [ ] Note target word count
|
||||
|
||||
### 2. Content Outline (30 min)
|
||||
- [ ] Create H2/H3 structure
|
||||
- [ ] Include keywords in headers
|
||||
- [ ] Plan internal links
|
||||
- [ ] Identify research needs
|
||||
|
||||
### 3. Write First Draft (2-4 hours)
|
||||
- [ ] Write naturally first
|
||||
- [ ] Focus on value
|
||||
- [ ] Answer user questions
|
||||
- [ ] Include examples
|
||||
|
||||
### 4. SEO Optimization (30-60 min)
|
||||
- [ ] Primary keyword in first 100 words
|
||||
- [ ] Keywords in headers (natural)
|
||||
- [ ] Add internal links (3-5)
|
||||
- [ ] Add external links (2-3)
|
||||
- [ ] Optimize images and alt text
|
||||
- [ ] Write meta description
|
||||
- [ ] Check keyword density
|
||||
|
||||
### 5. Quality Check (30 min)
|
||||
- [ ] Fact-check all claims
|
||||
- [ ] Verify links work
|
||||
- [ ] Read aloud for flow
|
||||
- [ ] Check readability score
|
||||
- [ ] Proofread carefully
|
||||
|
||||
---
|
||||
|
||||
## SEO Tools
|
||||
|
||||
### Free Tools
|
||||
- **Google Search Console** - Monitor performance
|
||||
- **Google Analytics** - Track traffic
|
||||
- **Google Keyword Planner** - Keyword research
|
||||
- **Ubersuggest** - Limited keyword data
|
||||
- **AnswerThePublic** - Question keywords
|
||||
- **Yoast SEO (WordPress)** - On-page optimization
|
||||
|
||||
### Paid Tools
|
||||
- **Ahrefs** ($99-$999/mo) - All-in-one SEO
|
||||
- **SEMrush** ($119-$449/mo) - Comprehensive suite
|
||||
- **Surfer SEO** ($49-$199/mo) - Content optimization
|
||||
- **Clearscope** ($170+/mo) - Content intelligence
|
||||
- **MarketMuse** ($149-$600/mo) - Content planning
|
||||
|
||||
### Free Browser Extensions
|
||||
- **Keywords Everywhere** - Search volume data
|
||||
- **MozBar** - Domain authority checker
|
||||
- **SEO Meta in 1 Click** - View meta tags
|
||||
- **Detailed** - View structured data
|
||||
|
||||
---
|
||||
|
||||
## Common SEO Mistakes
|
||||
|
||||
### ❌ Avoid These
|
||||
|
||||
**1. Keyword stuffing**
|
||||
- Overusing keywords unnaturally
|
||||
- Hurts readability and rankings
|
||||
|
||||
**2. Thin content**
|
||||
- < 500 words without depth
|
||||
- Doesn't fully answer question
|
||||
|
||||
**3. Duplicate content**
|
||||
- Copying content across pages
|
||||
- Plagiarizing from other sites
|
||||
|
||||
**4. Ignoring mobile**
|
||||
- Non-responsive design
|
||||
- 60%+ of traffic is mobile
|
||||
|
||||
**5. Slow page speed**
|
||||
- Large uncompressed images
|
||||
- Too many scripts
|
||||
- Poor hosting
|
||||
|
||||
**6. No internal linking**
|
||||
- Isolated pages
|
||||
- Lost link equity
|
||||
|
||||
**7. Bad user experience**
|
||||
- Intrusive popups
|
||||
- Auto-playing videos
|
||||
- Difficult navigation
|
||||
|
||||
**8. Ignoring search intent**
|
||||
- Wrong content type
|
||||
- Doesn't answer query
|
||||
|
||||
---
|
||||
|
||||
## Measuring SEO Success
|
||||
|
||||
### Key Metrics
|
||||
|
||||
**Rankings:**
|
||||
- Track target keyword positions
|
||||
- Monitor ranking changes
|
||||
- Tool: Google Search Console, Ahrefs
|
||||
|
||||
**Organic Traffic:**
|
||||
- Sessions from organic search
|
||||
- Growth over time
|
||||
- Tool: Google Analytics
|
||||
|
||||
**Click-Through Rate (CTR):**
|
||||
- % of impressions that click
|
||||
- Improve with better titles/descriptions
|
||||
- Tool: Google Search Console
|
||||
|
||||
**Engagement:**
|
||||
- Time on page (3+ minutes good)
|
||||
- Pages per session
|
||||
- Bounce rate (< 60% good)
|
||||
|
||||
**Conversions:**
|
||||
- Goal completions from organic
|
||||
- Newsletter signups
|
||||
- Lead forms submitted
|
||||
|
||||
### Timeline for Results
|
||||
|
||||
**Realistic expectations:**
|
||||
- **Week 1-4:** Indexed, minimal movement
|
||||
- **Month 2-3:** Start ranking for long-tail
|
||||
- **Month 4-6:** Ranking for target keywords
|
||||
- **Month 6-12:** Established authority
|
||||
|
||||
**Factors affecting timeline:**
|
||||
- Domain authority
|
||||
- Competition
|
||||
- Content quality
|
||||
- Backlinks
|
||||
|
||||
---
|
||||
|
||||
## SEO Checklist for Writers
|
||||
|
||||
### Before Writing
|
||||
- [ ] Keyword research complete
|
||||
- [ ] Search intent identified
|
||||
- [ ] Top 10 results analyzed
|
||||
- [ ] Target word count determined
|
||||
|
||||
### During Writing
|
||||
- [ ] Primary keyword in first 100 words
|
||||
- [ ] Keywords in H1, H2s naturally
|
||||
- [ ] Internal links planned (3-5)
|
||||
- [ ] External links identified (2-3)
|
||||
- [ ] Images with descriptive file names
|
||||
|
||||
### After Writing
|
||||
- [ ] Meta description written (150-160 chars)
|
||||
- [ ] All images have alt text
|
||||
- [ ] URL slug optimized
|
||||
- [ ] Schema markup added (if applicable)
|
||||
- [ ] Links tested
|
||||
- [ ] Readability check (Flesch score 60+)
|
||||
- [ ] Mobile preview
|
||||
- [ ] Page speed check
|
||||
|
||||
---
|
||||
|
||||
## Quick Reference
|
||||
|
||||
### Optimal Keyword Density
|
||||
- Primary: 0.5-2.5% of content
|
||||
- Don't force it, write naturally
|
||||
|
||||
### Word Count Targets
|
||||
- Blog: 1,500-2,500 words
|
||||
- Tutorial: 2,000-3,000 words
|
||||
- Landering page: 500-1,000 words
|
||||
|
||||
### Link Targets
|
||||
- Internal: 3-5 per post
|
||||
- External: 2-3 to authority sites
|
||||
|
||||
### Title Length
|
||||
- 50-60 characters
|
||||
- Include primary keyword
|
||||
|
||||
### Meta Description
|
||||
- 150-160 characters
|
||||
- Include keyword + CTA
|
||||
|
||||
### Image Optimization
|
||||
- < 200KB file size
|
||||
- Descriptive file name
|
||||
- Alt text 10-15 words
|
||||
|
||||
---
|
||||
|
||||
**Remember:** SEO is important, but user experience comes first. Write for humans, optimize for search engines.
|
||||
Reference in New Issue
Block a user