Google Still Shows the Old Site Name: What Should You Check After a Website Redesign?

If Google search results still show the old website name, first identify which element is wrong, then check the relevant pages and settings. Changing the name in the administration system only shows that the website has been edited. Whether Google has processed the change and which name it ultimately selects need separate observation.

In plain language, the site name identifies “which website this result comes from,” the title link explains “what this page is about,” the favicon is the small icon beside it, and Organization data represents the company or organization's identity. They may all use the same brand, but their settings and verification methods differ.

Save a Search Result That Clearly Shows the Problem

Record the search query, destination URL, displayed text, date, device, and the name you believe is correct. Keep the complete result in the screenshot so you can distinguish whether the old brand appears in the site name, page title, or icon.

Google handles site names separately from the title links for individual pages. Title links may also draw on the main page heading and other information instead of simply copying the SEO title in the administration system. Google's site name documentation and title link documentation explain these separate rules.

If the problem is an outdated year or product name in a title, assign it to the editor responsible for that page and use the checks for SEO titles and main page headings. If the company identity, official name, or logo relationships are unclear, first review how Organization information should match public facts.

Find the Correct Homepage, Then Check Name Preferences

The aim is to have developers inspect the page that actually carries the site name. First list the canonical homepage the website uses and its redirects from old addresses. Do not infer Google's entry point merely because the administration system has a section called “Homepage.”

According to Google's technical guidelines, site names are supported at the domain and subdomain levels, with the markup on the corresponding root homepage. https://example.com/ and https://news.example.com/ are such entry points. https://example.com/en/ is a subdirectory and cannot have its own separately specified site name.

Ask developers to check the existing WebSite data on the homepage: whether name is the approved name, url points to the canonical homepage, and alternateName genuinely represents an abbreviation or alternative name. If a node of the same type already exists, update it rather than leaving conflicting versions from the theme, plugins, and manually written code.

When the domain itself is used as an alternative name, Google's requirements call for lowercase, such as example.com. This applies to the domain used as a name preference; the homepage URL should still be the actual canonical address. Do not stuff a series of service keywords into the name for SEO. Google's alternative name guidance describes the conditions.

The check succeeds when the responsible owner has approved the name and abbreviation, developers can identify their configuration source and the homepage where they are output, and the existing nodes do not conflict.

Check Homepage Text, Duplicate Versions, and Redirects Together

The goal is to find inconsistent information that remains public, rather than only changing hidden code. Suppose a website changes from “Brand A” to “Brand B”: if the header uses the new name but the homepage title and theme settings still use the old one, record these locations separately and confirm the version to use.

Check the visible homepage name, og:site_name, title, and main text. Historical descriptions can explain the renaming, while the current identity should be clear to readers. When finding an old name, first determine whether it is historical information or an overlooked update; do not replace every occurrence indiscriminately.

If identical homepages still exist across HTTP/HTTPS or www/non-www versions, Google requires consistent site name data on these duplicate pages. Check existing redirects, their final destinations, and whether those destinations are accessible. Google's site name troubleshooting guidance explains both checks.

Give the following table to the maintainer. Record what was observed first, then the outcome. Leave items awaiting access or evidence marked as unconfirmed.

Use the Right Tools: A Pass Does Not Mean the Name Has Changed

First confirm that the technical output can be read, then observe the search result. Google explicitly states that Rich Results Test does not support site names. The official testing guidance makes this distinction.

Use Schema Markup Validator to check markup syntax, then Search Console's URL Inspection tool to check homepage accessibility. Record the two results separately so developers can identify whether they need to address an output error or an access problem.

Ask maintainers to record whether login requirements, crawling settings, or indexing settings affect the homepage. If a tool reports an issue, save the specific message and tested URL for developers to assess. Passing a syntax check does not prove the name is accurate, every homepage is consistent, or Google search results have adopted the new name.

The check succeeds when the live homepage output matches confirmed information, the checks needed for Google access have no unexplained issues, and the business owner understands which items remain outside the checked scope.

Keep Observation Records After Submission and Follow Up on Differences

After checks pass, you can request recrawling of the correct homepage and record the submission date and selected version. Google still needs to recrawl and process the information, and the system selects the name automatically. No submission button guarantees that a specified name will appear immediately. Google's processing and troubleshooting guidance sets these boundaries.

When reviewing results, use the previously recorded query and result URL where possible. If the homepage shows the new name but an internal page still shows the old one, record them separately instead of declaring everything complete because one location changed. If only one result remains incorrect, repeatedly changing an already approved brand name is not necessary.

If the preferred name is still not used, recheck the public text, markup, redirects, and access conditions against the original list. Evaluate an alternative name only when there is a genuinely used abbreviation. Retain separate records for “website changes completed,” “check results,” and “search display observations” so the next maintainer can identify the stage the work has reached.