Has JSON-LD DiscussionForumPosting reports whether RankGear finds an @type value of DiscussionForumPosting in a page’s raw source — a binary presence signal (1 = found, 0 = not found). It confirms the string is present, not that a valid JSON-LD graph surrounds it, so treat a 1 as a marker, not a certificate of correctness.
| Factor ID | RG-SCJ-075 |
|---|---|
| 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 DiscussionForumPosting in the page’s raw source. DiscussionForumPosting is the schema.org type used to mark up a single post within a discussion forum — the kind of user-generated thread entry that carries an author, dates, and interaction data. The factor answers one question only: is that type declared somewhere in the served markup?
How RankGear measures it
RankGear searches the raw HTML for "@type": "DiscussionForumPosting", allowing flexible whitespace around the colon and optionally a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. A match returns 1; no match returns 0.
What RankGear looks for
"@type": "DiscussionForumPosting"
// also matched (flexible whitespace, optional schema: prefix, case-insensitive):
"@type":"discussionforumposting"
"@type" : "schema:DiscussionForumPosting"| Value | Meaning |
|---|---|
| 1 | A DiscussionForumPosting @type string was found in the raw source. |
| 0 | No matching @type string was found in the raw source. |
How to optimize it
Use DiscussionForumPosting only for a genuine forum post — with an accurate author, correct creation and update dates, real discussion context, and interaction data — and make sure every declared property matches the content a visitor actually sees. This is an observation about what your markup declares, not a target to chase: adding the type to a page that is not a forum post misrepresents the content and adds risk without adding value. If the page truly is a forum post and the type is absent, adding correct DiscussionForumPosting markup is the fix.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a 1 does not confirm the surrounding structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection, because matching is case-insensitive.
- Validate the complete structured data independently (for example with a schema validator) rather than relying on this presence check alone.
- This is a correlation-based prioritization signal that describes what a page declares. It relates to patterns within a measured result set; it does not by itself cause or guarantee any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.