Yes, via the REST API data source. Provide the endpoint, the auth method, and a JSON path to the listings array. The plugin caches results based on your configured duration and renders one page per array item. Bridge, Spark, REI Data, and most major IDX vendors expose JSON endpoints that work with this pattern.

Map an array field of image URLs to a list mapping that renders into your gallery block - or store image URLs in a comma-separated column and split them in the mapping. The base page's slider, masonry, or carousel block stays the design surface; the data only supplies the URLs.

When a row drops from the feed, the URL returns 404 on the next cache refresh and is removed from the sitemap automatically. If you need a redirect to a sold archive instead, set up a wildcard 410 or 301 in WordPress before deleting the row to preserve any inbound links.

Each generated page is unique by data - different address, different price, different photos, different schema. Use the per-row metaDescription, H1, and lead paragraph fields to ensure variety beyond the boilerplate. SleekRank surfaces every field per row, not just a city swap, which is what keeps duplicate detection at bay.

Yes. Build it once into the base WordPress page using your normal block, shortcode, or builder widget. Every generated listing inherits it automatically because the base page is the rendered template - no per-listing wiring required.

Yes. Map fields to a JSON-LD selector in the page head. SleekRank performs the replacement on every generated URL, so each listing carries its own RealEstateListing structured data. Validate with Google's Rich Results Test once, then trust the template across the corpus.

Price updates flow from the MLS feed on the next cache refresh. If you want to surface the change visually, add a previous_price column and conditionally render a strikethrough badge via a selector mapping. Price-drop alerts make for sticky pages that users return to.

Yes. Run a second page group with /neighborhoods/{slug}/ as the URL pattern, sourced from a neighborhoods sheet. Use list mappings to render filtered listings per neighborhood by passing a neighborhood key into a per-row JSON column. One feed, two URL patterns.