Has Schema Search Action

This factor records whether the page’s body HTML contains the legacy Schema.org SearchAction type URI — the markup a site uses to describe a working search action to search engines. It returns a simple present/absent signal (1 or 0): it confirms the type string is there, not that the action’s properties are complete, valid, or functional.

What it measures

It detects the legacy Schema.org SearchAction type URI on the page. SearchAction describes a search operation a site exposes — the target endpoint that runs a query and the input the visitor supplies. This factor tells you only whether that type declaration is present in the body HTML; it does not confirm the search action works, points at a real endpoint, or names its query input.

How RankGear measures it

RankGear performs a case-insensitive search of the body HTML (scripts excluded) for the literal string http://schema.org/SearchAction. If the string is found, the factor returns 1; if not, it returns 0. Because the match is on the plain http:// type URI, it targets the older microdata/RDFa style of declaration rather than newer forms.

What RankGear looks for

<div itemscope itemtype="http://schema.org/WebSite">
  <div itemprop="potentialAction" itemscope
       itemtype="http://schema.org/SearchAction">
    <meta itemprop="target"
          content="https://example.com/search?q={query}">
    <meta itemprop="query-input"
          content="required name=query">
  </div>
</div>

How to optimize it

Use SearchAction only when the site genuinely exposes a working search action with an accurate target endpoint and a real query input — not as a decorative type string. Treat this factor as an observation of what markup exists, not a target to chase: adding the declaration to a page that offers no true search does nothing a search engine can trust. If you already describe your search box with modern HTTPS types or bare JSON-LD, this legacy http:// check may read 0 even though your structured data is valid; that is expected.

Important considerations

• The match is on the http:// URI, so https://schema.org/SearchAction and a bare JSON-LD "@type": "SearchAction" do not satisfy this detector.
• Presence does not validate the required or recommended properties — the target and query-input are not checked, only that the type string is there.
• The structured data should match visible, truthful content: declare a search action only where the site actually provides one.
• Validate the complete markup with current platform tools; a detected type URI is not proof the SearchAction is correctly or fully formed.
• This is a correlational prioritization signal within a measured result set, not a guarantee that adding SearchAction markup will change a page’s ranking.

Related factors

• Has Schema Review
• Has Schema Service

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