SleekRank for saint pages
Maintain saints in Google Sheets or JSON. SleekRank generates an indexable page per saint with feast day, patronages, birth and death dates, canonization, attributes, and miracles, plus per-saint OG cards via SleekPixel.
€50 off for the first 100 lifetime licenses!
Saints carry consistent metadata
Every recognized saint has the same set of biographical anchors: a birth date (where known), a death date or feast day, a patronage (the people, places, or occupations they're associated with), a canonization process and date, a set of iconographic attributes, and a biography that lays out the why behind the veneration.
SleekRank reads saint data from Google Sheets, CSV, or JSON and produces one page per saint at /saints/{slug}/. Tag mapping handles the title, selector mapping fills in feast day and canonization, list mapping renders patronage and attribute arrays. The base template is a normal WordPress page so theme typography supports the hagiographic content.
Because the source is one sheet, new beatifications and canonizations ship as row updates. Patronage clarifications after liturgical revisions become single cell edits. Feast-day corrections after reform propagate to every page on the next cache cycle.
Workflow
From saint sheet to per-saint URLs
Build the saint source
Design the saint template
Map saints to template
Add feast and patronage indexes
Data in, pages out
Saint rows to per-saint URLs
One row per saint with slug, name, feast day, era, and primary patronage.
| slug | name | feast_day | era | primary_patronage |
|---|---|---|---|---|
| francis-of-assisi | Francis of Assisi | October 4 | 1181-1226 | Animals, ecology, Italy |
| teresa-of-avila | Teresa of Avila | October 15 | 1515-1582 | Headache sufferers, lacemakers |
| patrick | Patrick | March 17 | c. 385-461 | Ireland, engineers |
| anthony-of-padua | Anthony of Padua | June 13 | 1195-1231 | Lost items, the poor |
| catherine-of-siena | Catherine of Siena | April 29 | 1347-1380 | Italy, Europe, nurses |
/saints/{slug}/
- /saints/francis-of-assisi/
- /saints/teresa-of-avila/
- /saints/patrick/
- /saints/anthony-of-padua/
- /saints/catherine-of-siena/
Comparison
Manual saint pages vs SleekRank
Hand-written page per saint
- Each saint takes a fresh editorial session in the editor
- Feast-day formatting drifts between pages
- Patronage lists get written inconsistently
- Canonization details retyped with occasional errors
- OG cards per saint rarely get attention
- Calendar, patronage, and era indexes need separate maintenance
SleekRank
- One URL per saint at /saints/{slug}/
- Feast day, canonization, and era render from columns
- List mapping handles patronage, attributes, and miracles arrays
- New canonizations and beatifications ship as row inserts
- Sitemap entries per saint, base template noindexed
- Pair with SleekPixel for OG cards labeled with the saint and feast day
Features
What SleekRank gives you for saint pages
Per saint
Each saint lives at /saints/{slug}/, ready to rank for name and patronage queries. The library scales across the calendar without per-page editorial bottlenecks.
Feast calendar
A second URL pattern groups saints by feast date, fed from the same source, so a March 17 calendar page lists every saint whose feast falls on that date.
Patronage indexes
List mapping renders patronage arrays per saint, and patronage-based indexes group saints by who or what they're associated with, all from the same source.
Use cases
Who builds saint pages with SleekRank
Catholic publishers
Parish, diocesan, and lay Catholic publishers ship a per-saint reference library with feast days, patronages, and biographies, all sourced from one shared sheet.
Religious education sites
Sunday school programs and religious education publishers cover the calendar with structured per-saint pages teachers and families return to throughout the year.
Heritage and cultural sites
Cultural publishers covering saints across Orthodox, Catholic, and other traditions maintain a unified library with respectful editorial treatment per row.
The bigger picture
Why saint pages benefit from programmatic publishing
Saint queries are seasonal and recurring: "saint of the day," "patron saint of lost things," "feast day of Saint Patrick," "who is Saint Catherine of Siena." Each query maps to a specific saint and a focused per-saint page outranks a generic listing every time. The structural problem is breadth: the canon includes thousands of recognized saints across traditions, and writing each one in WordPress is a multi-year editorial project. The data is well-documented in martyrologies and hagiographic references; the work is putting it into a publishing surface.
SleekRank lets the team maintain a sheet with structured fields (feast day, patronages, attributes, canonization details) and renders that sheet through a single template. New canonizations and beatifications ship as row inserts. Feast-day corrections after liturgical reform are single cell edits.
Calendar and patronage indexes run from the same source, so a March 17 calendar page automatically lists every saint whose feast falls on that date. Pair with SleekPixel for OG cards labeled with the saint and feast day; social shares from devotional and educational content look intentional rather than ad hoc.
Questions
Common questions about SleekRank for saint pages
The Roman Martyrology is the canonical Catholic source. Butler's Lives of the Saints, the Catholic Encyclopedia, and various national hagiographies supplement. For Orthodox saints, the Synaxarion serves a similar role. Most teams maintain a sheet derived from these references, with citation columns documenting which source supports each field. SleekRank reads the sheet without caring about upstream provenance, but citation discipline strengthens credibility.
 Add a recognition column noting which traditions recognize the saint (Catholic, Orthodox, Anglican, Lutheran). The template renders the recognition list per page. For saints venerated in different ways across traditions, a notes field explains the distinctions in plain prose. Cross-tradition coverage helps the library serve a wider audience.
 Yes. The patronages array is searchable on the listing page, and patronage-based indexes group saints by association. Build a search widget that queries the sheet (or the rendered listing) for patronages matching a user query. The data structure supports it; the search UI is template-side and can use existing site search infrastructure.
 Some saints have different feast days across calendars (Western vs Eastern, before and after a calendar reform). Store the primary feast day in feast_day and add a feasts array for alternates with calendar context. List mapping renders the alternate feasts. Calendar indexes can group on any of the dates depending on which calendar the index represents.
 Yes. Each URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new saints get crawled within hours of cache flush. Saint-name and patronage queries reward focused per-page content over generic listings.
 Yes. Add associated_places and associated_orders arrays. For saints with strong place associations (Padua, Assisi, Avila) and order associations (Franciscan, Dominican, Carmelite), explicit linking helps readers explore connected pages. Build coordinated page groups for places and orders to receive the cross-references.
 Add a recognition_level column (saint, blessed, venerable, servant of God) and selector-map it to a badge on the page. The template handles each level with appropriate language. For blesseds, include the beatification date and the canonization status (in process, awaiting miracle, etc.). The library serves devotional and academic interest in less-known figures alongside the canonized.
 No. Any WordPress theme handles the base template. The saint template is one page with structured sections (hero with feast day, key facts, patronage, attributes, biography). Style it however the parish or publisher's brand looks. A clean editorial theme suits hagiographic content; specialized themes are optional.
 Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Starter
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- 3 websites
- 1 year of updates
- 1 year of support
Pro
EUR
per year
further 30% launch-discount applied during checkout for existing customers.
- Unlimited websites
- 1 year of updates
- 1 year of support
Lifetime ♾️
Launch Offer
€299
EUR
once
further 30% launch-discount applied during checkout for existing customers.
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout