WebSite Search Schema
SkillWeb & browsingWebsite claude skill: a skill that guides adding WebSite SearchAction structured data so a site's internal search can appear as a Sitelinks Searchbox in Google's branded search results. It explains the schema, checks whether a page already has it, and shows how to fix missing or incorrect markup.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a site with internal site search functionality and access to its homepage markup.
Then ask your AI: use the WebSite Search Schema skill
What your AI can do with it
- Check a homepage for WebSite JSON-LD schema with a SearchAction potential action
- Add WebSite schema with target, {search_term_string} placeholder, and query-input properti
- Explain how the Sitelinks Searchbox works and why Google may not show it
- Review rendered HTML, structured data, and headers for WebSite Search Schema issues
- Flag exact routes or templates where search-facing output violates the rule
Getting started
- Have a site with internal site search functionality and access to its homepage markup.
- Add the skill to your agent's available skills.
- Ask the agent to check the homepage for a WebSite schema block with a SearchAction.
- Follow the agent's fix guidance to add or correct the JSON-LD in the homepage head.
- Verify the final rendered page output as the agent describes.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/website-search/SKILL.md and read by ahel’s review.
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.
Quick Reference
- Add
WebSiteschema withSearchActionto signal that your site has search functionality to Google - This enables Google to show a Sitelinks Searchbox below your brand's search result for branded queries
- The Searchbox only appears at Google's discretion — the schema is a signal, not a guarantee
- The
query-inputproperty must follow the formatrequired name=search_term_string
Check
Check 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.
Fix
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
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.
Code Review
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
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- Does adding the schema guarantee Google will show the Sitelinks Searchbox?
- No. The Searchbox only appears at Google's discretion, the schema is a signal, not a guarantee.
- What format does the query-input property need?
- It must follow the format required name=search_term_string.
- Where should the WebSite schema be added?
- In the homepage head, with url set to the canonical homepage URL and a SearchAction target pointing to your search results URL with a {search_term_string} placeholder.
- When is this skill useful?
- For sites with internal site search, when optimizing branded search result appearance, or when adding structured data for the first time.
Advanced
- Item type
- skill
- Key
website-search- Source
- github.com/thedaviddias/front-end-checklist