# Landing page import worksheet

Use this worksheet to turn a public-page import into a verified migration plan. Replace the examples with the client’s actual systems. Do not record passwords, tokens, secret values, private customer records, or other sensitive data here.

## 1. Project and authority

- Client:
- Source URL:
- Source owner:
- Permission to copy content and assets confirmed by:
- Evidence location:
- Import platform/project:
- Agency owner:
- Client approver:
- Intended production hostname:
- Planned cutover window:
- Rollback decision owner:
- Source-retention date:

## 2. Import contract

Choose one direction before importing.

- [ ] Close reconstruction: preserve the approved copy, design direction, paths, and behavior where supported.
- [ ] Content migration: preserve approved content and assets, but rebuild the design.
- [ ] Redesign reference: use the source only as evidence and inspiration; document every intentional change.

Required source states:

- [ ] Desktop width
- [ ] Phone width
- [ ] Navigation open
- [ ] Form empty
- [ ] Form validation errors
- [ ] Form success
- [ ] Hover/focus states
- [ ] Cookie/consent state
- [ ] Other:

## 3. Source record

| Item | Source evidence | Required in new page? | Owner | Notes |
|---|---|---:|---|---|
| Visible copy and headings |  |  |  |  |
| Images, icons, video, downloads |  |  |  | Rights and source files confirmed? |
| Fonts and licenses |  |  |  |  |
| Desktop layout |  |  |  |  |
| Phone layout |  |  |  |  |
| Navigation and menus |  |  |  |  |
| Forms and validation |  |  |  |  |
| Thank-you state or page |  |  |  |  |
| Analytics and advertising events |  |  |  | Record names, not secret values |
| Consent behavior |  |  |  |  |
| Metadata and social image |  |  |  |  |
| Canonical, robots, sitemap |  |  |  |  |
| Redirects and campaign links |  |  |  |  |
| Booking, CRM, email, payment, or other destinations |  |  |  |  |
| Legal and privacy text |  |  |  | Appropriate reviewer named? |

## 4. Capture / Rebuild / Reconnect / Retire matrix

Give every observed element one disposition.

| Element or workflow | Disposition | New implementation | Destination or dependency | Acceptance evidence | Owner | Status |
|---|---|---|---|---|---|---|
| Hero copy and image | Capture |  |  | Desktop and phone comparison |  |  |
| Contact form fields | Rebuild |  |  | Valid and invalid submissions |  |  |
| Form delivery | Reconnect |  | Approved inbox or CRM | Labeled record received |  |  |
| Old tracking script | Retire | Remove after approval |  | No production requests or duplicate events |  |  |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |

Disposition definitions:

- **Capture:** visible content or presentation can be brought into the draft, then reviewed.
- **Rebuild:** behavior must be implemented in the new system.
- **Reconnect:** the page must be connected to a named external destination or service.
- **Retire:** the old element is intentionally removed, with impact and approval recorded.

## 5. URL and discovery map

| Old URL | New URL | Action | Canonical | Internal links updated? | Tested status |
|---|---|---|---|---:|---|
|  |  | Keep / 301 / 308 / 404 / 410 |  |  |  |
|  |  |  |  |  |  |
|  |  |  |  |  |  |

Also verify:

- [ ] Production title and meta description
- [ ] Social title, description, and image
- [ ] Heading hierarchy
- [ ] Image alternatives
- [ ] Structured data contains approved facts only
- [ ] Production canonical
- [ ] Production robots rules and no migration-only `noindex`
- [ ] Sitemap uses intended canonical URLs
- [ ] Campaign, email, ad, QR, and partner links point to the intended page

## 6. End-to-end acceptance record

| Journey | Test input/state | Browser result | Destination result | Analytics result | Evidence | Status |
|---|---|---|---|---|---|---|
| Primary CTA |  |  |  |  |  |  |
| Valid form | Clearly labeled test |  |  |  |  |  |
| Invalid form | Missing/invalid field |  | Not applicable |  |  |  |
| Booking/checkout |  |  |  |  |  |  |
| Phone/email/download |  |  |  |  |  |  |

## 7. Release decision

- Candidate/version ID:
- Approved source comparison:
- Open blockers:
- Known non-blocking items, owners, and due dates:
- Checks to repeat after the latest change:
- Decision: [ ] Hold [ ] Ship [ ] Ship with recorded known items [ ] Roll back
- Decision owner:
- Decision time:

## 8. Production pass

- [ ] Opened the real production hostname in a fresh session
- [ ] Checked representative desktop and phone layouts
- [ ] Opened menus, dialogs, and interactive states
- [ ] Used the primary journey with a keyboard and visible focus
- [ ] Submitted a labeled production test and confirmed its destination
- [ ] Confirmed intended analytics events without duplicate firing
- [ ] Tested old URLs and redirects
- [ ] Checked canonical, robots rules, sitemap, and social preview
- [ ] Confirmed TLS, callbacks, cookies, and generated links use the canonical origin
- [ ] Checked production errors and monitoring without copying sensitive data
- [ ] Recorded rollback or source-retention timing

## 9. Handoff note

- What the client can edit:
- What requires agency review:
- Where evidence and source files are retained:
- How to report a problem:
- Recovery contact:
- Follow-up date:

This worksheet is an operational starting point, not legal, accessibility, privacy, or search-ranking advice. Adapt it to the landing page’s actual risks and the client’s jurisdiction.