Before installing another schema plugin, inspect what your WordPress site already produces. A theme, SEO plugin or custom integration may be describing the same page. The first job is to understand that output and make it accurate.
Structured data gives information an explicit format. Google recommends JSON-LD where it is practical, but adding more properties is not the same as making a page more useful or qualifying it for every search feature. Introduction to structured data.
Practical Rule
Start with the page you have, identify the markup already present, and correct its factual details. Use validation to find supported-feature issues. Do not add a second article object simply because a checklist says every post needs schema.
What We Found on SeoNative
On 19 September 2026, we inspected the JSON-LD exposed by SeoNative’s public homepage and Start Here page. The following is an inventory of the output. It is not a completed Rich Results Test or proof that Google has processed the markup.
| Page | Observed Objects | Editorial Question |
|---|---|---|
| Homepage | WebSite, CollectionPage and a publisher-related Person object | Does the publisher identity accurately describe who operates the site? |
| Start Here | WebSite, WebPage, Article and identity objects | Does Article accurately describe this guide, and are the author details suitable for readers? |
| Start Here author | An email address used as the name | Should the public byline and connected identity use a clearer editorial name? |
We have intentionally omitted the address from this article. The useful lesson is the mismatch between an account identifier and a public author identity. A technically readable value can still be a poor editorial choice.
The presence of several objects does not automatically mean a conflict. A website, a page and the article on that page describe related things. Follow their identifiers and references before deleting anything. Google’s policies allow multiple relevant items on a page and explain how connected items can refer to each other. Structured data policies.
Choose a Type That Describes the Content
For an editorial article, review the Article documentation and the applicable Article, NewsArticle or BlogPosting type. Google currently lists recommended properties rather than required properties for this feature. Add the properties you can supply accurately, including appropriate author details, dates, headline and representative images. Google’s Article documentation.
That is not a reason to invent an image, author credential or publication date. If the post has no suitable image yet, arrange a real asset and check its suitability before adding it. If a page is a navigation hub, consider its actual function rather than choosing an article type only because it is available in a dropdown.
Keep the language in your own checklist precise. “JSON parses” means the syntax can be read. “The test recognizes an Article” means the testing tool recognizes that item. Neither statement means an enhanced search result will be displayed.
Give the Markup a Clear Owner
- Open one representative public article and inspect its structured data. Record the types, identifiers and the fields that need attention.
- Identify the component that generates each object. In our setup, Rank Math is active, so its settings are a sensible place to investigate; plugin presence alone does not establish every object’s source.
- Correct the underlying page, author or publisher information where it belongs. Prefer maintaining a fact once when your configuration can reuse it.
- Reload the public page and check the output again. A saved setting is only half the task.
- Use Google’s Rich Results Test for supported search features and review both errors and the meaning of any warnings.
For a draft, validate the intended markup separately if necessary, then repeat the check against the public URL after publication. A test of copied code cannot prove that the live page serves the same code to every visitor.
Review Facts, Not Just Green Indicators
| Field or Relationship | Check Against |
|---|---|
| Headline | The article readers actually see |
| Author | The real public byline and relevant author information |
| Publisher | The actual person or organization responsible for the publication |
| Publication and modification dates | The real publication history and meaningful edits |
| Image | A relevant, accessible asset with appropriate rights |
| Main page and identifiers | The intended page URL and connected objects |
Keep visible content and markup aligned. Google’s quality rules require the structured data to represent the page and prohibit misleading material. Passing a syntax check does not override those requirements or guarantee a rich result. Quality requirements.
Keep a Small Verification Note
After a change, record the URL, date, generator, relevant fields and validation outcome. If you change the public author name, check both the visible byline and the structured data instead of assuming one edit updated everything. If cached output remains, investigate the serving layer before adding duplicate code.
For SeoNative, the next identity decision belongs in the publication review: confirm the public author and publisher, then check their visible and structured representations. The existing markup gives us something concrete to review; it does not justify inventing an editorial identity.
Continue with the technical checks in Start Here when the problem involves page output, redirects or conflicting signals. Schema maintenance works best as a small part of a clear publishing workflow.
Validate the Markup You Actually Publish
Schema is most useful when it accurately describes visible page content. Before adding another schema type, inspect what your theme and SEO plugin already output. WordPress plugins may add WebSite, Organization, Article, Breadcrumb, FAQ, or other structured data automatically, and layering a second system on top can create duplicate or conflicting markup.
After changing structured data, test the final public URL rather than relying only on a plugin preview. Check that the markup references the correct page, author or organization information and that required properties are present for any search feature you are targeting. A technically valid block is not automatically useful if it describes information the reader cannot see or if the page itself does not satisfy the feature’s content requirements.
Keep schema maintenance simple: know which plugin or template owns each type, avoid duplicating ownership, and revisit the output after major theme or SEO-plugin changes. The goal is a clean machine-readable description of the page, not the largest possible collection of schema types.
Watch the Topic in Context
Structured Data for Beginners
Martin Splitt explains what structured data is, how to add it, and how to check whether it works. That makes it a strong visual companion to the article’s practical WordPress schema setup.
Watch on YouTube ↗ · Google Search Central