Structured Data for a Small Business Blog: Article Schema That Helps, and What Google Retired (2026)

By PilotaSEO Editorial (GSPTeck) · Published 2026-10-30 · Last verified 2026-10-30

Does a small business blog need structured data?

It helps, but less than most plugins suggest, and it won't rank a weak post. Google says Article structured data (the types Article, NewsArticle and BlogPosting) can help it understand a page and show better title text, images and date information in results. Google's Article documentation lists no required properties: you add the recommended ones that apply, such as the headline, the author, the publish and update dates, and images. That makes a sensible setup small: one clean BlogPosting block per post, accurate dates, a real author, and good images. This guide covers what to include, what Google ignores or has retired, and a five-minute way to check your posts.

Based on Google Search Central documentation checked on 2026-10-30. Google doesn't guarantee that structured data will produce any rich result.

What structured data does, and doesn't, do

Structured data is code, usually JSON-LD in the page's HTML, that labels facts about the page: "this is the headline", "this person wrote it", "it was updated on this date". Google recommends JSON-LD, though it also supports Microdata and RDFa. Its general guidelines are clear on the limits: using structured data enables a feature to be present, it doesn't guarantee that it will be. Markup that misrepresents the page can lead to a manual action, which removes eligibility for rich results.

So treat it as accuracy work, not a ranking trick. The reason it matters for a small business blog is consistency: when your markup, your byline and your visible dates agree, Google has fewer reasons to guess. Whether to show those dates at all is covered in should small business blog posts show dates.

The properties worth adding

Google's Article documentation recommends these, and they cover almost every blog post:

• headline: the post title. Keep it consistent with your visible H1 and, ideally, your title tag.
• author: a Person or Organization, with author.name and author.url. Google asks that author.name contains only the name, not job titles or the publisher. List multiple authors separately.
• datePublished and dateModified: in ISO 8601 format, with a timezone. Only change dateModified when you've meaningfully updated the post.
• image: for best results, multiple high-resolution images (at least 50,000 pixels when you multiply width by height) in 16x9, 4x3 and 1x1 ratios. Our guide to image SEO for blog posts covers the rest.

A minimal BlogPosting example

This is the shape we'd use for a typical small business post. Replace the values with your own:

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to choose a boiler service plan",
  "datePublished": "2026-10-30T08:00:00+01:00",
  "dateModified": "2026-10-30T08:00:00+01:00",
  "author": [{
    "@type": "Person",
    "name": "Maria Rossi",
    "url": "https://example.com/about/maria-rossi"
  }],
  "image": ["https://example.com/img/boiler-16x9.jpg"]
}

The author.url should point to a real page about that person. If you don't have one, our post on whether author bios help SEO explains what to put on it.

What Google has retired or ignores

• FAQ rich results. Google's Search Central updates log lists the FAQ rich result as deprecated: it no longer appears in Google Search starting 7 May 2026. FAQ sections can still help readers; see do FAQ sections still help SEO. Leftover FAQ markup isn't a penalty, but don't expect extra lines in results.
• How-to rich results. Retired earlier; the documentation was removed because the result is no longer shown.
• Markup for things not on the page. Reviews, ratings or prices that readers can't see break Google's guidelines.
• Duplicate, conflicting blocks. Two plugins each adding an Article block with different dates or authors creates confusion. Keep one.

A five-minute check for your posts

1. Open one recent post and run it through the Rich Results Test. Fix critical errors.
2. Compare the markup's headline, author and dates with what readers see.
3. Make sure only one Article-type block exists per post.
4. Once a few pages are live, use the URL Inspection tool in Search Console to see how Google reads them.
5. Keep your sitemap submitted so updated posts get recrawled.

If someone else publishes your posts, including a done-for-you service like PilotaSEO, ask them which structured data they add and run the same five checks on a sample post. It takes a few minutes, and it tells you whether the dates, author and images that Google reads match what your readers see on the page.

Common mistakes we see on small business blogs

• Dates that never change, or always change. A theme that stamps today's date on every page load, or never updates dateModified after a real rewrite, makes the markup less useful. Dates should reflect real publishing and real updates.
• The business name as author on some posts and a person on others. Either can be valid, but be consistent, and use Organization when the author is the business.
• Images that don't match the post. Google says images in the markup must represent the marked-up content. A generic stock logo on every post isn't helpful.
• Markup on pages blocked from Google. Structured data on a page that's set to noindex, or blocked by robots.txt, can't be used. If a post isn't indexed at all, start with why a new blog post isn't indexed.
• Ignoring the visible page. Structured data describes the page; it doesn't replace a clear title, a byline, a visible date and a useful answer near the top.

Where structured data fits in your priorities

For most small businesses the order of work is simple. First, publish posts that answer real customer questions. Second, make sure they're indexed, linked from related pages, and listed in your sitemap. Third, tidy the technical layer: titles, canonical tags, images and structured data. Structured data sits in that third group. It's worth getting right once, in your theme or publishing setup, so every new post inherits it without anyone having to think about it again. After that, a quick check every few months, or whenever you change themes or plugins, is enough.

FAQ

Will structured data improve my rankings?

Not directly. Google says structured data helps it understand a page and makes features possible, but it doesn't guarantee any rich result or ranking change.

Should I use Article or BlogPosting?

Google supports both, along with NewsArticle. For a normal business blog post, BlogPosting is the natural fit.

Are there any required properties?

No. Google's Article documentation lists none; add the recommended properties that match your content.

Should I remove FAQ markup now that FAQ rich results are gone?

It's not urgent. It won't show as a rich result anymore, but keeping a helpful visible FAQ for readers is still fine.

How often should I check my structured data?

Check one post whenever you change your theme, plugins or publishing setup, and do a quick spot check every few months. Search Console's reports will also flag new errors for the structured data types Google supports, so keep an eye on those emails as well.

Sources

• Google Search Central: Article (Article, NewsArticle, BlogPosting) structured data (checked 2026-10-30)
• Google Search Central: General structured data guidelines (checked 2026-10-30)
• Google Search Central: Documentation updates (FAQ rich result deprecation) (checked 2026-10-30)