SleekRank reads the USGS GeoJSON feed 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 manual 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.

Yes. Run a related-events block that uses sleekRankRelatedEntries() filtered by region, year, or source network. Each seismic event surfaces up to six adjacent records, and the grid stays deterministic per slug so internal 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 network identifiers in the row. A list mapping renders each one with its own panel, and the schema mapping carries the primary source network into structured data so entity resolution stays clean across records that span multiple actors.

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 or reclassification.