Article and CreativeWork Schema

Your website probably has dozens of content pages. Blog posts, case studies, guides, landing pages. Each one is an opportunity to create a machine-readable connection between your entity, your topic, and your content. Most implementations waste this opportunity by deploying Article schema with nothing but a headline and a publish date.

That is like writing a book with no author name on the cover and no subject classification. The content exists, but it is disconnected from everything that matters for entity recognition.

The Content-Entity-Topic Chain

Effective Article schema creates a three-way connection: content to entity (who wrote this), content to topic (what is this about), and content to architecture (where does this fit in your body of work). When every article on your site carries these connections, you build a machine-readable topical map.

Each arrow in this diagram is a declared relationship that search engines can directly consume. The author property links the content to your Person entity. The about property declares the topic. The mentions property identifies entities referenced in the content. The isPartOf property places the article within your content architecture.

Key Article Properties for Recognition

The author Property: Do It Right

The author property is the most important link in the content-entity chain. It should not be a plain text string. It should be a reference to your Person entity, ideally using an @id that matches the Person entity declared elsewhere on your site.

"author": {
  "@type": "Person",
  "@id": "https://yoursite.com/#person",
  "name": "Jane Smith"
}

When the @id matches across your homepage Person schema, your About page Person schema, and every Article's author property, Google can consolidate all these signals into a single entity profile. Without the @id match, each author declaration might be treated as a separate, disconnected entity.

The about and mentions Properties

The about property tells search engines the primary subject of your content. Use it with a Thing or DefinedTerm type for stronger semantic signals than plain text.

"about": {
  "@type": "Thing",
  "name": "Entity SEO",
  "sameAs": "https://en.wikipedia.org/wiki/Search_engine_optimization"
}

The mentions property is different from about. It identifies entities that are referenced in the content but are not the primary subject. If your article about entity SEO mentions Google, Schema.org, and Jason Barnard, those are mentions. The distinction matters because about declares "this content covers this topic" while mentions declares "this content exists in the context of these entities."

The isPartOf Property: Content Architecture

The isPartOf property is underused but powerful. It declares that an article belongs to a larger work: a content series, a topic hub, or a publication. When 12 articles all declare isPartOf pointing to the same hub page, you are telling search engines "these 12 pieces form a comprehensive body of work on this topic."

Pair it with hasPart on the hub page pointing back to each article. This creates a bidirectional content hierarchy that mirrors your topical cluster architecture from Module 2.

CreativeWork Beyond Articles

Not all your content fits the Article type. Books use Book. Presentations use PresentationDigitalDocument. Videos use VideoObject. Courses use Course. All of these are subtypes of CreativeWork and support the same relationship properties: author, about, mentions, isPartOf.

If you have published a book, that Book schema with your Person as author and your core topic as about is one of the strongest content-to-entity signals you can deploy. A published book is a significant creative output, and declaring it in structured data makes it machine-readable.

Further Reading

• Article Type Documentation (Schema.org)
• CreativeWork Type Documentation (Schema.org)
• Article Structured Data (Google Search Central)
• Article Schema JSON-LD Guide (Unhead)