Stable @id
Use a persistent identifier such as https://example.com/#organization. Other nodes can reference this ID instead of duplicating the complete organization object.
Name and URL
name should contain the real company name and url the official site. Do not confuse Organization.url with a product or service page URL.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Organization example"
}
Contacts
telephone and email should match published contact information. When a company has multiple departments, ContactPoint can be clearer than taking an arbitrary phone number.
Address
PostalAddress separates locality, streetAddress, postalCode and country. Do not add a physical address when no reliable public address exists.
Logo
logo should point to a crawlable image of the company logo, preferably using an absolute HTTPS URL.
Relationships
WebSite.publisher, Article.publisher and Service.provider can reference Organization by @id, making the graph more compact and meaningful.
Common questions
Can structured data always be improved to 100% automatically?
Only when the required data actually exists in the JSON-LD or on the page. A tool should not invent prices, authors, ratings, addresses or other values.
Should every possible Schema.org property be added?
No. A smaller set of accurate properties is better than irrelevant or fabricated values.