跳至正文
B2B 外贸与询盘转化 · Google SEO

B2B Structured Data: Choose the Right Types for Products, Articles and Company Pages

// / / 光算科技

Choose B2B structured data from the page's actual content and the search feature you want to support. Company information, articles, products, services, videos and events serve different purposes. A type existing in Schema.org does not mean Google offers a dedicated rich result for it, and valid markup does not guarantee display, rankings or AI citations.

Separate vocabulary, eligibility and appearance

There are three checks. First, does the data use a valid format and appropriate vocabulary? Second, does it meet the requirements for a Google-supported feature? Third, has that feature actually appeared for the page? Passing the first two does not establish the third.

Google's general guidelines require markup to represent the page and explain that automated tools cannot easily judge all quality requirements. Use those rules alongside the documentation for the particular feature.

Map types to real page tasks

Page or contentType to considerInformation to verify
Company identityOrganization or a suitable subtypeReal name, identity, contacts and relevant administrative details
Site nameWebSite on the home pageConsistent name and home-page URL
Article or company newsArticle, BlogPosting or NewsArticleActual authorship, subject, images and dates
Navigation hierarchyBreadcrumbListA meaningful path and working destinations
Specific productProduct with applicable offer or review informationThe exact item and genuine data for the intended feature
Consulting or maintenance serviceAn appropriate Service descriptionReal scope; no assumed generic Service rich result
Watchable videoVideoObjectActual video, thumbnail, title and publication information
Public eventEvent when current requirements are metReal dates, location and public participation conditions

A page can contain several connected items, such as an article, its video and a breadcrumb trail. Model their real relationship rather than adding types to increase a count. Consult the Google feature gallery before claiming a search appearance is supported.

Organization and WebSite: describe identity consistently

The current Organization documentation has no universal required-property list; it recommends relevant information about the organization. Place it on the home page or a page describing the organization rather than assuming it must be repeated everywhere.

sameAs identifies pages that genuinely represent the same entity. Google does not require at least three social profiles. Its logo guidance includes a minimum of 112 by 112 pixels, but this is not a universal square-only or PNG-only rule and does not guarantee a knowledge panel. Choose a more specific subtype only when it accurately describes the organization.

Site-name guidance uses WebSite on the domain or subdomain home page, with the site name and home-page URL. Update the existing node where one already exists. Do not confuse this supported purpose with the retired sitelinks search box.

Articles and breadcrumbs: represent authorship and navigation

Article guidance recommends applicable information such as authors, images and dates rather than treating every listed field as mandatory. Use the real author and publication date. Record a meaningful modification when it occurs; do not reset the original date merely to make the article look new. “1200 × 630” is not a universal required size for all Article markup.

BreadcrumbList should describe a useful user path, which need not reproduce the URL's directory structure. Google's requirements include at least two ListItem entries and the applicable name, position and destination information. Check that the hierarchy makes sense and that each link reaches the intended page.

Quote-only products: do not invent an offer

A product can be described truthfully without a public price; eligibility for a product rich result is a separate question. Product snippets require the name and at least one qualifying review, aggregateRating or offers property. Merchant listings target purchasable products and have their own offer requirements.

Hypothetical example: an A100 machine is quoted for a particular application and has neither a public price nor an eligible review. This JSON describes the fictional product only. It is deliberately not a complete Google product-rich-result example, and its placeholder identity must not be deployed for a real item.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "A100 example",
  "sku": "EXAMPLE-A100"
}

A price of zero means zero, not “contact us.” InStock cannot substitute for unknown availability, and a rating cannot be fabricated to remove a warning. If a genuine qualifying product review exists, evaluate that route against its requirements. For the surrounding content and purchase journey, see the ten product-page SEO checks.

Reviews, videos and events need their own checks

Review guidance requires review information about a specific item to be available to users. It prohibits fake or undisclosed incentivized reviews and says not to aggregate ratings from other websites. When an organization controls reviews about itself on its own site, its Organization or LocalBusiness pages are ineligible for the self-serving star-review feature, including through third-party widgets. Do not extend that specific rule into a blanket prohibition on genuine product reviews.

The current required VideoObject properties are name, thumbnailUrl and uploadDate; duration is recommended. contentUrl points to the actual video file and embedUrl to the player, not an arbitrary article URL. Check access and the applicable video-search requirements as well as field presence.

The current Event search-experience rules require public participation eligibility and a physical location. Virtual-only events without a real-world component are not supported by that experience. Business hours, sales promotions and invitation-only events are not interchangeable with eligible public events. Schema.org's ability to describe an online event is a separate matter.

Account for retired Google features

  • FAQ rich results: Google's update log states that they stopped appearing on May 7, 2026. The earlier restriction to government and health sites is not the complete current rule.
  • How-to rich results: the September 2023 update extended removal to desktop. An older mobile-versus-desktop distinction is no longer a deployment opportunity.
  • Sitelinks search box: Google removed it starting November 21, 2024. Other sitelinks and the site-name use of WebSite are different features.

Keep useful answers, instructions and site search for readers. A retired appearance does not require deleting useful content, and relabeling it as another unrelated type does not restore eligibility.

Implement from a field map, then verify the published page

  1. Inventory existing output. Identify what the theme, SEO plugin, commerce system and custom code already generate. Locate conflicting prices, identities and dates before adding another block.
  2. Map each field to a maintained source. Product identity comes from product records; prices and availability from the actual offer; authors and dates from editorial records. Resolve missing facts instead of inventing values.
  3. Test the appropriate layer. Use Schema.org validation for vocabulary and structure, and Rich Results Test for currently supported Google features. Neither certifies the underlying claims.
  4. Read back the public result. Inspect delivered and rendered HTML, resource access and the content available through URL Inspection. Saving code is not evidence that the public page has changed.
  5. Monitor separate outcomes. Deployment, technical validity, indexing, actual appearance, clicks and qualified inquiries are different states. Compare equivalent reporting groups rather than averaging unrelated CTR percentages.

If Search Console reports a manual action, read its specific type and scope. Google's general guidelines state that a structured-data manual action removes rich-result eligibility and does not itself affect ordinary web-search rankings. Other spam or page-quality issues require their own diagnosis. An absent rich result alone does not prove a penalty.