Has JSON-LD BlogPosting reports whether a page’s raw rendered HTML contains an @type value of BlogPosting: it returns 1 when RankGear finds that string and 0 when it does not. It is a text-pattern presence check only — a 1 does not mean the JSON-LD is valid, complete, or agrees with the visible page.
| Factor ID | RG-SCJ-035 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
Has JSON-LD BlogPosting reports whether RankGear finds an @type value for BlogPosting in the raw source. A value of 1 means the expected string was present; a value of 0 means it was not. The factor confirms that the BlogPosting marker appears in the HTML text — it does not parse the JSON-LD graph, validate its structure, or check that its properties match the article a reader sees.
How RankGear measures it
RankGear performs a case-insensitive raw-HTML search with flexible whitespace around "@type": "BlogPosting", and permits an optional schema: prefix. When a matching string is found the factor returns 1; otherwise it returns 0. Because the check matches text rather than parsing the document, capitalization and spacing variations still register, but a matching string that sits outside a valid JSON-LD block can also produce a 1.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "...",
"author": { "@type": "Person", "name": "..." },
"datePublished": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of BlogPosting (optionally with a schema: prefix) was found in the raw HTML, in any case. |
| 0 | No BlogPosting type string was found (the page may use another type, or no JSON-LD at all). |
How to optimize it
Use BlogPosting only for a genuine blog post, and supply accurate properties that match the visible content — a correct headline, author, published and modified dates, publisher, and images. Do not add the type to pages that are not blog posts, and do not describe facts a reader cannot see. Treat the factor as an observation of presence rather than a target to chase: the goal is markup that helps machines understand a real article, not a matching string for its own sake. Because RankGear only checks for the type text, validate the complete structured data independently to confirm it is well formed and eligible.
Important considerations
- RankGear pattern-matches text rather than parsing or validating the JSON-LD graph.
- A matching string outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently with an appropriate tool.
- Presence relates to how pages are prioritized within a measured result set — it does not guarantee a rich result or a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.