Schema markup is structured data that describes the meaning of page content in a machine-readable format. For a service or personal website, useful types can include Person, Organization, LocalBusiness, Article or BlogPosting, BreadcrumbList, and other types that accurately match visible content and Google-supported features.
Good schema markup is boring in the best way: it tells the truth about what is already on the page. It should not invent a five-star rating, fake office, award, price, or author. Start with the page type and entity, add only properties you can support, validate the code, and keep it in sync when the visible page changes.
Schema markup should describe visible content
Structured data helps search engines understand entities and page types. Google supports many schema features, but not every schema.org property creates a special result. Use markup because it clarifies the page and may support eligible search features, not because you expect a guaranteed ranking boost.
If a page says the business is open from 9 to 5, do not put different hours in JSON-LD. If there is no visible review, do not add a made-up review object. Consistency is part of trust.
How to choose schema markup for a page
Ask what the page actually is. A blog article can use BlogPosting. A breadcrumb trail can use BreadcrumbList. A real business location may use the most specific LocalBusiness subtype. An author page can describe a Person. Avoid adding many unrelated types just because they exist.
Use Article or BlogPosting for real articles
Google’s Article documentation recommends useful properties such as headline, image, publication date, modification date, and author. Link the author to a real author or About page when possible. Keep dates honest; do not change dateModified every day just to make an old article look fresh.
On this blog, Article schema and BreadcrumbList are enough for normal posts. There is no need to add every possible creative-work property if it does not improve clarity.
Use LocalBusiness when a real local business is present
LocalBusiness markup can describe a physical or service business with details such as name, address, phone, hours, and URL. Use the most specific subtype that fits. If the site represents multiple real branches, each location needs accurate information.
For local visibility, schema is only one supporting layer. A correct Business Profile and useful local pages matter more. The local Maps SEO guide explains how these pieces connect.
Keep Person and Organization markup focused
A personal portfolio may use Person data on the About page or another clear identity page. An organization can use Organization markup with its name, URL, logo, contact details, and other supported properties. Google recommends placing organization details on a home or organization page rather than repeating a huge block everywhere.
Use sameAs only for profiles that genuinely represent the same person or organization. Do not add unrelated accounts simply to create more links in the markup.
Do not rely on outdated FAQ rich-result tactics
Visible FAQ sections can still be excellent for readers and answer engines, but Google announced that FAQ rich results would no longer appear in Search starting May 7, 2026. That means adding FAQPage markup to ordinary marketing articles just to chase a rich result is outdated.
Keep useful questions in the page when they help. For AEO and GEO, direct answers, clear entities, and good source context matter more than adding unsupported schema.
Validate schema markup before and after launch
Use Google’s Rich Results Test for Google-supported features and a schema validator for syntax and broader vocabulary. Check the live URL after deployment, not only a code snippet in development. A template error can affect many pages.
When a page changes, update the structured data too. If a phone number, author, business hour, or canonical URL changes, stale JSON-LD can create conflicting information.
Remember that schema is not a replacement for content
Structured data cannot rescue a weak page. Search engines still need useful visible text, crawlable links, correct status codes, and a clear user experience. Markup is a layer that explains, not a hidden content system.
Use the technical SEO checklist to verify the rest of the page. Strong schema markup works best when the underlying content and technical setup are already clean.
Common questions about schema markup
Does schema markup improve rankings?
Schema can help search engines understand content and can make pages eligible for supported rich features, but Google does not promise a ranking increase just for adding markup.
Is JSON-LD the best format?
Google supports JSON-LD for many structured data types and it is often easier to maintain because it is separate from visible HTML markup.
Should every page have LocalBusiness schema?
No. Add structured data where it accurately describes the page. Google notes that LocalBusiness markup can be placed on business information pages where it makes sense.
Final takeaway: schema markup
Schema markup should make the page easier to understand, not more impressive on paper. Choose the right type, match visible facts, use supported properties, validate the live page, and remove outdated tricks. When schema markup stays accurate and simple, it becomes a useful technical layer instead of maintenance debt.