Has JSON-LD OutletStore

This factor is a binary presence check: RankGear returns 1 when it finds an @type of OutletStore in the raw HTML, and 0 when it does not. It is a text pattern match, not a JSON-LD validator, so a matching string sitting outside a valid graph can still score 1.

What it measures

This factor reports whether RankGear finds an @type value of OutletStore in the raw source of the page. It is a signal that the page declares itself, via Schema.org JSON-LD, as an outlet retail store. The check answers a single yes/no question — is that type present in the markup — and returns nothing about how complete or accurate the surrounding structured data is.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "OutletStore", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not change the result. Because it inspects source text rather than parsing a JSON-LD graph, the detector keys on the pattern appearing anywhere in the HTML.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OutletStore",
  "name": "Riverside Outlet",
  "address": { "@type": "PostalAddress", "streetAddress": "..." },
  "openingHours": "Mo-Sa 10:00-20:00"
}
</script>

How to optimize it

Use OutletStore only for a genuine outlet retailer, and only when the page carries accurate products, offers, location, hours, return policies, and contact details. Every property in the markup should reflect content a visitor can verify on the page itself. Treat this factor as an observation of what your markup declares, not a target to chase — adding the type to a page that is not an outlet store, or that lacks the supporting content, misrepresents the page without earning the signal it implies.

Important considerations

• The detector pattern-matches source text instead of validating a full JSON-LD graph.
• A matching string that sits outside valid JSON-LD can still produce a 1.
• Capitalization differences do not affect detection.
• Validate the complete structured data independently — with a Schema.org or Rich Results validator — since this check confirms presence, not correctness.
• This is a correlation-based prioritization signal within a measured result set. Presence of the type relates to position; it does not by itself make a page rank or guarantee any placement.

Related factors

• Has JSON-LD Otolaryngologic
• Has JSON-LD Painting

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