Menu
Use when applies to sites with internal site search functionality. Use when optimizing branded search result appearance or adding structured data for the first time.
| name | website-search |
| description | Use when applies to sites with internal site search functionality. Use when optimizing branded search result appearance or adding structured data for the first time. |
| metadata | {"category":"seo","priority":"low","difficulty":"beginner","estimatedTime":"10","source":"frontendchecklist.io","url":"https://frontendchecklist.io/en/rules/seo/website-search"} |
The Sitelinks Searchbox lets users search your site directly from Google's search results page, reducing friction for brand-aware users and increasing the click-through quality from branded queries.
WebSite schema with SearchAction to signal that your site has search functionality to Googlequery-input property must follow the format required name=search_term_stringCheck the homepage (or primary entry URL) for a <script type='application/ld+json'> block with "@type": "WebSite" and a potentialAction of type SearchAction. Verify target is a valid search URL template and query-input is correctly set.
Add WebSite JSON-LD schema to the homepage <head>. Set url to the canonical-url homepage URL. Set potentialAction with SearchAction, target pointing to your search results URL with {search_term_string} placeholder, and query-input as required name=search_term_string.
Explain how the WebSite SearchAction schema works, what the Sitelinks Searchbox is, why Google may choose not to show it even with valid schema, and how to construct the search URL template.
Review metadata generation, rendered HTML, structured data, and response headers related to WebSite Search Schema. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/website-search
Use when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement valid BreadcrumbList schema. Verify the rendered HTML and HTTP response rather than relying only on source files.
Use when reviewing templates, rendered HTML, or shared components related to Declare UTF-8 character encoding. Validate the final browser-facing markup, not just the source framework abstraction.
Use when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages. Validate the final browser-facing markup, not just the source framework abstraction.
Use when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.
Use when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the rule's frontmatter.