May 2026 field note
Structured data without the magic.
Structured data can describe a page more explicitly, but it should reflect the website’s visible facts—not make claims the page cannot support.
Schema is a structured description of what a page contains. It can make relationships clearer to search systems, but it cannot turn a weak or unsupported page into authoritative evidence.
Use structured data to describe, not persuade
Structured data can identify an organization, website, service, article, breadcrumb trail, event, product, or another supported type. It sits alongside the visible page; it does not replace clear writing, accessible HTML, internal links, or evidence.
Adding schema does not guarantee a rich result, ranking, recommendation, or AI citation. The safest rule is straightforward: if a visitor cannot find a material fact on the page, do not add that fact only to the markup. JSON-LD is often the easiest format to maintain, but accuracy matters more than the number of properties.
Choose types that match the page
- Organization for the business’s verified name, URL, logo, and public contact details
- WebSite for the site and its publisher relationship
- Service where a page describes a real published service
- CollectionPage for an archive such as Insights or selected work
- BlogPosting for an individual editorial article
- BreadcrumbList for a visible, logical path through the site
Reuse stable @id values so references point to the same organization and website entities. Do not create several slightly different versions of the business across pages. Choose the most accurate type, not the type that appears to offer the most elaborate result.
Mark up articles honestly
An Insights article can identify its headline, description, canonical page, representative image, language, author, publisher, and dates. The visible publication date should match datePublished. Set dateModified only after a meaningful editorial update, and show that update date to the reader.
Vloom Studio can be the Organization author and publisher because this site uses a company-led voice. A personal author should be used only when that person is visibly credited and the linked information is accurate. Relevant, crawlable article imagery can add context; an unrelated image should not be used merely to satisfy a property.
Avoid tempting but unsupported markup
Do not add review scores, testimonials, aggregate ratings, service areas, locations, prices, credentials, or awards unless they are accurate, visible, and approved. A location-neutral business should not invent an office or LocalBusiness location for perceived search value.
Visible question-and-answer sections can help readers, but most commercial sites should not expect FAQPage markup to produce Google FAQ rich results. There is also no special “GEO schema” required for Google’s generative search features. Standard, accurate markup remains part of the technical foundation.
Accurate markup can clarify an entity or page and create eligibility for supported search features. It cannot create missing facts or force a search engine or AI system to feature the page.
Validate before and after release
Validate syntax during development, then confirm that URLs resolve publicly, images are crawlable, dates match the page, and every material claim appears visibly. Inspect deployed URLs through Google’s Rich Results Test, Search Console, and Bing tools where appropriate.
Monitor template changes that can create invalid items or stale entity references. Structured data is maintained content. It should change when the underlying facts change—not whenever a new schema trend appears.
Learn about Vloom Studio, see how website scopes are defined, or explore the visibility snapshot.