Store sources as an array of objects with author, work, passage reference, and edition (Hesiod, Theogony, lines 116-138, Loeb Classical Library 2018). Use a list mapping to render each citation as a structured entry. Citation format gets locked at the column-shape level, which means every Norse figure that cites the Poetic Edda uses the same edition and the same passage notation. Scholars and students can cite your reference with confidence.

Yes. Use one base WordPress page across multiple page groups, each pointing at a tradition-specific dataset (Greek, Norse, Egyptian, Hindu, Celtic, Mesopotamian). The base layout (tradition badge, role chip, domain heading, attribute chips, source list) stays consistent; the data drives every field. This is the cleanest way to maintain a multi-tradition mythology site without duplicating design work.

Add a parallels array column with figure slugs and a parallel_type column (etymological, functional, syncretic). Use a list mapping to render parallel chips, optionally linked to the parallel figure's own page. Athena and Minerva are syncretic; Loki and Hermes are functional tricksters. The column shape lets you document the relationship type without forcing a single equivalence convention.

Add an attributes array column where each entry has type (animal, object, plant, color) and item (eagle, lightning bolt, oak, gold). Use a list mapping to render each attribute as a chip. Editors stop forgetting to include attributes consistently because the array shape makes the field visible on every figure that has data.

Yes. Add a relationships array column where each entry has relationship_type (parent, child, consort, sibling) and figure slug. Use a list mapping to render each relationship as a labeled link. The structure handles polytheistic family trees without forcing a single-relationship convention; it also lets you express relationships across traditions when a figure migrated (Aphrodite to Venus).

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template. Mythology queries are figure-specific and tradition-specific ('Odin attributes', 'Kali symbolism'), so per-figure URLs matter more than tradition-level aggregation pages for organic traffic.

Use one canonical slug per tradition (zeus for Greek, jupiter for Roman) with a parallels link between them, rather than collapsing into a single page. Many traditions adopted figures with significant changes; collapsing loses the distinction. Cross-tradition linking via the parallels array gives readers a path between equivalents without erasing the editorial differences.

Yes. Add a modern_reception paragraph column and a pop_culture array column for film, literature, and game references. Use a selector mapping for the paragraph and a list mapping for the array. Many figures (Loki, Thor, Hades) have significant modern reception that students and casual readers care about; surfacing it as a dedicated section keeps it separate from the primary-source-driven content.