What is SearchResultsPage structured data?
SearchResultsPage identifies internal search results pages, complementing WebSite + SearchAction schema so search engines understand your on-site search context.
Eligibility & Status
This type is “not direct”; it acts as supportive context rather than producing a specific rich result. Use it alongside WebSite SearchAction to improve sitelinks searchbox eligibility.
Why it matters
- Clarifies that the page is a search results experience.
- Reduces confusion between category vs search pages.
- Complements WebSite SearchAction for site-search surfacing.
Essential properties to include
- nameandurl.
- Optional description,inLanguage,isPartOf.
- Pair with WebSitemarkup that includesSearchAction.
Implementation workflow inside SwiftSchema
- Select SearchResultsPage in the generator.
- Enter the search results page title and canonical URL.
- Include description/inLanguage if helpful.
- Ensure your site root has WebSite + SearchAction.
- Validate via the Rich Results Test.
Troubleshooting & QA
- Missing SearchAction: add to WebSite markup.
- Incorrect targeting: use this for internal search, not category pages.
- Ensure the search page is indexable (not blocked).
Maintenance
- Update schema if search URL patterns change.
- Keep lastReviewedcurrent.
Required properties
nameurl
Recommended properties
descriptioninLanguageisPartOf.nameisPartOf.url
Minimal JSON-LD
{
"@context": "https://schema.org",
"@type": "SearchResultsPage",
"name": "Search results for 'jackets'",
"url": "https://www.example.com/search?q=jackets"
}FAQs
Do I need WebSite SearchAction?Show
Recommended. Add SearchAction to your WebSite so search engines understand your site search endpoint.
Does this change rankings?Show
It improves understanding and eligibility for features, but rankings depend on many factors.