AgriciDaniel/claude-blog / skills/blog
blog
VerifiedFull-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.
references/eeat-signals.md
View on GitHub# Author E-E-A-T Requirements
## Contents
- [Named Author Attribution](#named-author-attribution)
- [Author Bio Structure](#author-bio-structure)
- [Author Page Requirements](#author-page-requirements)
- [Person Schema Properties](#person-schema-properties)
- [Experience Signal Markers](#experience-signal-markers)
- [Trust Indicators](#trust-indicators)
- [September 2025 QRG Key Principle](#september-2025-qrg-key-principle)
- [E-E-A-T Scoring Rubric](#e-e-a-t-scoring-rubric)
- [E-E-A-T Framing by Topic Risk](#e-e-a-t-framing-by-topic-risk)
- [E-E-A-T Signals by Content Type](#e-e-a-t-signals-by-content-type)
## Named Author Attribution
A named accountable author or editor is strongly preferred for every blog post.
Organization attribution is acceptable when the organization is the accountable
publisher and the page also exposes clear editorial ownership.
### Never Use
| Attribution | Problem |
|-------------|---------|
| "Admin" | No person, no trust |
| "Staff" | Indistinguishable from auto-generated |
| "Team" | No individual accountability |
| "Editor" | Not an author signal |
| No byline | Worst case: page appears authorless |
### Preferred
- Full real name (first + last)
- Crawlable author or profile page with a stable URL
- Same name used on social profiles linked via `sameAs`
- One author per post (co-authors acceptable with both named)
### Authorship Integrity (Google helpful-content page, updated 2026-10-05)
Source: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
(page shows "Last updated 2026-10-05 UTC"; fetched 2026-10-11).
- Google strongly encourages accurate authorship information, such as bylines,
where readers might expect it.
- Google describes fabricating creator profiles (AI-generated headshots,
made-up names, false credentials) as a form of deception. Never invent an
author, a headshot, or a credential. If no real accountable person exists, use
the real publisher or editorial team and state what is true.
- Google lists changing a page's date to look fresh, when the content has not
substantially changed, as a warning sign. Move `dateModified` only after a
substantive edit.
- Google asks whether automation, including AI generation, is self-evident to
visitors through disclosures or other ways. Disclose AI assistance where
readers would expect it (see
https://developers.google.com/search/docs/fundamentals/using-gen-ai-content,
updated 2026-10-01).
- Who, How, and Why: who created the content (byline, author page), how it was
created (method, testing, any automation), and why it exists (to help readers,
not to attract search traffic). Google calls Why perhaps the most important.
- Google also says E-E-A-T is not itself a ranking factor. Treat the above as
editorial integrity checks, not a score hack.
---
## Author Bio Structure
2-3 sentences. The bio establishes E-E-A-T credentials, not a sales pitch.
### Formula
**Sentence 1**: [Name] is a [role/title] with [N years] experience in [domain].
**Sentence 2**: [Credential, employer, or notable achievement relevant to the topic].
**Sentence 3** (optional): [Specific focus area or what they write about].
### Good Examples
> Sarah Chen is a content strategist with 8 years of experience in B2B SaaS.
> She's led content programs at HubSpot and Drift, specializing in data-driven
> blog optimization.
> Marcus Rivera is a senior frontend engineer at Vercel. He maintains two
> open-source React component libraries with 12K+ combined GitHub stars and
> writes about performance patterns for production applications.
> Dr. Elena Vasquez is a clinical psychologist and researcher at Stanford
> Medical Center. She has published 23 peer-reviewed papers on cognitive
> behavioral therapy and digital mental health interventions.
### Bad Examples (Anti-Patterns)
> "John is passionate about helping businesses grow through innovative digital
> solutions.": Vague, no credentials, sounds like marketing copy.
> "Our team of experts delivers world-class content marketing services."
>: Not a person, promotional, no specific expertise.
> "Jane is the CEO of GrowthMax Inc., the leading AI-powered marketing
> platform.": Sales pitch disguised as bio.
---
## Author Page Requirements
Every named author should have a crawlable author or profile page. The URL path
can follow the site's existing information architecture.
### Page Must Include
| Element | Details |
|---------|---------|
| Full name (H1) | Same name used in bylines |
| Professional photo | Real photo, not avatar or stock |
| Extended bio | 100-200 words with credentials |
| Social links | LinkedIn, Twitter/X, personal site, GitHub (as relevant) |
| Article list | All published posts by this author, newest first |
| ProfilePage schema | JSON-LD with Person entity |
### ProfilePage Schema Example
```json
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"@id": "https://example.com/author/sarah-chen#person",
"name": "Sarah Chen",
"jobTitle": "Content Strategist",
"description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.",
"url": "https://example.com/author/sarah-chen",
"image": "https://example.com/images/authors/sarah-chen.jpg",
"sameAs": [
"https://linkedin.com/in/sarahchen",
"https://twitter.com/sarahchen",
"https://sarahchen.com"
],
"worksFor": {
"@type": "Organization",
"name": "Example Corp"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "UC Berkeley"
}
}
}
```
---
## Person Schema Properties
The Person schema embedded in BlogPosting and on author pages.
The "This project" column is the house convention for author pages. Google's Article documentation recommends only `author.name` and `author.url`; the other properties are optional trust signals, not requirements.
| Property | This project | Description | Example |
|----------|----------|-------------|---------|
| `@type` | Yes | Always "Person" | `"Person"` |
| `@id` | Yes | Stable URI with fragment | `"https://example.com/author/sarah-chen#person"` |
| `name` | Yes | Full name | `"Sarah Chen"` |
| `jobTitle` | Yes | Current role | `"Content Strategist"` |
| `url` | Yes | Author page URL | `"https://example.com/author/sarah-chen"` |
| `image` | Yes | Headshot URL | `"https://example.com/images/authors/sarah-chen.jpg"` |
| `sameAs` | Yes | Array of social/profile URLs | `["https://linkedin.com/in/sarahchen"]` |
| `worksFor` | Recommended | Organization entity | `{"@type": "Organization", "name": "Example Corp"}` |
| `alumniOf` | Optional | Educational institution | `{"@type": "CollegeOrUniversity", "name": "UC Berkeley"}` |
| `description` | Recommended | Brief professional summary | `"B2B SaaS content strategist..."` |
| `knowsAbout` | Optional | Array of expertise topics | `["SEO", "content strategy", "B2B marketing"]` |
### Complete Person JSON-LD
```json
{
"@type": "Person",
"@id": "https://example.com/author/sarah-chen#person",
"name": "Sarah Chen",
"jobTitle": "Content Strategist",
"url": "https://example.com/author/sarah-chen",
"image": "https://example.com/images/authors/sarah-chen.jpg",
"description": "Content strategist with 8 years of experience in B2B SaaS, specializing in data-driven blog optimization.",
"sameAs": [
"https://linkedin.com/in/sarahchen",
"https://twitter.com/sarahchen",
"https://sarahchen.com"
],
"worksFor": {
"@type": "Organization",
"name": "Example Corp",
"url": "https://example.com"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "UC Berkeley"
},
"knowsAbout": ["SEO", "Content Strategy", "B2B SaaS Marketing"]
}
```
---
## Supported First-Hand Evidence
First-hand claims can add value only when they are true and supported by
methodology, measurements, screenshots, records, or other inspectable evidence.
Never add first-person phrasing merely to earn E-E-A-T points. Neutral,
well-sourced explainers are valid.
### Use These Patterns
| Pattern | Use Only When |
|---------|-------------|
| "When we tested..." | The test setup, sample, and result can be described |
| "In our experience..." | The relevant work and observation can be substantiated |
| "After implementing this for [client]..." | Case study context |
| "Over the past [N] years, I've found..." | Long-term observation |
| "Here's what our data shows..." | Introducing proprietary findings |
| "I've personally seen..." | Direct observation |
| "We ran this experiment across [N] sites..." | Multi-site testing |
| "What surprised us was..." | Counterintuitive findings |
| "The mistake most teams make is..." | Practitioner wisdom |
| "When I worked at [Company]..." | Named employer context |
### Signals to AVOID
| Anti-Pattern | Problem |
|-------------|---------|
| "As an expert in..." | Self-proclaimed authority, no evidence |
| "It is well known that..." | Vague consensus claim |
| "Studies show..." (no citation) | Unsourced authority claim |
| "Everyone agrees..." | Unfalsifiable |
| "Trust us when we say..." | Demands trust rather than earning it |
| Generic "top tips" language | Could have been written by anyone |
| Unsupported first-person claim | Performs experience without evidence |
| "In this article, we will..." | Filler, not experience signal |
---
## Trust Indicators
Trust is the most important member of the E-E-A-T family (September 2025 QRG).
Trust encompasses and validates all other signals.
### Site-Level Trust Signals
| Signal | Priority | Implementation |
|--------|----------|----------------|
| Contact page | Critical | Real email, phone, or contact form |
| About page | Critical | Company/author info, mission, team |
| Privacy policy | Critical | Required depending on jurisdiction, tracking, and data collection |
| Terms of service | High | Legal framework for content use |
| Editorial policy | High | How content is created, reviewed, updated |
| Physical address | High (local) | Required for LocalBusiness, helpful for all |
| Author social profiles | High | Verifiable external presence |
| HTTPS | Critical | Non-negotiable baseline |
| Clear ownership | High | Who publishes this site and why |
### Content-Level Trust Signals
| Signal | Implementation |
|--------|----------------|
| Source attribution | Every claim backed by named source |
| Transparent methodology | How data was collected, sample size |
| Conflict of interest disclosure | Affiliate links, sponsorships |
| Correction/update notes | "Updated [date]: corrected [what]" |
| Expert review | "Reviewed by [Expert Name], [credentials]" |
| Date transparency | Publish date AND last updated date visible |
**Trustworthiness requires source fidelity and claim-appropriate provenance.**
Experience and authority signals only land when the underlying claims are
verifiable. Include source identity, relevant dates, methodology, limitations,
stable URLs, and retrieval notes when those details are needed to identify or
interpret the evidence. No fixed citation form is required. See
`flow-alignment.md`.
---
## September 2025 QRG Key Principle
Google's Quality Rater Guidelines (September 11, 2025 revision) remain the
current QRG in mid-2026 as of 2026-07-07. That 182-page version renamed "YMYL
Society" to "YMYL Government, Civics & Society," added AI Overview evaluation
examples, and assigned lowest ratings to value-less auto or AI content.
The E-E-A-T framing is stable. Google's September 2025 revision established:
> "Trust is the most important member of the E-E-A-T family because untrustworthy
> pages have low E-E-A-T no matter how Experienced, Expert, or Authoritative they
> may seem."
This means a page with brilliant expert content but missing trust signals (no
author attribution, no contact info, no source citations) will score low overall.
Trust is the foundation; the other three factors build on it.
---
## E-E-A-T Scoring Rubric
These are internal scoring weights for the claude-blog quality rubric. Google
does not publish numeric E-E-A-T weights.
| Factor | Internal Weight | Key Signals |
|--------|-----------------|-------------|
| Experience | 20% | First-hand knowledge, original content, case studies, personal testing, process documentation |
| Expertise | 25% | Credentials, technical depth, accuracy, comprehensiveness, professional background |
| Authoritativeness | 25% | Industry recognition, external citations, backlinks, reputation, speaking/publication history |
| Trustworthiness | 30% | Contact info, transparency, security, source attribution, editorial policy, corrections |
### Scoring Flow
Trust is evaluated FIRST. If trust is low, the overall E-E-A-T score is capped
regardless of how strong the other three signals are.
```
Trust Assessment → If Low → Cap at "Low E-E-A-T"
→ If Adequate → Evaluate E + E + A → Combined Score
```
---
## E-E-A-T Framing by Topic Risk
Helpful, trustworthy content matters broadly, but evidence expectations scale
with topic risk and likely user harm. YMYL topics still carry the highest
scrutiny.
- **Highest risk**: health, finance, legal, safety, elections, civics, and other
YMYL topics need strong credentials, sourcing, review, and harm-prevention
language.
- **Medium risk**: technical, business, and product guidance needs evidence
proportionate to the claim and potential harm. First-hand testing and a
transparent methodology are required when the article claims a test or
recommends a consequential action; neutral sourced analysis can rely on
current, appropriate sources without inventing personal experience.
- **Lower risk**: hobby and entertainment topics still benefit from experience
signals, but they do not need the same proof burden as health or finance.
### Practical Impact
A blog post about "best mechanical keyboards" should show first-hand testing and
transparent recommendations. A post about "best health insurance plans" needs a
much higher bar for credentials, review, sourcing, and legal or financial caveats.
---
## E-E-A-T Signals by Content Type
| Content Type | Experience | Expertise | Authoritativeness | Trustworthiness |
|-------------|------------|-----------|-------------------|-----------------|
| **Blog Post** | Author tested/used what they write about; personal anecdotes | Deep topic knowledge; technical accuracy | Links from other sites; author published elsewhere | Sourced claims; editorial policy; contact page |
| **Product Review** | Hands-on testing; original photos/video; owns the product | Technical specs knowledge; comparison framework | Known reviewer; multiple reviews published | Disclosure of affiliates; transparent scoring method |
| **How-To Guide** | Author has done the process; screenshots of their work | Step accuracy; edge cases covered; troubleshooting | Recognized practitioner; cited by others | Tested instructions; warnings included; updated dates |
| **News Article** | Reporter was present or interviewed sources directly | Subject matter knowledge; context provided | Established publication; editorial oversight | Multiple sources; corrections policy; byline |
| **Opinion/Editorial** | Author has relevant professional experience | Informed perspective backed by evidence | Published track record; industry standing | Clearly labeled as opinion; counterpoints acknowledged |
### Minimum Requirements by Content Type
| Content Type | Must Have |
|-------------|-----------|
| Blog Post | Named author, 2+ sourced stats, author bio with credentials |
| Product Review | Original photos, hands-on testing evidence, disclosure |
| How-To Guide | Author's own screenshots, tested steps, last-updated date |
| News Article | Named journalist, 2+ sources, publication editorial policy |
| Opinion/Editorial | Author credentials for topic, "Opinion" label, evidence |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |