Has Schema Blog Posting

Abstract illustration of a blog post card carrying BlogPosting schema markup with author, date and image cues, in RankGear indigo and coral.

Has Schema Blog Posting checks whether a page declares the legacy Schema.org BlogPosting type, reported as a simple present/absent value (1 or 0). RankGear only looks for the older http://schema.org/BlogPosting URI, so HTTPS variants and bare @type values can be missed — and presence alone never guarantees a rich result.

Factor IDRG-SCH-006
FamilySchema.org
MeasurementBinary presence (0 / 1)
Measured zoneBody HTML without scripts

What it measures

This factor detects the legacy Schema.org BlogPosting type URI on the page. BlogPosting is the vocabulary type used to describe an individual blog entry — a post with an author, a publication date, a headline, and typically an image. The factor answers one question: does the page declare that type at all?

Back to Top

How RankGear measures it

RankGear performs a case-insensitive search of the page’s body HTML (scripts excluded) for the exact string http://schema.org/BlogPosting. If the string is found, the factor returns 1; if it is absent, the factor returns 0. It matches only that legacy HTTP URI — it does not resolve HTTPS forms, bare @type declarations, or the properties nested under the type.

Back to Top

What RankGear looks for

<div itemscope itemtype="http://schema.org/BlogPosting">
  <h1 itemprop="headline">…</h1>
  <span itemprop="author">…</span>
</div>
ValueMeaning
1The string http://schema.org/BlogPosting appears in the page’s body HTML.
0That exact legacy URI is not found (which includes pages using the HTTPS URI or a bare @type).
Back to Top

How to optimize it

Use BlogPosting for genuine blog entries, and back the markup with accurate author, publication date, headline, and image data. Because RankGear only matches the legacy HTTP URI, a page that marks up its blog posts with the newer HTTPS form may score 0 here even though its schema is valid — read this factor as an observation about which URI form is present, not as a target to chase by downgrading correct markup.

Back to Top

Important considerations

  • HTTPS URIs and bare @type values can be missed — only the exact http://schema.org/BlogPosting string is matched.
  • Properties are not validated. The factor confirms the type is declared, not that author, date, headline, or image are present or correct.
  • The type should match the visible content — apply BlogPosting only to pages that are genuinely blog entries.
  • Presence does not ensure eligibility for search enhancements or rich results.
  • This is a prioritization signal that relates to position within a measured result set; it does not by itself cause or guarantee a ranking. Correlation is not causation.
Back to Top

Related factors

Part of the Factors reference · how RankGear measures · glossary.

Back to Top