08-Jun-2026 — legacy site URL redirect mapping with scraping, auto-mapping, and admin UI #202

build 671 — commit 92f4c30

When migrating a legacy site (e.g. www.kentramblers.org.uk) to NGX Ramblers, external organisations and search engines hold links to specific URLs on the old site. This feature ensures those links continue to work by automatically discovering, mapping, and redirecting legacy URLs to their new equivalents.

Navigate to Admin > Legacy Redirects and select the Scrape tab.

The scraper can be re-run at any time to discover new or changed pages. Existing URLs are preserved and only new ones are added.

After scraping, click Auto-Map to run the mapping algorithm. It matches legacy URLs to new NGX pages using multiple strategies:

Each mapping receives a confidence score (high, medium, low, or unmapped).

The Mappings tab shows all discovered URLs with their proposed targets:

The Summary tab shows a dashboard with:

Once mappings are accepted, the system serves 301 permanent redirects for matching incoming requests. This happens automatically via Express middleware — no additional configuration is needed.

Each NGX site can have its own set of legacy URL mappings. To configure which legacy domains should trigger redirect lookups, add a legacy-redirect config key in the system settings with:

{
"legacyDomains": ["www.kentramblers.org.uk", "kentramblers.org.uk"],
"cacheRefreshMinutes": 5,
"hitFlushIntervalSeconds": 60
}

Multiple legacy domains are supported per site.

Shared Model:

Server — Database:

Server — Routes:

Server — Core Logic:

Frontend — Services:

Frontend — Admin Component: