Web marketing + product case study

Turning public weather data into a useful local brand

NCHurricane.com is an independent, real-time weather platform designed and developed by Chuck Copeland. The project combines audience research, content strategy, search foundations, product UX, front-end development, PHP automation, and ongoing quality assurance in one owned-media experience.

View Chuck Copeland's portfolio

The brief

Audience

Residents, visitors, and weather-aware decision makers who need fast access to local conditions, alerts, forecasts, radar, satellite imagery, and tropical information.

Problem

Official data is authoritative but fragmented across products and agencies. The opportunity was to organize it around the questions a local user asks before, during, and after hazardous weather.

Positioning

A focused regional utility: local weather first, tropical intelligence when it matters, clear links back to official sources, and no attempt to replace life-safety guidance.

My role

Product strategy, information architecture, visual design, copy, SEO foundations, accessibility, front-end engineering, PHP data automation, testing, and site operations.

Strategy translated into execution

Intent-based architecture: county pages serve local-weather needs while Atlantic and Eastern Pacific hubs serve tropical discovery.
Reusable content system: shared components keep navigation, weather modules, disclaimers, and trust signals consistent across markets.
Owned-channel utility: live NWS, NHC, NOAA satellite, and radar products create a repeat-use experience instead of a one-time campaign page.
Trust by design: official-source attribution, freshness handling, explicit limitations, secure administration, and exact storm identity checks reduce ambiguity.
Discoverability: canonical URLs, page-specific metadata, structured data, social previews, a sitemap, and crawler guidance provide a clean search foundation.
Inclusive performance: keyboard support, meaningful states, responsive layouts, deferred media, and optimized county imagery support more users on more devices.

Current product scope

The shared platform supports eight Eastern North Carolina counties, multi-zone coastal experiences, a San Diego market pilot, and two tropical basins. Its file-based data pipeline turns public feeds into resilient local pages without a framework or database dependency.

This is a working product, not a static mockup: automated cache jobs, current-condition selection, active-storm products, alerts, forecasts, maps, radar, satellite imagery, and meteograms are part of the operating system.

Verified audience results

Traffic over the last year

Measured during the 12-month reporting period ending August 11, 2026.

20,309 Visitors

228,329 Page impressions

1,400–1,600 Typical visitors per month

These figures are a fixed historical reporting snapshot rather than live counters.

Measurement framework

The verified traffic totals establish an audience baseline. The next measurement phase is designed around four questions:

Acquisition

Which organic queries, referring sites, social posts, and geographic markets bring qualified visitors?

Engagement

Which county, tropical, radar, satellite, and forecast interactions show that users found the information they needed?

Retention

How often do users return during normal weather versus high-impact events, and which entry pages build repeat use?

Quality

How do Core Web Vitals, data freshness, errors, accessibility checks, and broken-link monitoring affect trust and conversion?