Skip to content

Wrong site name on Google? Check the homepage markup

Fix a wrong site name in Google Search by tracing the homepage URL, comparing WebSite markup with visible branding, and testing what Google can read.

By Crawlito · 6 min read

In short

  • Google takes site name preferences from a domain or subdomain homepage.
  • One WebSite node can carry both the preferred name and a recognizable alternative.
  • Checking the indexed homepage and its current HTML helps date a branding change.
On this page

When Google shows the wrong name above a search result, inspect the homepage for the host that owns the result. Give that homepage one recognizable site name in its visible branding and its WebSite structured data. Google chooses the displayed name automatically, so you can verify the signals you publish and separately observe what appears in Search.

Identify the part of the result that is wrong

Suppose a search for a repair manual shows “Workshop Resources” above a blue link called “Replace a worn drive belt.” Someone on your team wants to rename the article. Before publishing that change, ask them to point to the incorrect words in a screenshot. The source name above the result, the blue title, the path beneath the name, and the description each answer a different question about the page. If the article title is accurate, a rewrite could undo good editorial work while leaving the homepage problem untouched.

Save the result URL and follow it to the final host. A manual on support.example.com can have a different homepage from a manual on example.com/support/. Google supports site names at the domain or subdomain level and generally treats the www and mobile prefixes as equivalent to the main host. A directory on the same host shares its site's name. A team that publishes several brands under directories can still identify each one clearly in the article title, visible heading, and navigation. Google’s site name documentation

Record the query, host, language, and observation date. A screenshot with the address cropped out is surprisingly difficult to interpret after a migration. If the wrong text is the blue link, work through the guide to rewritten title links before adjusting the site identity.

Trace the homepage a visitor actually reaches

Start a fresh browser session and open the root address on the result host. Follow any redirect to its destination. Note the final address, which name is visible in the header, what the footer calls the organization, and whether the page is a language chooser. Repeat the request without your usual account, preview cookie, or remembered region. This can explain why a content editor and an outside visitor report different names for the same homepage.

bash
curl -sSL -D home-headers.txt -o home.html https://support.example.com/

The headers file contains the responses on the way to the saved HTML. Look for the last status and check the body for a distinctive line of homepage copy. A successful response with only a “choose your workspace” screen deserves attention before you edit JSON. A redirect from the support root into a directory on another host also changes the document you have to inspect. For variants that actually serve duplicate homepages, keep the naming information consistent on those copies.

Make a small inventory, one row per address that serves a homepage. Useful columns are requested URL, final URL, visible name, canonical URL, and structured name. A row for a retired host that permanently redirects can name its destination. A row that returns an independent homepage needs a decision from the person responsible for that brand. See how canonical signals fit together.

Put the preferred name in the existing WebSite node

Find all homepage JSON-LD scripts and look inside graph arrays as well as top-level objects. A theme may create one WebSite entity while an SEO extension creates a second one. Edit the component that owns the site's identity. If the existing node uses an @id referenced elsewhere in the graph, preserve that identifier and add the name to that node. Recognizable short names can go in alternateName. Use a name that customers already encounter when opening the site.

json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://support.example.com/#website",
  "url": "https://support.example.com/",
  "name": "Elm Workshop Manuals",
  "alternateName": "Elm Manuals"
}

In this example the publisher might legally be Elm Manufacturing Ltd. That company can have its own Organization node. Check the difference with the organization markup guide. A company can operate a manual library, a shop, and a news publication under distinct public names. Putting the company registration string in every name field erases that distinction. Equally, adding a string of service keywords to the site name makes it harder to recognize the publication someone already knows.

Review the homepage title, visible heading, logo text where appropriate, and og:site_name along with the JSON. They can use natural wording. A homepage title such as “Elm Workshop Manuals | Service and parts guides” still identifies the publication. The concern is a contradiction like “North Works Archive,” left behind in social metadata after a rebrand.

Verify the release and date the evidence

Inspect the public root again after the release. Save the fetched HTML, check that the inspected node is present only as intended, and search the file for the retired name. Some occurrences might be accurate historical references. A former name in the history of the company has a different purpose from one emitted by the active site header. Review each occurrence in context before changing a global string.

Use a schema validator that shows WebSite markup and Search Console's URL Inspection for the homepage. Google's site name documentation points to the Schema Markup Validator for this feature. Record when the last indexed crawl occurred, then compare with your release time. The indexed copy can still describe yesterday's homepage even when a live fetch shows today's name. If your host has multiple active languages, inspect the root and the alternate entry paths actual visitors follow. The URL Inspection walkthrough explains where the live and indexed views differ.

Keep one short acceptance note. For example, the public support root now serves the manuals homepage, its JSON names Elm Workshop Manuals, and the last indexed crawl predates the change. That evidence gives the developer a clear finish line. The person following search appearance can return to the original query after a new crawl and compare the same part of the result.

Diagnose a rebrand with two homepages

Consider a publisher that renamed its main publication but kept a support subdomain under the old brand during a transition. A result for a support article and a result for the new publication might quite reasonably show different source names. Open both homepage roots and ask the owners whether each is supposed to represent the same brand today. If the old support identity is intentional, preserve it there and investigate only the publication that actually changed.

If the support library changed names too, look for where it inherits metadata. A shared logo component may have picked up the new name immediately while the support application still reads a separate site configuration for its structured data. Capture the relevant value in the source for each host and give the configuration owner the specific mismatch. This produces a small, testable repair and avoids imposing the publication's name on other independent sites operated by the same organization.

Frequently asked questions

Can each folder have a different Google site name?

Google documents support at the domain and subdomain level. A folder can have its own section title and clear page titles while sharing the site's source name.

Should every article contain another WebSite block?

Google asks for the preference on the homepage. Fix the homepage's existing entity and keep each article's own headline and publisher information accurate.

What if Google displays the domain itself?

Check access to the homepage and whether its preferred name is consistent and distinctive. A domain label alone does not identify a particular markup error.

Check the public homepage

Start with the exact host from the search result. Run the free page check on its homepage to see what a fresh request can read before you edit another article title.

Filed under Structure and schema. Topics: google, structured-data, troubleshooting