Do copywriters need to learn Gutenberg to work in WordPress?

Yes, enough to map copy to blocks. Delivering a Google Doc that ignores Heading, List, Button, and Group structure creates rewrite tickets when the client pastes into the block editor.

Where should SEO titles and meta descriptions live in WordPress?

In the SEO plugin fields (Yoast, Rank Math, or AIOSEO)–not only in the post title. Copywriters own the focus keyphrase, SEO title, meta description, and slug; developers own schema templates.

Should I write directly in WordPress or in a draft doc?

Draft outside for strategy and claim sheets, then assemble in Gutenberg so you catch character limits, empty H2s, and button labels. Final QA always happens in the editor the client uses.

How does Human Writes fit a WordPress workflow?

Use it as one voice pass on stiff AI drafts after facts are locked–hero, service blurbs, blog body. Do not run it on shortcodes, HTML attributes, or legal footers.

Copywriter's Guide to WordPress CMS

WordPress still runs most client sites you will touch. The copy problem is not “learn SEO.” It is delivering text that maps to Gutenberg blocks, SEO plugin fields, and reusable patterns without forcing a developer to re-slice your Google Doc.

This guide is for freelancers and agencies who ship WordPress deliverables: service pages, homepages, blog posts, and landing pages built in the block editor (or classic + page builders). Treat Human Writes as the polish step after structure and claims are true–not a generator for entire sites.

What you actually edit in WordPress

Surface	Where copy lives	Your job
Block editor (Gutenberg)	Heading, Paragraph, List, Quote, Button, Columns, Cover	Map hierarchy to H1–H3; keep button labels short
SEO plugin	Focus keyphrase, SEO title, meta description, slug, OG title/desc	Fill every field; do not leave “auto from excerpt”
Featured image alt	Media library	Write alt that describes the image, not keyword stuffing
Menus / labels	Appearance → Menus or Navigation block	Match nav to page H1 language
Reusable blocks / patterns	Synced patterns, template parts	Write once; flag what is global vs page-local
Custom fields (ACF, Meta Box)	Field groups on pages/CPTs	Ask for field names and character limits before drafting

If the site uses Elementor, Divi, or Beaver, ask for a field inventory PDF or Loom of the editor. Builder widgets have different length constraints than core Gutenberg.

Gutenberg deliverable format clients accept

Do not hand over a wall of prose. Hand over a block map:

Page: /services/roof-repair
H1 (Heading block): …
Hero subhead (Paragraph, max ~160 chars): …
Primary CTA (Button): label + destination URL
H2 + body pairs (Heading + Paragraph/List)
FAQ (Details or Accordion pattern if theme supports it)
SEO title / meta / slug (paste into Rank Math or Yoast)

Rules that prevent revision loops:

One H1 per page (Heading block level 1)–theme may already inject title; confirm before duplicating.
Buttons are labels, not sentences. “Get a free estimate” beats “Click here to learn more about our services.”
Lists for scannable proof, paragraphs for argument. AI dumps both as paragraphs.
Never paste raw HTML into Paragraph blocks unless the client asked for Custom HTML. It breaks on theme updates.
Mark synced patterns (“This CTA strip is global–change once”) vs page-only sections.

SEO plugin fields copywriters own

Field	Practical limit	Tip
Focus keyphrase	1–2 phrases	Match search intent; do not force three synonyms
SEO title	~50–60 characters	Brand at end if space; primary phrase near front
Meta description	~140–160 characters	Benefit + proof + CTA verb; no keyword list
Slug	Short, hyphenated	Match service noun, not date or “best-ever”
OG title / description	Same discipline	Social share often differs from SERP

Write these in the same document as body copy. Clients who “will fill SEO later” rarely do.

For E-E-A-T and proof blocks that help informational posts, see humanize AI content for SEO and E-E-A-T.

Common WordPress page types and copy constraints

Page type	Block pattern	Watch for
Homepage	Cover/hero, logo strip, services grid, testimonials, CTA	Generic AI heroes; see homepage humanize
Service page	H1 + intro, process steps, local proof, FAQ, CTA	Keyword stuffing in every H2
About	Narrative + team cards	Invented bios and awards
Blog post	Title, intro, H2s, images, FAQ schema	Thin AI outlines; see blog workflow
Landing (paid)	Single CTA, short form, trust strip	Competing CTAs in every section

AI draft → WordPress ship workflow

Intake: voice sheet, banned phrases, proof assets, competitor URLs, Rank Math/Yoast access or screenshots.
Outline in the block map, not in ChatGPT-first paragraphs.
Draft body with facts only; mark [NEED FROM CLIENT] for missing numbers.
One voice pass in Human Writes on stiff sections (hero, intros, FAQ answers)–not on SEO titles if they are already tight.
Paste into Gutenberg; fix empty blocks, orphan H3s, and button destinations.
Fill SEO plugin fields; preview SERP snippet.
Client review in WordPress preview, not only Google Docs–layout changes meaning.
Disclose AI use if the SOW requires it (disclosure guide).

Agency volume: humanize at scale.

What breaks when copywriters ignore the CMS

Long Paragraph blocks inside narrow Columns → mobile overflow and “can you shorten this?” tickets.
H2s that are questions for SEO only with no answer below → thin content and bounce.
CTA buttons that say “Learn more” three times → heatmaps show no preference.
Testimonials rewritten by AI → clients notice their own quote changed; keep quotes verbatim.
Classic editor clients still exist–ask. Your Gutenberg map may need conversion to shortcodes or TinyMCE headings.

Checklist before you send the invoice

Block map delivered (or pages built in staging)
One H1; H2s describe real sections
Button labels + URLs verified
SEO title, meta, slug filled in the plugin
Featured image alt written
Synced vs local patterns labeled
Claims match client proof sheet
One humanize pass max on AI-stiff prose
Preview checked on mobile width

Bottom line

WordPress copywriting is block literacy plus field discipline. Structure for Gutenberg and SEO plugins first; use Human Writes only to fix rhythm after the facts and hierarchy are locked. That is how you stop rewriting the same homepage in Docs while the live site still says “Welcome to our website.”