We now support sitenames for subdomains on all devices in some languages. We also updated how the site names system works, to increase its ability to make selections that are representative of sites listed in search results.
Google Search Central Blog
An update on site names Google for Developers
Stay organized with collections
Save and categorize content based on your preferences.
In May, we introduced support for site names for subdomains on mobile devices only, for English, French, German, and Japanese.
We now support subdomains on all devices in these languages.
In addition, we recently updated how the site names system works, to increase its ability to make selections that are representative of sites listed in search results.
As a reminder, the best way to indicate a preferred site name to Google is to make use of WebSite structured data, as explained on our site name documentation.
We’ve also now updated that documentation to encourage more use of the alternateName property.
Sometimes, a preferred site name isn’t available for use.
For example, our system generally won’t use the same site name for two different sites that are global in nature.
Providing an alternative name using the alternateName property allows our system to consider other options, if your preferred choice isn’t selected.
A workaround if your preferred or alternative names are not selected
In rare cases, our system might not select either a preferred or alternative site name.
This could happen if a name doesn’t appear to be unique, concise, or commonly-recognized with a particular site.
Our documentation now has a workaround for this case.
If you provide your domain or subdomain name as a site name, that will be generally used.
Before trying this workaround, we’d encourage reviewing that preferred and secondary names are provided through WebSite structured data and that other sources on your home page help support that structured data.
A known issue with internal pages
We’re aware that in some cases, a site name shown for a home page may not have propagated to appear for other pages on that site.
For example, https://example.com/ might be showing a site name that’s different from https://example.com/internal-page.html.
We’re actively working to address this.
We will update the documentation when this issue is resolved.
In the meantime, if your home page is showing the site name you prefer, understand that it should also appear for your internal pages eventually.
We’re also working to bring site name support to all languages globally in the future.
Should you have any questions, feel free to post in the Search Central help community.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
[
“type”: “thumb-down”,
“id”: “missingTheInformationINeed”,
“label”:”Missing the information I need”
,
“type”: “thumb-down”,
“id”: “tooComplicatedTooManySteps”,
“label”:”Too complicated / too many steps”
,
“type”: “thumb-down”,
“id”: “outOfDate”,
“label”:”Out of date”
,
“type”: “thumb-down”,
“id”: “samplesCodeIssue”,
“label”:”Samples / code issue”
,
“type”: “thumb-down”,
“id”: “otherDown”,
“label”:”Other”
]
[
“type”: “thumb-up”,
“id”: “easyToUnderstand”,
“label”:”Easy to understand”
,
“type”: “thumb-up”,
“id”: “solvedMyProblem”,
“label”:”Solved my problem”
,
“type”: “thumb-up”,
“id”: “otherUp”,
“label”:”Other”
]
Recent Comments