Website Schema Generator
Fill in the details below
Your output will appear here.
The website schema generator builds WebSite structured data in JSON-LD from your website name, home page URL and, if you have one, your site search URL. It is for site owners and SEOs who want Google to use the right site name in search results. It runs in your browser and is free with no sign-up. Copy the code onto your home page.
Fill in the details below
Your output will appear here.
Enter Website Name, URL and an optional Search URL. No coding or schema knowledge needed.
The name and url properties tell Google which site name you prefer for your home page.
The Search URL you enter becomes a SearchAction target. Leave it empty and no SearchAction is added.
The code is built on the page in your browser, so you can copy it straight away.
Three steps from a blank form to a result you can use.
Type the website name you want shown in search, the home page URL and your search results URL, ending where the search term goes.
Click Generate and the tool builds a WebSite JSON-LD block from exactly what you entered.
Copy the ready-to-paste script block into the head of your home page, then test it with a schema validator.
WebSite schema is a small piece of structured data on your home page that names your site. Google uses it as the strongest signal when it picks the site name shown above your results.
https://www.example.com/.https://www.example.com/search?q=. Run a search on your site and copy the address bar up to the term you typed. The tool adds {search_term_string} straight after it, so do not add it yourself. If your site has no search, leave Search URL empty and the tool leaves the potentialAction block out.<script type="application/ld+json"> block, ready to paste into your home page.The tool uses only what you type. It does not visit your site or check that the URLs work, so double-check them before you publish.
WebSite markup has two parts, and Google now treats them very differently.
| Part | Generated From | Current Use in Google |
|---|---|---|
name and url | Website Name, URL | Used to indicate your preferred site name in search results. Both properties are required. |
potentialAction SearchAction | Search URL | Powered the sitelinks search box, which Google removed from results in November 2024. Leftover markup does not cause problems. |
alternateName | Not a field in this tool | Recommended. Lets you list other names, such as an acronym, in order of preference. |
Google picks a site name from several signals, including the <title> element, headings, the og:site_name tag and other text on the home page. WebSite structured data is the clearest way to state your preference. If Google shows a shortened domain or an odd name instead of your brand, this markup is the first thing to add.
Only if your site really has a search page. The SearchAction no longer produces a search box in Google, and Google says leftover markup does not cause issues, so keeping an accurate one is harmless. If your site has no search, leave Search URL empty: the tool then leaves out the potentialAction block, because a target that points nowhere would describe a feature your site does not have.
Example: This is an illustration. A shop enters:
The tool returns a ready-to-paste block like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Northwind Garden Supply",
"url": "https://www.example.com/",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.example.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>Notice that {search_term_string} is added directly after the Search URL. That is why the Search URL must end with q= (or your site's equivalent). Entering https://www.example.com/search would produce a broken target.
If the shop is also known as "NGS", we would add "alternateName": "NGS", by hand after the name line before publishing. A shop with no site search would delete the potentialAction block and the comma before it.
https://example.com/de/index.html is not a home page for this purpose.<script type="application/ld+json"> tags, so paste it as it is, usually in the head. In WordPress or another CMS, use a header code field or a custom code setting.For other page types, such as articles, products or local business details, a general schema markup tool fits better. This generator covers WebSite markup only.
Quick answers about the Website Schema Generator.
WebSite schema is structured data from schema.org that describes a whole website, mainly its name and home page URL. Google uses WebSite markup on the home page to understand your preferred site name for search results. It can also include a SearchAction that describes how your on-site search works.
No. The website schema generator is a simple form that runs in your browser. It places your Website Name, URL and Search URL into a fixed WebSite JSON-LD block, so the same inputs always give the same code. Nothing is guessed or rewritten, which makes the output predictable and easy to check.
No. Google removed the sitelinks search box from search results in November 2024. SearchAction markup no longer creates that box, but Google said leftover markup will not cause issues in Search, so you do not need to remove it. The site name part of WebSite schema is still supported.
Add it to your home page only, ideally in the head section. The output already includes the script tags, so paste the whole block as it is. Google reads site name markup from the home page of a domain or subdomain. On WordPress, use a header code field or your SEO plugin's custom code setting.
Enter your search results address up to the point where the search term goes, such as https://www.example.com/search?q= or https://www.example.com/?s= on many WordPress sites. The tool adds {search_term_string} straight after it. If your site has no search, leave it empty and the tool leaves the potentialAction block out.
Use the Schema Markup Validator to check the code, because Google's Rich Results Test does not support site names. Then use the URL Inspection tool in Search Console to confirm Google can access your home page. Allow time for Google to recrawl the page before the site name changes.
This tool has no field for it, but you can add an alternateName line to the code by hand. Google recommends it for names such as acronyms and lets you list several, with the most preferred first. Keep the main name in the name property and alternatives in alternateName.
Our article schema generator builds Article, BlogPosting or NewsArticle structured data in JSON-LD from a...
Turn your questions and answers into FAQPage structured data in JSON-LD format.
The title tag generator writes SEO title tag options with AI from your keywords and a short note on what the...
This sales page generator writes a full sales page draft from a description of your product.