Glossary

schema.org Dataset markup

schema.org Dataset markup is structured markup that publishers embed on dataset landing pages so crawlers recognize the page as a dataset; Google Dataset Search coverage.geographic records "any publicly reachable dataset page with schema.org Dataset markup". Datadory's catalog of 1,744 datasets documents it directly in Google Dataset Search coverage.geographic.

What is schema.org Dataset markup?

Structured markup that publishers embed on dataset landing pages so crawlers recognize the page as a dataset.

Google Dataset Search indexes exactly these pages and surfaces a license only when the markup declares one.

In this catalog it appears concretely: - Google Dataset Search coverage.geographic — "any publicly reachable dataset page with schema.org Dataset markup".

Why does schema.org Dataset markup matter when choosing a dataset?

Conventions decide whether two sources can be joined at all. Buy one side of an analysis that ignores this convention and every reconciliation step — calendar alignment, unit conversion, entity matching — lands on your team instead of the vendor's.

The failure mode is concrete: a source can carry the schema.org Dataset markup label while differing from what you need on exactly the dimension that matters — any publicly reachable dataset page with schema.org Dataset markup. Comparing two sources on that line usually settles the choice faster than any feature matrix.

You rarely have to take a vendor's word for it. 82.4% of the 1,744 datasets Datadory catalogs are free to access, and Google Dataset Search coverage.geographic lets you inspect the real artifact before any budget is committed.

How do you evaluate schema.org Dataset markup in a data source?

Treat every claim of this attribute as testable:

  1. Open Google Dataset Search coverage.geographic and confirm its record — "any publicly reachable dataset page with schema.org Dataset markup" — against the files you actually receive.
  2. Pin down update cadence in writing. Across this catalog, 22.6% of 1,744 datasets refresh daily and 64 still arrive only through a manual request form, so ask exactly how fresh each release is.
  3. Check whether definitions are verified at all. Field definitions are verified for 1495 of 1,744 datasets (85.7%), and any source you license should meet that bar.
  4. Price the delivery route before the license. In this catalog bulk download is the most common access method (725 datasets) ahead of official APIs (574), and 379 sources still require scraping — a maintenance cost that lands on you, not the vendor.

See the term applied to real records: computer-electronics-retail data, leisure-facilities data.

Adjacent concepts worth reading next: - dataset meta search - commercial delivery terms government data

Frequently asked questions

What is an example of schema.org Dataset markup?

Google Dataset Search coverage.geographic is the clearest example in this catalog. Its record states: "any publicly reachable dataset page with schema.org Dataset markup". Across all 1,744 datasets Datadory averages a quality score of 7.81 out of 10, so a named example can be weighed rather than trusted blindly.

Is data described as "schema.org Dataset markup" free to use?

Treat access and permission separately. 82.4% of the 1,744 datasets in this catalog are free to access, but 235 are freemium and 61 are paid outright, so confirm both the price and the license on the exact distribution before building on it.

Datasets containing this field

Datasets containing schema.org Dataset markup

6 datasets carry schema.org dataset markup in the catalog. Open one, count the fields, judge for yourself.

Every listing shows the field dictionary, sample rows, and coverage before you commit. API, files, or your warehouse. Daily, weekly, or hourly.

Get sample rows