Google is now only showing the site name in mobile search results that are for the entire website, such as for the home page
Google appears to have stopped showing title tags for mobile search results for the entire website such as in searches for the name of a website which generally show the home page.
This feature does not work for subdomains.
According to Google’s Search Central documentation for site names:
Currently, Google Search supports site names from homepages at the domain level, not at the subdomain (for example, https://news.example.com) and/or subdirectory (for example, https://example.com/news) level.
What’s being shown in mobile searches is just the generic name for a website.
Non-branded searches for keywords appear to still show the title tags.
Brand name + keyword searches also appear to still show the title tags.
Why Is Google Using Site Names?
Google is using site names to make it easier for users to identify the specific website in the search results.
Google’s official announcement explained:
Today, Search is introducing site names on mobile search results to make it easier to identify the website that’s associated with each result…
This new feature is available in the English, French, Japanese, and German languages and will begin showing up in other languages over the next few months.
New Feature Doesn’t Always Work
A search for a compound word domain name like “The Seo Doctors” and “theseodoctors” return the same search results that featured the new site names as the title link.
Structured Data for New Site Names Feature
Google is recommending the use of the Website's structured data type.
Previously the Website structured data site was considered pointless because obviously, Google knows a website is a website and it didn’t need structured data to understand that Google was indexing a website.
But that’s changed because Google is now using the WebSite structured data type, specifically the “name” property, to understand a website's site name.
Google published an example of the WebSite structured data with the “name” property in use:
<title>Example: A Site about Examples</title>
<script type="application/ld+json">
{
"@context" : "http://schema.org",
"@type" : "WebSite",
"name" : "Example",
"url" : "https://example.com/"
}
</script>
The above-structured data must be shown on the home page.
Google’s Search Central page for site name recommends the following for placement of the WebSite structured data:
“The WebSite structured data must be on the homepage of the site.
By homepage, we mean the domain-level root URI.
For example, https://example.com is the homepage of the domain, while https://example.com/de/index.html isn’t the homepage.”
What if a Site Has an Alternate Name?
What’s useful about the Website structured data is that it offers the opportunity to tell Google the alternate name of the website.
Google explains how to do it:
If you want to provide an alternate version of your site name (for example, an acronym or shorter name), you can do this by adding the alternate name property.
This is optional.
The structured data for adding an optional name looks like this:
JSON Structured Data for Optional Name
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "WebSite",
"name": "Example Company",
"alternateName": "EC",
"url": "https://example.com/"
}
</script>
Google Uses More Than Structured Data
The Google documentation on-site names explain that Google is using on-page, off-page, and metadata information in addition to structured data to determine what a webpage site name is.
This is what Google uses to understand the site name:
- Website structured data
- Title tag
- Headings (H1, H2, etc.)
- Open Graph Protocol metadata, specifically the og:site_name
Something to take note of is that o the site_name property is an optional but recommended Open Graph property.
The Open Graph notation generally looks like this in the HTML code:
<meta property="on:site_name" content="Example Name of Site" />
Google Site Names
The new site names feature in Google search looks attractive on mobile devices
Content Source: Searchenginejournal.com
0 Comments