How to add Article schema to blog posts
A step by step guide to adding Article schema to WordPress blog posts so AI engines can read who wrote what, when, and about what.
You published the post. You named the author, dated it, set a featured image. To a machine reading the page, none of that may exist.
A human sees the byline and the date because you laid them out visually. An AI engine reads the page differently. It looks for structured labels that say, in machine terms, this is an article, this person wrote it, it was published on this date. Without that layer, the engine has to guess from layout, and it often guesses wrong or not at all.
This guide is for the WordPress blog owner who wants engines to read who wrote what, when, and about what.
What Article schema actually does
Article schema is a small block of structured data that labels a post for a machine. It states the headline, the author, the publish and modified dates, the image, and the publisher.
It does not change how the post looks. It changes what a machine can say about the post with confidence instead of inference.
That distinction matters because engines weight what they can verify. A date they can read in structured form is stronger than a date they have to scrape from a sentence that might be a quote or a comment.
The task, step by step
Do not start by adding a block. Start by finding out what you already have.
1. See the current schema
Run the post through a structured data tester or a scan. If you run Yoast or Rank Math, you almost certainly already emit a base Article block. Adding a second one by hand is how you end up with two plugins describing the same page in two voices.
2. Find the gaps
Look for the fields that are missing or thin: author, dateModified, image, publisher. A common one is a real human author on the page who appears nowhere in the schema.
3. Add through your plugin, into one graph
Use your SEO plugin's own schema settings or filter so the new fields merge into the single graph already on the page. The goal is one clean, complete description, not competing blocks.
4. Describe what the post really is
If the post is a step by step guide or carries an FAQ, say so in the structure. An engine that reads only Article sees generic prose. An engine that reads Article plus HowTo or FAQ sees an answer to named questions.
Old way versus new way
The old way pasted a hand built JSON-LD block into a custom HTML widget and hoped it did not collide with what the SEO plugin already emitted. Two blocks, one page, a confused engine.
The new way enriches the graph your plugin already builds, through its official filter, so there is exactly one Article description of the post and it is complete. You add the missing fields without fighting the plugin you already trust.
The damaging admission
Article schema is plumbing. It does not make a weak post worth reading, and it does not make an engine cite you. It removes a reason the engine cannot attribute or parse your post cleanly.
If your post is thin or the author is anonymous and unverifiable, schema will faithfully report that thinness to the machine. It describes what is there. It does not invent credibility.
Where Citedon fits
Citedon's scan reads your post the way ChatGPT, Perplexity, Gemini, and Claude do and shows you whether the Article schema is present and complete, and what is missing.
Where it applies the missing layer, that is WordPress only, additively, through the connected plugin with per fix approval, and it merges into the same graph your SEO plugin already emits. It works with Yoast and Rank Math and does not fight them. On Shopify, Wix, or a headless setup the scan still diagnoses you, but you apply the changes yourself.
See whether your posts carry the schema an engine needs to attribute them. Run a free scan on a recent post and read what the graph is missing.