Website content guide & voice
Owns the how it says it layer of a new site: tone of voice and EEAT signals,
captured in the per-site docs that everything downstream reads. Positioning
(what you offer, for whom, the market category) is owned by website-positioning
and worked out first; this guide reads it from POSITIONING.md and must stay
consistent with it — it does not redefine it. A quick "does this still read
clearly to a stranger" check on an already-built site is website-positioning-check,
not this guide — it's a read-only diagnostic, not a voice/EEAT audit.
Outputs
CONTENT_GUIDE.md (from the new-website skill's templates/content-guide.md)
— ToV rules, EEAT checklist, page inventory with target titles, per-page-type
copy templates, new-page checklist. Reads positioning/audience from POSITIONING.md.
POSITIONING.md is owned by website-positioning; this guide consumes it
and must not restate the positioning (single source of truth).
BRAND.md is owned by website-design-system, but its positioning line
comes from POSITIONING.md — keep them consistent. Each of its two parts, the palette and
the logo, has its own source: what the owner brought or chose at new-website §2b
(her own colours or logo, or the ones the optional website-brand-kit helped her to)
stands, and is not changed here. A part she neither brought nor wanted help with
keeps the starter's default until website-design-system fills it.
STORY.md (optional, owned by website-story): when present, the home page's
section order in the per-page-type copy template comes from its seven-section map.
The voice rules here apply unchanged.
How to use
- Positioning comes first:
website-positioning has already produced
POSITIONING.md (what you offer, for whom, the market category). Read it and
build the voice on top of it. Then pull insights: run customer-research for
ICP + voice-of-customer, and site-architecture if the topics and page hubs need planning.
Feed the findings in.
- Copy the template to
CONTENT_GUIDE.md and fill every [BRACKET].
- For actual page copy, hand off wording to
copywriting, then apply the voice
rules below and run the tone test.
Tone of voice — the hard rules (enforced by the tone test)
These mirror the tone guards proven on earlier production sites. The test is the source of
truth; the guide explains the why.
- No em dashes (—). Comma, period, or colon instead.
- Active voice; proof over claims.
- Exempt: genuinely quoted customer/human voice — wrap in
<blockquote>,
<q>, or add data-tov-exempt. Do not use this to smuggle brand copy past the
rules.
Role words (not checked by the tone test): where a page calls the reader by a role (owner,
user, client or member), say once, before the page first uses the word to say who does what, that
it means the reader. Call the people behind the site by name or "we", not by the same role word.
The rules below are lexical (specific words/mechanisms to avoid) and differ by
language — apply the subsection that matches the site's content language.
English content
- No contractions. Long form: "cannot", "it is", "you are", "we are".
- No buzzwords: supercharge, world-class, leverage, unlock, seamless, robust,
cutting-edge, empower, holistic, revolutionary, synergy, next-level (trim/extend
per brand).
- Speak to the reader as "you".
German content
English's "no contractions" rule has no German equivalent — German doesn't
contract "cannot" into "can't" the way English does, so there's no parallel
mechanism to enforce. The real formality lever in German is register:
informal "du" vs. formal "Sie" — and, more important than which one you
pick, staying consistent with that choice for the entire page. Mixing
"du" and "Sie" mid-page doesn't read as a stylistic choice; it reads as a
translation error.
- Pick du or Sie per brand, then hold it for the whole page. This is a
per-brand decision, not a universal rule — record the choice explicitly in
BRAND.md/CONTENT_GUIDE.md so every page follows the same one. A
community/consumer brand aiming for approachable and informal typically
picks "du" throughout; a B2B/enterprise or public-sector brand more often
picks "Sie" — either is fine as long as it's consistent.
- This is the German answer to "speak to the reader as 'you'" — the du/Sie
choice above settles it; don't treat "you" as a separate, unresolved
question for German copy. tone.spec.ts machine-checks the unambiguous
mixing cases (lowercase du-family vs. capitalized "Kontaktieren Sie ..."
imperatives on one page); subtler shifts still need a human read.
- No buzzwords: ganzheitlich, nahtlos, Synergie(n), Synergieeffekt(e/en),
bahnbrechend, revolutionär, wegweisend, erstklassig, hochmodern,
maßgeschneidert (Swiss spelling "massgeschneidert" is caught too — the
enforced test doesn't fold ß↔ss, so both spellings are listed explicitly),
zukunftsweisend, transformativ, unschlagbar, entfesseln/entfesselt,
Spitzenreiter (trim/extend per brand).
- AI-tell phrases to avoid:
- "In der heutigen ... Welt" (the enforced test tolerates up to two
modifiers and compound Welt-nouns like "Geschäftswelt")
- "Es ist wichtig zu betonen/beachten/erwähnen, dass..."
- "Zusammenfassend lässt sich sagen,..."
- "Lassen Sie uns / Lass uns / Lasst uns eintauchen / einen Blick werfen"
EEAT — build it in from the start
Google calls these signals E-E-A-T: Experience, Expertise, Authoritativeness and
Trust. It says E-E-A-T "itself isn't a specific ranking factor", but that "using a mix
of factors that can identify content with good E-E-A-T is useful", and that of the four
"trust is most important" (Google). Ship the signals, not just claims:
- Experience/Expertise: named authors with a real bio and a stable schema
@id; first-hand specifics and dates; inline citations on claim-heavy copy
(what a citation holds: Claims on the page, below).
- Authoritativeness:
sameAs profiles that actually resolve (LinkedIn,
GitHub, public register); Organization schema; corroborating external mentions.
- Trust: imprint/legal entity page, clear contact, privacy page, last-updated
timestamps, HTTPS, zero broken links.
Claims on the page. Give every figure what a reader needs to check it:
- Every figure carries its source, its date and what it counts: "120 clients since
2019", not "120+ happy clients"; a survey says who was asked and when.
- Name the seller. A study by a company that sells what it measures says so.
- Keep the finding apart from your conclusion: first what the source found, then
what the business takes from it.
- Put each figure in the
facts-check list (value, source, owner), so every page
says the same.
Do this for the reader's trust; don't promise that it raises AI citations.
The author/Organization/sameAs plumbing lives in website-seo-geo (schema) and
config.ts/SAME_AS; this skill decides what those signals should be.
Done means
CONTENT_GUIDE.md filled, voice consistent with POSITIONING.md and BRAND.md,
and the tone test green after any copy change (npm test runs tone.spec.ts).
1---2name: website-content-guide3description: >4 Create and maintain a new site's CONTENT_GUIDE.md and BRAND.md — Tone of Voice5 and EEAT (Experience/Expertise/Authoritativeness/Trust) signals — so every page6 hangs off one source of truth for HOW it says it. Reads positioning from7 POSITIONING.md (owned by website-positioning, which runs first); it does not8 redefine positioning. Use at the start of a new site (step 3 of the new-website9 pipeline, after website-positioning), before writing page copy, and whenever10 reviewing/editing copy for voice. Pairs with the tone test (tests/tone.spec.ts)11 which hard-enforces the voice rules. Trigger phrases: "content guide", "tone of12 voice", "brand voice", "is this on brand", "EEAT", "E-E-A-T", "write the content13 guide", "set up the brand doc", "review the copy", "does this sound like AI".14metadata:15 source: https://skillmd.com/skills/karero/website-content-guide16---1718# Website content guide & voice1920Owns the **how it says it** layer of a new site: tone of voice and EEAT signals,21captured in the per-site docs that everything downstream reads. **Positioning**22(what you offer, for whom, the market category) is owned by `website-positioning`23and worked out first; this guide reads it from `POSITIONING.md` and must stay24consistent with it — it does not redefine it. A quick "does this still read25clearly to a stranger" check on an already-built site is `website-positioning-check`,26not this guide — it's a read-only diagnostic, not a voice/EEAT audit.2728## Outputs2930- **`CONTENT_GUIDE.md`** (from the `new-website` skill's `templates/content-guide.md`)31 — ToV rules, EEAT checklist, page inventory with target titles, per-page-type32 copy templates, new-page checklist. Reads positioning/audience from `POSITIONING.md`.33- **`POSITIONING.md`** is owned by `website-positioning`; this guide consumes it34 and must not restate the positioning (single source of truth).35- **`BRAND.md`** is owned by `website-design-system`, but its positioning line36 comes from `POSITIONING.md` — keep them consistent. Each of its two parts, the palette and37 the logo, has its own source: what the owner brought or chose at `new-website` §2b38 (her own colours or logo, or the ones the optional `website-brand-kit` helped her to)39 stands, and is not changed here. A part she neither brought nor wanted help with40 keeps the starter's default until `website-design-system` fills it.41- **`STORY.md`** (optional, owned by `website-story`): when present, the home page's42 section order in the per-page-type copy template comes from its seven-section map.43 The voice rules here apply unchanged.4445## How to use46471. Positioning comes first: `website-positioning` has already produced48 `POSITIONING.md` (what you offer, for whom, the market category). Read it and49 build the voice on top of it. Then pull insights: run `customer-research` for50 ICP + voice-of-customer, and `site-architecture` if the topics and page hubs need planning.51 Feed the findings in.522. Copy the template to `CONTENT_GUIDE.md` and fill every `[BRACKET]`.533. For actual page copy, hand off wording to `copywriting`, then apply the voice54 rules below and run the tone test.5556## Tone of voice — the hard rules (enforced by the tone test)5758These mirror the tone guards proven on earlier production sites. The test is the source of59truth; the guide explains the *why*.6061- **No em dashes (—).** Comma, period, or colon instead.62- Active voice; proof over claims.63- **Exempt:** genuinely quoted customer/human voice — wrap in `<blockquote>`,64 `<q>`, or add `data-tov-exempt`. Do not use this to smuggle brand copy past the65 rules.6667**Role words (not checked by the tone test):** where a page calls the reader by a role (owner,68user, client or member), say once, before the page first uses the word to say who does what, that69it means the reader. Call the people behind the site by name or "we", not by the same role word.7071The rules below are lexical (specific words/mechanisms to avoid) and differ by72language — apply the subsection that matches the site's content language.7374### English content75- **No contractions.** Long form: "cannot", "it is", "you are", "we are".76- **No buzzwords:** supercharge, world-class, leverage, unlock, seamless, robust,77 cutting-edge, empower, holistic, revolutionary, synergy, next-level (trim/extend78 per brand).79- Speak to the reader as "you".8081### German content82English's "no contractions" rule has no German equivalent — German doesn't83contract "cannot" into "can't" the way English does, so there's no parallel84mechanism to enforce. The real formality lever in German is **register:85informal "du" vs. formal "Sie"** — and, more important than which one you86pick, staying **consistent** with that choice for the entire page. Mixing87"du" and "Sie" mid-page doesn't read as a stylistic choice; it reads as a88translation error.8990- **Pick du or Sie per brand, then hold it for the whole page.** This is a91 per-brand decision, not a universal rule — record the choice explicitly in92 `BRAND.md`/`CONTENT_GUIDE.md` so every page follows the same one. A93 community/consumer brand aiming for approachable and informal typically94 picks "du" throughout; a B2B/enterprise or public-sector brand more often95 picks "Sie" — either is fine as long as it's consistent.96- This *is* the German answer to "speak to the reader as 'you'" — the du/Sie97 choice above settles it; don't treat "you" as a separate, unresolved98 question for German copy. tone.spec.ts machine-checks the unambiguous99 mixing cases (lowercase du-family vs. capitalized "Kontaktieren Sie ..."100 imperatives on one page); subtler shifts still need a human read.101- **No buzzwords:** ganzheitlich, nahtlos, Synergie(n), Synergieeffekt(e/en),102 bahnbrechend, revolutionär, wegweisend, erstklassig, hochmodern,103 maßgeschneidert (Swiss spelling "massgeschneidert" is caught too — the104 enforced test doesn't fold ß↔ss, so both spellings are listed explicitly),105 zukunftsweisend, transformativ, unschlagbar, entfesseln/entfesselt,106 Spitzenreiter (trim/extend per brand).107- **AI-tell phrases to avoid:**108 - "In der heutigen ... Welt" (the enforced test tolerates up to two109 modifiers and compound Welt-nouns like "Geschäftswelt")110 - "Es ist wichtig zu betonen/beachten/erwähnen, dass..."111 - "Zusammenfassend lässt sich sagen,..."112 - "Lassen Sie uns / Lass uns / Lasst uns eintauchen / einen Blick werfen"113114## EEAT — build it in from the start115116Google calls these signals E-E-A-T: Experience, Expertise, Authoritativeness and117Trust. It says E-E-A-T "itself isn't a specific ranking factor", but that "using a mix118of factors that can identify content with good E-E-A-T is useful", and that of the four119"trust is most important" ([Google](https://developers.google.com/search/docs/fundamentals/creating-helpful-content)). Ship the signals, not just claims:120- **Experience/Expertise:** named authors with a real bio and a stable schema121 `@id`; first-hand specifics and dates; inline citations on claim-heavy copy122 (what a citation holds: **Claims on the page**, below).123- **Authoritativeness:** `sameAs` profiles that actually resolve (LinkedIn,124 GitHub, public register); Organization schema; corroborating external mentions.125- **Trust:** imprint/legal entity page, clear contact, privacy page, last-updated126 timestamps, HTTPS, zero broken links.127128**Claims on the page.** Give every figure what a reader needs to check it:129- **Every figure carries its source, its date and what it counts:** "120 clients since130 2019", not "120+ happy clients"; a survey says who was asked and when.131- **Name the seller.** A study by a company that sells what it measures says so.132- **Keep the finding apart from your conclusion:** first what the source found, then133 what the business takes from it.134- **Put each figure in the `facts-check` list** (value, source, owner), so every page135 says the same.136137Do this for the reader's trust; don't promise that it raises AI citations.138139The author/Organization/`sameAs` plumbing lives in `website-seo-geo` (schema) and140`config.ts`/`SAME_AS`; this skill decides *what* those signals should be.141142## Done means143144`CONTENT_GUIDE.md` filled, voice consistent with `POSITIONING.md` and `BRAND.md`,145and the tone test green after any copy change (`npm test` runs `tone.spec.ts`).