Submitting Fonteum datasets to Google Dataset Search + DCAT-US 3.0
The list below documents surfaces intended to emit schema.org/Dataset JSON-LD. Inspect the rendered response and current submission rules before relying on a listing. This page is an operator runbook, not proof that a crawler indexed a surface.
Dataset surfaces
8 surfaces emit Dataset JSON-LD. The /data surface aggregates the entries represented by that catalog in DCAT-US 3.0 format. Its coverage is incomplete relative to the active production source registry.
- https://fonteum.com/dataDataCatalog
DCAT-US 3.0 aggregate catalog for the dataset entries represented by this surface. It is not a complete enumeration of the active production registry.
- https://fonteum.com/researchDataCatalog (per-study Dataset entries)
Catalog of published research entries represented by the current research registry. A study page can emit its own Dataset record when that page supplies the required metadata.
- https://fonteum.com/freshnessDataset + 6 DataFeed
A six-feed healthcare subset, not the full active production registry. It exposes available row-count observations and dates for the feeds represented there; a current observation is not proof that an upstream release or ingest completed that day.
- https://fonteum.com/trust/integrityDataCatalog (per-attestation Dataset entries)
Stored snapshot-attestation entries represented on the integrity surface. Attestation coverage is incomplete, and an attestation applies only to its identified snapshot object; it does not sign every provenance fact.
- https://fonteum.com/identityDataset + WebAPI
Supported provider-identity relationships where the participating rows publish a compatible key (for example NPI or CCN). The Dataset record does not imply that every NPPES, PECOS, LEIE, HRSA, or facility row is linked.
- https://fonteum.com/searchDataset + WebSite + SearchAction
Public search over supported healthcare-provider records. The Dataset.potentialAction describes the available SearchAction; it is not a claim of whole-registry or whole-market coverage.
- https://fonteum.com/providers/<npi>ProfilePage + Dataset-backed provider record
Public provider records backed by supported healthcare source families. Each surface states its available fields and limitations.
- https://fonteum.com/care-compare/<module>Dataset (one per Care Compare module)
Per-Care-Compare-module Dataset records (nursing-homes, home-health, hospice, dialysis, asc).
One-time submission steps
1. Google Dataset Search
Submit each Dataset URL via Google Search Console > URL Inspection > Request Indexing. Once a single Dataset URL is indexed, Google Dataset Search picks up the rest from the sitemap. The fastest path is to submit /data — its DataCatalog record links the Dataset entries represented by that catalog.
Confirm via search.google.com/search-console > URL Inspection > paste https://fonteum.com/data > Request Indexing
2. data.gov DCAT ingestion (federal-agency catalogs)
data.gov accepts DCAT-US 3.0 catalogs via its CKAN harvester. Submit /data to catalog.data.gov via the publisher form. Once registered, agency catalogs (NIH ODSS, AHRQ research portal, CMS data.gov listings) auto-harvest the catalog on their published cadence.
3. Verify with Google Rich Results Test
Before broad submission, verify each Dataset URL renders valid structured data:
https://search.google.com/test/rich-results?url=https://fonteum.com/data
Replace the URL parameter with each surface from the list above. The tool flags any required-field gaps that would block ingestion. The launch gate dataset-jsonld:every-surface-validates catches the same gaps in CI.