{"id":"6a26dd74ddc38a01aa372060","title":"2026 06 08 Issue 202","path":"how-to/committee/release-notes/2026-06-08-issue-202","contentMarkdown":"# 08-Jun-2026 — legacy site URL redirect mapping with scraping, auto-mapping, and admin UI [#202](https://github.com/nbarrett/ngx-ramblers/issues/202)\n\n## [build 671](https://github.com/nbarrett/ngx-ramblers/actions/runs/27146990563) — [commit 92f4c30](https://github.com/nbarrett/ngx-ramblers/commit/92f4c3010b26acd2ad99ecd4b8f6bac0c8e42414)\n\n_____\n\nWhen migrating a legacy site (e.g. www.kentramblers.org.uk) to NGX Ramblers, external\norganisations and search engines hold links to specific URLs on the old site. This feature\nensures those links continue to work by automatically discovering, mapping, and redirecting\nlegacy URLs to their new equivalents.\n\nNavigate to **Admin > Legacy Redirects** and select the **Scrape** tab.\n\n- Enter the legacy domain (e.g. `www.kentramblers.org.uk`)\n- Configure options: max pages to crawl, delay between requests, and whether to respect robots.txt\n- Click **Run Scrape** to start the crawler\n- Real-time progress is displayed via WebSocket as the crawler discovers pages\n- Fragment identifiers (e.g. `#WW`) are recorded as separate mappable URLs\n- Metadata is captured for each URL: page title, HTTP status, and content type\n\nThe scraper can be re-run at any time to discover new or changed pages. Existing URLs are\npreserved and only new ones are added.\n\nAfter scraping, click **Auto-Map** to run the mapping algorithm. It matches legacy URLs\nto new NGX pages using multiple strategies:\n\n- **Walk URL match** (high confidence) — matches against imported walk/event URLs\n- **Slug match** (high confidence) — compares normalised path slugs against CMS page paths\n- **Title similarity** (medium confidence) — token overlap between scraped titles and page names\n- **Path pattern** (medium confidence) — recognises common patterns like `/walks/*`, `/gallery/*`, `/contact*`\n\nEach mapping receives a confidence score (high, medium, low, or unmapped).\n\nThe **Mappings** tab shows all discovered URLs with their proposed targets:\n\n- **Filter** by status (pending, accepted, ignored) or confidence level\n- **Search** across URLs and titles\n- **Sort** by any column\n- **Accept** a mapping to activate the redirect\n- **Edit** the target URL with autocomplete against all known NGX pages and walks\n- **Ignore** URLs that don't need redirects (e.g. admin pages)\n- **Bulk Accept** all high-confidence mappings with one click\n- **Delete** unwanted entries\n\nThe **Summary** tab shows a dashboard with:\n\n- Total URLs discovered\n- Mapped vs unmapped counts\n- Progress bar showing accepted/pending/ignored breakdown\n- Breakdown by confidence level and status\n\nOnce mappings are accepted, the system serves **301 permanent redirects** for matching\nincoming requests. This happens automatically via Express middleware — no additional\nconfiguration is needed.\n\n- Redirects are cached in memory and refreshed every 5 minutes\n- Redirect hit counts are tracked for monitoring (batched writes every 60 seconds)\n- API requests (`/api/*`) are never redirected\n\nEach NGX site can have its own set of legacy URL mappings. To configure which legacy\ndomains should trigger redirect lookups, add a `legacy-redirect` config key in the\nsystem settings with:\n\n```json\n{\n\"legacyDomains\": [\"www.kentramblers.org.uk\", \"kentramblers.org.uk\"],\n\"cacheRefreshMinutes\": 5,\n\"hitFlushIntervalSeconds\": 60\n}\n```\n\nMultiple legacy domains are supported per site.\n\n---\n\n**Shared Model:**\n- `projects/ngx-ramblers/src/app/models/legacy-url-redirect.model.ts` — interfaces and enums\n\n**Server — Database:**\n- `server/lib/mongo/models/legacy-url-mapping.ts` — Mongoose schema (collection: legacyUrlMappings)\n- `server/lib/mongo/models/legacy-scrape-run.ts` — Mongoose schema (collection: legacyScrapeRuns)\n\n**Server — Routes:**\n- `server/lib/mongo/routes/legacy-url-mapping.ts` — CRUD + /bulk-update-status, /auto-map, /summary, /target-urls\n- `server/lib/mongo/routes/legacy-scrape-run.ts` — CRUD routes\n\n**Server — Core Logic:**\n- `server/lib/legacy-redirect/redirect-middleware.ts` — Express middleware with in-memory cache and batched hit counting\n- `server/lib/legacy-redirect/auto-mapper.ts` — multi-strategy mapping algorithm\n- `server/lib/legacy-redirect/legacy-url-scraper.ts` — starts at the home page and follows links outward to find every internal page, fetching each one via the integration worker\n- `server/lib/legacy-redirect/legacy-redirect-ws-handler.ts` — WebSocket handler for long-running scrape operations\n\n**Frontend — Services:**\n- `projects/ngx-ramblers/src/app/services/legacy-redirect/legacy-url-mapping.service.ts`\n- `projects/ngx-ramblers/src/app/services/legacy-redirect/legacy-scrape-run.service.ts`\n\n**Frontend — Admin Component:**\n- `projects/ngx-ramblers/src/app/pages/admin/legacy-redirects/legacy-redirects.component.ts`\n- `projects/ngx-ramblers/src/app/pages/admin/legacy-redirects/legacy-redirects.component.sass`\n\n- `projects/ngx-ramblers/src/app/models/config.model.ts` — added LEGACY_REDIRECT ConfigKey\n- `projects/ngx-ramblers/src/app/models/websocket.model.ts` — added LEGACY_URL_SCRAPE EventType\n- `projects/ngx-ramblers/src/app/modules/admin/admin-routing.module.ts` — added legacy-redirects route\n- `server/lib/mongo/controllers/extended-group-event.ts` — exported convertTitleToSlug for reuse\n- `server/lib/server.ts` — registered routes and redirect middleware\n- `server/lib/websockets/websocket-server.ts` — registered WebSocket handler\n\n- `legacyUrlMappings` — compound unique index on (legacyDomain, legacyPath, legacyFragment)\n- `legacyScrapeRuns` — scrape operation history with audit logs\n\n- `GET/POST/PUT/DELETE /api/database/legacy-url-mapping` — standard CRUD\n- `POST /api/database/legacy-url-mapping/bulk-update-status` — bulk status changes\n- `POST /api/database/legacy-url-mapping/auto-map` — trigger auto-mapping\n- `GET /api/database/legacy-url-mapping/summary` — aggregate counts\n- `GET /api/database/legacy-url-mapping/target-urls` — autocomplete data\n- `GET/POST/PUT/DELETE /api/database/legacy-scrape-run` — scrape history CRUD\n- WebSocket: `LEGACY_URL_SCRAPE` event type for long-running scrape+map operations","contentHtml":"

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

\n

build 671 — commit 92f4c30

\n
\n

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

\n

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

\n\n

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

\n

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

\n\n

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

\n

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

\n\n

The Summary tab shows a dashboard with:

\n\n

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

\n\n

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

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

Multiple legacy domains are supported per site.

\n
\n

Shared Model:

\n\n

Server — Database:

\n\n

Server — Routes:

\n\n

Server — Core Logic:

\n\n

Frontend — Services:

\n\n

Frontend — Admin Component:

\n\n"}