---
title: "Google shows the wrong site name on WordPress | WP Ministry"
url: https://wpministry.co/blog/google-shows-wrong-site-name-wordpress/
description: "Google chooses the site name automatically. WebSite data on the home page states a preference. WordPress does not print it. The name is not each page's title."
lang: en-US
---

Skip to content

# Google shows the wrong site name: what you can set on WordPress

The site name in Google's results is chosen automatically. Google says WebSite structured data on the home page is the strongest way to state a preference, and that it may still show the domain. WordPress does not print that data. The name is not the title of each page.

By

WP Ministry

Published

November 15, 2026

## In short

- The site name is the source shown for the whole site. Title links are a different line, one per page.
- Google generates the site name automatically from the home page and from how other sites refer to it. It says it cannot change a name by hand.
- WebSite structured data on the home page is what Google calls most important if you want to name a preference. It also reads the title, headings and og:site_name.
- A default WordPress prints none of that structured data. The home page has to gain a single WebSite block.
- The data is supported on a domain or a subdomain, not on a subdirectory. www and the bare domain count as one site.
- Google may still show the domain. Providing the domain as an alternate name is the fallback its own page describes.

Google's site name is the name it shows as the source of a result. It is not the title of each page. Google's documentation says title links are specific to each page, and the site name is for the whole site. A wrong title is a different problem from a wrong site name. This page is the site name.

Google says the name is generated automatically from the home page and from references to the site elsewhere on the web. The goal it states is to represent the source of each result. It also says it cannot manually change a name the system selected. What you can do is state a preference and give an alternative.

## What Google reads

Google's page on site names says to add `WebSite` structured data on the home page if you want to specify a preference. It also considers `og:site_name`, the `title` element, heading elements and other text on the home page. It calls the structured data the most important of those if you want to name a preference.

The same page's rules for the name:

- One name per site. A site, for this feature, is a domain or a subdomain. A subdirectory such as `example.com/news` cannot have its own site name. `www` and a host that starts with `m` are generally treated as the same site as the bare domain. A subdomain such as `news.example.com` can have its own, and if that subdomain's home page has no structured data, the domain's name may be used as a fallback.
- The `WebSite` data has to be on the home page, meaning the root of that domain or subdomain. It does not have to be repeated on every page.
- The home page has to be crawlable. If it is blocked, Google says it may not be able to generate a site name.
- If several addresses serve the home page, such as `http` and `https`, or `www` and the bare host, each duplicate should carry the same structured data, not only the canonical one.
- If a `WebSite` block is already on the home page, add the name to that block. Do not add a second one.
- The name should be the one the site actually uses, concise, and not a generic phrase. Google says a generic name is unlikely to be selected unless it is a genuinely well-known brand. A long name may be cut off on some devices.

Two properties are required: `name`, and `url` set to the canonical home page. `alternateName` is optional. Google says to list alternatives in the order you prefer. It also says its system sometimes will not use the same name for two different sites that are global in nature, and sometimes prefers an acronym. The alternative is what it considers in those cases.

A test recorded on what WordPress does with no SEO plugin (https://wpministry.co/blog/wordpress-seo-without-a-plugin/) found no JSON-LD on the home page: no `WebSite`, no `Organization`. The home page's title and headings are present. The preference Google calls most important is not. An SEO plugin may add the block. If it does, edit that block rather than adding another, which is Google's instruction.

## State the preference

Put one `WebSite` block in the head of the home page. This is the shape Google's documentation shows, with the name and the home page URL replaced by yours. Use the canonical home page, including the trailing slash if that is the address WordPress serves.

html

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Your site name",
  "url": "https://example.com/"
}
</script>
```

If you want a shorter alternative, Google's page adds `alternateName`. It can be a list. To give the domain as a last resort, add the domain in all lowercase as the last item. Google says the domain has to be lowercase for the system to treat it as a site-name preference, and that it will strongly consider the domain if the preferred name is not selected.

html

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Your site name",
  "alternateName": ["Short name", "example.com"],
  "url": "https://example.com/"
}
</script>
```

Use the name as it appears elsewhere on the home page. Google says the structured data should be consistent with the title, the headings and `og:site_name`. A default WordPress does not print `og:site_name` either, which the same no-plugin test recorded. If you add only the JSON-LD, keep the visible name in the header and in the title in line with it.

Google says site names are not supported in its Rich Results Test. It says to validate the JSON with a schema checker so the syntax is valid, then to inspect the home page in the URL Inspection tool and confirm it is not blocked by robots.txt, a noindex or a login. If the page looks right, you can ask Google to recrawl it.

WordPress will not keep a block you paste into a post. The home page's head is where it has to be, which means the theme, a small must-use plugin, or a plugin that already prints `WebSite` data. Whichever you use, view the source of the home page afterward and confirm there is one block, that `url` is the canonical home page, and that the page is not a subdirectory.

## If the name still does not change

Google's page says the system generally tries to use the name in `WebSite` data, and that if it is less confident it may generate a name from other sources or show the domain. The steps it lists:

1. Confirm the `name` is the one you want, that the JSON has no syntax errors, that the rest of the home page uses the same name, and that you are not trying to name a subdirectory.
2. If the home page redirects, the site name reflects the redirect target, provided the target is visible to Googlebot. Fix the redirect, then ask for a recrawl. Redirect error (https://wpministry.co/errors/redirect-error-search-console/) and Page with redirect (https://wpministry.co/errors/page-with-redirect/) are the Search Console rows for redirects that fail or succeed.
3. Use the same name on `http` and `https` if both still answer.
4. Allow time. Google says crawling can take from several days to several weeks, and that internal pages lag the home page even after the home page shows the name you wanted.

If that is still not enough, Google's own fallback is the `alternateName` list, then the lowercase domain as the preferred `name`. It calls the domain-as-name a last resort. It also says that if you have followed the steps and the name is still wrong, the place to report it is the Search Central help community, and that this helps Google look at the system. It does not say a report changes your site's name.

Nothing here changes the title link of an individual page. Google's site-name page keeps those separate on purpose.

A WordPress SEO audit (https://wpministry.co/services/wordpress-seo-audit/) can check that the home page sends one `WebSite` block, that the home page is the address Google can fetch, and that the visible name matches it. The name Google then shows is still Google's choice. The audit does not include a promise that the preference will be the one displayed.

## Common questions

Is the site name the same as the title tag?

No. Google says title links are per page and the site name is for the whole site. Changing a post's title does not change the site name. The home page is where the site name is set.

Will Google use the name I put in the structured data?

It might. Google says it generally tries to, and that it sometimes uses another source or the domain when it is less confident. The page says there is no manual change. An alternative name, and the domain in lowercase as a further alternative, are the options it documents.

Do I add the block to every page?

No. Google says the home page is enough, and that a second `WebSite` block on that home page should be avoided if one already exists.

My site lives in a folder, not on its own domain. Can I set a name?

Google says site names are not supported for a subdirectory. The name it can show is the domain's or the subdomain's. A folder such as `example.com/news` is the case it marks as not supported.

## More on this subject

- WordPress SEO: https://wpministry.co/topics/wordpress-seo/
- Error fix "Discovered - currently not indexed" on WordPress: Google has not fetched the page yet: https://wpministry.co/errors/discovered-currently-not-indexed/
- Error fix "Duplicate without user-selected canonical" on WordPress: https://wpministry.co/errors/duplicate-without-user-selected-canonical/
- Error fix "Indexed, though blocked by robots.txt" on WordPress: https://wpministry.co/errors/indexed-though-blocked-by-robots-txt/
- Error fix "Redirect error" in Search Console: a chain, a loop, or a bad address: https://wpministry.co/errors/redirect-error-search-console/
- Error fix "Sitemap could not be read" in Search Console: the fetch failed: https://wpministry.co/errors/sitemap-could-not-be-read/
- Error fix Soft 404 on WordPress: the page says it is missing, and answers 200: https://wpministry.co/errors/soft-404/

## SEO audit, done for you

SEO audit is $249. A written audit, each finding with its source, and up to 2 hours of fixes done and tested again.

More about this work: WordPress SEO audit (https://wpministry.co/services/wordpress-seo-audit/)

May we measure how this site is used?

A yes notes the pages of this visit and loads Google Analytics. A no keeps and loads nothing. See the cookies page (https://wpministry.co/legal/cookies/).

If you say yes, we note the pages you look at during this visit and load Google Analytics. If you say no, nothing is kept and nothing is loaded. The site works the same either way. The cookies page (https://wpministry.co/legal/cookies/) has the details.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://wpministry.co/#organization",
      "name": "WP Ministry",
      "url": "https://wpministry.co/",
      "logo": "https://wpministry.co/brand/logo.png",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "1309 Coffeen Ave STE 1200",
        "addressLocality": "Sheridan",
        "addressRegion": "WY",
        "postalCode": "82801",
        "addressCountry": "US"
      },
      "sameAs": [
        "https://www.linkedin.com/company/wp-ministry/",
        "https://x.com/wpministryco",
        "https://www.instagram.com/wpministryco/",
        "https://www.facebook.com/wpministryco",
        "https://www.tiktok.com/@wpministryco",
        "https://www.pinterest.com/wpministryco/",
        "https://www.youtube.com/channel/UCOZRuAukk5QSTRPG6BaHl3Q"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://wpministry.co/#website",
      "name": "WP Ministry",
      "url": "https://wpministry.co/",
      "inLanguage": "en-US",
      "publisher": {
        "@id": "https://wpministry.co/#organization"
      }
    },
    {
      "@type": "Article",
      "@id": "https://wpministry.co/blog/google-shows-wrong-site-name-wordpress/#article",
      "headline": "Google shows the wrong site name: what you can set on WordPress",
      "description": "Google chooses the site name automatically. WebSite data on the home page states a preference. WordPress does not print it. The name is not each page's title.",
      "url": "https://wpministry.co/blog/google-shows-wrong-site-name-wordpress/",
      "mainEntityOfPage": "https://wpministry.co/blog/google-shows-wrong-site-name-wordpress/",
      "inLanguage": "en-US",
      "image": "https://wpministry.co/og/blog/google-shows-wrong-site-name-wordpress.png",
      "author": {
        "@id": "https://wpministry.co/#organization"
      },
      "publisher": {
        "@id": "https://wpministry.co/#organization"
      },
      "datePublished": "2026-11-15T00:00:00.000Z",
      "dateModified": "2026-11-15T00:00:00.000Z"
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://wpministry.co/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Guides",
          "item": "https://wpministry.co/blog/"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Google shows the wrong site name: what you can set on WordPress"
        }
      ]
    }
  ]
}
```