Task Library
Publish a finished Content Factory article on the client's WordPress site in the Gutenberg block editor with clean formatting, ready for categorization, SEO, and distribution.
Category: Content Factory – Post
Use this when an article has cleared Process (Steps 1-11: written, photographed, linked, video-embedded, proofread) and is ready to go onto the site.
Inputs
- Final proofread article with title, headings, hook, photos, internal links, and embedded source video
- WordPress editor access to the target site with the Gutenberg block editor enabled
- Unique featured image file (real photo, never stock) plus all in-article photos
- The article's GCT (Goals, Content, Targeting) established in Step 3
Steps
- Create a new Post (not a Page) and build the article in the Gutenberg block editor – never Cornerstone or any proprietary builder; builder content is opaque to AI agents and hard to update programmatically.
- Rebuild the structure in blocks: one H1 (the title), H2s for major sections, H3s for subsections, short paragraphs (2-4 sentences), active voice, no AI-fluff phrases.
- Confirm the primary keyword appears in the first paragraph (Blog Posting Guidelines requirement).
- Insert every image at its planned position with descriptive alt text; set the unique featured image. All photos real – zero stock imagery.
- Embed the source video where Step 10 placed it and confirm it plays in preview.
- Verify every internal link from Step 9 survived the paste: descriptive 3-6 word anchor text (never "click here"), targets per the entity-linking decision tree (people → personal sites, companies → company sites, concepts → definitive articles).
- Set the permalink slug: short, lowercase, contains the focus keyword.
- Save as draft, preview on desktop and mobile, fix any broken blocks or image overflow. Do not publish yet – Steps 13-14b, author check, SEO Tree placement, and the Blog Posting checklist gate publication.
Definition of done (QA checklist)
- Post exists as a draft in Gutenberg with zero builder shortcodes; previews cleanly on desktop and mobile
- H1/H2/H3 hierarchy correct; paragraphs short; active voice; primary keyword in first paragraph
- All images real with alt text; unique featured image set; source video embedded and playing
- All internal links intact with 3-6 word descriptive anchors following the entity-linking decision tree
- Permalink contains the focus keyword
- Linked back to the definitive article and relevant siblings
- Complies with Blog Posting Guidelines (if it publishes content)
Example(s)
- First documented run candidate: a Marko Sipila (HVAC Quote) one-minute-video article posted through this step. Example needed – run the Meta-Article Prompt after first real run.
Learned in the field
Appended automatically by the self-improvement loop (Skill-Learnings/): dated lessons from real runs. Newest at the bottom.
<!– learning:2026-07-18-verify-published-not-just-posted –> July 18, 2026 (from: skill-pack-propagation follow-up session with Dennis, July 18, 2026)
After any REST publish, verify the LIVE rendered result, not just the 200 response: fetch the public URL cache-busted and confirm the new date/link/text actually renders (Elementor pages cache their own copy in _elementor_data and can ignore REST content writes; edge caches can serve stale HTML). A 200 from wp-json is a receipt that WordPress accepted the write – not proof a visitor sees it. July 18, 2026: standing rule promoted into this skill from the pack-propagation run.
File in the zip: skills/content-factory-post/step-12-post-article-on-wordpress.md. Download the Task Library zip.
Index: Task Library. Article guidelines.