Sitelinks Search Box Schema

22 Apr 2026

Structured Data

Sitelinks Search Box Schema: A Complete Guide For Your Website Or App

A Sitelinks Search Box allows users to search directly within your website or app from Google’s search results. This feature, powered by Google, provides a quick and seamless search experience by displaying a search box that is specific to your website or app.

This functionality was particularly beneficial for large websites with extensive content, as it helped users bypass multiple navigation steps and directly find relevant information. By integrating sitelinks schema, businesses could improve user experience and reduce bounce rates significantly.

However, Google has removed the sitelinks search box feature from its search results starting November 21, 2024. This means that websites and apps no longer have the opportunity to display this visual element in search results, and any existing sitelinks search boxes will be removed.

Why the Sitelinks Search Box Was Important

Before its removal, the sitelinks search box was considered a valuable enhancement in search engine results pages (SERPs). It provided:

Faster navigation for users
Improved click-through rates (CTR)
Enhanced brand visibility
Better on-site engagement

For websites with thousands of pages—like eCommerce stores, media portals, and SaaS platforms -- the sitelinks search box schema helped users directly access internal search results without landing on the homepage first.

How to Implement a Sitelinks Search Box on Your Website/App (Before the Removal)

While the feature is no longer available, it’s worth understanding how the sitelinks search box and sitemap worked for those still looking to optimize their websites for similar functionalities.

1. Install a Working Search Engine on Your Website or App

Website:

Ensure your website has a functioning search engine that can process search queries. The search engine must support UTF-8 encoded queries, as specified in the structured data markup. A well-optimized internal search system also improves overall SEO by helping users discover deeper pages on your site.

Apps:

For Android apps, refer to the Android Developer’s Search Overview to integrate the search box. Your app should be able to handle the Action_View intent from search results, which corresponds to the URL specified in the potentialAction.target property in your markup.

2. Add the Structured Data to Your Website

For websites, the structured data must be added to the homepage, even if it's a single-page site. Here’s how to proceed:

Add SearchAction markup only to the homepage.
Make sure that even if the app is the preferred search target, the SearchAction must be linked to the website.
Verify the structured data using Google’s Rich Results Test.
Ensure that the search engine’s implementation is correctly configured by testing the URL that handles the query (replacing {search_term_string} with a test search term).
Use the rel="canonical" link element on all homepage variants to prevent Google from indexing the wrong URL.

Implementing sitelinks schema correctly ensured that Google understood how your internal search worked and could present it in SERPs when relevant.

3. Working with Apps

For Android apps, ensure that your markup specifies the correct URL for the app’s search handler. Follow the Firebase App Indexing documentation for Android to set up the necessary intent filters.

App developers often use the sitelinks search box schema to connect app content with web search results, improving discoverability and user engagement across platforms.

Preventing the Sitelinks Search Box from Appearing

If you don’t want the sitelinks search box to appear for your website, you can add the following metadata to your homepage:

This will prevent Google from displaying the search box in search results for your site. This was useful for brands that preferred controlled navigation rather than direct search access.

Key Markup Properties

When implementing the Sitelinks Search Box Schema, you will need to understand the properties involved in the markup:

Website: The entity representing the website.
PotentialAction: The entity that holds the URL to which the query will be sent, along with the syntax for the query. Ensure the search handler can receive and process the query.
SearchAction: This object is needed to enable search functionality for desktop and app searches. It includes the following properties:

potentialAction.@type: Specifies the type of the action.
potentialAction.query-input: The required string (search_term_string) or a placeholder.
potentialAction.target: The URL format for sending the query (search_handler_uri{search_term_string}).

Example Markup for Websites:

{

"@context": "https://schema.org",

"@type": "Website",

"url": "https://www.yourwebsite.com/",

"potentialAction": {

"@type": "SearchAction",

"target": "https://www.yourwebsite.com/search?q={search_term_string}",

"query-input": "required name=search_term_string"

}

This structured data snippet was the foundation of the sitelinks search box schema, allowing search engines to interpret and use your internal search functionality.

Monitoring and Troubleshooting

Once you’ve implemented the sitelinks search box schema (while it was still available), you could monitor its performance and troubleshoot issues using Google Search Console. Make sure to check for any errors related to the markup and verify that your search box displays correctly in search results.

Additionally, webmasters often analyzed impressions and click data to understand how users interacted with the sitelinks schema feature. Any inconsistencies in search queries or broken URLs could prevent the feature from appearing.

What to Do After the Removal

Although Google has discontinued the sitelinks search box, there are still several ways to maintain strong internal navigation and user experience:

Optimize your internal search functionality
Use structured data for other rich results
Improve site architecture and navigation menus
Implement breadcrumbs and schema markup
Focus on user intent and content discoverability

These strategies ensure that even without the sitelinks search box schema, your website remains user-friendly and SEO-optimized.

Conclusion

While Google has removed the sitelinks search box feature as of November 21, 2024, it’s important to understand how this schema worked in the past and what you could do to optimize your website or app for similar functionalities. Even though this feature is no longer available, following best practices for search engine optimization and structured data markup remains crucial for improving user experience on your site.

The legacy of sitelinks schema, sitelinks searchbox, and sitelinks search box schema still serves as a valuable lesson in enhancing usability and aligning technical SEO with user intent.

Related Blogs:

Author

Nirlep Patel

I am an internet entrepreneur and also the Co-Founder of GBIM Technologies, India’s fastest growing internet marketing company. My forte lies in actively lending technical expertise in Search Engine Optimisation, SEM Google AdWords, SMM. Spanning about 14 years of focus on Digital Marketing, GBIM today has become one of the greatest digital marketing company. This could have been possible only because of the trust which our clients have on us, and the quality services we have delivered to them I have always believed that more is lost from indecision than wrong decisions and as a result, we have managed to create an environment where people are encouraged to challenge process and innovate. This culture has cultivated a highly motivated team with an open approach where anyone can share their thoughts and ideas freely.