No. SleekRank does not generate tsunami content. You provide the catalog (source event, runup, coasts, casualties, and so on) and SleekRank renders one page per row. Editorial responsibility for accuracy and source attribution stays with you. SleekRank's role is the rendering and routing layer between the dataset and the live site.

Yes. Add a runup_map_url column and map it via a tag mapping that injects an image. For survey photos add an images array and render via a list mapping that emits each as a captioned figure.

Use a casualties_range column with a low/high pair and a casualties_source column citing the survey. Render via selector mappings so readers see both the range and the source on every event page.

Store an arrival_times array with station name and minutes-after-source. A list mapping renders each entry, and the layout stays identical from one event to the next.

SleekRank caches the source per cacheDuration set in seconds. Edit the sheet, clear the SleekRank cache via WP-CLI or admin, and the next request rebuilds the page with new data. For tsunami catalogs (slow to update) set cacheDuration high so the source is not constantly refetched.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real event pages. Run a rewrite flush after adding new slugs so the routes resolve immediately on production.

Yes, but that's a hub page rather than the per-event URL. Build /tsunamis/ as a filter page that pulls from the same catalog and filters by basin, source type, or year. SleekRank handles the per-event detail pages; the hub uses the same source as the single point of truth.

Update the max_runup_m value in the source row and clear the SleekRank cache. The page rebuilds with the revised value. Keep a measurement_note column if you want to render an editorial footnote describing how the figure was revised.