Understanding the listing status for Google Vacation Rentals

When connecting your Guesty's listings to Google Vacation Rentals (Google VR), the listing status can be one of the following: Live on channel, Pending, Failed, Pending disconnect, or Disconnected.

To view the listing's status, access the relevant channel's integration page. Next to the listing's row, hover over the status to display additional information.

Live on channel

Your request has been approved by Google VR and the listing is ready to be published. However, this status doesn't necessarily mean the listing is published on Google VR.

For Google Vacation Rentals, allow up to three weeks after publishing your listings for them to become live on Google. After three weeks, follow the instructions below to search for your listings on Google.

  1. Open Google Travel.
  2. Click Vacation rentals.
  3. Use the search bar to find the city/neighborhood/area in which your listing is located.
  4. Use the map to zoom in on the property’s location.
  5. If you are not able to find the listing, contact us.

Pending

Your request has been sent to Google VR and is being reviewed for approval, which can take up to 2 weeks. To learn more about the "Pending" status, hover over the status in the Google VR integration page in Guesty to see when the listing is expected to be connected.

Pending status info

One possible reason your listings may be pending is having images that are incompatible with Google's requirements. To check the resolution of your images, navigate to the Marketing tab of the property page in Guesty, right-click each image, and select Inspect.

In case your listing can accommodate 10 or more guests, it needs to be listed by Google manually, which can take up to six weeks.

If the listing's status is "Pending" after more than 20 days and the issue is not resolved, contact us.

Pending verification

Failed

Your request hasn't been approved by Google VR. Click Learn more next to the "Failed" status to see how to resolve the issue.

Failed status info

It may be that your listing was rejected because it was not eligible. Contact us for more information.

Rejection reason

If you receive an error such as “status: 403, error: Forbidden”, contact Google VR’s support team directly. This error means Google VR has rejected the connection.

Once the rejection error has been fixed, click Retry listing to retry the connection.

Google failure statuses

Check the failure reason and fix as needed.

Common errors

Your listing may not be validated if there's a missing title, missing public description, or not enough photos.

Validation error

Images don't meet requirements

The validation may have failed if images don't meet Google's requirements.

Image requirement error

Error "VR_BRAND_MISSING_LANDING_PAGE”

This error means Google detected no landing page. Reconnect the listing to resolve this.

Error "Website access for URL...is not reachable"

This error means the connected Booking Engine has an active custom domain added.

Website unreachable error

To resolve this issue, remove the custom domain from your Guesty Booking Engine. Note that this can harm your SEO if the site is already established.

Step by step:

  1. Sign in to your Guesty account.
  2. In the side navigation menu, click icon Marketing and sales and select Distribution.
  3. Click the Guesty Booking Engine thumbnail.
  4. Next to the relevant Booking Engine, click icon and select Edit Booking Engine.
  5. In the Custom Booking Engine custom domain (web address) section, remove the URL from the textbox.
    Remove domain screen
  6. In the left-side menu, click Languages (optional).
  7. At the top right, click Save Booking Engine.

Return to the Google Vacation Rentals integration page to reconnect the listing.

Pending disconnect

This status means your listing is waiting to be disconnected. This may take up to 24 hours to finalize.

Disconnected

This status is displayed when you stop the syncing of a listing. Updates will no longer sync between platforms.

Contact us if issues persist.

Was this article helpful?
0 out of 0 found this helpful