This commit is contained in:
8
seo-audit/.skillshare-meta.json
Normal file
8
seo-audit/.skillshare-meta.json
Normal file
@@ -0,0 +1,8 @@
|
||||
{
|
||||
"source": "github.com/coreyhaines31/marketingskills/tree/main/skills/seo-audit",
|
||||
"type": "github-subdir",
|
||||
"installed_at": "2026-01-30T02:28:22.991976577Z",
|
||||
"repo_url": "https://github.com/coreyhaines31/marketingskills.git",
|
||||
"subdir": "skills/seo-audit",
|
||||
"version": "a04cb61"
|
||||
}
|
||||
394
seo-audit/SKILL.md
Normal file
394
seo-audit/SKILL.md
Normal file
@@ -0,0 +1,394 @@
|
||||
---
|
||||
name: seo-audit
|
||||
version: 1.0.0
|
||||
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
|
||||
|
||||
**Check for product marketing context first:**
|
||||
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
|
||||
|
||||
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
|
||||
|
||||
---
|
||||
|
||||
## References
|
||||
|
||||
- [AI Writing Detection](references/ai-writing-detection.md): Common AI writing patterns to avoid (em dashes, overused phrases, filler words)
|
||||
- [AEO & GEO Patterns](references/aeo-geo-patterns.md): Content patterns optimized for answer engines and AI citation
|
||||
|
||||
---
|
||||
|
||||
## 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
|
||||
|
||||
---
|
||||
|
||||
## Task-Specific Questions
|
||||
|
||||
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
|
||||
279
seo-audit/references/aeo-geo-patterns.md
Normal file
279
seo-audit/references/aeo-geo-patterns.md
Normal file
@@ -0,0 +1,279 @@
|
||||
# AEO and GEO Content Patterns
|
||||
|
||||
Reusable content block patterns optimized for answer engines and AI citation.
|
||||
|
||||
---
|
||||
|
||||
## Answer Engine Optimization (AEO) Patterns
|
||||
|
||||
These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.
|
||||
|
||||
### Definition Block
|
||||
|
||||
Use for "What is [X]?" queries.
|
||||
|
||||
```markdown
|
||||
## What is [Term]?
|
||||
|
||||
[Term] is [concise 1-sentence definition]. [Expanded 1-2 sentence explanation with key characteristics]. [Brief context on why it matters or how it's used].
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
## What is Answer Engine Optimization?
|
||||
|
||||
Answer Engine Optimization (AEO) is the practice of structuring content so AI-powered systems can easily extract and present it as direct answers to user queries. Unlike traditional SEO that focuses on ranking in search results, AEO optimizes for featured snippets, AI Overviews, and voice assistant responses. This approach has become essential as over 60% of Google searches now end without a click.
|
||||
```
|
||||
|
||||
### Step-by-Step Block
|
||||
|
||||
Use for "How to [X]" queries. Optimal for list snippets.
|
||||
|
||||
```markdown
|
||||
## How to [Action/Goal]
|
||||
|
||||
[1-sentence overview of the process]
|
||||
|
||||
1. **[Step Name]**: [Clear action description in 1-2 sentences]
|
||||
2. **[Step Name]**: [Clear action description in 1-2 sentences]
|
||||
3. **[Step Name]**: [Clear action description in 1-2 sentences]
|
||||
4. **[Step Name]**: [Clear action description in 1-2 sentences]
|
||||
5. **[Step Name]**: [Clear action description in 1-2 sentences]
|
||||
|
||||
[Optional: Brief note on expected outcome or time estimate]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
## How to Optimize Content for Featured Snippets
|
||||
|
||||
Earning featured snippets requires strategic formatting and direct answers to search queries.
|
||||
|
||||
1. **Identify snippet opportunities**: Use tools like Semrush or Ahrefs to find keywords where competitors have snippets you could capture.
|
||||
2. **Match the snippet format**: Analyze whether the current snippet is a paragraph, list, or table, and format your content accordingly.
|
||||
3. **Answer the question directly**: Provide a clear, concise answer (40-60 words for paragraph snippets) immediately after the question heading.
|
||||
4. **Add supporting context**: Expand on your answer with examples, data, and expert insights in the following paragraphs.
|
||||
5. **Use proper heading structure**: Place your target question as an H2 or H3, with the answer immediately following.
|
||||
|
||||
Most featured snippets appear within 2-4 weeks of publishing well-optimized content.
|
||||
```
|
||||
|
||||
### Comparison Table Block
|
||||
|
||||
Use for "[X] vs [Y]" queries. Optimal for table snippets.
|
||||
|
||||
```markdown
|
||||
## [Option A] vs [Option B]: [Brief Descriptor]
|
||||
|
||||
| Feature | [Option A] | [Option B] |
|
||||
|---------|------------|------------|
|
||||
| [Criteria 1] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 2] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 3] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 4] | [Value/Description] | [Value/Description] |
|
||||
| Best For | [Use case] | [Use case] |
|
||||
|
||||
**Bottom line**: [1-2 sentence recommendation based on different needs]
|
||||
```
|
||||
|
||||
### Pros and Cons Block
|
||||
|
||||
Use for evaluation queries: "Is [X] worth it?", "Should I [X]?"
|
||||
|
||||
```markdown
|
||||
## Advantages and Disadvantages of [Topic]
|
||||
|
||||
[1-sentence overview of the evaluation context]
|
||||
|
||||
### Pros
|
||||
|
||||
- **[Benefit category]**: [Specific explanation]
|
||||
- **[Benefit category]**: [Specific explanation]
|
||||
- **[Benefit category]**: [Specific explanation]
|
||||
|
||||
### Cons
|
||||
|
||||
- **[Drawback category]**: [Specific explanation]
|
||||
- **[Drawback category]**: [Specific explanation]
|
||||
- **[Drawback category]**: [Specific explanation]
|
||||
|
||||
**Verdict**: [1-2 sentence balanced conclusion with recommendation]
|
||||
```
|
||||
|
||||
### FAQ Block
|
||||
|
||||
Use for topic pages with multiple common questions. Essential for FAQ schema.
|
||||
|
||||
```markdown
|
||||
## Frequently Asked Questions
|
||||
|
||||
### [Question phrased exactly as users search]?
|
||||
|
||||
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
||||
|
||||
### [Question phrased exactly as users search]?
|
||||
|
||||
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
||||
|
||||
### [Question phrased exactly as users search]?
|
||||
|
||||
[Direct answer in first sentence]. [Supporting context in 2-3 additional sentences].
|
||||
```
|
||||
|
||||
**Tips for FAQ questions:**
|
||||
- Use natural question phrasing ("How do I..." not "How does one...")
|
||||
- Include question words: what, how, why, when, where, who, which
|
||||
- Match "People Also Ask" queries from search results
|
||||
- Keep answers between 50-100 words
|
||||
|
||||
### Listicle Block
|
||||
|
||||
Use for "Best [X]", "Top [X]", "[Number] ways to [X]" queries.
|
||||
|
||||
```markdown
|
||||
## [Number] Best [Items] for [Goal/Purpose]
|
||||
|
||||
[1-2 sentence intro establishing context and selection criteria]
|
||||
|
||||
### 1. [Item Name]
|
||||
|
||||
[Why it's included in 2-3 sentences with specific benefits]
|
||||
|
||||
### 2. [Item Name]
|
||||
|
||||
[Why it's included in 2-3 sentences with specific benefits]
|
||||
|
||||
### 3. [Item Name]
|
||||
|
||||
[Why it's included in 2-3 sentences with specific benefits]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Generative Engine Optimization (GEO) Patterns
|
||||
|
||||
These patterns optimize content for citation by AI assistants like ChatGPT, Claude, Perplexity, and Gemini.
|
||||
|
||||
### Statistic Citation Block
|
||||
|
||||
Statistics increase AI citation rates by 15-30%. Always include sources.
|
||||
|
||||
```markdown
|
||||
[Claim statement]. According to [Source/Organization], [specific statistic with number and timeframe]. [Context for why this matters].
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
Mobile optimization is no longer optional for SEO success. According to Google's 2024 Core Web Vitals report, 70% of web traffic now comes from mobile devices, and pages failing mobile usability standards see 24% higher bounce rates. This makes mobile-first indexing a critical ranking factor.
|
||||
```
|
||||
|
||||
### Expert Quote Block
|
||||
|
||||
Named expert attribution adds credibility and increases citation likelihood.
|
||||
|
||||
```markdown
|
||||
"[Direct quote from expert]," says [Expert Name], [Title/Role] at [Organization]. [1 sentence of context or interpretation].
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
"The shift from keyword-driven search to intent-driven discovery represents the most significant change in SEO since mobile-first indexing," says Rand Fishkin, Co-founder of SparkToro. This perspective highlights why content strategies must evolve beyond traditional keyword optimization.
|
||||
```
|
||||
|
||||
### Authoritative Claim Block
|
||||
|
||||
Structure claims for easy AI extraction with clear attribution.
|
||||
|
||||
```markdown
|
||||
[Topic] [verb: is/has/requires/involves] [clear, specific claim]. [Source] [confirms/reports/found] that [supporting evidence]. This [explains/means/suggests] [implication or action].
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
E-E-A-T is the cornerstone of Google's content quality evaluation. Google's Search Quality Rater Guidelines confirm that trust is the most critical factor, stating that "untrustworthy pages have low E-E-A-T no matter how experienced, expert, or authoritative they may seem." This means content creators must prioritize transparency and accuracy above all other optimization tactics.
|
||||
```
|
||||
|
||||
### Self-Contained Answer Block
|
||||
|
||||
Create quotable, standalone statements that AI can extract directly.
|
||||
|
||||
```markdown
|
||||
**[Topic/Question]**: [Complete, self-contained answer that makes sense without additional context. Include specific details, numbers, or examples in 2-3 sentences.]
|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||
**Ideal blog post length for SEO**: The optimal length for SEO blog posts is 1,500-2,500 words for competitive topics. This range allows comprehensive topic coverage while maintaining reader engagement. HubSpot research shows long-form content earns 77% more backlinks than short articles, directly impacting search rankings.
|
||||
```
|
||||
|
||||
### Evidence Sandwich Block
|
||||
|
||||
Structure claims with evidence for maximum credibility.
|
||||
|
||||
```markdown
|
||||
[Opening claim statement].
|
||||
|
||||
Evidence supporting this includes:
|
||||
- [Data point 1 with source]
|
||||
- [Data point 2 with source]
|
||||
- [Data point 3 with source]
|
||||
|
||||
[Concluding statement connecting evidence to actionable insight].
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Domain-Specific GEO Tactics
|
||||
|
||||
Different content domains benefit from different authority signals.
|
||||
|
||||
### Technology Content
|
||||
- Emphasize technical precision and correct terminology
|
||||
- Include version numbers and dates for software/tools
|
||||
- Reference official documentation
|
||||
- Add code examples where relevant
|
||||
|
||||
### Health/Medical Content
|
||||
- Cite peer-reviewed studies with publication details
|
||||
- Include expert credentials (MD, RN, etc.)
|
||||
- Note study limitations and context
|
||||
- Add "last reviewed" dates
|
||||
|
||||
### Financial Content
|
||||
- Reference regulatory bodies (SEC, FTC, etc.)
|
||||
- Include specific numbers with timeframes
|
||||
- Note that information is educational, not advice
|
||||
- Cite recognized financial institutions
|
||||
|
||||
### Legal Content
|
||||
- Cite specific laws, statutes, and regulations
|
||||
- Reference jurisdiction clearly
|
||||
- Include professional disclaimers
|
||||
- Note when professional consultation is advised
|
||||
|
||||
### Business/Marketing Content
|
||||
- Include case studies with measurable results
|
||||
- Reference industry research and reports
|
||||
- Add percentage changes and timeframes
|
||||
- Quote recognized thought leaders
|
||||
|
||||
---
|
||||
|
||||
## Voice Search Optimization
|
||||
|
||||
Voice queries are conversational and question-based. Optimize for these patterns:
|
||||
|
||||
### Question Formats for Voice
|
||||
- "What is..."
|
||||
- "How do I..."
|
||||
- "Where can I find..."
|
||||
- "Why does..."
|
||||
- "When should I..."
|
||||
- "Who is..."
|
||||
|
||||
### Voice-Optimized Answer Structure
|
||||
- Lead with direct answer (under 30 words ideal)
|
||||
- Use natural, conversational language
|
||||
- Avoid jargon unless targeting expert audience
|
||||
- Include local context where relevant
|
||||
- Structure for single spoken response
|
||||
190
seo-audit/references/ai-writing-detection.md
Normal file
190
seo-audit/references/ai-writing-detection.md
Normal file
@@ -0,0 +1,190 @@
|
||||
# AI Writing Detection
|
||||
|
||||
Words, phrases, and punctuation patterns commonly associated with AI-generated text. Avoid these to ensure writing sounds natural and human.
|
||||
|
||||
Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Walter Writes (2025), Textero (2025), Plagiarism Today (2025), Rolling Stone (2025), MDPI Blog (2025)
|
||||
|
||||
---
|
||||
|
||||
## Em Dashes: The Primary AI Tell
|
||||
|
||||
**The em dash (—) has become one of the most reliable markers of AI-generated content.**
|
||||
|
||||
Em dashes are longer than hyphens (-) and are used for emphasis, interruptions, or parenthetical information. While they have legitimate uses in writing, AI models drastically overuse them.
|
||||
|
||||
### Why Em Dashes Signal AI Writing
|
||||
- AI models were trained on edited books, academic papers, and style guides where em dashes appear frequently
|
||||
- AI uses em dashes as a shortcut for sentence variety instead of commas, colons, or parentheses
|
||||
- Most human writers rarely use em dashes because they don't exist as a standard keyboard key
|
||||
- The overuse is so consistent that it has become the unofficial signature of ChatGPT writing
|
||||
|
||||
### What To Do Instead
|
||||
| Instead of | Use |
|
||||
|------------|-----|
|
||||
| The results—which were surprising—showed... | The results, which were surprising, showed... |
|
||||
| This approach—unlike traditional methods—allows... | This approach, unlike traditional methods, allows... |
|
||||
| The study found—as expected—that... | The study found, as expected, that... |
|
||||
| Communication skills—both written and verbal—are essential | Communication skills (both written and verbal) are essential |
|
||||
|
||||
### Guidelines
|
||||
- Use commas for most parenthetical information
|
||||
- Use colons to introduce explanations or lists
|
||||
- Use parentheses for supplementary information
|
||||
- Reserve em dashes for rare, deliberate emphasis only
|
||||
- If you find yourself using more than one em dash per page, revise
|
||||
|
||||
---
|
||||
|
||||
## Overused Verbs
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| delve (into) | explore, examine, investigate, look at |
|
||||
| leverage | use, apply, draw on |
|
||||
| optimise | improve, refine, enhance |
|
||||
| utilise | use |
|
||||
| facilitate | help, enable, support |
|
||||
| foster | encourage, support, develop, nurture |
|
||||
| bolster | strengthen, support, reinforce |
|
||||
| underscore | emphasise, highlight, stress |
|
||||
| unveil | reveal, show, introduce, present |
|
||||
| navigate | manage, handle, work through |
|
||||
| streamline | simplify, make more efficient |
|
||||
| enhance | improve, strengthen |
|
||||
| endeavour | try, attempt, effort |
|
||||
| ascertain | find out, determine, establish |
|
||||
| elucidate | explain, clarify, make clear |
|
||||
|
||||
---
|
||||
|
||||
## Overused Adjectives
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| robust | strong, reliable, thorough, solid |
|
||||
| comprehensive | complete, thorough, full, detailed |
|
||||
| pivotal | key, critical, central, important |
|
||||
| crucial | important, key, essential, critical |
|
||||
| vital | important, essential, necessary |
|
||||
| transformative | significant, important, major |
|
||||
| cutting-edge | new, advanced, recent, modern |
|
||||
| groundbreaking | new, original, significant |
|
||||
| innovative | new, original, creative |
|
||||
| seamless | smooth, easy, effortless |
|
||||
| intricate | complex, detailed, complicated |
|
||||
| nuanced | subtle, complex, detailed |
|
||||
| multifaceted | complex, varied, diverse |
|
||||
| holistic | complete, whole, comprehensive |
|
||||
|
||||
---
|
||||
|
||||
## Overused Transitions and Connectors
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| furthermore | also, in addition, and |
|
||||
| moreover | also, and, besides |
|
||||
| notwithstanding | despite, even so, still |
|
||||
| that being said | however, but, still |
|
||||
| at its core | essentially, fundamentally, basically |
|
||||
| to put it simply | in short, simply put |
|
||||
| it is worth noting that | note that, importantly |
|
||||
| in the realm of | in, within, regarding |
|
||||
| in the landscape of | in, within |
|
||||
| in today's [anything] | currently, now, today |
|
||||
|
||||
---
|
||||
|
||||
## Phrases That Signal AI Writing
|
||||
|
||||
### Opening Phrases to Avoid
|
||||
- "In today's fast-paced world..."
|
||||
- "In today's digital age..."
|
||||
- "In an era of..."
|
||||
- "In the ever-evolving landscape of..."
|
||||
- "In the realm of..."
|
||||
- "It's important to note that..."
|
||||
- "Let's delve into..."
|
||||
- "Imagine a world where..."
|
||||
|
||||
### Transitional Phrases to Avoid
|
||||
- "That being said..."
|
||||
- "With that in mind..."
|
||||
- "It's worth mentioning that..."
|
||||
- "At its core..."
|
||||
- "To put it simply..."
|
||||
- "In essence..."
|
||||
- "This begs the question..."
|
||||
|
||||
### Concluding Phrases to Avoid
|
||||
- "In conclusion..."
|
||||
- "To sum up..."
|
||||
- "By [doing X], you can [achieve Y]..."
|
||||
- "In the final analysis..."
|
||||
- "All things considered..."
|
||||
- "At the end of the day..."
|
||||
|
||||
### Structural Patterns to Avoid
|
||||
- "Whether you're a [X], [Y], or [Z]..." (listing three examples after "whether")
|
||||
- "It's not just [X], it's also [Y]..."
|
||||
- "Think of [X] as [elaborate metaphor]..."
|
||||
- Starting sentences with "By" followed by a gerund: "By understanding X, you can Y..."
|
||||
|
||||
---
|
||||
|
||||
## Filler Words and Empty Intensifiers
|
||||
|
||||
These words often add nothing to meaning. Remove them or find specific alternatives:
|
||||
|
||||
- absolutely
|
||||
- actually
|
||||
- basically
|
||||
- certainly
|
||||
- clearly
|
||||
- definitely
|
||||
- essentially
|
||||
- extremely
|
||||
- fundamentally
|
||||
- incredibly
|
||||
- interestingly
|
||||
- naturally
|
||||
- obviously
|
||||
- quite
|
||||
- really
|
||||
- significantly
|
||||
- simply
|
||||
- surely
|
||||
- truly
|
||||
- ultimately
|
||||
- undoubtedly
|
||||
- very
|
||||
|
||||
---
|
||||
|
||||
## Academic-Specific AI Tells
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| shed light on | clarify, explain, reveal |
|
||||
| pave the way for | enable, allow, make possible |
|
||||
| a myriad of | many, numerous, various |
|
||||
| a plethora of | many, numerous, several |
|
||||
| paramount | very important, essential, critical |
|
||||
| pertaining to | about, regarding, concerning |
|
||||
| prior to | before |
|
||||
| subsequent to | after |
|
||||
| in light of | because of, given, considering |
|
||||
| with respect to | about, regarding, for |
|
||||
| in terms of | regarding, for, about |
|
||||
| the fact that | that (or rewrite sentence) |
|
||||
|
||||
---
|
||||
|
||||
## How to Self-Check
|
||||
|
||||
1. Read your text aloud. If phrases sound unnatural in speech, revise them
|
||||
2. Ask: "Would I say this in a conversation with a colleague?"
|
||||
3. Check for repetitive sentence structures
|
||||
4. Look for clusters of the words listed above
|
||||
5. Ensure varied sentence lengths (not all similar length)
|
||||
6. Verify each intensifier adds genuine meaning
|
||||
Reference in New Issue
Block a user