Yes. Filter by status in the source so only open grants reach SleekRank, or include a status column and only render rows marked open. Closed grants drop off the site entirely, or you can keep the page live with selector mappings that swap in closed-cycle copy. Most foundations prefer to remove closed grants since they confuse applicants who arrive via search.

Add columns for each stage with deadlines, descriptions, and links. Map them into the page as a stages section. SleekRank renders whatever your source provides, so a two-stage LOI plus full proposal flow renders cleanly. List mappings work well when stages are stored as an array rather than separate columns, which keeps the data model clean for grants with varying numbers of stages.

Yes. Include an apply URL column and map it into a button on the base page. SleekRank doesn't handle submissions itself. Most funders use Submittable, Fluxx, SmartSimple, or a custom portal, and a link out is the typical pattern. The page is the public-facing record; the application system handles the workflow.

Each source has a configurable cache duration, typically set between one and twelve hours depending on how time-sensitive the data is. Flush the cache manually after a cycle launch or a closure to push updates immediately rather than waiting for the standard refresh. For Google Sheets sources, refresh is essentially instant after a manual flush.

Yes. Build separate page groups for arts, education, energy, infrastructure, and other categories using filtered sources from the same master tracker. Each index page can list every grant in that category, with links down to individual opportunity pages. The same approach works for per-funder pages on aggregator sites.

Yes. The base page is a normal WordPress page, so any theme or builder works. Bricks, Elementor, Gutenberg, Oxygen, Beaver Builder, and classic templates all render fine. SleekRank operates on rendered HTML through tag and selector mappings, so theme internals don't matter.

Yes. Build a separate widget or block that reads the same JSON or Google Sheet and renders the next five upcoming deadlines, sorted by date. SleekRank handles per-grant pages; a small custom block handles the deadline ticker. Both can read from the same source, which keeps maintenance to one place.

Add a column flagging invitation-only opportunities and either filter them out of the public source entirely or use selector mappings to hide eligibility and apply sections while keeping the page live as a reference. Some funders prefer the second pattern because it surfaces program existence without inviting unsolicited applications, which still saves staff time on triaging.