Implement Dataset structured data correctly, understanding it only affects Google Dataset Search and not general Search rich results
domain: developers.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add Dataset JSON-LD with required properties name and description on the dataset's canonical landing page
Add recommended properties like url, sameAs, citation, distribution (with contentUrl/encodingFormat), and license to improve Dataset Search discoverability
Validate the markup with the Rich Results Test or the schema.org validator
Verify the property in Search Console so the crawled page can be associated with the Datasets report
Scope expectations correctly: this markup surfaces the dataset only in datasetsearch.research.google.com, a separate product from general Google Search
Known gotchas
Dataset structured data produces no rich result or special treatment in regular Google Search — its only surface is Dataset Search
Because of that narrow scope, don't budget organic-traffic impact for Dataset markup the way you would for Product or Recipe markup
The dataset must be freely downloadable/accessible as described, or usage restrictions must be declared via license/usageInfo, or it risks exclusion
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?