Wrong Hotel Amenity Being Pulled Into Meta Description

[mbochic]

Hey Mozzers,

Have a quick question for you hospitality folks.

We have a hotel property that has amenities being pulled into the meta description that aren't correct. We do have a custom meta description in the CMS but it is only pulling a portion of our meta description and is then including what appears to be a dynamic list of hotel amenities: "free covered parking; full service catering; complimentary airport shuttle".

The airport shuttle is no longer free and the property is charging a small fee. All copy on the page (and across the site) has been updated to reflect this change.

My main questions are:

1.) Are these amenities just pulled by Google? Do we have any control over this?

2.) Is there anything we can do to correct this error? Or do we just need to wait for it to hopefully update automatically?

Thanks for the help!

[MiriamEllis]

Hey Meisha,

Where exactly are you seeing these amenities listed? As the second line in your organic search result? In a branded local result? A Google local finder view? Local knowledge panel?

[Vijay-Gaur]

Hi Meisha,

I recently reviewed and provided a solution to a website with a similar issue on Moz Q&A. They had a DIV element with name description, which was being pulled as meta description.

Or check if there is some HTML tag that is not closed properly.

Reards,

Vijay

[mbochic]

This begins showing on the second line of our meta description. It used the first ~100 characters of our custom meta description then uses "..." and begins to list the amenities.

[mbochic]

Thank you, we'll definitely look into that! Do you happened to have the link for your response handy?

[Vijay-Gaur]

Here you go .. https://moz.com/community/q/google-serps-show-different-title

[MiriamEllis]

Hi Meisha,

If Vijay's suggestion doesn't prove to be the root of the issue, it's important to know that Google can pull info for both the first and second lines of your organic listing from a variety of sources. If that's what's happening in your case, and the data they are pulling is wrong, you need to search Google for the source of that data and correct it there, in hopes that Google will eventually update what they are showing in your second line.