Only if your data is exposed as JSON, CSV, or a REST endpoint your WordPress server can pull. SleekRank does not connect to FRIEDA or ERAS directly. Aggregators typically maintain a curated database by tracking program landing pages and FRIEDA listings, then expose it as a stable URL the SleekRank page group reads each cycle.

Use a status column with values like open, paused, and unfilled. Either drop paused rows from the urlPattern, or keep URLs live and render a status block conditionally. The second pattern preserves backlinks and helps applicants tracking historical Match data, which matters in specialty-specific research.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining hospital name, specialty, and PGY1 salary. Each program gets a unique social card for the times it is shared in med-school Slack workspaces or applicant forums during Match cycle.

No. SleekRank renders pages and does not process applications, recommendations, or document uploads. Most residency pages link out to the program portal or ERAS because applications run through AAMC systems. Use a CTA column on the database to drive the apply button per row.

Yes. Add columns for call frequency, average work hours, rotation breakdown, and elective time, then surface them through selector or list mappings in the base page template. The data lives in your database and the page renders the references on demand.

Use a specialty column and either reference it in the urlPattern as /medical-residencies/{specialty}/{slug}/, or run parallel page groups per specialty with distinct base pages. Each group reads the same database, filtered at the data source level so URLs stay clean per applicant audience.

As fast as your cacheDuration allows. Set a tight cache during ERAS open weeks and Match Week, often hourly to two hours, so edits land quickly. For instant updates after a program posts cycle changes, clear the SleekRank cache manually so the next render pulls fresh data.

Yes. Add a column for program resources with an array of URLs, titles, and brief descriptions, then surface them through a list mapping in the base page template. Each residency page can carry a growing library of applicant-side guidance that strengthens its authority across Match cycles.