Quick answer
RDFa adds structured-data meaning through attributes such as typeof, property, and vocab on ordinary HTML elements. NOTABIS records rdfa-present when it measures an element with typeof or property. The pass confirms attribute presence, not valid vocabulary, complete entities, or search-feature eligibility.
What the issue means
An RDFa fragment can annotate visible content like this:
<div vocab="https://schema.org/" typeof="Product">
<span property="name">Example trail shoe</span>
</div>
RDFa, Microdata, and JSON-LD are different syntaxes for expressing structured information. They should describe the same visible page content when more than one is used.
Why it matters for SEO
Useful structured data can help machines interpret entities, but the syntax alone does not improve rankings or guarantee a rich result. Invalid, hidden, or misleading annotations can be ignored. Treat this as a semantic and interoperability choice, not a requirement for every page.
How NOTABIS detects it
The rdfa-present rule is a page-level passed check created when the measured DOM contains one or more elements with typeof or property attributes. NOTABIS does not validate vocab, CURIEs, property relationships, values, required fields, or search-engine policies. Absence is not an error; it simply means RDFa was not measured.
How to check it yourself
Inspect View Source and the DOM for RDFa attributes, then trace each property to visible text or a meaningful resource. Validate the chosen vocabulary and compare the result with any JSON-LD or Microdata on the page. Test representative templates and locales rather than one page only.
How to fix it
Use a documented vocabulary, keep entity relationships complete, and generate values from the canonical content source. Remove abandoned attributes and avoid adding duplicate formats without a maintenance plan. Revalidate after template changes and confirm that annotations still describe what users see.
When this is intentional or does not need fixing
JSON-LD or Microdata may be a better fit for the application, and many pages need no structured data. RDFa can remain on legacy or standards-driven content when it is accurate. Do not migrate a working vocabulary merely to change a NOTABIS pass count.
Related issues
Read valid JSON-LD, invalid JSON-LD, and Microdata. Google’s structured-data policies explain quality expectations for supported features.
Run a NOTABIS audit
NOTABIS records when RDFa attributes were present in measured HTML, giving you a starting point for vocabulary and visible-content validation.