Structured Data for Exporter Websites: A Practical Guide

Structured data is code that tells search engines what a page is about in a standard vocabulary (schema.org). For an exporter website, the useful core is small: Organization on your home or About page, BreadcrumbList on inner pages, and Product markup on product pages that match what buyers can actually see. Google does not guarantee that markup produces rich results, so treat it as clarity for machines, not a ranking shortcut.

01What is structured data, and why does an exporter need it?

Structured data is a block of machine-readable code, usually JSON-LD, that describes the page in the same terms every search engine understands: this is an organization, this is a product, this is a breadcrumb trail. Visitors never see it. Crawlers read it alongside the page text.

For exporters, the value is practical. A buyer in Kuala Lumpur or Houston who has never heard of your company will find you through a product search, then judge you in a few seconds. Structured data helps search engines connect your company name, logo, profiles and products into one consistent entity.

Two honest limits first:

• Structured data does not make a page rank higher by itself.
• Google says it "does not guarantee that your structured data will show up in search results".

02Which structured data types matter for exporter websites?

Not every schema.org type is worth your time. This table shows where we would start for a manufacturer or trading company.

03How should you mark up your company with Organization?

Organization markup is the foundation. It describes your company, not a single page.

Properties Google recommends include:

• name and alternateName, matching the name used on your site.
• url, logo and sameAs (links to your official profiles, such as a LinkedIn company page).
• contactPoint, with telephone and email. Phone numbers should include the country and area code.
• address, description, foundingDate and numberOfEmployees.
• Identifiers such as legalName, vatID and taxID.

A minimal example for an exporter looks like this. Replace every value with your own real details.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Machinery Co., Ltd.",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-machinery"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "sales",
    "email": "sales@example.com",
    "telephone": "+86-000-0000-0000"
  }
}
</script>

04How do you add BreadcrumbList to product and category pages?

A breadcrumb trail shows where the page sits, for example Home > Products > Hydraulic Presses > 200-Ton Press. On a catalogue with many categories, that trail also helps buyers move up one level.

• A BreadcrumbList needs at least two ListItem entries in itemListElement.
• Each ListItem needs position and name, plus an item URL. The last item can omit the URL, and Google then uses the page's own URL.
• Build the trail around a typical user path, "instead of mirroring the URL structure".
• Google says it does not guarantee that breadcrumbs will appear in results.

A short example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Products", "item": "https://www.example.com/products/" },
    { "@type": "ListItem", "position": 2, "name": "Hydraulic Presses", "item": "https://www.example.com/products/hydraulic-presses/" },
    { "@type": "ListItem", "position": 3, "name": "200-Ton Four-Column Press" }
  ]
}
</script>

05How do you mark up an industrial product page with Product?

Product markup is where exporters most often make mistakes, because B2B pages rarely look like retail pages.

1. Mark up what is on the page: product name, description and main image. Do not add a price if your page does not show one.
2. Do not add reviews or ratings unless they are real, visible to visitors and from genuine customers. Google's guidelines name fake reviews as an example of misleading markup.
3. Keep the markup in step with the page. If you change the model name or specification, change the code too.
4. Keep the page's visible specification table complete. Buyers and AI tools read the visible text first. Our industrial product page checklist shows what that table should contain.

A minimal Product example for a quote-based page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "200-Ton Four-Column Hydraulic Press",
  "description": "Four-column hydraulic press for metal forming. Request a quotation for configuration and lead time.",
  "image": "https://www.example.com/uploads/press-200t.webp",
  "brand": { "@type": "Brand", "name": "Example Machinery" }
}
</script>

06Is FAQ markup still worth adding?

Less than it used to be.

07Do you need special schema for AI search?

08What are Google's rules for structured data?

• Do not mark up content readers cannot see. The page should describe the same entities as the markup.
• The markup must truly represent the page. Do not mark up misleading or irrelevant content, such as fake reviews.
• Do not use structured data to impersonate people or organizations.
• Include all required properties for a rich result type. Recommended properties improve quality.
• Put the markup on the page it describes, and use the most specific schema.org types available.
• Do not block pages with structured data from Googlebot using robots.txt, noindex or other access controls.
• Structured data problems can lead to a manual action, which removes rich result eligibility.

09What are common structured data mistakes on exporter sites?

• Copying one block everywhere. The same Organization block pasted onto every page is unnecessary, and a product block copied between pages describes the wrong product.
• Markup that does not match the page. A product named in the code but not on the page, or a price that never appears.
• Invented reviews or awards. If you cannot show it on the page, do not mark it up.
• Translated pages with untranslated markup. On a multilingual site, update the name and description on each language version. Pair this with correct hreflang.
• Blocked pages. A page that Googlebot cannot access cannot use its markup.
• Never testing. Code that looks fine can contain a broken bracket.

10Structured data checklist for an exporter website

1. Add Organization markup to the home page or About page, with name, URL, logo, sameAs and a contact point.
2. Add BreadcrumbList to product and category pages, matching a visible breadcrumb.
3. Add Product markup to product pages, using only information visible on the page.
4. Remove or avoid any review, rating or price data that visitors cannot see.
5. Make sure every language version has its own correct markup.
6. Confirm the pages are not blocked by robots.txt or noindex.
7. Validate with the Rich Results Test and check pages with the URL Inspection tool.
8. Submit your sitemap and monitor Search Console for errors.
9. Review the markup whenever product names, logos or contact details change.

11Frequently asked questions

Does structured data improve Google rankings?

Google does not say it does. What it describes is eligibility for certain search features, and even that is not guaranteed. The reliable benefit is clearer understanding of your pages.

Which format should an exporter use, JSON-LD or Microdata?

Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD. It sits in one block, separate from the page layout, which makes it easier to maintain.

Can I add structured data to every page?

You can add the type that fits each page. Organization markup is not needed on every page. Google suggests placing it on the home page or one page that describes your organization.

Should I add review stars to my product pages?

Only if you have genuine reviews that visitors can see on the page. Google's guidelines name fake reviews as misleading markup.

Do I need special markup to appear in AI Overviews?

Google says no additional requirements or special optimizations are needed. Its guidance is to keep structured data matching visible text and keep pages indexed and eligible for snippets.

How do I test my structured data?

Use Google's Rich Results Test and the URL Inspection tool, then monitor the relevant reports in Search Console after launch.

12Next step

Structured data works best as part of a site built for global buyers: clear product pages, correct language versions and fast loading. Our website development service builds this into every project, and you can contact us for a review of your current markup.

Source: General structured data guidelines; Organization structured data; Breadcrumb structured data; Introduction to Product structured data; FAQ structured data; AI features and your website; Search Engine Journal: Google drops FAQ rich results.

Website • Oct 15, 2026

Product Page Checklist for Industrial Equipment Exporters

Website • Oct 10, 2026

An Independent Foreign Trade Website Is a Growth Hub, Not Just an “Official Site”

AI Search • Oct 15, 2026

The Era of AI Search Is Here: What Is GEO, and How Does It Differ from SEO?