Not directly. Use a public summary template with the public columns visible, and link out to a gated detail page or login flow handled by a membership plugin like Paid Memberships Pro or MemberPress. The gating logic runs in that plugin; SleekRank produces the public summary page and the link to the gated detail. Many boards run a teaser model where rate and duration are public but client and apply URL are member-only.

Remove the row from the feed and the page returns a 404 on the next cache cycle. Add a server-level redirect from removed slugs to the matching skill collection page if you want to retain link equity, or to a related-gigs archive. Some boards keep filled gigs visible with a 'filled' badge for case-study purposes; that requires keeping the row and adding a status column rather than removing it.

Yes. Add a rateMin and rateMax column or a single rate column. Map them with tag or selector mappings into the template. Some boards show ranges as a pill like $90-$120/h on the collection page and the exact range on the gig detail. SleekRank injects whatever the columns contain; rate logic and currency formatting is up to the template.

Yes. Add a comma-separated skills column and use a list mapping to render skill tags on the page. For per-skill collection pages, use the primary skill column to group, since SleekRank does not split a single row into multiple collection pages automatically. If a gig is genuinely cross-skill, decide which collection it belongs on or run two near-duplicate rows with different primary skills.

Add an applyUrl column to the feed and inject it into the apply button via a selector mapping. The URL can be an email mailto, a hosted form, a partner platform link, or a Calendly. SleekRank does not handle applications itself; the application logic runs wherever the URL points. Most boards use a generic form with the gig slug pre-filled by query string for analytics.

Add a featured flag column and use the flag in the template to show featured styling, a highlight border, or top placement on collection pages. Payments and gating still need a dedicated plugin like Easy Digital Downloads or WooCommerce. SleekRank handles the styling logic based on the column; the transaction sits elsewhere. Some boards run paid tiers manually via Stripe links and update the column when payment clears.

If you collect them and add them as columns, yes. Add a clientRating column or a clientReview column and inject them via tag or selector mapping. SleekRank does not collect reviews itself; pair with a plugin that handles ratings if you want a full review system. Most freelance boards skip per-client ratings to avoid the moderation overhead.

Add a locationType column with values like remote, hybrid, on-site and either filter into separate page groups or render as a tag. Some boards run /gigs/remote/ as a dedicated collection page that pulls only remote rows. SleekRank renders subsets via list mapping based on the column you key on, so the same source feeds remote-only and full-coverage collections.