Store both as columns on the same row. Devanagari (विष्णु) goes in one column, IAST (Visnu, with proper diacritics if your editorial system supports them) goes in another. Both render on the page; the URL uses a simplified slug for shareability. List a few common popular spellings in an alternate_names array (Vishnu, Visnu, Vishnoo) for search coverage.

Yes. Make the attestations array an array of objects with text (Rigveda, Mahabharata, Bhagavata Purana, etc), reference (mandala-hymn, book-chapter, skandha-adhyaya), and a short note. List mapping renders them as a structured citation list. For scholarly sites this turns each figure page into a navigable index of primary attestations.

Use a sect column with values like Vaishnava, Shaiva, Shakta, Smarta (universal), or sant (bhakti-tradition figures). Selector mapping renders a styled badge. For figures with cross-sect significance (Ganesha, for instance, is universal in Smarta practice but central in Ganapatya tradition), use the primary affiliation and mention secondary affiliations in the summary.

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. Hindu deity queries are competitive but structured per-page content (IAST, sect, vahana, mantras) signals authority.

Yes. Wikimedia Commons holds extensive collections of Hindu temple sculpture, miniature paintings (Pahari, Rajasthani, Mysore styles), and modern devotional art. Store image URLs in the sheet and use selector mapping for hero images and og:image per page. For doctrinally sensitive iconography, use temple-tradition references rather than generic stock imagery.

Store avatar_of as a slug pointing to the primary deity (Krishna's avatar_of is vishnu, for instance) and an avatars array on the primary deity's row listing every avatar's slug. Selector mapping resolves both into linked cards. The dashavatara becomes a navigable structure; partial or regional avatars get the same treatment with a status field if you need to mark canonical vs regional.

Yes. Store mantras as an array of objects with text (Devanagari and transliterated), context (japa, puja, specific tradition), and audio_url (optional). List mapping renders them on the page. For accessibility, an audio file linked from each mantra helps both learners and devotees, especially for less-common mantras.

No. The base template is a normal WordPress page. Style it however the rest of the site looks. The structured fields (Devanagari, IAST, sect, vahana, mantras) render through your theme's typography and spacing, with a Devanagari-capable font fallback. SleekRank only injects values into matched elements; the visual identity stays in the theme.