Store the kanji as a regular text column (UTF-8 in the sheet or JSON). Selector mapping renders it into the template via a span or heading element. Web browsers handle CJK rendering natively, especially with a system font fallback or a web font like Noto Sans JP. For best appearance, pair kanji with kana furigana in a separate column.

Yes. Make the attestations array an array of objects with text (Kojiki, Nihon Shoki, regional folk sources), book and section reference, and a short note. List mapping renders them as structured citations on every page. For scholarly sites this turns each figure page into a navigable index of primary attestations.

Store syncretic_slugs as an array. Under honji suijaku, many kami had paired bosatsu (Amaterasu paired with Dainichi Nyorai, for example). Selector mapping resolves each slug into a linked card on the page, with a note describing the syncretic relationship. The full medieval theological structure becomes navigable.

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. Japanese mythology queries are competitive but structured per-page content (kanji name, category, shrine) signals authority.

Yes. Wikimedia Commons holds extensive shrine photography (from open-source uploaders) and large public-domain collections of ukiyo-e prints featuring yokai and deities. Store image URLs in the sheet and use selector mapping for hero images and og:image per page. Hokusai and Hiroshige yokai prints are particularly evocative.

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. Build a second page group for shrines and temples (rows with slug, name, kami_slugs array, prefecture, founding date). Each shrine page links to the kami enshrined there. Both groups read from coordinated sources so adding a kami makes the shrine list update and vice versa.

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