SleekRank does not run a scraper itself. It reads any feed you give it: REST, CSV, JSON file, or Google Sheet. Most operators run a daily scraper in Make or n8n that drops a CSV into the theme folder. SleekRank picks the file up on the configured cache duration and rebuilds the pages.

No. SleekRank uses one base WordPress page as the template, and the URLs underneath it are virtual, served straight from the data source. You never create one post per dome, which is what makes 500 listings practical without an editor melting down.

Drop the row from the feed. On the next cache refresh, the URL stops resolving and the sitemap regenerates without it. If you want a polite 410 instead of a 404, SleekRank emits the correct status; you can also route sold domes to a redirect map.

Yes. The base page is a normal WordPress page, so any Gutenberg block, Timber template, or shortcode lives alongside the data-driven hero. Most operators keep agent contact, financing widget, and shell-vs-finished guide on the base page, and let the row fill in the dome-specific parts.

Image URLs are columns in the feed. A list mapping renders them into your slider or gallery block; a meta mapping wires the lead image into the OG card. You can host on Cloudinary, S3, or your WordPress media library, whatever the feed points to.

Yes. The same REST connector that handles Bridge and Spark for general MLS listings works here. For dome-specific filters you typically post-process the feed in a small step, write the filtered rows to a JSON file, and point SleekRank at the file.

Map your fields to schema properties with a meta mapping that emits JSON-LD into the page head. Google reads the structured data and surfaces price, address, and floor area in rich results, with no per-listing manual JSON.

SleekRank is a one-time license per site. You can publish 50 or 5,000 listings without per-listing fees, which makes dome niches viable that would never pay for a national IDX seat. Hosting and feed costs are separate and stay yours.