Yes. Add a query_status column with values like open, closed, by_referral, paused, opening_in_august. A selector mapping renders the status on the agent's page, and a /agents/open-to-queries/ hub auto-lists the agents whose status is currently open.

Set the cache duration per page group. For active query directories, an hour is reasonable. Some sites push updates more often around major industry events. The data layer is decoupled from the WordPress template, so updates do not require any theme deploy.

Yes. Store MSWL highlights as a JSON array (each item a short pitch summary or comp title) and recent deals as another JSON array. List mappings render them on the agent's page and on relevant hubs, with the same data appearing wherever an agent is listed.

Edit the agency column in the sheet. On the next cache refresh the agent's page reflects the new agency, the old agency hub drops them, and the new agency hub picks them up. If the agent has built ranking for their personal URL, the slug stays the same so the URL does not change.

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.

If the agency uses a single QueryManager or similar submission portal, link to it from the agent's page. For agencies that take direct queries, build the form into the base template and inject the agent's routing email via a hidden-field selector mapping.

Store genres as a JSON array. The agent appears on every genre hub their array matches. For the agent's own page, a list mapping renders all their genres. Avoid forcing a single primary genre if the agent genuinely represents across several.

Yes. SleekRank uses an existing WordPress page as the template. Whatever theme or builder rendered that page renders every generated URL identically. The directory inherits whatever the site already looks like.