Listdom Google Places Addon Documentation

Questi contenuti non sono ancora disponibili nella tua lingua.

The Listdom Google Places Addon links a Listdom listing to a Google Place ID. Administrators can create minimal draft shells from map search results, review current Google details as editor suggestions, and display attributed Google rating, review-count, and business-link information on the listing details page.

Google data remains separate from native Listdom content unless an editor deliberately copies a supported suggestion and saves or publishes the listing.

Requirements and configuration

Install and activate the Listdom Google Places Addon.
Use an administrator account for draft creation and an account with listing-edit permission for editor suggestions.
Open Listdom → Settings → Addons → Google Places.
Enter Google Places API Key for place search and live Place Details suggestions.
Configure the map’s Google Maps API key separately under Listdom → Settings → General → Map Module.
Set Max Temporary Queue Size from 1 to 20 (default: 20). The queue exists only in the current browser screen; leaving or reloading the page can discard it.

The administration map starts at the backend latitude, longitude, and zoom configured under Listdom → Settings → General → Map Module. The map key requires Maps JavaScript API, while the addon key requires Places API (New). Both APIs require a billed Google Cloud project.

Create minimal drafts from Google Places

Go to Listdom → Import / Export → Google Places.
Enter a Search Query, select a Place Type, and position the map over the required area.
Select Search. Leave Update search results when the map moves enabled if results should refresh for the visible map area.
Select a map marker or business row and adjust its proposed draft title if needed.
Add the business to the Temporary Queue.
Review the queue, remove unwanted items, and select Make Drafts.

Search returns up to 20 businesses for the current query, type, and map area. Supported choices include All supported types, Restaurant, Cafe, Bakery, Bar, Hotel, Laundry, Gym, Store, Beauty Salon, Hospital, Pharmacy, School, and Tourist Attraction.

The same Place ID cannot be queued twice. During draft creation, Listdom also skips a place when a draft, pending, published, scheduled, or private listing already uses that Place ID.

Editing a queued title changes the title used by Make Drafts; removing an entry affects only the temporary queue. Listings in Trash are not included in the duplicate check.

What a generated draft contains

Draft creation intentionally stores only:

Confirmed listing title
Google Place ID
Current administrator as post author
Draft post status

The result address is available for review but is not written to the draft’s native address field. Photos, featured images, ratings, reviews, phone numbers, websites, opening hours, categories, and coordinates are not imported into native Listdom fields during draft creation.

Link or change a listing’s Google business

Create or edit a Listdom listing and find the Google Places metabox.
If no Place ID is saved, enter at least two characters in Search Google Places and select the correct business.
If a Place ID already exists, select Fetch Data to refresh its suggestions.
Use Change Business to search for and link another place.
Review the linked business and save the listing when ready.

Selecting a business saves its Place ID immediately through the editor. Copied native fields still require Save Draft, Update, or Publish. Changing the business changes the source of future suggestions and frontend Google output, but it does not clear native values copied from the previous business; review the title, address, phone, website, category, and coordinates manually.

Review and copy suggestions

The metabox can retrieve live suggestions for:

Place name and formatted address
Phone number and website
Opening hours
Primary Google place type
Matching Listdom category when an exact normalized name or slug match exists
Latitude and longitude
Price level

The editor notice states: Review before copying. Saved values become native Listdom content. Copy actions can place supported title, address, phone, website, category, and coordinate values into their native editor fields. Save or publish the listing to retain them.

Available actions include Copy to Title, Copy to Address, Copy to Phone, Copy to Website, Apply Category, and Copy to Map Fields. Address copying can also provide location data; nevertheless, review the address selector, map object, marker, latitude, and longitude before saving. Map copying selects marker-based output when available.

Opening hours and primary type remain review information. Price Level is display-only and is not copied to a native searchable price field. Category matching compares normalized Google type labels and codes with existing Listdom category names and slugs; it does not perform approximate matching. When no exact match exists, choose or create the category manually.

Google photos and featured images

Google Places photos are not requested for draft search, listing suggestions, or frontend output. The addon does not download a Google photo, create a WordPress attachment from it, or assign one as the featured image.

There is no Include images in search results setting or Import Featured Image action. Add media through the normal Listdom or WordPress image controls using content you are permitted to publish.

Display live Google data on listing details

Go to Listdom → Settings → Single Listing, open the active details-page style, and add or enable the Google Places element. Its general settings include:

View on Google Button: Display the business link when Google returns a Maps URL.
Google Rating & Reviews: Display the current rating and review count when available.

Frontend output uses explicit labels:

Rating from Google: value
Reviews on Google: count
View Business on Google

The business button opens Google in a new tab. If both settings are disabled, or Google returns none of the enabled values, the element produces no visible output. Standard details-page element settings can also provide a section title, custom title, and title alignment.

These values are fetched through the Place ID and can change when Google updates the business. They are not merged into native Listdom ratings or reviews.

Page-builder integrations

Elementor Elementor: add the Google Places widget and configure View Business Button and Rate & Reviews.
Bricks Bricks: add the Google Places listing element and configure the same two content controls.
Divi Divi: add the Google Places module and show or hide its business button and rating/reviews output.

Each builder needs a valid preview listing with a saved Place ID. The Google Places addon must remain active. Developers can override the frontend template from a listdom-google-places directory in the active theme or child theme; use a child theme and recheck the override after addon updates.

Permissions, requests, and performance

Map-based draft creation is restricted to administrators with the required capability.
A user must be allowed to edit the listing before searching for or saving its Place ID; protected WordPress actions use nonces.
The frontend exposes display data, not the configured API key.
Refresh-on-map-move can increase Places requests, and each frontend element can require current Place Details.
Quotas, billing, key restrictions, network conditions, or Google availability can cause the live element to return no output. Previously saved native fields remain available.

Data ownership and updates

The Place ID is the persistent link; other Google details are fetched as live data.
Draft creation does not silently populate native fields.
Suggestions become native content only after an editor copies a supported value and saves the listing.
Later Google changes do not overwrite previously copied native values automatically.
Frontend rating, review count, and business URL remain attributed Google data.
Google media is not stored in the WordPress Media Library by this addon.

Troubleshooting

The screen requests an API key: Configure the Places key under Listdom → Settings → Addons → Google Places and the map key under General → Map Module.
The administration map is blank: Verify the map key, Maps JavaScript API, billing, browser restrictions, and scripts that may block Google Maps.
The map loads but search fails: Verify the addon key, Places API (New), server-compatible restrictions, billing, and quota.
Search returns no businesses: Reposition the map, broaden the query, try a supported type, and verify the key. Metabox search requires at least two characters.
A place cannot enter the queue: The queue may be full or already contain that Place ID.
A draft was skipped: Search non-trashed listings, including draft, pending, published, scheduled, and private statuses, for the same Place ID.
A suggestion disappeared after reload: Copy the supported value and save or publish if it should become native content.
No category is suggested: Automatic matching requires an exact normalized type-to-category name or slug match.
Rating, reviews, or business link are hidden: Confirm the Place ID, enable the Google Places details-page element and its display settings, and verify that Google returns the value.
Import Featured Image is missing: This is intentional; photo import has been removed.
A copied address points to the wrong position: Use Copy to Map Fields, then review and adjust the marker before publishing.

FAQ

Does Make Drafts import complete Google business profiles?

No. It creates minimal drafts with the confirmed title and Place ID.

Are suggestions copied automatically?

No. An editor must copy a supported value and save or publish the listing.

Can the addon import a Google photo?

No. It does not request, download, or attach Google Places photos.

Is Google Price Level saved as a Listdom field?

No. It is display-only in the suggestions.

Are Google ratings merged with Listdom reviews?

No. Google ratings and review counts remain explicitly attributed Google data.

How are duplicate businesses prevented?

Listdom blocks duplicate Place IDs in the queue and skips draft creation when another non-trashed listing already uses the ID.

Why are two API keys recommended?

The administration map and Places requests use different APIs and request contexts. Separate keys allow restrictions appropriate to each use.