Place a single Organization (or the most specific subtype such as OnlineStore or LocalBusiness) entity on your homepage or primary about page in JSON-LD
Include name, url, logo (as an ImageObject with URL, width, height), sameAs pointing to official social profiles and Wikipedia if present, and contactPoint for customer support channels
Add iso6523 or leiCode if applicable to help Google disambiguate your entity from organizations with similar names in knowledge graphs
Validate with the Rich Results Test; while Organization itself does not produce a standard rich result, errors here can affect knowledge panel population
Monitor your brand's knowledge panel in Search and report incorrect entity information via the feedback link to align Google's understanding with your structured data
Known gotchas
Organization structured data does not guarantee a knowledge panel and does not by itself produce a visual rich result in standard SERPs; its value is disambiguation and logo selection rather than a direct SERP feature
The logo property must reference a publicly accessible image URL; logos behind authentication or returning non-200 responses will not appear in search results even if the markup is technically valid
Do not place multiple conflicting Organization entities across different pages with different names or URLs; Google may use any of them and the inconsistency can confuse entity disambiguation
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp