SearchAction
SearchAction is structured data that describes a website’s internal search function when that search function actually exists.
SearchAction is one of those schema features people love to add because it sounds advanced.
Advanced is not always better.
Sometimes advanced is just wrong with extra punctuation.
SearchAction should only be used when your website has a real site search feature.
What Is SearchAction?
SearchAction is a structured data property commonly used with WebSite Schema.
It tells search engines how users can search within a website.
For example, a large documentation site may allow users to search all pages in the catalog.
SearchAction can describe that search pattern in a machine-readable way.
Why SearchAction Exists
Large websites often have internal search.
Think documentation sites.
Knowledge bases.
Large ecommerce stores.
Resource libraries.
SearchAction helps describe how that search works.
It connects the website entity to its internal search function.
When SearchAction Makes Sense
SearchAction may make sense when a website has:
- a real search box
- a working search results page
- a predictable search URL pattern
- a useful index of searchable content
If those things are not true, do not use it.
Schema should document reality.
Not aspirations.
When SearchAction Does Not Make Sense
SearchAction does not belong on every website.
Do not use it when:
- the site has no internal search
- the search page does not work
- the search results are empty or useless
- the feature is planned but not built
- you are adding it only because another SEO checklist said so
There is no trophy for adding unnecessary schema.
There should probably be a penalty box.
Common SearchAction Properties
| Property | Purpose |
|---|---|
| potentialAction | Defines a possible action users can take on the website. |
| SearchAction | Identifies that the action is an internal search. |
| target | The URL pattern for search results. |
| query-input | Defines the search query input parameter. |
A Simple Example
This is a simplified SearchAction example inside WebSite Schema.
{
"@context":"https://schema.org",
"@type":"WebSite",
"name":"Firm IQ Knowledge Catalog",
"url":"https://knowledge.firmiq.io/",
"potentialAction":{
"@type":"SearchAction",
"target":"https://knowledge.firmiq.io/search/?q={search_term_string}",
"query-input":"required name=search_term_string"
}
}
This example should only be used if the search URL actually works.
SearchAction and Static Sites
A static HTML site can have search.
But it does not automatically have search.
If this Knowledge Catalog later includes a real search function, SearchAction may become appropriate.
Until then, adding SearchAction would be premature.
And premature schema is just technical glitter.
SearchAction and AI Understanding
SearchAction does not explain your business.
It does not define your services.
It does not improve your authority.
It simply describes site search functionality.
That can help machines understand how users navigate a large knowledge resource.
But it is not a replacement for Organization Schema, Article Schema, or Breadcrumb Schema.
Common Mistakes
- Adding SearchAction without a working search feature.
- Using the wrong search URL pattern.
- Forgetting to test the search results page.
- Adding SearchAction to every page instead of the website entity.
- Assuming SearchAction helps rankings.
SearchAction is functional schema.
If the function does not exist, the schema should not either.
Firm IQ Definition
At Firm IQ, SearchAction is machine-readable documentation for real internal site search.
It belongs only on websites where users can actually search the site.
It is useful when accurate.
It is noise when invented.
Here’s what we’ve learned: the best schema is not the most complicated schema. It is the schema that accurately describes what exists. SearchAction is a perfect example. Use it when it is true. Skip it when it is not.