1. Home
  2. Blog
  3. Search Engine Optimization (SEO)

Mark Up WordPress Articles in One Connected Schema Graph

Search engines can infer a lot from HTML. AI assistants deciding whether to name you as a source need something clearer: this page is an article, published on this date, by this person, who belongs to this organization, which is the same entity as these social accounts. Rankify’s schema settings are built around that idea of WordPress article schema inside a single connected graph, which is what Google recommends and what AI crawlers parse most reliably.

This guide focuses on WordPress article schema inside that graph: the free site-wide Schema Markup controls, Organization or Person identity, and the Pro advanced types (including Article) you select per post when you want rich-result eligibility. It stays inside Rankify’s Schema docs and free and Pro tables, and it links out to the How-To schema walkthrough for step-by-step content.

What Rankify outputs by default

Open Rankify > Settings > Schema.

  • Schema Markup (default on). Outputs JSON-LD for the site, posts, pages, and authors as one connected graph rather than separate blocks.
  • This Site Represents. Choose organization (default) or person. Everything else in the graph attaches to that site-level entity.
  • Name. The name used in the site-level entity. It defaults to your site title, but they are often different: the site might be “The Widget Blog” while the organization is “Widget Co Ltd”.
  • Advanced Schema Types (Pro, default on with Pro). Adds per-post schema selection with the fields each type needs: Article, Product, Recipe, Event, FAQ, How-To, Course, and Job Posting.
  • Organization Logo. Square, at least 112 by 112 pixels, on a solid background. Google requires a logo of at least that size for organization rich results.
  • Sitelinks Search Box (default on). Declares that your site has its own search so results can include a search box. Google decides whether to show it.

Settings keys include schemaMarkup, schemaSiteType, schemaSiteName, schemaSiteLogo, and schemaSitelinksSearch. Per-post SEO values (title, description, canonical, robots, social overrides, and schema type) live in post meta in the Rankify editor panel, not only in the site option.

Why “one graph” beats a pile of blocks

Many themes, page builders, and SEO plugins emit their own schema. Two graphs describing the same page create ambiguity: search engines may pick the wrong one or ignore both. Rankify’s docs tell you to view source and search for application/ld+json. You should find one connected graph, not several disconnected blocks.

The connected approach also matters for AI. A crawler that sees explicit relationships between Organization, WebSite, WebPage, Article, and Author has less guesswork than one that sees five unrelated scripts. Rankify’s product positioning on the site page matches the docs: one @graph with Organization, WebSite, WebPage, Article, and Author cross-referenced.

That is the difference between being a page that mentions a topic and being a source with an identity attached. Identity is what an assistant needs before it will name you.

Free and Pro for schema

From Rankify’s free and Pro table under search fundamentals:

FreePro
Schema markup as one JSON-LD graphAdvanced schema types, per post
Organization or Person site identityNews sitemap
Sitelinks search boxVideo sitemap
Breadcrumbs with BreadcrumbList markupLocal SEO and locations
Open Graph tags and X cards
Fallback share image and social profiles

So the connected graph and site identity are free. Choosing Article (or Recipe, Event, FAQ, How-To, Course, Job Posting, Product) with the full per-post field set is Pro via Advanced Schema Types. How-To rich results are covered in the related guide on How-To schema. This post stays on the article and identity layer.

Pro is part of the DaftPlug membership. See pricing.

Set site identity before you worry about Article fields

Organization or Person

Choose Person for a personal blog, portfolio, or consultant trading under their own name. Choose Organization for anything with a business name, even a one-person business. Getting this wrong makes every attached node point at the wrong kind of entity.

Name and logo

Set Name to the legal or brand name you want recognized, not necessarily the witty site title. Upload a square logo at least 112 by 112 on a solid background. Soft, transparent logos that disappear on light SERP chrome waste the field.

Social profiles become sameAs

On Rankify > Settings > Social, your official accounts become sameAs links on the site entity. Rankify has fields for X, Facebook, Instagram, LinkedIn, YouTube, and Pinterest. Only list accounts you control and use. A dead 2016 account adds nothing; pointing at an account that is not yours is worse than leaving the field empty.

The Schema docs call this out: social profiles strengthen everything else on the tab because they confirm the site and those accounts are the same organization. That confirmation matters for AI assistants judging whether you are a nameable source.

Sitelinks search box

Leave it on unless you have a reason not to. Declaring it does not guarantee a SERP search box; it mostly appears for brand-name searches. It costs little and documents that your site has search.

Using Article schema on a post (Pro)

With Advanced Schema Types on, open a post and use the Rankify panel to select Article (or the type that matches the content). Fill the fields that type requires. Markup makes a page eligible for rich results; it does not guarantee them.

Rankify’s rules for rich results:

  1. The content has to match the markup. Marking a page as a Recipe when it is a blog post about food does not make it a recipe. Mismatched markup can be ignored or penalized.
  2. Required fields are required. The Rich Results Test names missing fields.
  3. Google chooses when to show them. Correct markup on a page that ranks poorly still shows nothing, because there is no result to enrich.

For ordinary blog posts and news-style articles, Article is the honest type. Do not force How-To or FAQ markup onto a narrative post just because those types feel “more SEO.” Use FAQ blocks when you truly have questions and answers, and How-To when you truly have steps.

Check your work

  1. Google Rich Results Test at search.google.com/test/rich-results. Paste a URL. It reports eligible rich result types and errors.
  2. Schema Markup Validator at validator.schema.org for the whole graph, not only Google’s subset.
  3. View source and search for application/ld+json. Confirm one connected graph.
  4. If another plugin or the theme also outputs schema, deactivate the duplicate source. Two graphs are worse than one complete graph.

Competing plugins and leftover data

If you are migrating from Yoast, Rank Math, or similar, Rankify can read many stored values as a fallback for titles, descriptions, and social fields. Schema is still something you should validate on the live HTML after the switch. Do not assume two SEO plugins can both emit JSON-LD peacefully. Run one.

Practical rollout for an editorial site

  1. Enable Schema Markup if it was ever turned off.
  2. Set Organization or Person, Name, and logo.
  3. Fill active social profile URLs on the Social tab.
  4. Purge caches and test the homepage and a representative post in Rich Results Test.
  5. On Pro, open your top ten posts and set Article (or the correct type) with complete fields.
  6. Add How-To or FAQ only where the content format matches.
  7. Re-test those URLs after publish.

Article fields teams usually forget

When you select Article on a Pro post, fill the human facts before you chase exotic properties:

  • Headline that matches the visible H1 closely enough that a crawler does not see two different titles.
  • Author that maps to a real Person node already in the graph, not a display nickname with no profile.
  • Dates that match what WordPress stores for published and modified times.
  • An image that is actually on the page. Pointing schema at a CDN URL that 404s wastes the field.

If your authors publish under guest accounts without bios, fix the author profiles first. Article markup that points at empty Person nodes is weak identity, which undercuts the AI naming story Rankify is built around.

How schema interacts with titles, social, and sitemaps

Schema does not replace title templates or Open Graph tags. Each layer answers a different consumer:

  • Title and meta description templates shape the search snippet text.
  • Open Graph and X cards shape the preview when someone pastes a link into a chat or feed.
  • JSON-LD schema shapes how machines classify the page and its relationships.

Keep them aligned. A social title that contradicts the Article headline is a small inconsistency for humans and a larger one for systems that read both. Rankify’s Social tab can set a fallback share image for pages without featured images; use it so homepage and pricing shares are not bare text links.

Sitemaps list URLs you want indexed. Schema describes what those URLs are. Noindexed types should stay out of the sitemap (Rankify’s default “Leave it out” behavior for noindexed content). Listing a noindexed Article URL in the sitemap sends a contradictory signal.

Editorial workflow you can hand to writers

  1. Write the post until the format is clear (narrative article, steps, Q&A, product).
  2. Pick the schema type that matches that format, not the type that “sounds more SEO.”
  3. Complete required fields in the Rankify panel before scheduling.
  4. Add taxonomy so related content systems and internal tools have something to latch onto.
  5. After publish, paste the URL into Rich Results Test once for template-changing posts (new layouts, new author types).

Writers should not edit raw JSON-LD. If a field is missing, fix it in the panel or the site identity settings.

FAQ

Is the connected graph free?

Yes. Schema markup as one JSON-LD graph, Organization or Person identity, and sitelinks search box are on the free side of Rankify’s table.

Is Article schema free?

Per-post advanced types including Article are Pro under Advanced Schema Types. The free graph still describes posts and authors at the site level; Pro adds the richer per-post type fields that rich results expect for specific formats.

Can I emit Article and How-To on the same URL?

Only if the content honestly supports both. Prefer one primary type that matches the page. See the How-To guide for step content.

What if my theme already prints schema?

View source. If you see multiple application/ld+json blocks that duplicate Organization or Article, disable the theme’s output or Rankify’s, not both left on. Rankify’s docs warn that search engines may pick the wrong graph or ignore both.

Wrap up

WordPress article schema works best when it sits inside one connected graph with a correct Organization or Person at the root, real sameAs profiles, and honest per-post types on Pro. Turn Rankify’s Schema Markup on, set identity carefully, validate with Rich Results Test and view source, and only then chase specialized types like How-To or FAQ where the content earns them.

Explore Rankify for the full SEO and GEO toolkit, or compare membership plans on the pricing page.