Has JSON-LD TravelAgency

Abstract illustration of a JSON-LD brace enclosing a travel-agency suitcase and location pin under a magnifier, in RankGear indigo and coral.

Has JSON-LD TravelAgency reports whether RankGear finds a "@type": "TravelAgency" declaration in a page’s raw HTML — a 1 when the string is present, 0 when it is not. It is a text-pattern check on source, not a validation of the structured-data graph, so the presence of the string does not confirm the schema is well-formed or that it relates to a page’s position.

Factor IDRG-SCJ-257
FamilyStructured Data — JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether RankGear finds an @type value of TravelAgency in the raw source of the page. It is a single yes/no signal: the markup that declares a page as representing a travel agency is either detectable in the HTML or it is not.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "TravelAgency", allowing flexible whitespace around the colon and value and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences in the source do not change the result. A match returns 1; no match returns 0.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TravelAgency",
  "name": "Example Travels",
  "url": "https://example.com/"
}
</script>
ValueMeaning
1A TravelAgency @type string was found in the raw HTML (whitespace-flexible, case-insensitive, schema: prefix allowed).
0No matching string was found in the source.
Back to Top

How to optimize it

Use TravelAgency only for a page that genuinely represents a real travel agency, and make every property accurate: services, destinations, credentials, offers, location, hours, and contact details. Each value should reflect content a user can verify on the page itself. Treat this factor as an observation of what your markup declares, not a target to reach by inserting the string — adding the type where it does not describe the page is misrepresentation, not optimization.

Back to Top

Important considerations

  • The detector pattern-matches source text rather than validating a JSON-LD graph, so a 1 does not confirm the structured data is well-formed or complete.
  • A matching string that appears outside valid JSON-LD — for example in a comment, an example block, or escaped text — can still produce a 1.
  • Capitalization differences do not affect detection; matching is case-insensitive.
  • Validate the complete structured data independently (for example with a schema validator) before relying on it.
  • This is a prioritization signal that relates to position within a measured result set. Its presence does not cause a page to rank and guarantees nothing — correlation is not causation.
Back to Top

Related factors

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

Back to Top