Schema Markup Guide

WebSite Schema + SearchAction

Schema MarkupPublished Jul 17, 2026Updated Jul 19, 20263 min readLinkedInX

WebSite schema names your entire site as an entity, and its potentialAction — a SearchAction — tells Google where your internal search lives. Together they historically powered the sitelinks search box in results and still help Google understand your site’s name and search capability. Like Organization and Article, this is foundational markup your SEO plugin normally emits, so the job is understanding it and configuring one clean copy — not hand-coding a duplicate.

What WebSite Schema Does

It declares the site as a WebSite entity with a name and url, letting Google associate a preferred site name with your domain — which is what can appear as the site name in search results.

The name here is a strong signal for the site-name feature in the SERP. It sits alongside your Organization entity — WebSite describes the site, Organization describes the publisher — and both are usually emitted together by your SEO platform.

The SearchAction Property

Inside WebSite, a potentialAction of type SearchAction gives Google the URL template for your internal search, e.g. https://example.com/?s={search_term_string}.

This is what historically let Google render a search box directly in your branded result. The template must point at a working search endpoint — on WordPress that is typically the native /?s= query, the same surface the site’s header search uses. If the endpoint is wrong, the markup is inert.

Google deprecated the dedicated sitelinks search box feature, so the markup no longer reliably renders an in-SERP search box — but WebSite + SearchAction still helps Google understand your site name and search capability.

Do not add this markup expecting the old search box to appear; treat it as entity and site-name signaling. This is the same “valid but the rich result was retired” pattern seen with HowTo — the markup stays useful for understanding even when the visual feature is gone.

Who Should Output It

Your SEO plugin almost always emits WebSite schema with the correct SearchAction — configure your site name there and leave it as the single copy.

Adding a second WebSite block by hand duplicates the entity and can conflict on the search-template URL. Confirm what your platform outputs with the Rich Results Test before considering any manual addition.

Example Markup

WebSite with a SearchAction (shown as code):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Example Co",
  "url": "https://example.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://example.com/?s={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>

See JSON-LD vs Microdata for why this format is preferred.

Key Takeaways

  • WebSite schema names your site as an entity and supports the site-name feature in results.
  • SearchAction declares your internal search URL template — it must point at a working search endpoint.
  • The sitelinks search box feature was deprecated, so the markup no longer reliably renders a SERP search box.
  • It still helps Google understand site name and search capability — keep it as signaling, not a rich-result play.
  • Let your SEO plugin own the single copy; do not hand-add a duplicate WebSite block.

Frequently Asked Questions

Does SearchAction still show a search box in Google?

Not reliably — Google deprecated the sitelinks search box feature. The WebSite + SearchAction markup remains valid and still helps Google understand your site name and internal search, but you should not expect the in-SERP search box to appear.

What URL should the SearchAction target?

Your working internal search endpoint with a query placeholder — on WordPress that is usually https://yoursite.com/?s={search_term_string}. Test that the URL actually returns search results; a broken endpoint makes the markup useless.

Do I need WebSite schema if I have Organization schema?

They serve different purposes — WebSite describes the site (and its name and search), Organization describes the publisher. Most SEO plugins emit both together, so you generally do not choose between them, just configure them once.

The Bottom Line

WebSite schema and SearchAction are quiet, foundational markup: they reinforce your site name and search capability even though the old search-box rich result is gone. Let your platform emit one clean copy pointing at a real search endpoint, and move on to the page-specific types in the schema cluster that still earn visible results.


Further reading & sources

See how your site actually shows up in AI search. An AI visibility audit maps where you’re cited, where you’re invisible, and what to fix first — in plain English.

Get your AI visibility auditTry the free SEO tools →

Prefer self-serve? The interactive checklists turn guides like this one into a working to-do list.

Keep reading in Schema Markup

Get one email when something genuinely changes

AI search moves fast and most of it is noise. We send one short email when a real shift is worth your time. Unsubscribe anytime.

Published by Plain Intelligence — practical AI SEO, GEO, and technical SEO, documented in plain English. About Plain Intelligence →

↑ Back to Schema Markup · Explore all articles · Free tools & resources · Glossary