Build a content system
Build an AI blog content system for WordPress. The machinery, not one post.
Most AI writing tools stop at the draft. This builds the machinery underneath: the post type and field group the content lives in, the taxonomy that organises it, the archive template that displays it, and the per-post SEO metadata and schema that make it findable.
Free: Elementor and blocks; Pro: advanced and additional modules, Draft content; review shared changes separately, All build briefs
PROJECT TYPE: CONTENT SYSTEM
FIELDS PLUGIN: [ACF / ACPT / META BOX / PODS / JETENGINE]
SEO PLUGIN: [YOAST / RANK MATH / AIOSEO / SEOPRESS]
CONTENT TYPE: [ARTICLES / GUIDES / CASE STUDIES / RECIPES / NEWS] about [SUBJECT].
MODEL: Propose the post type, its supports, and a field group covering [FIELDS]. Show me the model and wait for approval before creating it.
TAXONOMY: [TAXONOMY NAMES] with initial terms [TERMS]. Hierarchical or flat, say which and why.
TEMPLATE: Build the archive and single templates in [BUILDER], bound to the fields above rather than hard-coded text.
EDITORIAL RULES: House style is [STYLE]. Every post needs [WORD RANGE], [STRUCTURE], and a named source for any claim.
SEO: Set per-post title, meta description and schema type. Do not touch global SEO plugin settings.
DRAFTS: Create posts as drafts. I publish.
SOURCES: Every factual claim needs a supplied source. Unsourced claims are [CONFIRM] and stay out of the draft body.Content models are hard to change once posts exist. Get the agent to propose the model and wait for your approval before it creates anything.
What happens next
One brief, many typed calls
Nothing here is a black box. Each step is a separate ability call, checked against the connected user's WordPress capabilities, the safety profile and the confirmation rules before it runs.
Start on staging. A draft page does not isolate shared menus, templates, styles, taxonomy, access or delivery settings: inspect affected routes and approve those changes separately. These briefs describe planned calls, not completed runtime tests; verify saved data, the native editor and rendered output before launch.
Abilities this run calls
acf-create-post-typeacf-create-taxonomyacf-create-fieldgroupacf-get-fieldgroup-schemametabox-create-post-typejetengine-create-post-typepods-create-cptcreate-postcreate-termassign-termsset-featured-imageyoast-edit-post-seorank-math-edit-post-seoaioseo-edit-post-schemaseopress-create-redirect
Registered names from the shipped plugins. Schemas and descriptions are in the ability reference.
Proposes the model before building it
Post type, supports, field group, taxonomy, described first, created after you agree. Retro-fitting a field group onto two hundred existing posts is the expensive mistake this step prevents.
Creates the post type and fields
Use the installed fields module for its supported post types, taxonomies and field groups. Operation names, edition gates and schemas differ across ACF, ACPT, Meta Box, Pods and JetEngine; inspect that module before creating the model.
Builds archive and single templates
Bind supported template controls to the reviewed fields, then preview representative records, including missing values. A binding needs saved-data and rendered checks; adding later posts can still expose template or query gaps.
Writes drafts into the model
Posts are created as drafts with their taxonomy terms assigned and featured images attached. Draft is the default in the source, not a setting you have to remember.
Sets per-post SEO and schema
Title, meta description and supported schema operations through the installed SEO module. Its settings readers are read-only; a separately authorized execute-php call under Developer Full Access can change global settings. This brief excludes that developer path and requires review of exact fields, edition and recovery limits.
Reports what it could not source
Ask for unsourced claims in a separate review list and exclude them from the draft. Review the actual draft against supplied evidence; this instruction does not enforce model compliance.
Scope
What it drives, and where it stops
GoBuildWP Pro ships 89 integrations. Pro modules require an active GoBuildWP Pro licence and the supported plugins installed on your site. Check feature-specific version and edition gates in the linked references; Free Elementor and block-editor basics have separate coverage.
Plugins this brief can drive
- Content modelling
- ACF, ACPT, Meta Box, Pods, JetEngine, Admin Site Enhancements, Etch
- SEO
- Yoast SEO, Rank Math, AIOSEO, SEOPress
- Templates
- Bricks, Divi 5, Oxygen 6, Breakdance, Etch, Mosaic, Beaver Builder
- Translation
- Polylang, Weglot
Where it stops and asks you
- This brief excludes global SEO configuration. The dedicated settings readers do not write it, but a separately authorized Developer Full Access operation can. Review supported per-post/per-term metadata, schema and redirects against the installed module and edition.
- Redirects are written in the plugin that owns them: Rank Math, Redirection, AIOSEO, SEOPress or Yoast Premium. A SEOPress redirect GoBuildWP created or edited can be rolled back; deleting one is permanent. Rank Math, Redirection, AIOSEO and Yoast Premium keep redirects in their own storage, so the change ledger records those writes as irreversible.
- Posts are created as drafts. Publishing is an explicit instruction with its own capability check.
- AI-written volume is not a strategy. The useful pattern is a strong model plus reviewed drafts, not a hundred near-identical pages with a keyword swapped.
- Content modelling changes are structural. Deleting a post type or field group is destructive and needs explicit confirmation.
The editorial loop around the model
What an AI blog content system for WordPress looks like after launch
The brief above builds the structure. The part that decides whether a blog keeps going is the weekly loop that runs on top of it: someone proposes topics, a draft is written into the model, an editor reviews it in the place they already work, it is published by a person, and the archive is checked for decay. An agent can take a share of every step except the judgement calls, and GoBuildWP gives each step a named, logged action rather than a pasted block of text.
Think of three roles. The agent drafts and checks. The editor decides what is true and what fits the house style. The publisher, often the same editor, presses publish. Keeping those apart is what stops an AI-assisted blog drifting into volume for its own sake.
Review inside the block editor with Notes
On WordPress 7.1 or newer, review does not have to happen in a chat window. The free add-block-note leaves a Note on a single block of a draft, shown in the editor's Notes sidebar beside that block and labelled as written by an AI agent. Use it the other way round from what you might expect: let the agent flag its own doubts, such as a statistic it could not source or a paragraph that needs a quote, so the editor sees each question in place.
When the editor replies, list-block-notes reads the threads back, with each note's block, status and replies, and the agent can act on answered threads. Notes are feedback, not commands; the agent acts on them only when you ask it to work through the review. Adding a note makes a revision but changes nothing else in the content, and undoing a note is refused once a person has replied, so a conversation is never erased from under the editor.
One post through the system, step by step
A single well-sourced post is usually a sitting of drafting and an editor's pass, not a click. Budget for the editor's time in the plan, because that is the step that makes the post worth publishing.
- search-content checks whether the site already covers the topic, so the new post links to existing ones instead of competing with them.
- create-post makes the draft in your content type; acf-write-values (or the fields plugin you run) fills the structured fields such as summary, sources and reading level.
- create-term and assign-terms file it under the taxonomy you agreed; set-featured-image attaches an image you supplied or approved.
- yoast-edit-post-seo or its Rank Math, AIOSEO, SEOPress counterpart sets the title and meta description for this post only; these per-post editors are in the free edition.
- add-block-note marks anything the editor must decide, and the post stays a draft until a person publishes it.
Keeping the archive healthy
Old posts rot quietly: links break, meta descriptions go missing, and pages nobody links to sit unread. audit-content, in the free edition, checks published content for broken internal links, orphans, thin pages, missing SEO meta and schema problems, and audit-content-status reads a background audit's findings worst first. routines-save can run that audit weekly with no agent connected and email the report to administrators you choose.
Fixing is the Pro step. content-fix-plan turns a finished audit into a list of concrete changes with before and after previews and a confidence for each, and content-fix-apply carries out the ones you approve. For SEO fields at scale, seo-bulk-update-meta sets titles and descriptions on up to a hundred posts per call through the active SEO plugin, with a dry run first and a ledger row per post.
When an edit needs undoing
Most per-post writes in this loop keep a before-image: an ACF value on a post, a term assignment, or an SEO title in Yoast, Rank Math or SEOPress can be rolled back with rollback-change, and a drafting session with undo-session when none of its targets changed since. The exceptions are worth knowing before you rely on them. Field values on terms, users or options pages are recorded as irreversible. Pro's All in One SEO writes and term SEO in Rank Math or SEOPress are too, and the bulk SEO writer marks All in One SEO rows the same way. Redirects depend on the plugin: a SEOPress redirect GoBuildWP created or edited can be rolled back, while deleting one is permanent, and Rank Math, Redirection, AIOSEO and Yoast Premium redirects live in those plugins' own storage, so the ledger records them as irreversible. Note those writes down, or export the affected meta before running them.
Questions
Build a content system: questions
Does it write the posts as well as the system?
It can draft them, and drafting is the least valuable part. The durable win is the model, taxonomy, templates and SEO wiring. That is what makes the next two hundred posts cheap to publish.
Can it publish automatically on a schedule?
Posts land as drafts by design. If you want scheduled publishing, set the status explicitly and keep a human in the approval path. That is a deliberate choice you make, not a default the agent takes.
Which fields plugin works best?
ACF and ACPT have the widest ability coverage, including options pages. Meta Box, Pods and JetEngine are all supported for post types, taxonomies and field groups. Use whichever your site already runs.
Will it mess up my existing SEO configuration?
This brief changes supported per-item metadata, schema and redirects rather than promising harmless SEO changes. Inspect the installed module's exact fields and edition in the reference. Preserve canonical and robots values unless separately approved, preview every affected redirect URL, retain before values, and verify saved fields and rendered tags. Recovery covers only supported writers and cannot reverse crawling, indexing or external effects.
Send the brief. Review the blog and content system.
Install GoBuildWP Free for the connection and supported Elementor/block basics. Add eligible Pro when the selected task needs advanced or additional builder, commerce or plugin operations; inspect each module's dependencies.