Site name not showing in Google Search is one of those problems where the fix is small and the waiting is long. The line above the URL in a result, the one that says the name of your site rather than the domain, is generated by Google, not read from a setting. You cannot set it. You can only feed it better inputs and then wait.
I add this markup on every property I set up, including this one, so I have watched it land and watched it get ignored. The difference between the two is almost always one of the four things below.
Why is my site name not showing in Google?
Start with what Google actually says, from the site names documentation:
Google’s generation of site names on the Google Search results page is completely automated and takes into account content from a site’s home page and references to it that appear on the web.
And immediately after that, the sentence that ends most support tickets:
While we can’t manually change automatically selected site names, you can indicate alternatives.
So there is no field, no form, and no request button. What you get is a vote. Google says it reads WebSite structured data on the home page first, then “will also consider content in og:site_name, <title>, heading elements, and other text on a home page”. Four inputs, all of them on one page.
The four common reasons the name you want does not appear:
- The markup is not on the home page. It has to be at the root of the domain or subdomain, not on an inner page, not on every page instead of the home page.
- Google cannot reach the home page. Google is blunt about this: “If we don’t have access to the content on your home page because it is blocked, we may not be able to generate a site name.”
- Your four signals disagree with each other. The WebSite name says one thing, the title tag says another, the og:site_name says a third.
- The name is generic. Google says names like “Best Dentists In Iowa” are “unlikely to be selected”, and a name already used by another well known global site generally will not be reused for you.
Source: Google Search Central, site names documentation, read 23 August 2026.
What structured data does Google want?
WebSite, on the home page, with two required properties and one that does the real work. name is the name you want. url is the home page URL. alternateName is where you list the other forms of your name, and Google’s instruction is specific: “You can list more than one alternative name”, with “the most important one listed first”.
That third property is the one people skip, and it is the one that helps. If your brand is “Northgate Roofing Ltd” but everyone links to you as “Northgate Roofing”, both belong in the markup. The alternates are not a fallback list you hope Google ignores; they are you telling Google which strings refer to the same entity.
The other detail worth knowing before you test: the Rich Results Test will not help you here. Google says plainly that site names are not supported in it. Use the Schema Markup Validator to confirm the markup parses, and then confirm Google can fetch the home page at all with the URL Inspection tool.
While you are in there, it is worth a glance at whether your JSON-LD is even being read correctly, because Google changed how it unescapes JSON-LD this week and a name containing an ampersand is exactly the kind of value that change affects.
Does the site name work for subdomains and subdirectories?
This is the rule that decides whether the answer is “fix your markup” or “you cannot have what you want”, so it is worth quoting in full:
Currently, Google Search only supports one site name per site, where a site is defined by the domain or subdomain. Google Search does not support site names at the subdirectory level.
One name per domain or subdomain. If you run example.com/uk/ and example.com/de/ and you want them named differently in search results, there is no way to do that; they are one site as far as this feature is concerned. If you run shop.example.com, that is a separate site and can carry its own name, and if you leave its home page without markup, Google says “the domain-level site name may be used for the subdomain”.
www and m prefixes are treated as equivalent to the bare domain, which is the sensible outcome and saves you worrying about which one is canonical for this purpose.
Site names are available in every language Google Search runs in, on mobile and desktop, so a missing name is not a regional rollout problem.
How long does a site name change take?
Google’s own troubleshooting section says to allow “anywhere from several days to several weeks” after the fix and a recrawl. That is the honest range and it matches what I see: the markup is not the slow part, the recrawl and the confidence-building are.
The order I work in, which is designed to remove every reason for Google to disagree with you before the clock starts:
- Put WebSite markup on the home page with
name,url, and the alternates in priority order. - Make the other three signals say the same thing. The
og:site_name, the home page<title>, the main heading. Google’s guidance is to use the same name “consistently across your home page” and across the HTTP and HTTPS versions if both still resolve. - Check your redirects. If
wwwand non-www both serve a home page with different names, you have two votes fighting. - Confirm the home page is crawlable and indexed. If it is not, nothing above matters, and the reason it is not is usually one of the statuses in the Search Console indexing statuses guide.
- Request a recrawl of the home page in URL Inspection, then leave it alone.
The step people get wrong is 5, in the same way they get it wrong with fix validation: they resubmit every few days, which achieves nothing. There is no queue position to improve. If you want to know whether Google has picked the change up at all, check whether the home page’s last crawl date has moved, not whether the name has changed. If you are checking a batch of properties at once, that is what the bulk URL inspection tool is for.
One thing I will not tell you is that the markup guarantees the name. It does not. Google reserves the automated decision explicitly, and I have set up properties where the correct markup sat there for a month while the results kept showing the domain. In every case I have seen it resolve, the resolution came after the site started being referred to by that name off-site as well, which fits Google’s own description of “references to it that appear on the web” being part of the input.
Sources
- Google Search Central, Provide a site name to Google Search, including the technical guidelines and troubleshooting sections, read 23 August 2026
- Google Search Console Help, URL Inspection tool
- Schema.org, Schema Markup Validator