Has JSON-LD MovingCompany

This factor reports whether RankGear finds a JSON-LD @type of MovingCompany in a page’s raw source — a simple 1 (present) or 0 (absent). It is a text-pattern match on the raw HTML, not a validated JSON-LD graph, so it confirms the string is there but not that the structured data is well-formed.

What it measures

This factor reports whether RankGear finds an @type value of MovingCompany in the page’s raw source. MovingCompany is the schema.org type used to describe a business that relocates people’s belongings, and its presence signals that the page declares itself as a moving-company entity to search engines and other machine readers. The factor returns a single 1 when the type is detected and 0 when it is not.

How RankGear measures it

RankGear searches the raw HTML for "@type": "MovingCompany", tolerating flexible whitespace around the colon and quotes and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. Because the check runs against the raw source text rather than a parsed graph, it looks only for the string pattern.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MovingCompany",
  "name": "Example Movers",
  "telephone": "+1-555-0100"
}
</script>

How to optimize it

Use MovingCompany only for a genuine moving company, with accurate services, service area, credentials, location, hours, and contact details. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of whether the declaration exists, not a target to chase: adding the string to a page that is not a moving company — or that cannot back up the claim on-page — misrepresents the entity and does not earn a legitimate signal.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so a returned 1 confirms the string exists but not that the structured data is valid.
• A matching string that sits outside valid JSON-LD — for example in a comment, code sample, or broken block — can still produce 1.
• Capitalization differences do not affect detection, since matching is case-insensitive.
• Validate the complete structured data independently with a dedicated schema validator; this factor does not replace that step.
• Correlation is not causation — this signal tracks how a page relates to others in a measured result set and helps prioritize work; it does not by itself make a page rank or guarantee any position.

Related factors

• Has JSON-LD MovieTheater
• Has JSON-LD Museum

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