SEO SaaS Blog Guidelines

SEO SaaS Blog Guidelines

This document defines the content strategy, tone, and technical requirements for all SEO SaaS blog posts.

Note: This file should be excluded from blog rendering (CLAUDE.md in all caps won't be processed by most static site generators).

---

Brand Positioning

SEO SaaS is a Google Search Console analytics platform targeting SMB SaaS companies and SEO professionals.

Tagline: TBD

Key differentiators:

• Deep GSC data analysis and interpretation
• Data-driven SEO decision making
• Educational content focused on understanding what the data means
• Practical, actionable insights over vanity metrics

We are NOT competing for:

• Enterprise SEO platforms (Semrush, Ahrefs, Moz)
• Rank tracking tools (SERPWatcher, AccuRanker)
• All-in-one marketing suites

We ARE positioning as:

• The expert resource for GSC analysis
• The bridge between data and action
• The go-to guide for diagnosing SEO problems

---

Content Strategy

Pillar Pages (5)

These are comprehensive hub pages that link out to related content:

Content Categories

1. GSC Core Features (15 posts) - Setup, filters, metrics, reports
2. GSC Reports Deep Dives (6 posts) - Queries, Pages, Devices, Countries
3. Technical GSC Reports (5 posts) - Index, Crawl, Core Web Vitals
4. Diagnosis & Troubleshooting (13 posts) - Traffic drops, ranking issues
5. Strategy & Optimization (11 posts) - Prioritization, content gaps, competitive analysis
6. Planning & Fundamentals (5 posts) - SEO basics, keyword research, on-page

SEO Strategy

High-value keywords we target:

• "google search console" + [feature] (educational, high volume)
• "traffic drop diagnosis" (intent signal)
• "[problem] gsc" (long-tail, high intent)
• "how to read gsc" (beginner-focused)
• "data-driven seo" (our unique positioning)

Content gaps we exploit:

• GSC data interpretation (no competitor owns this deeply)
• Diagnosis frameworks beyond checklists
• What the data actually means, not just what it shows
• Evidence-based decision making over guesswork

---

Tone and Voice

Do

• Be direct and practical - SEO professionals value clarity over fluff
• Use second person ("you") to speak directly to readers
• Include real GSC screenshots and examples in posts
• Be honest about limitations - acknowledge what GSC can't tell you
• Teach interpretation over mechanics - "what it means" not just "what it is"
• Use concrete scenarios over abstract theory
• Show real data patterns with specific numbers

Don't

• Use marketing fluff or buzzwords ("game-changing", "revolutionary")
• Oversell GSC as the only tool needed
• Oversimplify to the point of being unhelpful
• Use excessive exclamation points or hype language
• Add unnecessary emojis
• Pad content to hit word counts
• Mention word count to readers - Users don't care if a post is 1,500 or 3,500 words. They only care about value. Never write "This comprehensive 2,500-word guide..." or similar
• Promote black-hat or spammy tactics

Product Mentions

• 0-1 natural mentions per post - often zero
• Best placements: conclusion, feature comparison sections
• Frame as "here's how our tool helps with this" not "buy our product"
• Always provide value even if reader doesn't use our product
• Educational first, promotional never

Writing Tight, Value-Packed Prose

SEO SaaS blog content prioritizes density over length. Every sentence must earn its place. Target a 15-20% reduction in typical blog post word count through ruthless elimination of filler while preserving all analytical depth.

Cut This (Filler That Adds No Value):

Transition padding:

• "Before we dive into the Performance Report, it's important to understand the context..."
• "As your website grows, you'll start to see patterns emerge in your GSC data..."
• "The question isn't whether you should use GSC—it's how to interpret what it shows you..."
• Replace with: Direct statements that skip the obvious setup.

Redundant explanations:

• "The Performance Report shows your search performance data. It's where you'll find clicks, impressions, CTR, and position metrics for your site." (both sentences say the same thing)
• Replace with: "The Performance Report shows clicks, impressions, CTR, and average position—your core search metrics."

Filler phrases:

• "This is important for", "Fortunately", "one thing... entirely different"
• "Here is", "It is", "The fact that"
• "At their core", "In essence", "Basically"
• Future-tense filler: "you will", "you can", "you'll"
• "The good news is", "This sounds straightforward, but"
• "It's worth noting that", "Keep in mind that"
• Replace with: Direct, active voice.

Section intros that restate the header:

• Header: "## Traffic Drop Diagnosis Checklist"
• Content: "When traffic drops, you need a systematic approach to identify the root cause."
• Replace with: Delete the intro, jump straight to the checklist.

Verbose lead-ins before content:

• "Before analyzing your data, consider what questions you're trying to answer:" (obvious)
• "These reports provide deep insights into your search performance, helping you make better decisions." (marketing fluff)
• Replace with: Just show the reports.

Marketing adjectives that weaken meaning:

• "essential", "critical", "comprehensive", "powerful", "significantly impacts"
• Replace with: Concrete specifics. Instead of "essential metric", say "tracks 16 months of search data."

Explanatory sentences that don't add value:

• "Understanding the difference between impressions and clicks is fundamental to analyzing your search performance." (obvious from section title)
• "This is perfect for identifying which pages are underperforming and need optimization." (self-evident)
• Replace with: Delete and move to next sentence.

SEO content clichés:

• "In today's competitive digital landscape..."
• "SEO is constantly evolving..."
• "Content is king..."
• "The only constant in SEO is change..."
• Replace with: Specific, actionable information.

Keep This (Value-Dense Content):

✓ All GSC screenshots and data examples ✓ Concrete scenarios and diagnostic steps ✓ Specific numbers: "16-month retention", "1,000 row limit", "72-hour data lag" ✓ Real patterns: "5-15 position = quick win territory" ✓ Tables, frameworks, and checklists ✓ Filter combinations and analysis techniques ✓ Why something matters (with concrete consequences) ✓ Real diagnosis examples with outcomes

Examples of Good Edits:

Before (98 words):

Google Search Console is an essential tool for anyone serious about SEO. It provides invaluable insights into how Google sees your website, what queries are driving traffic, and which pages are performing well or poorly. Understanding how to properly interpret this data is fundamental to making smart SEO decisions that actually move the needle. This comprehensive guide will walk you through everything you need to know about reading and analyzing your GSC performance data.

After (42 words):

Google Search Console shows how Google sees your site: which queries drive traffic, which pages perform, and where opportunities hide. This guide covers reading and analyzing your GSC performance data to make decisions that improve rankings.

Before (85 words):

Before you can start analyzing your GSC data, you need to understand the four core metrics that the Performance Report tracks. Each metric tells you something different about your search performance, and understanding what each one means is critical to interpreting the patterns you'll see in your data.

After (28 words):

The Performance Report tracks four metrics:

• Clicks: Users who clicked your result
• Impressions: Times your URL appeared in search
• CTR: Click-through rate
• Position: Average ranking

Before (92 words):

Traffic drops can be alarming, especially when they happen suddenly and without an obvious cause. The good news is that most traffic drops follow recognizable patterns, and with the right diagnostic approach, you can identify the root cause and build a recovery plan. This checklist will walk you through a systematic process for diagnosing traffic drops using GSC data.

After (35 words):

Most traffic drops follow recognizable patterns. Use this checklist to diagnose the root cause with GSC data:

1. Check for seasonality (compare year-over-year)
2. Identify algorithm updates
3. ...

Pillar Page Specifics:

Pillar pages are navigation hubs. They should be even tighter than regular posts:

• Remove "What You Will Learn" sections (redundant with TOC)
• Delete intro sentences explaining what the section title already conveys
• Convert verbose post descriptions into single-line summaries with key topics
• Replace "Learn to..." intros with just the link: [How to Read GSC Performance Report](./link)

Self-Editing Checklist:

Before shipping, scan for:

• Any sentence starting with "This is", "Here is", "At their core", "In essence" → cut or rewrite
• Any paragraph intro that restates the header → delete
• Any explanation of something obvious from context → cut
• Filler phrases: "it's important to", "keep in mind that", "it's worth noting" → remove
• Marketing adjectives without specifics → replace with concrete numbers
• Sentences longer than 25 words → consider breaking into two or cutting
• Any "you will", "you can", "you'll" future tense filler → use present tense or imperative
• SEO content clichés → replace with specific insights

---

Post Structure

Frontmatter (Required)

---
title: "Post Title Here"
description: "SEO-friendly description, 150-160 characters"
author: "SEO SaaS Team"
publishedAt: "2026-01-20"
category: "gsc-core" | "gsc-reports" | "diagnosis" | "strategy" | "fundamentals"
tags:
  - google-search-console
  - relevant-tag
keywords:
  - target keyword
  - secondary keyword
---

Body Structure

1. Introduction (2-3 paragraphs)

   • Hook with a problem or data pattern readers will recognize
   • State what they'll learn
   • No "In this post, we'll cover..." - just get to it

2. Main Content (organized with H2/H3 headers)

   • Each major section: H2
   • Subsections: H3
   • Include GSC screenshots where relevant
   • Use tables for comparisons and frameworks
   • Use bullet lists for scannable content
   • Show filter combinations and analysis steps

3. Conclusion (1-2 paragraphs)

   • Summarize key takeaways
   • Link to next logical step in learning journey

Screenshots and Examples

• Use real GSC screenshots (anonymize client data)
• Show filter combinations, not just default views
• Include date range selections to demonstrate time-based analysis
• Highlight specific data points being discussed
• Show before/after comparisons when relevant

---

Internal Linking

Inline Links

Add contextual inline links where they provide value:

Good:

Before diagnosing the drop, check if it's seasonal by comparing year-over-year data.

Bad:

Learn more about GSC and traffic drops and filters.

Link Anchor Text

Use descriptive anchor text, not "click here" or "learn more":

Pillar Page Links

Every post should link to its relevant pillar page at least once:

• GSC feature posts → Pillar 1 (GSC Mastery)
• Diagnosis posts → Pillar 2 (Performance Analysis)
• Strategy posts → Pillar 3 (Data to Action)
• Beginner posts → Pillar 4 (SEO Basics)
• AI search posts → Pillar 5 (AI Search)

---

File Naming

Use kebab-case slugs matching content strategy:

post-01-how-to-set-up-google-search-console.md
post-22-traffic-drop-diagnosis-checklist.md
post-45-what-is-seo.md

Pillar pages use descriptive names:

pillar-1-complete-guide-google-search-console-analysis.md
pillar-2-seo-performance-analysis-diagnose-fix-traffic.md

---

Quality Checklist

Before publishing, verify:

• Frontmatter complete (title, description, category, tags, keywords)
• Target keyword appears in title and first paragraph
• At least one GSC screenshot or data example (for technical posts)
• 5-15 inline links to related content following user journey paths
• Link to relevant pillar page
• Product mention is natural or absent (educational first)
• No broken internal links
• Proper markdown formatting (headers, code blocks, lists)
• Tight prose: No filler phrases, redundant explanations, or marketing adjectives
• Self-editing checklist applied (see "Writing Tight, Value-Packed Prose" section)
• Target ~15-20% less than typical SEO blog length while maintaining analytical depth
• 1000-2500 words (compress to value density, not word count)
• NO word count mentions - Never tell readers how many words the post is. Users don't care about length, only value

---

Updating Posts

When updating existing posts:

1. Update updatedAt in frontmatter (if it exists)
2. Keep original publishedAt date
3. Add new inline links if relevant content has been published
4. Update internal links if better matches exist
5. Don't change URLs/slugs (breaks external links)
6. Apply tight prose editing to remove filler

---

Revision History

2026-01-21

• Initial version adapted from Hook Mesh blog guidelines
• Focused on GSC analysis and data interpretation
• Emphasized educational over promotional content
• Added tight prose guidelines for SEO content
• Included specific SEO content clichés to avoid

Last updated: 2026-01-21