Store the canonical English name as the title field and keep an alternate_names array with every common variant (Mjolnir/Mjollnir/Mjolner, Inanna/Innina/Ninanna). List mapping renders them on the page so search engines see the variants and visitors find the right page no matter which spelling they searched. The canonical slug stays stable for backlinks.

Yes. Build a second page group for myths (rows with slug, title, deity_slugs array, summary, source_text) and a third for sources (Iliad, Eddas, Book of the Dead, Popol Vuh). All groups read from coordinated sources so adding a deity makes related myths link back automatically. Cross-referencing is just selector mapping resolving slugs into linked cards.

Many deities appear in more than one pantheon (Roman versions of Greek gods, syncretic Greco-Egyptian deities like Serapis). Add a pantheon_primary column and a pantheons_all array. Selector mapping picks the primary badge; list mapping shows the full list. For cases like Zeus/Jupiter, decide whether to maintain one combined row or two with cross-links. Both work; the source data drives it.

Yes. Each URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new pages get crawled within hours of cache flush. Deity-name queries (and pantheon-themed queries like Greek gods or Egyptian gods) rank well because the structured per-page content signals authority.

Yes. Store consort_slugs, parent_slugs, and child_slugs arrays per row. A small filter resolves each slug to a name and URL, then list mapping renders them as linked cards on the page. Family-tree style relationships stay consistent automatically because they read from the same dataset.

Cache duration is configurable per source. For active library development, set fifteen to sixty minutes; for stable references, a day or longer is fine. A manual flush via wp-cli makes urgent corrections appear immediately. The next request after flush rebuilds pages from the updated source.

Yes. Store image URLs (Wikimedia Commons covers most classical and ancient depictions) and use selector mapping for hero images and og:image per page. For deities without surviving ancient artwork, modern commissioned illustrations or museum-licensed images work. Store one canonical URL per row and every page renders the same image, every time.

No. The base template is a normal WordPress page. Style it however the rest of the site looks. The structured fields (name, pantheon, symbols) render through your theme's typography and spacing. SleekRank only injects values into matched elements; the visual identity stays in the theme.