This factor reports whether the legacy entry-content MicroFormat class appears in the page’s body markup, returning 1 when present and 0 when absent. It is a presence signal only — RankGear does not confirm that the class sits inside a valid hentry, and its presence neither makes a page rank nor guarantees a position.
| Factor ID | RG-SCF-005 |
|---|---|
| Family | Structured Data — MicroFormat |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Body HTML without scripts |
What it measures
This factor reports whether the legacy entry-content MicroFormat class is present in the page. The entry-content class comes from the hAtom / hentry MicroFormats vocabulary, where it wraps the main content of a published entry. RankGear records only whether that class string is present, not whether it is used correctly.
How RankGear measures it
RankGear searches the body HTML (scripts excluded) case-insensitively for the exact double-quoted sequence class="entry-content" and returns 1 or 0. The match is literal: the class must be the complete attribute value, so a multi-class attribute that merely contains the word among others is not counted.
What RankGear looks for
<div class="entry-content">
<!-- main published entry body -->
</div>| Value | Meaning |
|---|---|
| 1 | The exact string class="entry-content" was found in the body HTML. |
| 0 | The string was not found — the class is absent, spelled differently, or combined with other classes in the same attribute. |
How to optimize it
Treat this as an observation about your template, not a target to chase. Retain entry-content only where an existing hAtom or publishing integration genuinely uses it. If nothing in your stack consumes the class, there is no reason to add it, and a 0 here is not a defect to correct.
Important considerations
- The detector requires the class to be the complete attribute value — a combined attribute such as
class="entry-content post"will not match. - It does not validate an hentry parent, so a present class is not proof of valid Microformats markup.
- Modern implementations may prefer Microformats2 (for example
e-content), which this legacy check does not detect. - Do not add legacy classes solely to move this score.
- Presence correlates with certain publishing templates within a measured result set; it is a prioritization signal, not a cause of ranking, and never a guarantee of position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.