This factor reports whether RankGear finds an EmailMessage @type declared in JSON-LD structured data in a page’s raw source. It returns 1 when the pattern is present and 0 when it is absent — and because it pattern-matches source text rather than validating a JSON-LD graph, a match does not by itself confirm valid, correctly structured markup.
| Factor ID | RG-SCJ-081 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of EmailMessage in the page’s raw source. EmailMessage is the schema.org type for a single email message, describing its sender, recipients, dates, subject, and body relationships. The check is a straightforward presence test: the type is either declared in the source or it is not.
How RankGear measures it
RankGear searches the raw HTML for the @type assignment to EmailMessage, allowing flexible whitespace around the value and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result. Any match anywhere in the source sets the value to 1; no match sets it to 0.
What RankGear looks for
"@type": "EmailMessage"
"@type":"schema:EmailMessage" (whitespace flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | An EmailMessage @type string was found in the raw source. |
| 0 | No EmailMessage @type string was found. |
How to optimize it
Use EmailMessage only for a genuine email message, with accurate sender, recipient, dates, subject, and content relationships, and with properties that match the visible content. Do not add the markup to score a 1 on a page that is not actually an email message — treat the reading as an observation about the page’s structured data, not a target to hit for its own sake. If your page legitimately represents an email message, mark it up properly; if it does not, a 0 here is the correct and expected result.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the markup is valid.
- A matching string outside valid JSON-LD — for example inside a comment, an example block, or an unrelated script — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set; it does not cause or guarantee a ranking. Correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.