Schema Markup for WordPress Without a Paid Plugin

WordPress schema markup workflow using JSON-LD and validation without a paid plugin.

You do not need a paid SEO plugin just to add structured data to a WordPress site. In many cases, the markup itself is straightforward. The difficult part is deciding deve should be marked up, making sure it accurately describes the page, and avoiding duplicated or outdated schema that another plugin or theme is already generating.

That is why I prefer to treat schema as part of the wider SEO workflow rather than as another box to tick. Before adding anything, understand the page, check what WordPress is already outputting, add only the markup that genuinely belongs there, validate it, and then monitor the live page.

If you want to review the page before making changes, you can audit it with ActionSEO first. This can help you identify schema and structured-data opportunities alongside the rest of the page’s technical and on-page SEO signals.

First check what WordPress already outputs

Before writing a single line of JSON-LD, find out what is already there. WordPress sites often have several different systems contributing structured data at the same time: the theme, WooCommerce, an SEO plugin, a page builder, or custom code added in the past.

For example, your site may already be outputting Organization, WebSite, BreadcrumbList, Article ou Produto markup. Adding a second version of the same entity does not automatically make the page “more optimized”. In some cases, it simply creates duplicate or conflicting information that becomes harder to maintain.

Start by testing the live URL with Google’s Rich Results Test. Then inspect the page source and search for application/ld+json to see whether JSON-LD is already present.

You can also use the Schema.org Validator to inspect the structured data itself. The two tools answer slightly different questions: Schema.org’s validator checks Schema.org markup and syntax, while Google’s tool focuses on structured-data features supported by Google Search.

Use JSON-LD when you add custom schema

If you do need to add structured data manually, JSON-LD is usually the easiest format to manage. Instead of wrapping visible page elements in special attributes, the structured information sits inside a separate script block.

That makes it easier to read, update and troubleshoot — particularly on WordPress, where page layouts may be controlled by themes or builders that you do not want to modify every time the schema changes.

Depending on how widely the markup needs to appear, you could add JSON-LD through a code snippet, a theme/template, a custom field system, or a Custom HTML block. The best option depends on whether the schema belongs to one individual page or needs to be generated consistently across a whole content type.

The main rule is simple: do not create structured data that becomes disconnected from the visible page. If the content changes, the schema needs to change too.

Common schema types worth considering

You do not need every available Schema.org type. Start with the type that most accurately describes the content you actually have. A smaller, accurate implementation is more useful than a large block of markup added simply because a tool generated it.

  • Article or BlogPosting: useful for genuine editorial content such as guides, tutorials and blog posts.
  • Product: appropriate for real product pages where the product and relevant offer information are visible to visitors.
  • BreadcrumbList: describes the page’s position within the site’s navigational hierarchy.
  • Organization or Person: useful when the markup accurately represents the business, publisher or individual behind the content.
  • SoftwareApplication: appropriate when the page genuinely represents a software application and the information provided in the markup can be supported by the page.

Google supports particular structured-data features in Search, but that list is not the same thing as the complete Schema.org vocabulary. You can review Google’s current supported features in the structured data gallery.

Do not add schema because a checklist says so

This is where schema implementation often goes wrong. Someone reads that a certain markup type is “good for SEO”, a plugin offers a toggle, and the markup gets added whether or not it serves a real purpose.

FAQPage is a useful example of why this approach becomes outdated. For years, SEO guides recommended FAQ markup partly because Google could display FAQ rich results directly in Search. Google reduced that visibility over time and then discontinued the FAQ rich result feature entirely in May 2026.

That does not mean questions and answers suddenly became bad content. If an FAQ genuinely helps the visitor, keep it. The point is that you should not add FAQ markup today because an old checklist promises an expanded Google result that is no longer available.

Schema should describe the page honestly. It should not be treated as a way to manufacture search features that the page is not eligible for.

A safe implementation workflow

The safest way to add schema is to treat it like any other technical SEO change: understand the current state, make the smallest useful change, test it, and verify the live result. This reduces the chance of creating duplicate entities or leaving outdated markup behind months later.

  1. Identify the real page type.
    Decide what the page actually represents before choosing the markup.
  2. Check existing structured data.
    Look for schema already generated by WordPress, your theme, WooCommerce or an SEO plugin.
  3. Create the smallest accurate JSON-LD needed.
    Do not add properties merely because they exist in an example.
  4. Match the markup to the page.
    Important claims and entity information should be supported by the visible content or the actual entity being described.
  5. Validate the markup.
    Use Schema.org Validator for the structured data itself and Google’s Rich Results Test when you are working with a Google-supported search feature.
  6. Publish and inspect the live URL again.
    Validation before publishing is useful, but always verify the final rendered page.
  7. Request indexing only after the page is stable.
    There is little value in repeatedly requesting a crawl while you are still changing the markup.
  8. Monitor rather than forget.
    If your content, pricing, authorship or product information changes, check whether the structured data needs to change as well.

If you prefer to work through SEO changes in a sequence rather than changing everything at once, the Plano de ação de SEO para 14 dias can help you place structured-data work alongside the other technical and on-page foundations that should be checked first.

Example: simple Article JSON-LD

The example below shows the basic shape of Article structured data. It is intentionally simple. A real implementation may need additional properties depending on the page and the feature you are targeting.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your article title",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2026-11-03",
  "dateModified": "2026-11-03"
}
</script>

Do not copy this blindly. Replace the example values with real information, and add properties only when they are accurate and relevant. If your existing SEO plugin or theme already generates Article schema correctly, you may not need to add another Article block at all.

Schema is not a shortcut around the page itself

Structured data can help machines understand what a page represents, but it does not rescue weak content, unclear authorship, a poor product page or a technically broken site. The page still needs to do its normal SEO job first.

That is why I prefer to review schema in context. Check the page’s indexability, canonical, content structure, internal links and trust signals before treating JSON-LD as the priority. If the page has a bigger problem, fix the bigger problem first.

You can use ActionSEO to audit the page and review structured-data opportunities alongside technical, on-page, content and trust signals. Then add the markup that actually helps describe the finished page.

Final checklist

  • Check whether schema already exists before adding more.
  • Choose a type that genuinely describes the page.
  • Prefer maintainable JSON-LD for custom implementations.
  • Keep structured data synchronized with visible content.
  • Validate the markup before and after publishing.
  • Do not assume valid schema guarantees a Google rich result.
  • Do not follow old schema recommendations without checking whether the search feature still exists.
  • Revisit structured data whenever important page information changes.

Useful structured data resources

Carrinho de compras
  • Seu carrinho está vazio.
yourseoebook.com
Privacy Overview

Este site utiliza cookies para que possamos oferecer a você a melhor experiência de usuário possível. As informações dos cookies são armazenadas no seu navegador e executam funções como reconhecê-lo quando você retorna ao nosso site e ajudar nossa equipe a entender quais seções do site você considera mais interessantes e úteis.