{"id":9213,"date":"2023-04-26T12:50:51","date_gmt":"2023-04-26T12:50:51","guid":{"rendered":"https:\/\/craighordlow.com\/index.php\/2023\/04\/26\/google-updates-site-names-in-search-results-after-numerous-complaints\/"},"modified":"2023-04-26T12:50:51","modified_gmt":"2023-04-26T12:50:51","slug":"google-updates-site-names-in-search-results-after-numerous-complaints","status":"publish","type":"post","link":"https:\/\/craighordlow.com\/index.php\/2023\/04\/26\/google-updates-site-names-in-search-results-after-numerous-complaints\/","title":{"rendered":"Google updates site names in search results after numerous complaints"},"content":{"rendered":"

Google has pushed out a fix to resolve some of the inappropriate or unexpected site names selections displayed in the Google Search results. This comes days after Google posted a web form asking for user feedback about site names that were inaccurate, inappropriate, or wrong, as we reported earlier this week<\/a>.<\/p>\n

As a reminder, Google added site names months ago on\u00a0desktop<\/a>\u00a0and last year on\u00a0mobile<\/a>\u00a0search.<\/p>\n

The issue. <\/strong>Google can sometimes disregard the specified site name and replace it what it thinks the site name should be. For example, when it came to searching for [salesforce<\/a>], Google was showing a space between \u201csales\u201d and \u201cforce,\u201d and the CMO of Salesforce called it \u201cextremely damaging to our brand.\u201d<\/p>\n

<\/a><\/p>\n

The fix. <\/strong>Google\u2019s Search Liaison, Danny Sullivan, posted<\/a> an update in the Google support forms saying a fix was pushed out that resolves some of the issues. He wrote, \u201cWe recently rolled out a change that seems to be helping with some of the cases reported here and through our form (and likely some others that weren\u2019t reported).\u201d \u201cThis change may take time to populate so that internal pages also reflect updated sitenames,\u201d Sullivan added.<\/p>\n

It resolved the issue for Salesforce, as you can see from this screenshot below:<\/p>\n

<\/a><\/p>\n

Not fixed for all. <\/strong>However, this did not resolve all the issues reported by all users. Glenn Gabe shared some examples of site names not resolved by this fix on Twitter<\/a>. \u201cHere are 3 examples of site name problems that were not fixed with the changes rolled out by Google yesterday. The worst is DNN Software that says \u201cWeight Loss Forum\u201d. The others are just wrong & one is causing legal issues,\u201d he wrote:<\/p>\n

Controlling site names.\u00a0<\/strong>Google back in October\u00a0explained<\/a>\u00a0that Google Search uses a number of ways to identify the site name for the search result. But if you want, you can use structured data on your home page to communicate to Google what the site name should be for your site. Google has specific documentation on this new\u00a0Site name structured data available over here<\/a>.<\/p>\n

Upgrading the favicon<\/strong>. Google also recommended revisiting the documentation for\u00a0favicons<\/a>\u00a0for the latest best practices. Google is now also suggesting you provide an icon that\u2019s at least 48 pixels and follows the existing\u00a0favicon guidelines<\/a>.<\/p>\n

Ads<\/strong>. This is also rolled out to the Google search ads on desktop, so the size of the site name, favicons, and also the ad label will be more prominent in mobile search. In fact, Google rolled out the\u00a0\u201cSponsored\u201d label in mobile search<\/a>\u00a0last October and today on desktop, officially replacing the\u00a0\u201cAds\u201d label from January 2020<\/a>.<\/p>\n

Why we care. <\/strong>When Google gets your site name, it can not only be upsetting and unprofessional, but it can also cause confusion and legal issues for some businesses.<\/p>\n

It is good that Google is collecting feedback about the issues and working to address most, if not, all the reported issues.<\/p>\n

The post Google updates site names in search results after numerous complaints<\/a> appeared first on Search Engine Land<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

Google has pushed out a fix to resolve some of the inappropriate or unexpected site names selections displayed in the Google Search results. This comes days after Google posted a web form asking for user feedback about site names that were inaccurate, inappropriate, or wrong, as we reported earlier this week. As a reminder, Google added site names months ago on\u00a0desktop\u00a0and last year on\u00a0mobile\u00a0search. The issue. Google can sometimes disregard the specified site name and replace it what it thinks the site name should be. For […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"h5ap_radio_sources":[],"cybocfi_hide_featured_image":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-9213","post","type-post","status-publish","format-standard","hentry","category-best-seo-blogs"],"featured_image_src":null,"featured_image_src_square":null,"author_info":{"display_name":false,"author_link":"https:\/\/craighordlow.com\/author\/"},"_links":{"self":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts\/9213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/comments?post=9213"}],"version-history":[{"count":0,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/posts\/9213\/revisions"}],"wp:attachment":[{"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/media?parent=9213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/categories?post=9213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/craighordlow.com\/index.php\/wp-json\/wp\/v2\/tags?post=9213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}