What are the requirements for site name structured data?

ProcrustesPR

The core requirement for site name structured data is to add WebSite markup to a domain or subdomain homepage that Google can crawl. The markup must include name (the site name) and url (the canonical homepage URL), and the name should be consistent with other text on the homepage. Only one site name is supported per domain or subdomain; subdirectories are not supported. This setting communicates a preference to Google but does not guarantee that search results will use the specified name.

ProcrustesPRProcrustesPRHow should you balance CNAME convenience and performance?

Make sure the homepage is at the domain or subdomain level

A site name represents the entire website and is distinct from the title link for an individual page. Google defines the homepage as the root address (root URI) of a domain or subdomain, not any page within a website that happens to be called a “homepage.”

  • example.com and news.example.com: these are at the domain and subdomain levels, respectively, and can have site names.
  • example.com/news: this is a subdirectory and cannot have its own site name.
  • Subdomains beginning with www or m are generally treated as equivalent, so you should not assume that each can have its own name.

If a subdomain homepage has no structured data, the system may use the domain-level site name as a fallback, but this is not guaranteed.

Check the required properties and markup placement

You can add WebSite markup using JSON-LD, RDFa, or Microdata. The required properties are:

  • name: the site name, which must follow the guidelines for choosing a site name.
  • url: the canonical homepage URL of the domain or subdomain, not the URL of an article or category page.

The markup only needs to be placed on the homepage, not on every page. However, if you have duplicate homepages with identical content across HTTP/HTTPS or www/non-www versions, all versions should use the same structured data; updating only the canonical version is not enough. If the homepage already has WebSite markup, integrate the site name properties into the same node wherever possible rather than creating an additional block.

Use an accurate, consistent name, and consider providing alternatives

Choose a concise, widely recognized name that accurately reflects the website without misleading users. There is no length limit, but an overly long name may not display in full on some devices. Generic names are generally less likely to be selected unless they belong to a very well-known brand.

The system also considers the homepage’s og:site_name, title, heading elements, and other text, so these should be consistent with the name in the markup. You can use alternateName to provide alternatives for the system to consider if it does not use your preferred name. This does not mean that the same website can display multiple site names at once.

Beyond validating syntax, make sure the homepage is accessible

The Rich Results Test does not support site names. Use a tool such as the Schema Markup Validator to check the syntax, then use the URL Inspection tool to check how Google renders the homepage. The homepage should not be blocked by robots.txt, noindex, or a login requirement.

Once you have checked everything, you can request recrawling, but Google may take a few days to several weeks after publication to discover and crawl the page. Even with correct markup, the system still selects the name automatically. If it cannot determine that a name is appropriate, it may use other sources or display the domain or subdomain name.

ProcrustesPRProcrustesPRShould you use a 302 redirect to a temporary alias for the new server during a DNS update?

Site name structured data: perspectives from across the web

Does correct markup syntax guarantee compliance with Google’s requirements?

No. Beyond having correct syntax, structured data must accurately represent the page’s content. It must not mark up information that readers cannot see, that is irrelevant, or that could be misleading. It must also not impersonate others or misrepresent the website’s ownership, affiliation, or primary purpose. Google notes that automated tools cannot easily check full compliance with its quality guidelines, so you still need to review the content yourself.

Do you also need to add article or product markup when setting up a site name?

No. You do not need to add other types of markup just to set up a site name. Google lists name and url as the required WebSite properties for site names. Whether to add article, product, or video markup depends on the website’s content and needs. A 2022 awoo article listed these markup types as examples to consider, not as requirements for setting up a site name.

ProcrustesPRHow does HSTS protect websites and subdomains?

References

  1. 結構化資料通用指南 | Google 搜尋中心  |  Documentation  |  Google for Developersdevelopers.google.com — Discusses: Does correct markup syntax guarantee compliance with Google’s requirements?
  2. Google 搜尋中的網站名稱 | Google 搜尋中心  |  Documentation  |  Google for Developersdevelopers.google.com — Discusses: Do you also need to add article or product markup when setting up a site name?
  3. 2023 SEO十大趨勢,讓企業掌握流量新高度www.awoo.ai · 2022-12-11T04:20:20+00:00 — Discusses: Do you also need to add article or product markup when setting up a site name?

Related articles

How should you balance CNAME convenience and performance?Should you use a 302 redirect to a temporary alias for the new server during a DNS update?How does HSTS protect websites and subdomains?How do SSL certificates protect websites, and why are they needed?Should a Tumblr blog use the platform’s domain or the company’s domain?What types of URLs are there, and what are they used for?When should you use relative or absolute paths in WordPress?What are www subdomains and relative links used for?
ProcrustesPR
ProcrustesPR