WordPress structured data adds search-engine–readable markers to a page’s code. They can specify that content is an article, identify its author, or describe the breadcrumb trail. However, they don’t replace good content or normal indexing.
The risk arises when a plugin or manual addition declares information that’s missing, outdated, or exaggerated. A perfectly valid JSON-LD can therefore still be misleading. The right approach is to mark up only what the page actually demonstrates, then verify the result before and after publishing.
What structured data can do, and what it doesn’t promise
Structured data typically uses the Schema.org vocabulary to name a page’s elements. Google often recommends the JSON-LD format because it’s simpler to integrate and maintain. However, Google’s documentation remains the reference for which properties can have an effect in its search results.
Compliant markup can make a page eligible for certain rich displays. It never guarantees their appearance. Google chooses a result’s presentation based on several factors, including the query, context, and the perceived quality of the page. See the’Google introduction to structured data before targeting a specific display.
In other words, don’t add WordPress structured data to «force» stars, a date, or a rich snippet. Add it to accurately describe useful information that’s already present for your readers.
Choose the type that truly describes the page
Start with each page’s primary function. For an editorial site, a few types are often sufficient. It’s better to publish a small amount of complete, accurate data than to multiply types without justification.
Articles and blog posts
For an editorial publication, Article or BlogPosting may be appropriate. This markup can specify the headline, relevant image, publication date, modification date, and author. Google states that the Article type helps it better understand pages for articles, news, or blog posts.
Each value must match the published page. Don’t declare a modification date if you haven’t changed anything. Don’t list an organization as the author if an individual wrote the piece. If multiple authors are visibly present, the markup must include them all. Google’s guidelines for Article structured data detail, among other things, the proper identification of authors.
The breadcrumb trail
One BreadcrumbList is appropriate when the site displays a true breadcrumb trail or logical hierarchy. The marked path should reflect a reader’s usual route, not merely copy the URL mechanically. For example, an editorial category followed by the article may be relevant if it’s actually used for navigation.
Before adding it, make sure your categories and navigation links also serve visitors. A coherent WordPress internal linking strategy helps maintain a comprehensible path. Google’s breadcrumb guidelines require at least two items in marked breadcrumb markup and recommend representing a typical path to the page.
Organization and author
Data Organization are used to describe the entity behind the site. They’re more appropriate on the homepage or on a page that actually presents the organization. Do not invent an address, phone number, social profile, or logo to fill optional fields.
Similarly, an author profile page deserves markup only if it actually presents that person and their role. An author name must lead to a consistent identity across content, profile pages, and structured data.
The central rule: all marked information must be true and visible
Google requires that structured data accurately reflect the content of the page. Information hidden from readers, irrelevant, or misleading may prevent rich results from appearing. In some cases, a structured data issue may also lead to manual action against those rich results.
So use this simple check for each added property:
- Is the information displayed to a reader on this page?
- Is it accurate today, without approximation?
- Does it describe the main subject of the page?
- Could you justify it if a reader compared it to the visible content?
A negative answer is enough to remove or correct the property. The general Google rules on structured data emphasize visibility, relevance, accuracy, and keeping information up to date.
Common mistakes to avoid
- Adding fake reviews: never create an aggregate rating or testimonials in markup if the page does not present real corresponding reviews.
- Using an overambitious type: an explanatory article is not automatically a recipe, an event, a course, or a Q&A page.
- Keeping expired data: check dates, prices, availability, contact details, and authors after each major change.
- Marking off-topic content: markup should describe the main item, not a brief secondary mention in the text.
- Duplicate the JSON-LD: an SEO plugin, a theme and a custom add-on can all produce markup. Check the rendered code before enabling a second source for the same type.
Implementing markup in WordPress without losing control
An SEO plugin can generate structured data from the title, author, featured image and site settings. This automation is useful only if the WordPress fields are well maintained. Fix the source information first rather than editing the JSON-LD page by page.
If you add custom code, work in a test environment and keep a backup copy. Then view the published page’s source code and look for application/ld+json. That way you can see the blocks actually sent to search engines.
Also check that the page remains indexable. Good markup doesn’t make up for a directive noindex, a protected access or a misconfigured canonical. If needed, reread how using noindex in WordPress without removing an important page and how to control a WordPress canonical URL.
Validate before and after publishing
Validation is done in two stages. First, test the content or URL in Google’s recommended Rich Results Test. Fix critical errors and review warnings. This test mainly confirms the technical structure and expected properties for supported features.
Then publish a few representative pages and use URL Inspection in Search Console to check what Google can crawl. Google also recommends monitoring the rich results status reports after deployment, since a theme, template or plugin change can alter the rendered markup.
To access these checks and interpret site reports, start by adding your WordPress site to Google Search Console. Finally, recheck a page after any change to the post template, author, categories or your SEO plugin.
WordPress structured data works best when it stays modest, verifiable and aligned with the page. Your goal is not to fill every possible field. It is to provide precise signals your site can maintain over time.









