SeedProd Pro registers seedprod as a custom post type and stores layout, settings, and integration metadata in wp_postmeta. Subscriber sign-ups from squeeze pages are written to wp_postmeta on the page record (or to the configured ESP). The default Landing Pages screen shows a card grid with status icons but no inline data on subscriber counts, last edit, or conversion settings, so multi-page launches turn into card-by-card clicking.

SleekView reads wp_posts (post_type=seedprod) joined to wp_postmeta for type (Coming Soon, Maintenance, 404, Login, Sales), status, and integration mapping. Subscriber counts pulled from the page's stored leads array become a column, alongside last-modified and live URL. Filters separate live from draft pages, surface 404 fallbacks needing review, and group by page type for launch planning.

Inline edits update status, title, and slug through the plugin's own save flow, so the builder sees the same data on the next load. Bulk publish or revert keeps a coordinated launch coherent across multiple landing pages, and CSV export ships subscriber lists per page straight to the marketing team.

SeedProd Pro is a popular choice for fast landing pages and pre-launch screens, but its default Landing Pages screen treats each page as an isolated card. That works when a site has two pages, it breaks when a brand runs a dozen across a launch wave. SleekView reads wp_posts (post_type=seedprod) and the postmeta rows behind each page and renders the whole portfolio as a sortable grid.

Type, status, subscriber count, and last-modified become first-class columns, so launch coordination is a tab switch rather than a builder marathon. Filters separate Coming Soon, Sales, Squeeze, 404, and Login pages, which is exactly the slice a launch manager needs the morning of go-live. Subscriber counts pulled from wp_postmeta tell the team which squeeze pages are pulling weight without opening each builder.

Bulk publish runs through wp_update_post so integration hooks fire and capability checks hold. Compliance teams export per-page subscriber lists when subject-access requests come in. None of this changes the SeedProd builder, it simply unlocks the data SeedProd already stores.