Yes. Store platforms as a JSON array column. A /publishing-consultants/{platform}/ pattern generates a hub per platform (KDP, IngramSpark, ACX, Findaway, Draft2Digital). Each hub lists the consultants whose platforms array includes that value.

Store rate models as a JSON object keyed by service, or as separate columns per service if the consultant works across a small fixed set. A list mapping renders the rates by service on the consultant's page, so authors see the cost for the specific service they need.

Yes. Store sample project URLs as a JSON array with fields for url, project_type, and a short description. A list mapping renders them on the consultant's page and any relevant service hub, which is the social proof that converts inquiries.

Add a platform_notes column where consultants can flag recent platform changes they are tracking. A list mapping renders the notes on relevant pages. For directory-wide updates, a single edit to a shared notes column propagates to every consultant page that lists that platform.

Each generated URL is a real WordPress page with full HTML, sitemap inclusion, and per-page meta mappings. The base template page is auto-noindexed. New rows typically index within a few crawls of the sitemap update.

Yes. Build the form into the base template and inject the consultant's email via a hidden-field selector mapping. Inquiries route directly without per-page form configuration.

Store rate_model as a string column with the human-readable description and a numeric reference column for sort logic. A selector mapping renders the description, and hubs can sort by the numeric reference even when the display strings vary widely across consultants.

Yes. SleekRank uses an existing WordPress page as the template. The directory inherits whatever the site's theme or builder produces.