How the sitelinks search box worked
When someone searched for a brand, Google sometimes placed a search field directly inside that brand’s result. Typing into it took the visitor to the site’s own search results page for that phrase, so they arrived already looking at matches rather than at the homepage.
Google generated the box automatically for sites it was confident about, and site owners could influence one detail. By adding WebSite structured data containing a SearchAction, you told Google the URL pattern of your internal search, so the box used your search page instead of falling back to a Google search restricted to your domain. That markup is why the feature still appears on so many old SEO checklists: it was one of the few schema types with a visible, easily demonstrated outcome.
Google has since retired it. The box no longer appears in results, and Google has said the associated markup is not used any more.
Why the sitelinks search box matters
It matters mainly as a correction. The sitelinks search box is still listed in audit templates, agency proposals and course material, and clients are still asked to pay for markup that cannot produce anything. Knowing it has gone saves that money and stops a report promising a result no site can now achieve.
The second reason is that the underlying need did not disappear with the feature. People do arrive at a brand looking for one specific thing, and they used to be able to jump straight to it. That job now falls entirely to your own site: a search facility that is easy to find and actually works, plus navigation clear enough that most visitors never need it.
Common mistakes with the sitelinks search box
The first is selling or buying it. If a proposal lists the sitelinks search box as a deliverable, the proposal has not been reviewed since the feature was withdrawn, and it is fair to ask what else in it is out of date.
The second is ripping the markup out in a panic. Leftover WebSite and SearchAction markup is not a penalty and not an error; it is simply ignored. Removing it during ordinary housekeeping is fine, but it is not urgent and does not warrant an emergency release. The third is concluding that because one type was retired, structured data in general is unreliable. Google withdraws individual features fairly regularly while the types behind breadcrumbs, products, reviews and organisation details keep working.
What to do about it
Check what your site is currently claiming. If a WebSite SearchAction block is still there, leave it or tidy it away with your next release, and take the item off any checklist that still treats adding it as a task worth billing.
Then put the effort where it now pays. If your site has internal search, make sure it is visible on a phone, returns useful matches for the words customers actually use, and logs those queries so you can see what people cannot find. Those logs are one of the most honest sources of content ideas a site has. If you have no internal search, decide whether the navigation covers it — on a small brochure site it usually does, and a bad search box is worse than none. Beyond that, keep the schema markup types that still earn something, and review them when the documentation behind them changes rather than when a checklist says so. The related question of how sitelinks themselves are generated is unaffected by any of this.
