✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekRank for historical tsunami event pages

Historical tsunami data lives in the NOAA NCEI tsunami database with no per-event public URL. SleekRank reads the file and emits one WordPress page per event under /tsunami-events/{slug}/, with source, magnitude, runup, deaths, and Event schema fields.

€50 off for the first 100 lifetime licenses!

SleekRank for Historical tsunami events

Tsunami events need a page each, not a search-only database

The NOAA NCEI tsunami database catalogs roughly 1,500 historical tsunami events from antiquity through the most recent year. The canonical record is a search form and a downloadable CSV that paleotsunami researchers, coastal hazard planners, and emergency management agencies pull and parse independently because the public-facing surface is a paginated table, not an indexable URL set per event with the full runup and casualty detail.

SleekRank reads the NCEI file directly and renders one WordPress page per event. Each page carries event ID, date, source type, source magnitude, region, maximum water height, runup count, deaths, damage estimate, validity grade, and an Event schema block, driven by tag and selector mappings on a shared base page. The URL pattern is /tsunami-events/{slug}/, and the corpus refreshes after the next cache window.

Operations stays in the NCEI export. New paleotsunami research updates validity grades, the cache flushes, and every URL reflects the revised classification. The data file remains the source of truth across both historical and instrumented record entries.

Workflow

From NCEI database to a tsunami event corpus

1

Design the tsunami base page

Build one WordPress page with header, source card, runup block, region section, casualty panel, and Event JSON-LD container. This base becomes every event's template across the NCEI historical record.
2

Connect the NCEI source

Point SleekRank at the NCEI tsunami database CSV mirror. Confirm the slug column, NCEI event ID, and a sensible cache duration. Most tsunami publishers set 24 hours for the archive of historical events.
3

Wire schema, runup, and source

Tag mappings for event ID and source region, selector mappings for runup and source magnitude, meta mapping for Event JSON-LD, and a list mapping rendering the runup observations and related-events grid.
4

Handle validity grade updates

Reference a validity grade column in the row. A selector mapping swaps the validity banner across reported, observed, and confirmed states. Editors update one cell when NCEI upgrades a historical record.

Data in, pages out

NOAA NCEI database, one page per tsunami

Tsunami researchers pull the NOAA NCEI database export periodically. SleekRank reads it directly and produces a full landing page per event.
Data source: NOAA NCEI tsunami database
slug event_id date source_region max_runup_m
tohoku-2011-03-11 NCEI-2011-001 2011-03-11 Japan 40
sumatra-2004-12-26 NCEI-2004-002 2004-12-26 Indonesia 51
cascadia-1700-01-26 NCEI-1700-001 1700-01-26 Cascadia 10
krakatoa-1883-08-27 NCEI-1883-001 1883-08-27 Indonesia 42
chile-1960-05-22 NCEI-1960-001 1960-05-22 Chile 25
URL pattern: /tsunami-events/{slug}/
Generated pages
  • /tsunami-events/tohoku-2011-03-11/
  • /tsunami-events/sumatra-2004-12-26/
  • /tsunami-events/cascadia-1700-01-26/
  • /tsunami-events/krakatoa-1883-08-27/
  • /tsunami-events/chile-1960-05-22/

Comparison

NCEI search form vs SleekRank tsunami pages

NCEI database search form

  • Tsunami events sit behind a search form with no canonical per-event URL
  • Runup data fragmented into a separate runup table with no shared page anchor
  • Maximum water height and casualty figures buried in column-toggle interactions
  • No structured Event schema rendered on NCEI tsunami records by default
  • Source type and magnitude require manual cross-reference to seismic database
  • Validity grade updates ship through database refresh, not per-page revisions

SleekRank

  • Every event gets an indexable URL under /tsunami-events/{slug}/
  • Event and Place JSON-LD generated from date, source region, runup, and deaths
  • Source type, magnitude, and validity grade render from one row via mappings
  • Runup observations rendered from the row's runup array via list mapping
  • Sitemap covers every event ID in the NCEI tsunami export automatically
  • Related-events grid links by source region, magnitude band, and century cluster

Features

What SleekRank gives you for Historical tsunami events

Event schema per tsunami

Map date, source region, source magnitude, and runup to Event and Place JSON-LD via meta mappings. Each tsunami gets a structured data block so search engines can resolve the entity from the NCEI event ID without scraping prose.

Runup and casualty fields

Render maximum runup, source magnitude, deaths, and damage estimate from the row via tag and selector mappings. The base page exposes the same template per event across historical and instrumented record entries.

Source region and validity

Pull source region, source type, and validity grade directly from the NCEI export. The base template renders a context summary block that adapts per event without per-page twig edits or duplicate templates.

Use cases

Who runs tsunami event indexes on SleekRank

Paleotsunami research labs

Academic paleotsunami groups publish event corpora for citation. Each NCEI row resolves to a stable URL so working papers can cite individual events without breaking links across validity grade revisions.

Coastal hazard planners

State and county hazard planners publish public tsunami archives for member coastal jurisdictions. Each event resolves to a stable URL with runup and casualty data for citation in inundation planning.

Earth science news desks

Science desks cover major tsunami events through historical context. SleekRank turns the NCEI file into per-event pages on the publication's domain so coverage links to indexed event context.

The bigger picture

Why tsunami event data belongs on a public corpus

Tsunami event data is public and curated by NOAA NCEI, but the public-facing surface is a search form and a paginated table. Paleotsunami researchers, coastal hazard planners, and earth science newsrooms all pull the same export and rebuild fragments because there is no indexable URL set that surfaces individual events for citation, ranking, or deep linking. SleekRank closes that gap by turning the NCEI file into one indexable URL per event on the publishing organization's own domain.

Each page ranks for its own date, source region, and runup pairing. Event and Place schema make every tsunami eligible for entity-level surfaces. Internal links across source regions, magnitude bands, and centuries form a navigation network that strengthens the publisher's authority on tsunami science.

The export file stays in the same workflow editors already use, and the public corpus refreshes through cache cycles rather than a manual pipeline.

Questions

Common questions about SleekRank for Historical tsunami events

SleekRank reads the NOAA NCEI tsunami export directly. The agency publishes it on a rolling basis. Point the data source at your local mirror, set a cache window, and every page reflects the source on the next refresh without rebuilds.

 

Most safety publishers set a 24-hour cache. The base page rerenders with new totals on the next cache window. A WP-CLI manual flush handles urgent corrections when a record updates between scheduled refresh cycles on the public corpus.

 

Yes. Run a related-events block that uses sleekRankRelatedEntries() filtered by region, year, or source region. Each tsunami event surfaces up to six adjacent records, and the grid stays deterministic per slug so links remain stable.

 

Event and Place are valid Schema.org types and Google parses both. Whether enhanced result tiles render varies by query intent and competition, but the structured data improves entity resolution and underpins knowledge-panel eligibility.

 

Store an array of county codes in the row. A list mapping on the base template renders each county chip with its own internal link, and the canonical URL stays anchored to the primary county so the slug strategy does not fragment by jurisdiction.

 

Yes. Adjust the row in the source export and SleekRank reflects the new totals on the next cache refresh. A revision history column lets the base page expose the change log via a list mapping for transparency on amended records.

 

Yes. Store an array of source region identifiers in the row. A list mapping renders each one with its own panel, and the schema mapping carries the primary source region into structured data so entity resolution stays clean across multi-actor records.

 

Keep the original record name at the time of occurrence in the row. Add a current-name column for succession. The base page renders both, and a related-events grid filtered by current name gives readers continuity across renaming.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€99

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€179

EUR

per year

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Launch Offer

€299

€249

EUR

once

Get started

further 30% launch-discount applied during checkout for existing customers.

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView