SEO & AI Engine Optimization Framework · May 2026

Helpful Content System: Google's Who/How/Why framework

A comprehensive installation and audit reference for ensuring website content meets Google's Helpful Content System standards — the framework that became part of Google's core ranking infrastructure…

Google's "People-First Content" Framework

A comprehensive installation and audit reference for ensuring website content meets Google's Helpful Content System standards — the framework that became part of Google's core ranking infrastructure in 2024 and continues to drive ranking outcomes across every core update. This document is dual-purpose: installation manual and audit document.

Cross-stack implementation note: the code samples in this framework are written in plain HTML for clarity. For React, Vue, Svelte, Next.js, Nuxt, SvelteKit, Astro, Hugo, 11ty, Remix, WordPress, Shopify, and Webflow equivalents of every pattern below, see framework-cross-stack-implementation.md. For pure client-rendered SPAs (no SSR/SSG) see framework-react.md. For Tailwind-specific concerns (purge, dynamic classes, dark-mode CLS, focus accessibility) see framework-tailwind.md.

1. Document Purpose & How to Use This Document

1.1 What This Document Is

This is the canonical reference for implementing Google's Helpful Content System (HCS) on a website. HCS is the framework Google uses to distinguish content created for people (helpful, original, satisfies the searcher's need) from content created for search engines (manipulative, derivative, designed to rank rather than serve). HCS was launched in August 2022 as a standalone update, became part of Google's core ranking system in March 2024, and now operates continuously rather than as a periodic update.

This document specifies how to evaluate every piece of content against the HCS framework, what signals to install on every page to demonstrate "people-first" content creation, and how to audit existing content for HCS compliance.

1.2 Three Operating Modes

Mode A — Install Mode: Building HCS-compliant content infrastructure. Follow Sections 2 → 14 in order.

Mode B — Audit Mode: Evaluating existing content against HCS criteria. Skip to Section 11.

Mode C — Hybrid Mode: Audit then install for failing items.

1.3 How Claude Code CLI Should Consume This Document

  1. Read Section 2 — collect client variables
  2. Run Section 3 self-assessment — apply the HCS questions to each piece of content
  3. Identify SEO-first patterns — flag content showing signals of "made for search engines"
  4. Install per-article HCS markers (Section 5) and per-site HCS infrastructure (Section 6)
  5. Validate — Section 11
  6. Generate report — Section 14

1.4 Conflict Resolution Rules

Conflict Rule
Existing thin content optimized for search Flag for either deep enrichment or removal/consolidation. Do not preserve in current state.
Existing manipulative SEO patterns (keyword stuffing, doorway pages) Remediate or remove. These pages drag down site-wide HCS score.
Existing content that's good but lacks HCS markers Add markers without rewriting.
Existing content quantity vs quality tension Quality always wins. Reduce scale if needed.

1.5 Required Tools

2. Client Variables Intake

# ============================================
# HCS FRAMEWORK CLIENT VARIABLES
# ============================================

# --- Business Context (REQUIRED) ---
business_name: ""
primary_domain: ""
business_industry: ""
business_focus_topics: []            # 3-7 topics this site is genuinely the authority on

# --- Content Audit Baseline (REQUIRED) ---
total_content_pieces: 0
content_publication_rate: ""         # "high_volume" (>10/week), "medium" (1-5/week), "low" (<1/week)
content_creation_method: ""          # "in_house_experts", "freelancers", "ai_assisted", "outsourced", "mixed"
average_content_length: 0            # Words

# --- Audience (REQUIRED) ---
primary_audience_description: ""     # Who is this content actually for?
audience_pain_points: []             # 3-5 specific problems they're trying to solve
audience_expertise_level: ""         # "beginner", "intermediate", "expert", "mixed"

# --- Content Strategy Honesty Check (REQUIRED — answer truthfully) ---
publishes_for_search_intent_only: false  # Be honest. Were any articles published only because keywords had volume?
publishes_thin_content: false        # Articles under 500 words on substantive topics
publishes_aggregated_content: false  # Content that mostly summarizes others without adding value
uses_ai_for_bulk_content: false
ai_content_review_quality: ""        # "minimal", "moderate", "rigorous", "expert_review_required"
content_serves_genuine_user_need: ""  # 1-10 self-rating of how well content serves users vs ranks

# --- Helpful Content Markers (RECOMMENDED) ---
has_about_us_explaining_purpose: false
has_author_bios_with_credentials: false
has_original_research: false
has_first_hand_experience_demonstrated: false
has_clear_topical_focus: false
has_practical_value_per_article: false
publishes_only_what_audience_needs: false

# --- SEO-First Anti-Patterns (RECOMMENDED — be honest) ---
has_pages_targeting_high_volume_low_intent_keywords: false
has_doorway_pages: false
has_thin_aggregator_pages: false
has_AI_content_passed_off_as_expert: false
has_content_promising_what_it_doesnt_deliver: false
has_clickbait_titles_not_matching_content: false
has_padded_content_to_hit_word_count: false

# --- Refresh & Maintenance (REQUIRED) ---
content_review_cadence: ""           # "monthly", "quarterly", "annually", "never"
has_content_decay_process: false
retires_outdated_content: false
consolidates_redundant_content: false

3. What HCS Is

The Helpful Content System (HCS) is Google's evaluation framework — and now, ranking infrastructure — for distinguishing content that genuinely helps people from content that's primarily designed to rank in search. Launched August 2022 as a sitewide signal, HCS was integrated into Google's core ranking systems in the March 2024 core update. It now operates continuously rather than as a periodic update.

The HCS framework is centered on a simple but uncomfortable question: was this content made primarily for people, or made primarily for search engines? Google's algorithms attempt to detect content optimized for search rankings without genuinely serving the searcher's need. When detected, that content gets demoted — and the demotion can cascade across the entire site if the pattern is widespread.

HCS evaluates content using a "Who, How, and Why" framework:

The framework is documented in Google's public guidance at developers.google.com/search/docs/fundamentals/creating-helpful-content. It overlaps significantly with E-E-A-T but is distinct: E-E-A-T evaluates whether the source is trustworthy; HCS evaluates whether the content itself serves users. A site can have strong E-E-A-T (credentialed authors, good security, accurate information) but weak HCS (publishing thin content, optimizing for keywords rather than user need).

The 2024-2026 evolution of HCS reflects Google's response to the AI content explosion. Google's December 2025 helpful content guidance updated the "Who, How, and Why" framework to explicitly address AI-generated content. The position: AI involvement isn't disqualifying. Low effort, generic content that doesn't serve users IS disqualifying. AI-assisted content that is thoroughly reviewed by experts, enriched with original insights, and serves a genuine user need can pass HCS. AI content that's mass-produced for SEO with minimal review fails HCS — and the December 2025 core update specifically targeted these patterns, with significant ranking losses for content farms.

The four behaviors HCS most directly punishes:

  1. Volume-over-quality content strategies — sites that publish many articles per day on topics they don't have genuine expertise in
  2. Search-intent-first content — articles that exist because a keyword has volume, not because the audience needs an answer
  3. Aggregated/derivative content — articles that summarize what others have said without adding original insight
  4. AI-generated content without expert review — bulk AI content optimized for ranking rather than helping

The four behaviors HCS rewards:

  1. Topical authority through depth — sites that cover a focused set of topics deeply rather than broadly
  2. First-hand experience and original insight — content that demonstrates the author actually did, used, or experienced what's being discussed
  3. Clear practical value per article — every article should leave the reader with something they didn't have before
  4. Editorial integrity — content created by people who care about the topic, reviewed by people who know the topic

4. Google's Self-Assessment Questions

Google publishes specific questions creators should ask themselves about their content. This is the official HCS self-evaluation framework. Apply these to every piece of content.

4.1 People-First Content Questions

Score each question Yes/No/Partial for each article being evaluated:

Content quality

Expertise

Page experience

4.2 SEO-First Content Red Flags (Avoid These)

Google explicitly warns that creating content with these patterns is a problem:

4.3 The "Who, How, Why" Framework

For every piece of content, document:

Who created it?

How was it created?

Why was it created?

The "why" is the hardest to be honest about. Most low-quality SEO content is created by people who would never admit it's primarily for search engines. The honest test: would you publish this article if Google didn't exist? If no, it's probably search-first content.

5. Per-Article HCS Implementation

What every article must include to demonstrate HCS compliance.

5.1 The Five HCS Markers

Every article must visibly demonstrate these markers:

5.1.1 Clear creator identity

Author byline at the top of every article with link to author page. The author must be a real person with verifiable expertise. See framework-eeat.md Section 4.2 for full implementation. HCS adds the requirement that anonymous content is a red flag — even pseudonymous bylines should explain why pseudonymity is appropriate.

5.1.2 Demonstrable original value

Every article must add something not available in the top-ranked search results for the query. Original value can be:

Build an "original value" sidebar on long-form articles:

<aside class="original-value" aria-label="What this article adds">
  <h3>What This Article Adds</h3>
  <p>Most articles on {{TOPIC}} cover {{COMMON_COVERAGE}}. This article goes further with:</p>
  <ul>
    <li>{{ORIGINAL_CONTRIBUTION_1}}</li>
    <li>{{ORIGINAL_CONTRIBUTION_2}}</li>
    <li>{{ORIGINAL_CONTRIBUTION_3}}</li>
  </ul>
</aside>

5.1.3 Comprehensive coverage when relevant

If the article promises to be a "complete guide" or "everything you need to know," it must actually be comprehensive. Use a coverage checklist in the article structure:

<nav class="article-coverage" aria-label="What this article covers">
  <h2>What This Guide Covers</h2>
  <ol>
    {{LIST_OF_SECTIONS_WITH_LINKS_TO_HEADINGS}}
  </ol>
</nav>

If you can't be comprehensive, don't claim to be. Title and meta should match the actual depth.

5.1.4 Honest meta and titles

Title and meta description must accurately describe the content. Anti-patterns:

Honest title test: would the article meet the searcher's expectation if they clicked from the title alone, without reading the meta?

5.1.5 No trailing fluff

End the article when the value is delivered. HCS-compliant articles avoid:

End the article with: a clear takeaway, a next step, a related resource, or a question for the reader. Not filler.

5.2 The HCS Article Template

Combining the markers above:

<article class="article hcs-compliant">
  <!-- Metadata header -->
  <header>
    <h1>{{ACCURATE_TITLE_THAT_MATCHES_CONTENT}}</h1>

    <div class="article-byline">
      <img src="{{AUTHOR_PHOTO}}" alt="{{AUTHOR_NAME}}">
      <p>By <a href="/authors/{{AUTHOR_SLUG}}/" rel="author">{{AUTHOR_NAME}}</a></p>
      <p class="byline-credentials">{{RELEVANT_CREDENTIALS_FOR_THIS_TOPIC}}</p>
      <time datetime="{{PUBLISHED}}">Published {{PUBLISHED_HUMAN}}</time>
      <time datetime="{{UPDATED}}">Updated {{UPDATED_HUMAN}}</time>
    </div>

    {{IF_AI_USED}}
    <aside class="ai-disclosure">
      This article {{AI_USAGE_LEVEL}}. Reviewed and verified by {{REVIEWER_NAME}}.
    </aside>
    {{/IF}}
  </header>

  <!-- Original value indicator -->
  <aside class="original-value">
    <h2>What This Article Adds</h2>
    <ul>
      {{ORIGINAL_CONTRIBUTIONS}}
    </ul>
  </aside>

  <!-- Coverage promise (if comprehensive guide) -->
  {{IF_COMPREHENSIVE_GUIDE}}
  <nav class="article-coverage">
    <h2>What This Guide Covers</h2>
    {{TOC}}
  </nav>
  {{/IF}}

  <!-- Article body — substantive content -->
  <div class="article-body">
    {{CONTENT_THAT_DELIVERS_ON_THE_TITLE_PROMISE}}

    <!-- First-hand experience callout when applicable -->
    {{IF_PRACTICAL_CONTENT}}
    <aside class="experience-callout">
      <h3>How I Know This Works</h3>
      <p>{{SPECIFIC_EXPERIENCE_DETAILS}}</p>
    </aside>
    {{/IF}}

    <!-- Original imagery, screenshots, data visualizations -->
    {{ORIGINAL_VISUAL_CONTENT}}

    <!-- Failure cases for practical content -->
    {{IF_LONG_FORM_PRACTICAL}}
    <section class="failures-edge-cases">
      <h2>What Doesn't Work</h2>
      {{SPECIFIC_FAILURES_OR_EDGE_CASES}}
    </section>
    {{/IF}}
  </div>

  <!-- End cleanly: takeaway, next step, or related -->
  <footer>
    <section class="article-takeaway">
      <h2>Key Takeaway</h2>
      <p>{{ONE_SENTENCE_TAKEAWAY}}</p>
    </section>

    <section class="article-next-step">
      <h2>Next Step</h2>
      <p>{{SPECIFIC_RECOMMENDATION_FOR_THE_READER}}</p>
    </section>

    {{REFERENCES_IF_FACTUAL_CONTENT}}
    {{AUTHOR_BOX}}
    {{RELATED_ARTICLES_GENUINELY_RELATED}}
  </footer>
</article>

5.3 What to Remove from Articles

To be HCS-compliant, audit every article for and remove:

6. Site-Wide HCS Implementation

Beyond per-article work, the site as a whole must signal HCS compliance.

6.1 Phase 1: Topical Focus Audit

Sites that try to cover everything do worse than sites with clear topical focus. HCS rewards depth over breadth.

6.1.1 Define the site's topical pillars

Identify 3-7 topics this site is genuinely the authority on. These should be:

Document at /topics/ or in an internal strategy doc:

Primary Topics (we are the authority):
1. {{TOPIC_1}} - {{WHY_WE_ARE_AUTHORITY}}
2. {{TOPIC_2}} - {{WHY_WE_ARE_AUTHORITY}}
3. {{TOPIC_3}} - {{WHY_WE_ARE_AUTHORITY}}

Secondary Topics (we have meaningful coverage):
1. {{TOPIC_4}}
2. {{TOPIC_5}}

Topics We Don't Cover (and why):
- {{ADJACENT_TOPIC}} - {{REASON_NOT_COVERED}}

6.1.2 Audit existing content against pillars

For every existing piece of content:

The result: a content inventory where every remaining article reinforces topical authority on a defined pillar.

6.2 Phase 2: Topical Hub Pages

Each primary pillar gets a dedicated hub page demonstrating depth.

<article class="topical-hub" itemscope itemtype="https://schema.org/CollectionPage">
  <h1>{{TOPIC_NAME}}</h1>

  <section class="hub-introduction">
    <p>{{200_400_WORD_AUTHORITATIVE_INTRO_DEMONSTRATING_DEPTH}}</p>
  </section>

  <section class="hub-our-perspective">
    <h2>Our Perspective on {{TOPIC}}</h2>
    <p>{{WHAT_MAKES_THIS_SITES_TAKE_ON_THE_TOPIC_DISTINCTIVE}}</p>
  </section>

  <section class="hub-content-organized">
    <h2>{{TOPIC}} — Complete Coverage</h2>

    <h3>Foundations</h3>
    <ul>{{FOUNDATIONAL_ARTICLES}}</ul>

    <h3>Practical Application</h3>
    <ul>{{PRACTICAL_ARTICLES}}</ul>

    <h3>Advanced Topics</h3>
    <ul>{{ADVANCED_ARTICLES}}</ul>

    <h3>Original Research</h3>
    <ul>{{RESEARCH_ARTICLES}}</ul>
  </section>

  <section class="hub-related-pillars">
    <h2>Related Topics We Cover</h2>
    <ul>{{LINKS_TO_RELATED_HUBS}}</ul>
  </section>

  <section class="hub-not-covered">
    <h2>Topics We Don't Cover (And Where to Find Them)</h2>
    <p>{{HONEST_GUIDANCE_TO_OTHER_AUTHORITATIVE_SOURCES}}</p>
  </section>
</article>

The "honest guidance to other sources" section is counterintuitive but powerful. Pointing readers to legitimate authorities on adjacent topics demonstrates editorial integrity and improves user satisfaction.

6.3 Phase 3: About Page That Explains the Site's Purpose

Google's HCS guidance specifically asks: "If you researched the site producing the content, would you come away with an impression that it is well-trusted or widely-recognized as an authority on its topic?"

The About page is the answer. Build at /about/ with:

<article class="about-page">
  <h1>About {{BUSINESS_NAME}}</h1>

  <section class="why-we-exist">
    <h2>Why We Exist</h2>
    <p>{{SPECIFIC_PROBLEM_THE_SITE_SOLVES_FOR_AUDIENCE}}</p>
    <p>{{HOW_THE_SITE_IS_DIFFERENT_FROM_ALTERNATIVES}}</p>
  </section>

  <section class="who-we-are">
    <h2>Who We Are</h2>
    <p>{{FOUNDER_BIO_WITH_RELEVANT_EXPERIENCE}}</p>
    <p>{{TEAM_INFO_IF_APPLICABLE}}</p>
  </section>

  <section class="what-we-cover">
    <h2>What We Cover</h2>
    <ul>{{LIST_OF_PRIMARY_PILLARS_WITH_LINKS}}</ul>
  </section>

  <section class="what-we-dont-cover">
    <h2>What We Don't Cover</h2>
    <p>{{HONEST_DESCRIPTION_OF_TOPICS_OUTSIDE_SCOPE}}</p>
  </section>

  <section class="our-process">
    <h2>How We Create Content</h2>
    <ul>
      <li>{{CONTENT_CREATION_PROCESS_DETAIL}}</li>
      <li>{{REVIEW_PROCESS_DETAIL}}</li>
      <li>{{FACT_CHECKING_DETAIL}}</li>
      <li>{{IF_AI_USED_HOW}}</li>
    </ul>
    <p>See our <a href="/editorial-policy/">editorial policy</a> for full details.</p>
  </section>

  <section class="our-relationships">
    <h2>Our Relationships and Commitments</h2>
    <p>{{INDEPENDENCE_STATEMENT}}</p>
    <p>{{ANY_AFFILIATE_OR_PARTNERSHIP_CONTEXT}}</p>
    <p>See our <a href="/disclosure/">full disclosures</a>.</p>
  </section>

  <section class="contact">
    <h2>How to Reach Us</h2>
    <p>{{CONTACT_INFO}}</p>
    <p>Editorial questions: <a href="mailto:editorial@{{DOMAIN}}">editorial@{{DOMAIN}}</a></p>
  </section>
</article>

6.4 Phase 4: Content Removal & Consolidation

Sites with significant low-quality content drag their entire site's HCS score down. HCS evaluates the site holistically — even good articles can underperform if they're surrounded by low-quality content.

6.4.1 Removal candidates

Remove or noindex content that:

6.4.2 Consolidation candidates

Consolidate content where:

6.4.3 Consolidation pattern

When merging multiple articles into one comprehensive piece:

  1. Identify the strongest URL to keep (best-ranked, oldest authoritative URL, or cleanest URL structure)
  2. Merge content from the others into the kept URL
  3. Improve the merged article significantly — don't just stitch text together
  4. 301 redirect the consolidated URLs to the kept URL
  5. Update internal links to point to the kept URL
  6. Re-submit sitemap

6.5 Phase 5: AI Content Disclosure & Strategy

If AI is used in content creation, HCS requires more than just disclosure. Google's December 2025 guidance specifically asks "Why" content was created — using AI for bulk publication is a "Why" failure.

6.5.1 What's acceptable AI use under HCS

6.5.2 What's not acceptable

6.5.3 AI disclosure on every AI-assisted article

<aside class="ai-content-disclosure">
  <h3>About this article</h3>
  <p>{{SPECIFIC_DESCRIPTION_OF_HOW_AI_WAS_USED}}</p>
  <p>This article was reviewed and edited by {{REVIEWER_NAME}}, {{CREDENTIALS}}.</p>
  <p>{{REVIEWER_NAME}} verified all factual claims, citations, and recommendations. They take professional responsibility for the accuracy of this content.</p>
  <p>See our <a href="/disclosure/">full AI use policy</a>.</p>
</aside>

6.6 Phase 6: Refresh Strategy (Not Date Manipulation)

HCS specifically warns against "changing the date of pages to make them seem fresh when the content has not substantially changed."

6.6.1 Genuine refresh process

When refreshing an article:

  1. Read the article from the user's perspective — what's no longer accurate?
  2. Update outdated information with current data
  3. Add new sections covering developments since the last update
  4. Remove sections that are no longer relevant
  5. Update statistics, examples, screenshots
  6. Verify all citations still work
  7. Get reviewer sign-off if YMYL

Then update dateModified and add a changelog entry.

6.6.2 Article changelog

For substantive refreshes, document what changed:

<details class="article-changelog">
  <summary>Last updated {{UPDATED_DATE}} — see what changed</summary>
  <ul>
    <li><time datetime="{{UPDATE_1_DATE}}">{{UPDATE_1_DATE_HUMAN}}</time>: {{WHAT_CHANGED}}</li>
    <li><time datetime="{{UPDATE_2_DATE}}">{{UPDATE_2_DATE_HUMAN}}</time>: {{WHAT_CHANGED}}</li>
    <li><time datetime="{{UPDATE_3_DATE}}">{{UPDATE_3_DATE_HUMAN}}</time>: {{WHAT_CHANGED}}</li>
  </ul>
</details>

This proves the refresh was substantive, not just a date change.

7. Per-Article HCS Audit Criteria

Score each article:

# Criterion Severity
H1 Article addresses a genuine user need (not just a keyword) Critical
H2 Title and meta accurately describe the content Critical
H3 Content delivers on what the title promises Critical
H4 Author has demonstrable expertise on this specific topic Critical
H5 Article adds original value beyond what's in top SERP results High
H6 First-person experience or original research demonstrated High
H7 No padding to hit word count Medium
H8 No unnecessary fluff intro or trailing filler Medium
H9 Original imagery (not just stock) Medium
H10 Comprehensive coverage if claimed High
H11 Honest about what's not covered Low
H12 If AI was used, transparently disclosed and reviewed Critical (if applicable)
H13 Last refresh was substantive (if claimed as updated) High
H14 Content is well-organized and scannable Medium
H15 Page experience is good (load speed, no intrusive ads) High

Score: 30 max. World-class HCS article: 26+/30 with zero Critical fails.

8. Site-Wide HCS Audit Criteria

# Criterion Severity
HS1 Site has clear topical focus (3-7 pillars, not unlimited topics) Critical
HS2 About page explains the site's purpose, audience, and creators Critical
HS3 Topical hub pages exist for each primary pillar High
HS4 Editorial policy documented High
HS5 All authors have credentials matching topics they cover Critical
HS6 No thin content or doorway pages Critical
HS7 No content that exists only because keyword has volume Critical
HS8 AI use is disclosed where applicable Critical (if applicable)
HS9 Refresh strategy is genuine, not date manipulation High
HS10 Outdated content is refreshed or retired High
HS11 No mass-produced content patterns Critical
HS12 Site doesn't make promises content doesn't deliver Critical

Score: 24 max. World-class HCS site: 21+/24 with zero Critical fails.

9. Common HCS Mistakes & Anti-Patterns

9.1 Keyword-First Content Strategy

Anti-pattern: Selecting topics based on keyword volume regardless of whether the site has genuine expertise.

Why it fails: Google's HCS specifically targets this pattern. Even well-written articles on topics outside the site's authority struggle.

Fix: Topic selection must start with "what does our audience genuinely need?" not "what has high search volume?"

9.2 AI Content Volume Strategy

Anti-pattern: "We can publish 100 articles per month with AI." Mass-produced AI content with minimal review.

Why it fails: December 2025 core update specifically targeted this. Sites with this pattern lost significant traffic.

Fix: Either dramatically slow publication and improve review quality, or remove the AI content. Quality > quantity.

9.3 "Comprehensive Guide" Without Depth

Anti-pattern: Title says "complete guide" but article is 1500 words of basics.

Why it fails: Title-content mismatch is a Trust violation and HCS failure.

Fix: Either deliver actual comprehensive coverage (often 3000-8000+ words for genuinely comprehensive guides) or change the title.

9.4 Forced Word Count

Anti-pattern: "Articles need to be 2000 words to rank." Padded content to hit a number.

Why it fails: HCS specifically warns about this. Padded content is detectable and fails the user.

Fix: Length matches content needs. A 600-word article that perfectly answers the question outranks a padded 2000-word article.

9.5 Trending Topics Without Genuine Coverage

Anti-pattern: Site that normally covers cooking suddenly publishes articles about cryptocurrency because crypto is trending.

Why it fails: HCS asks "Are you writing about things simply because they seem trending?" Yes is a failure.

Fix: Stay in your lane. Cover what you genuinely know.

9.6 Date Refresh Without Content Refresh

Anti-pattern: Updating dateModified without substantively updating content.

Why it fails: Google detects this pattern. It's a Trust violation.

Fix: Update dates only when content was genuinely updated. Document what changed.

9.7 Generic AI Boilerplate

Anti-pattern: AI-generated articles with telltale phrases ("It's important to note...", "Furthermore...", "In conclusion...") and no specific examples or insights.

Why it fails: Detectable, generic, doesn't serve users.

Fix: Either rewrite to remove AI boilerplate and add specific value, or remove the article.

9.8 Aggregator Pages Without Original Insight

Anti-pattern: "The 10 best X tools" articles that just describe what each tool does without any actual evaluation, testing, or insight.

Why it fails: Low original value. The article doesn't add anything beyond visiting each tool's homepage.

Fix: Test the tools, document the testing, share specific findings, give a recommendation based on real evaluation.

9.9 Hidden Affiliate Optimization

Anti-pattern: "Best X for Y" article that's structured around which products have the best affiliate commissions.

Why it fails: HCS detects mismatch between recommendation and user need. Long-term Trust damage.

Fix: Recommendations based on actual user benefit. Disclose affiliates clearly.

9.10 Content Without a Real Person

Anti-pattern: "Editorial Team" or no byline at all on substantive content. Generic about pages.

Why it fails: HCS asks who created the content. Anonymous content is suspect.

Fix: Real author bylines. Real about pages.

10. Stack-Specific HCS Implementation

10.1 WordPress

10.2 Next.js / Astro / Hugo

10.3 Universal Pattern

The HCS workflow:

  1. Topic selection: passes "is this in our authority area?" test
  2. Drafting: passes "what does this add?" test
  3. Reviewing: passes "would a reader feel this was worth their time?" test
  4. Publishing: HCS markers all present
  5. Monitoring: track engagement metrics; revise or retire underperforming content
  6. Refreshing: substantive updates only; document changes

11. Validation Protocol

11.1 Per-Article Validation

Sample 10% of articles. For each:

  1. Read it as if you found it in search results
  2. Apply Google's self-assessment questions (Section 4.1)
  3. Score Pass/Partial/Fail per HCS criterion (Section 7)
  4. Document findings

11.2 Site-Wide Validation

  1. Audit topical focus — do articles cluster around clear pillars?
  2. Inventory content quality — what percentage is high-quality vs thin/derivative?
  3. Check for HCS-failing patterns (Section 9)
  4. Evaluate About page against Section 6.3 requirements
  5. Score against Section 8 criteria

11.3 Honesty Test

The hardest HCS validation: ask someone outside the site (a peer, a target audience member, an industry colleague) to read sample articles and answer:

External honest feedback is the most reliable HCS signal.

12. Audit Mode

Total HCS audit: 54 points (30 per-article average + 24 site-wide).

Score Status
48-54 World-class HCS compliance
41-47 Compliant with minor gaps
30-40 Significant gaps requiring remediation
<30 Critical HCS failures — major content overhaul needed

A site with critical HCS fails (HS1, HS5, HS6, HS7, HS11, HS12) is at significant risk for ranking suppression in core updates regardless of E-E-A-T or technical SEO strength.

13. Maintenance Schedule

13.1 Weekly

13.2 Monthly

13.3 Quarterly

13.4 Annually

13.5 Post-Core-Update

After every confirmed Google core update (typically 3-4 per year):

  1. Identify pages that lost ranking
  2. Apply HCS criteria to those pages
  3. Look for patterns — what failed?
  4. Remediate per HCS framework
  5. Track recovery over 30-60 days

14. Implementation/Audit Report Templates

14.1 HCS Implementation Report Template

# HCS Framework Implementation Report

**Project**: {{BUSINESS_NAME}}
**Implementation Date**: {{TODAY}}

## Summary
- Total content audited: {{COUNT}}
- Content kept (high quality): {{COUNT}}
- Content refreshed substantively: {{COUNT}}
- Content consolidated: {{COUNT}}
- Content removed: {{COUNT}}

## Topical Pillars Defined
{{LIST_OF_PILLARS}}

## Hub Pages Created
{{LIST_OF_HUB_URLS}}

## About Page Updated
{{STATUS_AND_KEY_ADDITIONS}}

## AI Use Policy
{{POLICY_STATUS}}

## HCS Markers Installed Per Article Type
{{TABLE}}

## Items Flagged for Manual Review
{{LIST}}

## Validation Results
{{AUTOMATED_AND_MANUAL_RESULTS}}

## Sign-Off
Implementation complete: {{DATE}}

14.2 HCS Audit Report Template

# HCS Framework Audit Report

**Site**: {{BUSINESS_NAME}}
**Audit Date**: {{TODAY}}

## Executive Summary
{{ONE_PARAGRAPH_ASSESSMENT}}

**Overall Score**: {{X}}/54
**Status**: {{STATUS}}

## Topical Focus Assessment
{{FINDINGS}}

## Content Quality Distribution
- High-quality content: {{PERCENTAGE}}%
- Acceptable content: {{PERCENTAGE}}%
- Thin/derivative content: {{PERCENTAGE}}%

## Critical HCS Failures
{{LIST_WITH_REMEDIATION}}

## Per-Article Findings (Sample of 10%)
{{DETAILED_FINDINGS}}

## Site-Wide Findings
{{DETAILED_FINDINGS}}

## Recommended Remediation Order
1. Critical: {{PRIORITY_1}}
2. High: {{PRIORITY_2}}
3. Medium: {{PRIORITY_3}}

## Estimated Remediation Effort
{{HOURS}}

## Sign-Off

End of Framework Document

Document version: 1.0 Last updated: 2026-04-29 Maintained by: ThatDeveloperGuy

HCS is the evaluation framework for content quality — but more importantly, it's an honest mirror for content strategy. Sites that genuinely serve their audience pass HCS naturally. Sites that prioritize search rankings over user value fail HCS regardless of how clever the SEO is. The fastest path to HCS compliance is the hardest one: be honest about why content exists, who it's for, and whether it's genuinely useful.

Companion documents:

Want this framework implemented on your site?

ThatDevPro ships these frameworks as productized services. SDVOSB-certified veteran owned. Cassville, Missouri.

See Engine Optimization service ›