Only for the subset of Whalesync use cases where the destination is a WordPress site. Whalesync's core strength is two-way sync into Webflow, Framer, and similar external CMSes, and SleekRank does not try to compete in those ecosystems. If the goal is programmatic pages on WordPress backed by a Notion, Airtable, Sheets, or REST source, SleekRank covers that natively. If the goal is keeping a Webflow project in two-way sync with a Postgres database, Whalesync is the right tool and SleekRank is not in scope.

No. SleekRank is read-only on purpose. Programmatic pages rarely need to write changes back to the source of truth, and read-only sync is much simpler to reason about, especially at scale. Edits happen in Notion or Airtable directly, then propagate to the site after the cache duration on the data source expires, or immediately if the cache is cleared.

Whalesync charges by synced records and active syncs, so a directory with 10,000 rows and a few connections climbs into a meaningful monthly bill. SleekRank is a WordPress plugin with a flat license. There is no per-record fee, no active-sync surcharge, and no separate destination CMS subscription. The trade-off is that SleekRank only renders into WordPress, not into Webflow or Framer.

Not as a first-class source today. The native sources are JSON, CSV, Google Sheets, Notion, Airtable, and any REST API. For Postgres or Supabase, the typical pattern is to expose a small REST endpoint that returns rows as JSON, then point SleekRank at that endpoint. This keeps the database credentials on the application server and lets SleekRank treat the result like any other JSON source.

Nothing automatic. SleekRank only manages WordPress URLs. If Whalesync was syncing into a Webflow project that still needs to exist, that project keeps working independently. If the Webflow project existed only to host the programmatic pages, you can redirect those URLs to the new WordPress ones once SleekRank is serving them, then retire the Webflow site or repurpose it.

Yes. Whalesync can keep its existing syncs running while SleekRank reads from the same source into WordPress on a fresh URL pattern. Verify the new pages, set up redirects from the old URLs, and only then disable the Whalesync connection. There is no shared state, so the two do not collide.

Each page group's mappings array can target title, the h1, the meta description, list items inside a selector, and arbitrary inline content via CSS selectors. The base page's structured data, schema, and Open Graph image template are inherited. Yoast, Rank Math, and similar plugins keep working on the base page, and per-row values come from the data source.

Each data source declares a cacheDuration in seconds. Resolved rows live in the sleek_rank_items table for that duration. Requests after expiry trigger a refresh from the source. Editing a row in Notion or a cell in Google Sheets propagates after the window, or immediately after running DELETE FROM wp_xxx_sleek_rank_items to force a refresh.