Issue #58 · standard
WebSite schema is missing from your homepage.
What is this issue?
WebSite schema is missing from your homepage. WebSite schema defines your website as a named entity, enabling Google's Sitelinks Search Box and helping search engines understand your site's identity.
Without WebSite schema:
- Your site won't have a Sitelinks Search Box in search results
- Google can't properly identify your site as a distinct entity
- Your site's identity is weaker in the Knowledge Graph
- AI search engines have less context about your website
A proper WebSite schema should include: @type (WebSite), name, url, @id (canonical site URL), description, and optionally potentialAction (for Sitelinks Search Box).
Why does it matter?
WebSite schema is important for site identity and search experience:
- Sitelinks Search Box: Enables users to search your site directly from Google search results
- Entity recognition: Helps Google understand your website as a distinct entity
- Knowledge Graph: Strengthens your site's presence in Google's Knowledge Graph
- AI search readiness: Provides AI engines with clear context about your website
- Brand consistency: Ensures your site name appears consistently in search results
Resolving this issue improves your SEO health score by establishing your website as a recognized entity in search engines.
How to fix it
-
Add WebSite JSON-LD structured data to your homepage
<head>:{ "@context": "https://schema.org", "@type": "WebSite", "@id": "https://www.example.com/#website", "name": "Your Website Name", "url": "https://www.example.com", "description": "Description of your website", "potentialAction": { "@type": "SearchAction", "target": "https://www.example.com/search?q={search_term_string}", "query-input": "required name=search_term_string" } } -
Include recommended properties:
@id: Use a consistent anchor (e.g.,https://www.example.com/#website)name: Your website name as you want it to appear in searchurl: Your website's canonical URLdescription: Brief description of your website
-
For Sitelinks Search Box, add
potentialActionwithSearchActiontype -
Make it referenceable: Other schemas (Article, BreadcrumbList) can reference this via
isPartOf -
Validate with Google's Rich Results Test
Examples
Example 1: Missing WebSite Schema on Homepage
Problematic state:
<!-- Homepage without WebSite schema -->
<html>
<head>
<title>Example Corp - Home</title>
</head>
<body>
<h1>Welcome to Example Corp</h1>
<p>Your trusted partner for digital solutions.</p>
</body>
</html>
Corrected state:
<!-- Homepage with WebSite schema -->
<html>
<head>
<title>Example Corp - Home</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"@id": "https://www.example.com/#website",
"name": "Example Corp",
"url": "https://www.example.com",
"description": "Your trusted partner for digital solutions."
}
</script>
</head>
<body>
<h1>Welcome to Example Corp</h1>
<p>Your trusted partner for digital solutions.</p>
</body>
</html>
Example 2: WebSite Schema with Sitelinks Search Box
Corrected state (with SearchAction):
{
"@context": "https://schema.org",
"@type": "WebSite",
"@id": "https://www.example.com/#website",
"name": "Example Corp",
"url": "https://www.example.com",
"description": "Your trusted partner for digital solutions.",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.example.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
Example 3: Incomplete WebSite Schema
Problematic state:
{
"@context": "https://schema.org",
"@type": "WebSite"
}
Missing required properties: name, url
Corrected state:
{
"@context": "https://schema.org",
"@type": "WebSite",
"@id": "https://www.example.com/#website",
"name": "Example Corp",
"url": "https://www.example.com",
"description": "Your trusted partner for digital solutions."
}
How PixyScan detects this
PixyScan follows these logical steps to detect missing WebSite schema:
-
Check homepage only: The crawler specifically examines the homepage (index page) of the website
-
Extract structured data: The crawler looks for JSON-LD, Microdata, or RDFa blocks on the homepage
-
Check for WebSite schema: The crawler verifies if any schema block has:
@typeset toWebSite- Required properties:
name,url
-
Validate schema completeness: If WebSite schema is found, the crawler checks for:
- Proper
@idproperty (canonical site URL) descriptionpropertypotentialActionfor Sitelinks Search Box (optional but recommended)
- Proper
-
Trigger conditions: The issue is flagged when:
- Homepage doesn't have WebSite schema
- WebSite schema exists but is missing
nameproperty - WebSite schema exists but is missing
urlproperty