If your HR system exposes a JSON or REST feed of open postings, SleekRank can render from it on the configured cacheDuration. There is no direct integration with Workday, PageUp, or Interfolio. Most universities export a daily JSON feed from the HR system or maintain a parallel sheet for SEO-facing role pages while the HR system handles applications.

They appear as quickly as cacheDuration allows. Set the cache low during peak hiring season, often thirty to sixty minutes, and clear the SleekRank cache manually for instant publication after a search is approved. Pages reflect the feed value on the next request after cache expiry.

Yes. The SleekRank page is the SEO-facing brochure that surfaces the role and links out to the vendor application URL. The application itself stays in the HR system. Most universities use SleekRank for discoverability and the HR system for compliance and applicant tracking.

Use a status column with open and closed values. After the deadline passes, the base page reads the status through a selector mapping and renders a closed banner with the apply button hidden. Keep the URL alive as an archival record so accumulated backlinks from disciplinary lists survive across hiring cycles.

Yes. Run multiple page groups, each with its own base page and urlPattern filter. Tenure-track searches route through one base page with research statement and teaching demonstration sections while postdocs route through another with project description blocks. Both groups read the same feed.

When a row drops from the feed, the URL returns 404 on the next cache refresh and exits the sitemap automatically. For multi-year role series, mark searches as closed via status rather than deleting them, so the URLs hold their accumulated authority and applicants can still find the historical posting.

Each generated page is unique by data: different department, rank, tenure flag, deadline, required qualifications, and contact. Use per-row metaDescription and pageTitleHtml fields to vary the heading and meta beyond the boilerplate template, which keeps duplicate detection at bay across two hundred concurrent searches.

Yes. Map fields to a JSON-LD selector mapping that emits JobPosting schema per role into the page head, including title, hiringOrganization, datePosted, validThrough, and employmentType drawn from row data. Validate with Google Rich Results Test once, then trust the template across every faculty URL.