Map URLs (main)

Classifies each batch of old URLs and chooses each one’s destination, a content path to create, or 410 Gone.
prompt.mapUrls · default value

The old website is {{sourceDomain}}. Its domain is moving to a new site built from the Tenant website template. Every old URL that people or search engines may still use needs a destination on the new site that serves the same need.

## The new site's structure (site map)

## Destinations available for this customer

Choose targetId from this list. Paths containing {tenantFacilityId} are facility pages whose Tenant ID is not known yet; choose them normally.

## What to return for each old URL

- kind: what the old page is (home, facility, facility-subpage, city, state, locations-index, storage-type, unit-size-guide, contact, pay-login, company, faq, careers, legal, blog-index, blog-post, tips, specials, reviews, asset, junk, other).
- action:
  - "redirect" — send it to targetId (an id from the target list), or, when the right destination is a content page that does not exist yet, to proposedPath (a path matching a site-map pattern whose Exists line is "content", with {slug} filled in). Give either targetId or proposedPath, not both.
  - "gone" — content that should not live on (expired one-off promotions, test pages, spam, duplicate tag/search/print pages with no equivalent). The server will answer 410 Gone. Use sparingly; a relevant fallback is usually better for visitors.
  - "keep" — the old path already exists unchanged on the new site (identical to a target path), or it already has the exact form of a site-map content pattern (e.g. /blogs/{slug}/) so the content can be recreated at the same path; no redirect needed.

## How to choose

1. Facility pages and anything about one facility (its units, reserve, rent, specials, reviews, directions, gallery) go to that facility's page. Identify the facility by the address/facility given for the URL, or by the city and name in the URL and title.
2. Standard pages (contact, pay bill/login, size guide, locations, legal, blog index) go to their standard target.
3. Content pages go to the matching existing target if there is one; otherwise propose the content path, keeping the old slug when it is clean. Mark these clearly in the reason ("content to migrate").
4. When nothing specific fits, use the site map's Fallback lines for that kind (a facility subpage → its facility; a blog post → /blogs/; a storage type → /storage-types/). Use the homepage only as a last resort; search engines treat many redirects to the homepage as errors.
5. Old pages for cities or areas: a city with its own city page → that page; a city with one facility → that facility; otherwise the state page.
6. Never redirect a page to an unrelated facility just because it is in the same state.

Plain text sent to Claude. The opening  explains the prompt and is removed before sending; {{placeholders}} are filled in at run time.

Cancel