Use UTF-8 throughout the source and store the diacritic-bearing form directly in the sheet. Tag mapping passes the value through unchanged. Avoid auto-correct features on the sheet by disabling smart quotes and locale-specific replacements. If terms render incorrectly, check that the WordPress database charset is utf8mb4 and that the template does not call functions that strip non-ASCII characters.

Yes. Add columns for tibetan_term, japanese_term, or any other script you need. Each gets its own tag mapping into a corresponding element on the page. The data shape grows by columns, not by separate sources. Templates can show or hide script blocks conditionally so concepts without a Tibetan equivalent do not render an empty block.

Use a second URL pattern that filters rows by tradition. The same source feeds both per-concept and tradition pages, so adding a row to Vajrayana populates the Vajrayana index automatically. For deeper navigation, add a lineage column and create sublineage index pages from the same source.

Yes. Store an audio URL column and inject it via selector mapping into an audio element on the template. Self-hosted files or a CDN both work. For longer-form recordings like a teacher reciting the term in context, embed via the same URL field with a wrapper that handles iframe or audio tags depending on the source.

Yes. Each URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new concepts get crawled within hours of cache flush. Concept queries are competitive in spiritual and academic niches, but per-page structured content (term, tradition, definition, citations) signals topical depth to search engines.

No. Definitions and expositions come from the source. SleekRank only injects what is in the data. Buddhist concepts are doctrinally sensitive and tradition-specific, so the wording should be authored by a teacher or scholar who understands the lineage being represented. SleekRank handles publishing, not authorship.

Two patterns work. The first keeps one concept per row and uses a long_exposition column structured by tradition with subheadings. The second creates per-tradition variants as separate rows like /concepts/anatta-theravada/ and /concepts/anatman-mahayana/. Choose based on whether the differences are subtle enough for one page or distinct enough to warrant separate URLs.

Yes. Build a second page group for talks (rows with title, teacher, audio URL, concept slugs covered) and link from each talk page to the concept pages it references. Both groups read from coordinated sources so adding a new concept makes it discoverable from any talk that cites it.