spaceboxstorage.com

Summary

Discovery found 586 old URLs on spaceboxstorage.com (a StoragePug site). The plan has 585 301 redirects, 0 410s and 1 URL that needs no redirect. Of the 585 redirects, 308 have a confident destination and 277 need human review. The plan is not ready to launch. 291 redirects point to facility URLs that contain a {tenantFacilityId} placeholder. These cannot work until the facilities exist on the new site and their IDs are known. 8 content pages must also be created on the new site. No new site address was given for this run.

Key findings

• Coverage: 586 old URLs found. 585 get a 301, 1 is unchanged, and none are marked gone (410). Of the 585 redirects, 308 are confident and 277 need review.
• Sources: 110 URLs came from the sitemap, 70 from the crawl and 548 from the archive. Sources overlap, so these counts do not add up to 586.
• Methods: 18 redirects come from fixed rules, 277 from facility data and 291 from Claude matching. The 277 facility-data redirects equal the 277 needing review.
• 8 facilities were found on the old site.
• 291 redirects use facility URLs with a {tenantFacilityId} placeholder. Re-running the plan with the new site's address will give exact URLs.
• 8 content pages must be created on the new site before their redirects will resolve. Each one must use a path that fits the template's content patterns.
• The crawl covered only 33 pages. 32 JavaScript-built pages were rendered in a headless browser, within the limit of 60. 120 more known URLs were mapped from their address and sitemap entry only.

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 (586 unique): 110 from 1 sitemap files, 70 from crawling 33 pages, and 548 past URLs from the Internet Archive. URLs that differ only by tracking parameters, letter case or a trailing slash were treated as one. 0 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 (8) from street addresses in structured data and page text, with Claude removing non-facility addresses and merging duplicates, and each facility’s own page on the old site.
4. Listed the destinations (30) 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 (277 by facility address, 18 by standard page rules or identical paths, 0 by the old site’s own redirects), then Claude (claude-sonnet-5-5) for the rest, 291 URLs in 8 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: 10 calls, 90,215 input and 25,831 output tokens, about $0.43.

The old site

Facilities (8)

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}.

Before launch: to-do

Facility IDs to fill in (291 redirects)

These redirects point to facility pages whose Tenant ID is not known yet. Once the facilities exist on the new site, run daleg again with its address (exact URLs), or replace {tenantFacilityId} by hand using the facility named on each entry.

Content pages to create (8)

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 (277)

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 (585)

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