Content modelling
ACFACPTMeta BoxPodsJetEngineAdmin Site EnhancementsEtch
Build a content system
A publishing system. Not one blog 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.
Content system brief
This is the whole input.
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.
Paste into your AI client
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.One prompt from you becomes hundreds of typed ability calls from the agent, each one checked against your WordPress capabilities, the active safety profile and the confirmation rules before it runs.
What happens next
The run, step by step
Nothing here is a black box. Every step is a typed call you can see in the change log afterwards.
- 1
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.
- 2
Creates the post type and fields
Through whichever fields plugin you run: ACF, ACPT, Meta Box, Pods or JetEngine each have their own create-post-type, create-taxonomy and field-group abilities, with schemas read first.
- 3
Builds archive and single templates
Templates are bound to the fields rather than to typed-in text, so the hundredth post renders correctly without anyone opening the builder again.
- 4
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.
- 5
Sets per-post SEO and schema
Title, meta description and schema type per post through your SEO plugin's typed abilities. Global plugin settings are read-only. The agent cannot reconfigure Yoast or Rank Math behind your back.
- 6
Reports what it could not source
Claims without a supplied source come back as a list rather than appearing in the draft with a confident tone. That list is the editorial work only a human can close.
Plugins it can drive
It works with what you already run.
WPPilot Pro ships 53 integration families. A module only registers once its plugin is detected on the site and a Pro licence is active.
SEO
Yoast SEORank MathAIOSEOSEOPress
Templates
BricksDivi 5Oxygen 6BreakdanceEtchMosaicBeaver Builder
Translation
PolylangWeglot
Under the prompt
The abilities this run actually calls
Real registered ability names from the shipped plugin source. Each one has a schema, a permission check and a risk classification.
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
Where it stops
What stays yours.
Speed is only useful if you can trust the result. These are real constraints in the plugin source, not a disclaimer paragraph.
Read the security model- Global SEO plugin settings are read-only. The agent edits per-post and per-term SEO, schema and redirects. It does not reconfigure the plugin itself.
- Rank Math has no redirect abilities in the current module. Yoast, AIOSEO and SEOPress do.
- 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.
Questions
Build a content system, answered
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?
It cannot. There is no global settings writer for any of the four SEO plugins: only per-post metadata, per-term metadata, schema and, on three of the four, redirects.
Your site · your policy · your AI client
Send the brief. Get the blog and content system.
Install WPPilot Free to connect your AI client, then add Pro for the builder, commerce and plugin modules this run depends on.