Structured Data · Type Gallery · Part 12

WebSite Sitelinks Search Box: Deprecated Feature and Site Names

~11 min read Updated 2026-06-24 MagicSEO Editors · Human Reviewed Search Box Deprecated
Bottom Line: Site Search Box DiscontinuedGoogle deprecated Sitelinks search box rich results in late 2024 and no longer displays this site search input in search results. The approach of using WebSite + SearchAction to trigger a search box is no longer effective. However, the WebSite markup itself hasn't disappeared—it now primarily serves the Site Names feature.

This article covers two things: how an old feature disappeared, and how a still-useful feature is properly implemented. The Sitelinks search box previously enabled a direct site search input to appear in branded keyword search results, triggered by WebSite's SearchAction. It has been discontinued. But the same WebSite type now plays a role in helping Google determine your site name for search results, making it worth implementing correctly.

What Happened to the Search Box#

Sitelinks search box was a site search input previously displayed in branded keyword search results, allowing users to directly search your site content. It was triggered by the potentialAction (SearchAction) of a homepage WebSite markup. Google announced the deprecation of this rich result in late 2024 and stopped displaying it, and the corresponding report in Search Console has been removed.

Official documentation: Google Search Central: Site names. Please refer to the official documentation's current state.

Current Focus: Site Names Feature#

Site names determine the name displayed for your site in search results (in the domain/breadcrumb line). Google considers multiple signals, and WebSite structured data is an important one. The proper implementation is to place a WebSite markup on your homepage, providing name and url, and optionally alternateName when needed.

website-sitename.json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "MagicSEO",
  "alternateName": "Magic SEO Guide",
  "url": "https://magic-seo.com/"
}

Keeping this consistent with your page <title>, og:site_name, and other signals helps Google more confidently adopt your desired site name. Whether Google ultimately uses it remains their decision.

Legacy Implementation (For Reference Only)#

The following is the legacy implementation that previously triggered Sitelinks search box. It's provided only for historical understanding and migration decisions—not recommended for new implementation seeking search box functionality.

website-searchaction-legacy.json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "MagicSEO",
  "url": "https://magic-seo.com/",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://magic-seo.com/search?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}
SearchAction No Longer Triggers Search BoxThis implementation remains syntactically valid but will no longer produce the site search box display. Keeping it is usually harmless, but you can remove SearchAction during maintenance while retaining name and url for the Site Names feature.

Migration Recommendations#

  1. New sites: Place a streamlined WebSite (name + url + optional alternateName) on homepage, without SearchAction;
  2. Existing sites: Keep WebSite, remove SearchAction from potentialAction during maintenance;
  3. Ensure WebSite's name aligns with page title, og:site_name, and brand name;
  4. WebSite and Organization can coexist: the former handles site name, the latter handles organizational identity;
  5. Site search as a page feature can still be retained (for user experience), but it no longer relies on structured data for search result display.

How This Site Uses WebSite#

This site appropriately uses a streamlined WebSite on the homepage to declare the site name (MagicSEO), without adding SearchAction for the discontinued search box. This article continues to use Article, BreadcrumbList, and FAQPage.

Site Example"Use what still works (site names), abandon what's deprecated (search box)"—this is exactly the judgment approach to take when facing feature evolution.

WebSite Decision Checklist#

  • Aware that Sitelinks search box was discontinued in late 2024
  • Don't write new SearchAction seeking search box display
  • Use WebSite on homepage with name and url for Site Names
  • Use alternateName when backup names are needed
  • Keep name consistent with title, og:site_name, and brand
  • Remove SearchAction from potentialAction during maintenance
  • WebSite and Organization serve different purposes
  • Check official documentation's current status before investing

Frequently Asked Questions#

Does Sitelinks search box still work?

No. Google announced the deprecation of Sitelinks search box rich results in late 2024 and stopped displaying this site search box in search results. Therefore, using WebSite with SearchAction (potentialAction) to trigger the search box no longer produces that display effect, and the corresponding report in Search Console has been removed.

Is WebSite structured data still useful now?

Yes, but its purpose has changed. WebSite structured data now primarily serves the Site Names feature: Google uses it to help determine the name displayed for your website in search results. You should mark name (and optionally alternateName) with WebSite on your homepage, rather than expecting it to bring a site search box.

How do I implement the Site Names feature?

Place a WebSite structured data on your homepage, providing name and url. Use your desired website display name for name, and optionally use alternateName to provide a backup name (such as an abbreviation). Additionally, keep it consistent with page title, og:site_name, and other signals. Whether Google ultimately adopts it remains their decision.

Should I delete existing WebSite with SearchAction?

No urgent deletion needed. The SearchAction in potentialAction will no longer trigger a search box, but keeping it is usually harmless. You can remove SearchAction during maintenance while retaining WebSite's name and url for the Site Names feature. Before deciding, check the official documentation's current status.