Recent Posts

Categories

Semantic Graph Engine

Structured data governance

Generate and validate connected JSON-LD for nutrition entities

Build and inspect connected JSON-LD drafts that describe food records, source data, nutrition tools, and editorial trust entities.

Verified SR Legacy baseline 7,793 SR Legacy foods should be used as the safe baseline claim unless a broader index is batch-verified.
Primary source anchor FDC IDs and canonical USDA source URLs should anchor food identity.
Production rule production JSON-LD should be injected server-side after validation, not by client-side preview scripts.

Best use

  • Generate graph drafts for food profiles, dataset pages, tools, categories, and reviewer entities.
  • Check whether FDC IDs, USDA source links, authors, reviewers, and publisher nodes are connected.
  • Use the output as a validation and transparency aid before production schema is approved.

Source and safety model

Outputs should stay connected to visible page content, source-backed nutrition data, clear assumptions, and educational limitations. This improves user trust while keeping the page understandable to crawlers and retrieval systems.

Semantic entity segmentation

Food graph

Connect WebPage → Food → source identifier → USDA dataset → publisher, with nutrition values only when visible on the page.

Tool graph

Connect each tool page to one SoftwareApplication node, visible FAQ content, methodology notes, and publisher identity.

Trust graph

Connect Organization and Person nodes only when the visible page accurately supports publisher, author, or reviewer claims.

Does structured data guarantee rankings?

No. It helps machines understand content and entities, but it does not guarantee rankings or rich results.

Should this replace Rank Math?

No. It should merge with Rank Math safely and avoid duplicate or conflicting graph nodes.

What is the highest-value check?

Confirm that each food entity has a stable FDC ID, a real canonical page URL, and a USDA source reference.

Structured-data validation checklist

CRITICAL

FDC identity

Food records should expose a canonical FDC ID and source URL.

CRITICAL

Stable @id policy

Graph nodes should use stable page anchors such as #food, #nutrition, #webpage, and #software.

HIGH

Rank Math bridge

Keep Organization, WebSite, and BreadcrumbList nodes while avoiding duplicate Article/WebPage conflicts.

HIGH

Visible FAQ match

FAQPage schema should only exist when the questions are visible on the page.

HIGH

No tool pollution

WebApplication nodes should live on tool pages, not every food profile.

CRITICAL

Review truthfulness

Only add reviewedBy when a qualified reviewer actually reviewed the page.

Entity count verification

How broader food-entity claims should be verified

Use 7,793 SR Legacy foods as the safe public baseline until broader USDA-derived entities are batch-matched to published URLs, source records, and visible nutrition data.

STEP 1

Match source IDs

Each candidate entity must have a valid FDC ID or approved source identifier.

STEP 2

Confirm published URL

Do not count records that do not resolve to an indexable eNutritionFacts page.

STEP 3

Verify visible values

Nutrition values used in schema should also be visible or clearly linked on the page.

STEP 4

Audit freshness

Branded-food and prepared-food records need formula/date checks before broad public claims.

OUTPUT

Claim only verified totals

After the batch passes, expose the verified count in the homepage and dataset schema.

FAILSAFE

No silent inflation

If source or URL validation fails, keep the conservative SR Legacy count in public copy.