Has Schema Service

This factor records whether the page’s body HTML contains the legacy Schema.org Service type URI. It returns a simple present/absent signal (1 or 0) — it confirms the literal type string is there, not that the service markup is complete, valid, or truthful.

What it measures

It detects the legacy Schema.org Service type URI on the page. The Service type describes an offered service — something a provider performs for a consumer, such as a repair, a consultation, or a delivery. This factor tells you only whether that type declaration is present in the body HTML; it does not read the provider, service area, terms, or any other property.

How RankGear measures it

RankGear performs a case-insensitive search of the body HTML (scripts excluded) for the literal string http://schema.org/Service and returns 1 when it is found, 0 when it is not. Because the match is on the plain http:// type URI, it targets the older microdata/RDFa style of declaration rather than an HTTPS URI or a bare JSON-LD type.

What RankGear looks for

<div itemscope itemtype="http://schema.org/Service">
  <span itemprop="name">Emergency Plumbing</span>
  <span itemprop="provider">Example Co</span>
  <span itemprop="areaServed">Denver, CO</span>
</div>

How to optimize it

Use Service only for a real offered service, and describe its provider, service area, and terms accurately. Treat this factor as an observation of what markup exists, not a target to chase — adding the type string to a page with no genuine service adds nothing a search engine can trust. If you already declare a service with a modern HTTPS URI or a bare JSON-LD "@type": "Service", this legacy check may read 0 even though your structured data is valid; that is expected.

Important considerations

• The match is on the literal http://schema.org/Service; an HTTPS https://schema.org/Service URI and a bare JSON-LD "@type": "Service" do not satisfy this detector.
• Presence does not validate the type’s required or recommended properties — only that the type string is there.
• Structured data should match visible, truthful content on the page.
• Validate the complete markup with current platform tools; a detected type URI is not proof the Service is correctly or completely formed.
• This is a correlational prioritization signal within a measured result set, not a guarantee that adding Service markup will change a page’s ranking.

Related factors

• Has Schema Search Action
• Has Schema Store

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