Functionally overlapping for the programmatic-page use case but architecturally different. Greenshift Dynamic Pages is a strong fit when the rest of the site already runs on Greenshift's block stack and you want one cohesive editing experience. SleekRank is a better fit when the site uses multiple builders, a custom theme, or wants the programmatic layer to be independent of any specific block library.

Indirectly. If Greenshift was reading from a CSV, a Google Sheet, a Notion database, or a REST API, SleekRank can read the same source directly. Internal Greenshift query loops over WordPress posts/CPTs are a different model — you'd point SleekRank at whichever underlying data store makes sense (often the same CPT, or a JSON export).

Only if other parts of the site still depend on Greenshift blocks. SleekRank doesn't need it. The base page can use any editor's blocks (or none) — what matters is that the page renders standalone and exposes the right elements for the mappings to target.

Whatever theme and editor produced the base page. SleekRank doesn't render its own styles or inject its own components — it modifies the existing HTML of the base page based on the data row. Theme styles, builder styles, and any front-end assets the base page already loads are what users see.

Greenshift's strength is dynamic blocks driven by query loops. SleekRank's primary model is one data row per page, not a query loop inside a single page, but you can use list-type mappings to populate repeated elements (cards, list items, table rows) from arrays in the row's fields. For complex query loops the answer is to keep using whichever query mechanism your builder provides on the base page.

Each page group sets its own urlPattern with {slug} tokens, and multi-segment patterns work for nested directories. Rewrite rules are managed by the plugin; running wp rewrite flush after adding a new page group registers the new pattern.

Mappings are by tag, CSS selector, or meta attribute, so they're tied to the base page's HTML structure. If you redesign the base page and rename or remove an element a mapping was targeting, that mapping needs updating. The upside is that the config is small and lives in the page group JSON, not buried inside block attributes.

Yes. Greenshift Dynamic Pages keeps running for the templates it owns, and SleekRank can be added against a separate URL pattern for new programmatic page groups. Once the new flow is verified, individual templates can be migrated over without forcing a full rip-and-replace.