walletme.eu

Summary

We found 38 old URLs on walletme.eu. 37 need a 301 redirect and 1 needs no redirect. 24 redirects have a confident destination. 13 need human review before launch. One content page must be created on the new site for its redirect to work. No sitemap was found, so the list comes from the crawl of 38 pages and an archive lookup that returned 20 URLs.

Key findings

• 38 old URLs found, all by crawl. The sitemap contributed 0. The archive also listed 20 URLs.
• 37 URLs get a 301 redirect, 0 are marked gone (410), and 1 is unchanged and needs no redirect.
• 24 redirects are confident and 13 need review.
• By method: 22 came from existing redirects on the old site, 11 were matched by Claude, and 5 by rule.
• 1 content page must be created on the new site. The redirect to it will not work until the page exists.
• No facility pages were found, so 0 placeholders need Tenant facility IDs.
• No street addresses were found on the old site, so nothing could be matched by address.
• No URLs were skipped for budget.

Summary written by Claude (claude-sonnet-5-5) from the run’s numbers.

Contents

1. What daleg did
2. The old site
3. Facilities
4. Before launch: to-do
5. All redirects
6. Not redirected
7. How to apply the redirect file
8. After launch
9. Settings used

What daleg did

When this domain moves to the Tenant platform, every URL people or search engines still use must land on the page that now serves the same need, with a permanent (301) redirect. daleg built the list in these steps:

1. Found every old URL it could (38 unique): 0 from 1 sitemap files, 38 from crawling 38 pages, and 20 past URLs from the Internet Archive. URLs that differ only by tracking parameters, letter case or a trailing slash were treated as one. 37 CMS, feed, image and code URLs were left out.
2. Checked what the old site does with them today: 0 uncrawled URLs got a quick request to see whether they still work or already redirect. Where the old site already redirects a URL, the new redirect goes straight to the final destination, so there are no redirect chains.
3. Identified the facilities (0) from street addresses in structured data and page text, and each facility’s own page on the old site.
4. Listed the destinations (11) from the Tenant site map: standard pages every Tenant site has, plus state, city and facility pages for this customer.
5. Matched old URLs to destinations: fixed rules first (0 by facility address, 5 by standard page rules or identical paths, 22 by the old site’s own redirects), then Claude (claude-sonnet-5-5) for the rest, 33 URLs in 1 batches, choosing only from the destination list or proposing a content page the site map allows. 0 got the site map’s fallback for their kind of page.
6. Checked the plan: no redirect points to itself; no old path that the new site uses as a real page is redirected away (0 held back); entries below 85% confidence are flagged for review.

Claude: 2 calls, 14,327 input and 2,935 output tokens, about $0.06.

The old site

Facilities (0)

Facility pages carry the most search value. Each old facility page redirects to that facility’s page on the new site. Their Tenant IDs are not known yet, so new paths show {tenantFacilityId}.

No facility addresses were found on the old site.

Before launch: to-do

Facility IDs to fill in (0 redirects)

None.

Content pages to create (1)

These redirects point to content pages that are not standard Tenant pages. Create each page on the new site with exactly this path (moving the old content), or change the redirect.

Redirects to review (13)

Matched with low confidence or by fallback. Check each one; the notes say why it was chosen. URLs still on the old site (found in its sitemap or by the crawl) come first; past URLs known only from the Internet Archive matter less.

All redirects (37)

Grouped by kind of old page. The same list is in the downloadable redirect file.

Not redirected

Same path on the new site (1)

Held back: the new site uses this path (0)

None.

Left out on purpose (37)

CMS internals, feeds, images, scripts and other non-page URLs matching the “Paths never redirected” setting.

How to apply the redirect file

walletme.eu-redirects.json holds the same plan. Each entry has from, to, status (301 or 410) and flags. Apply only entries with "ready": true; check "needsReview": true entries first.

# Tab-separated: status, old path, new path
jq -r '.redirects[] | select(.ready) | [.status, .from, (.to // "")] | @tsv' walletme.eu-redirects.json

# Loop in a shell script
jq -c '.redirects[] | select(.ready)' walletme.eu-redirects.json | while read -r r; do
  from=$(jq -r .from <<<"$r"); to=$(jq -r '.to // empty' <<<"$r"); status=$(jq -r .status <<<"$r")
  echo "$status $from -> $to"   # replace with your platform's redirect command
done

Match old paths with and without a trailing slash, case-insensitively, and ignore query strings unless matchQuery is true.

After launch

1. Request every old URL in the redirect file on the live domain and confirm each answers 301 once and lands on a 200 page (no chains, no 404s).
2. Submit the new sitemap in Google Search Console and watch the Pages report for “Not found (404)” for 30 days; add redirects for any old URLs that appear.
3. Update the Google Business Profile website link of each facility to its new facility page.
4. Keep the redirects in place for at least a year.

Settings used