Organization (Organization) structured data
You can use organization structured data to let Google know about your organization's administrative details, for example, logo, address, contact information, and business identifiers. Google can make use of this markup in knowledge panels and other visual elements (such as attribution), which helps users to find your organization's details on Google Search.
How to add structured data
Structured data is a standardized format for providing information about a page and classifying the page content. If you're new to structured data, you can learn more about how structured data works.
Here's an overview of how to build, test, and release structured data.
- Add as many recommended properties that apply to your web page. There are no required properties; instead, add the properties that apply to your content. Based on the format you're using, learn where to insert structured data on the page.
- Follow the guidelines.
- Validate your code using the Rich Results Test and fix any critical errors. Consider also fixing any non-critical issues that may be flagged in the tool, as they can help improve the quality of your structured data (however, this isn't necessary to be eligible for rich results).
- Deploy a few pages that include your structured data and use the URL Inspection tool to test how Google sees the page. Be sure that your page is
accessible to Google and not blocked by a robots.txt file, the
noindextag, or login requirements. If the page looks okay, you can ask Google to recrawl your URLs. - To keep Google informed of future changes, we recommend that you submit a sitemap. You can automate this with the Search Console Sitemap API.
Examples
Organization
Here's an example of organization information in JSON-LD code.
<html>
<head>
<title>About Us</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"image": "https://www.example.com/example_image.jpg",
"url": "https://www.example.com",
"sameAs": ["https://example.net/profile/example1234", "https://example.org/example1234"],
"logo": "https://www.example.com/images/logo.png",
"name": "Example Corporation",
"description": "The example corporation is well-known for producing high-quality widgets",
"email": "contact@example.com",
"telephone": "+47-99-999-9999",
"address": {
"@type": "PostalAddress",
"streetAddress": "Rue Improbable 99",
"addressLocality": "Paris",
"addressCountry": "FR",
"addressRegion": "Ile-de-France",
"postalCode": "75001"
},
"vatID": "FR12345678901",
"iso6523Code": "0199:724500PMK2A2M1SQQ228"
}
</script>
</head>
<body>
</body>
</html>
OnlineStore with return policy (example subtype of Organization)
Here's an example of online store information in JSON-LD code.
<html>
<head>
<title>About Us</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "OnlineStore",
"name": "Example Online Store",
"url": "https://www.example.com",
"sameAs": ["https://example.net/profile/example12", "https://example.org/@example34"],
"logo": "https://www.example.com/assets/images/logo.png",
"contactPoint": {
"contactType": "Customer Service",
"email": "support@example.com",
"telephone": "+47-99-999-9900"
},
"vatID": "FR12345678901",
"iso6523Code": "0199:724500PMK2A2M1SQQ228",
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": ["FR", "CH"],
"returnPolicyCountry": "FR",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 60,
"returnMethod": "https://schema.org/ReturnByMail",
"returnFees": "https://schema.org/FreeReturn",
"refundType": "https://schema.org/FullRefund"
}
... // Other Organization-level properties
}
</script>
</head>
<body>
</body>
</html>
Guidelines
You must follow these guidelines to enable structured data to be eligible for inclusion in Google Search results.
Technical guidelines
We recommend placing this information on your home page, or a single page that describes your organization, for example the about us page. You don't need to include it on every page of your site.
We recommend using the most specific schema.org subtype of Organization
that matches your organization. For example, if you have an ecommerce site, then we recommend using the
OnlineStore subtype instead of
OnlineBusiness.
And if your site is about a local business, for example a restaurant or a physical store, then we
recommend providing your administrative details using the most specific
subtype(s) of LocalBusiness
and following the required and recommended fields for Local business
in addition to the fields recommended in this guide.
Structured data type definitions
Google recognizes the following properties of an
Organization.
To help Google better understand your page, include as many recommended properties that apply
to your web page. There are no required properties; instead, add the properties that apply to
your organization.
| Recommended properties | |
|---|---|
address |
The address (physical or mailing) of your organization, if applicable. Include all properties that apply to your country. The more properties you provide, the higher quality the result is for users. You can provide multiple addresses if you have a location in multiple cities, states, or countries. For example:
"address": [{
"@type": "PostalAddress",
"streetAddress": "999 W Example St Suite 99 Unit 9",
"addressLocality": "New York",
"addressRegion": "NY",
"postalCode": "10019",
"addressCountry": "US"
},{
"streetAddress": "999 Rue due exemple",
"addressLocality": "Paris",
"postalCode": "75001",
"addressCountry": "FR"
}]
|
address.addressCountry |
The country for your postal address, using the two-letter ISO 3166-1 alpha-2 country code. |
address.addressLocality |
The city of your postal address. |
address.addressRegion |
The region of your postal address, if applicable. For example, a state. |
address.postalCode |
The postal code for your address. |
address.streetAddress |
The full street address of your postal address. |
alternateName |
Another common name that your organization goes by, if applicable. |
contactPoint |
The best way for a user to contact your business, if applicable. Include all support methods available to your users following Google recommended best practices. For example:
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+9-999-999-9999",
"email": "contact@example.com"
}
|
contactPoint.email |
The email address to contact your business, if applicable.
If you are using a |
contactPoint.telephone |
The phone number to contact your business, if applicable.
Be sure to include the country code and area code in the phone number.
If you are using a |
description |
A detailed description of your organization, if applicable. |
duns |
The Dun & Bradstreet DUNS number for identifying your |
email
|
The email address to contact your business, if applicable. |
foundingDate |
The date your |
globalLocationNumber |
The GS1 Global Location Number identifying the location of your |
hasMerchantReturnPolicy
|
The return policy used by your |
iso6523Code
|
The ISO 6523 identifier of your organization, if applicable.
The first part of an ISO 6523 identifier is an
|
legalName |
The registered, legal name of your |
leiCode |
The identifier for your |
logo |
A logo that is representative of your organization, if applicable. Adding this property can help Google better understand which logo you want to show, for example in Search results and knowledge panels. Image guidelines:
If you use the |
naics |
The North American Industry Classification System (NAICS) code
for your |
name |
The name of your organization. Use the same |
numberOfEmployees |
The number of employees in your Example with a specific number of employees:
"numberOfEmployees": {
"@type": "QuantitativeValue",
"value": 2056
}
Example with the number of employees in a range:
"numberOfEmployees": {
"@type": "QuantitativeValue",
"minValue": 100,
"maxValue": 999
}
|
sameAs
|
The URL of a page on another website with additional information about your organization,
if applicable. For example, a URL to your organization's profile page on a social media or
review site. You can provide multiple |
taxID
|
The tax ID associated with your |
telephone
|
A business phone number meant to be the primary contact method for customers, if applicable. Be sure to include the country code and area code in the phone number. |
url
|
The URL of the website of your organization, if applicable. This helps Google uniquely identify your organization. |
vatID
|
The VAT (Value Added Tax) code associated with your |
MerchantReturnPolicy
Use the following properties to describe general return policies for your entire Organization, if applicable to your business.
If you have specific policies for individual products, use
merchant listing markup instead.
| Required properties (choose the option that best suits your use case) | |
|---|---|
| Option A | |
applicableCountry |
The country code that the return policy applies to, using the two-letter ISO 3166-1 alpha-2 country code formatting. You can specify up to 50 countries. |
returnPolicyCategory |
The type of return policy. Use one of the following values:
If you use |
returnPolicyCountry |
The country where the product has to be sent to for returns. This country can be different from the country where the product was originally shipped or sent to. ISO 3166-1 alpha-2 country code formatting. You can specify up to 50 countries. |
| Option B | |
merchantReturnLink |
Specify the URL of a web page that describes the return policy. This can be your own return policy, or a third-party policy from a service that handles the returns. |
| Recommended properties | |
|---|---|
customerRemorseReturnFees |
A specific type of return fee if the product is returned due to customer remorse.
See |
customerRemorseReturnLabelSource |
The method by which the consumer obtains a return shipping label for a product.
See |
customerRemorseReturnShippingFeesAmount |
The cost of shipping for returning a product due to customer remorse. This property
is only required if there's a non-zero shipping fee to be paid by the consumer to return a product.
See |
itemCondition |
The acceptable conditions of an item which can be returned. You can provide multiple conditions which are accepted. Use the following values:
|
itemDefectReturnFees |
A specific type of return fee for defect products. See |
itemDefectReturnLabelSource |
The method by which the consumer can obtain a return shipping label for a product.
See |
itemDefectReturnShippingFeesAmount |
The cost of shipping for returning a product due to defect products. This property
is only required if there's a non-zero shipping fee to be paid by the consumer to return a product.
See |
merchantReturnDays |
The number of days from the delivery date that a product can be returned. This
property is only required if you set the |
refundType |
The type of refund(s) available for the consumer when returning a product.
|
returnFees |
The default type of return fee. Use one of the following supported values:
|
returnLabelSource |
The method by which the consumer can obtain a return shipping label for a product. Use one of the following values:
|
returnMethod |
The type of return method offered. This is only recommended if
|
returnPolicySeasonalOverride |
A seasonal override of a return policy to specify return policies for special events, such as holidays.
For example, your usual return policy category is set to
"returnPolicySeasonalOverride": {
"@type": "MerchantReturnPolicySeasonalOverride",
"startDate": "2024-11-29",
"endDate": "2024-12-06",
"merchantReturnDays": "10"
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow"
}
|
returnPolicySeasonalOverride.endDate |
The end date of the seasonal override. |
returnPolicySeasonalOverride.merchantReturnDays |
The number of days from the delivery date that a product can be returned. This
property is only required if you set the |
returnPolicySeasonalOverride.returnPolicyCategory |
The type of return policy. Use one of the following values:
If you use |
returnPolicySeasonalOverride.startDate |
The start date of the seasonal override. |
returnShippingFeesAmount |
The cost of shipping for returning a product. This property is only required if there's a
non-zero shipping fee to be paid by the consumer to the merchant to return a product, in which case |
Alternative approach to configuring return settings with Google
Retailer return policies can get complicated and may change frequently. If you're having trouble indicating and keeping your return details up-to-date with markup and have a Google Merchant Center account, consider configuring your return policies in Google Merchant Center Help.
Troubleshooting
If you're having trouble implementing or debugging structured data, here are some resources that may help you.
- If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.
- Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the General Structured Data Guidelines.
- You might have an error in your structured data. Check the list of structured data errors and the Unparsable structured data report.
- If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix structured data issues, use the Manual Actions report.
- Review the guidelines again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues.
- Troubleshoot missing rich results / drop in total rich results.
- Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the Google Search crawling and indexing FAQ.
- Post a question in the Google Search Central forum.