Start with an inventory of what the page contains and what it depends on. Record the copy, source assets, link destinations, form handling and domain arrangements. Give each item an intended use before asking an assistant to recreate the page.
A screenshot can explain the layout. It does not supply an editable image file, establish reuse permission or show where a submitted request ends up. Keep those inputs separate.
The output of this exercise is a preparation packet: usable material, an old-to-intended destination map and named dependencies. The fictional workshop below demonstrates that packet. No website has been copied or moved, and this guide establishes no ClickFunnels AI import, sync or migration capability.
Define the page you are preparing
Record the current full URL, the page's purpose and the date of your inspection. List the sections and visitor actions you intend to keep, change or omit. Keep the current page available while preparing the new draft unless a separate, already scoped change requires otherwise.
Use only source content and assets you are permitted to reuse. For each item, record its origin, the permission or ownership basis you are relying on and any conditions. If that information is missing, mark the item unresolved and name who will settle it. A picture being visible on the old page is not your reuse record.
Keep account credentials, private customer records and administrative access links out of the packet. Point to your normal access process when someone needs a restricted source file.
A fictional old-page inventory
Imagine a studio preparing a new draft of its beginner ink-drawing workshop page. The existing address is https://studio.example/workshops/ink-drawing. The page explains the workshop, accepts enquiries, provides a materials PDF and links existing learners to a course on CF2.
Every page detail, permission statement and system association in this example is invented. The .example addresses are documentation names, as described in RFC 6761; they are not working destinations to visit or submit to.
Scroll horizontally to compare all columns.
| ID | Existing item | Intended use in the draft | Decision or dependency |
|---|---|---|---|
| C01 | Studio-written workshop title and introduction | Explain the same beginner workshop | Keep the supported offer; reorganize wording |
| C02 | “Book by Friday” banner with no full date | Omit the unsupported deadline | Organizer must supply any current deadline separately |
| A01 | Studio-owned ink-table.jpg
|
Use the supplied original in the workshop section | Reuse permitted in this fictional example; review crop and image purpose |
| A02 |
guest-artist.jpg from a past photographer |
Leave out for now | Reuse terms and current relevance unresolved |
| A03 | Studio-owned ink-materials.pdf
|
Link to the existing finished file | Preserve its current destination; no file transfer assumed |
| L01 | “Ask about the workshop” link to #enquire
|
Lead to the draft's enquiry section | Section and form behavior need separate checks |
| L02 | “Existing learners: course sign-in” | Keep the intentional CF2 destination | Preserve the exact course link and its meaning |
| F01 | Email and question fields with a submit button | Describe the same enquiry task | Receiving system, validation and reply process need confirmation |
| E01 | Embedded date calendar | Record the dependency before recreating it | Provider, allowed use and supported replacement unresolved |
| H01 | Existing marketing domain and hosting | Leave current public routing in place | Any future domain or hosting change is a separate task |
The inventory allows useful draft work now. C01 and A01 can inform the layout. C02 and A02 should not be carried forward as if their missing facts were settled. F01 remains a functional dependency even if the new fields look correct.
Separate image files from their job on the page
For each reusable image, collect the original file, its intended placement and what it contributes. Record any required credit or reuse conditions. Keep an unresolved image out of the usable asset set until that decision is settled.
Write alternative text for the image's role in the new context. W3C's image decision tree distinguishes meaningful, functional and decorative images. Moving an image from an illustration to a link can change what its alternative text needs to communicate.
In the fictional example, ink-table.jpg shows the workshop materials. Its placement and description need review together. The unknown photographer terms for guest-artist.jpg are a different dependency; rewriting its alternative text does not resolve them.
Map destinations before carrying links forward
Record both the written link and its full resolved destination. Relative links depend on the document's location, as explained in MDN's URL guide.
For example, /downloads/ink-materials.pdf on the old page resolves to https://studio.example/downloads/ink-materials.pdf. On a different preview host, the same relative path can point somewhere else. In this plan, the draft should retain the existing full download destination until a file move is separately arranged.
Use a destination map like this. It records intentions, not configured routes.
Scroll horizontally to compare all columns.
| Item | Existing destination | Intended treatment |
|---|---|---|
| Marketing page | https://studio.example/workshops/ink-drawing |
Keep the public page; new draft has no assigned public URL |
| L01 enquiry link | https://studio.example/workshops/ink-drawing#enquire |
Provide a draft section with that purpose; verify its actual link and behavior later |
| A03 materials | https://studio.example/downloads/ink-materials.pdf |
Keep this exact full destination in the draft |
| L02 CF2 course | https://courses.studio.example/sign-in |
Keep this exact full destination for existing learners |
| F01 form receiver |
https://forms.studio.example/enquiries in the fictional notes |
Record for investigation; do not assume the new page can submit to it |
| E01 calendar |
https://calendar.studio.example/ink in the fictional notes |
Hold the embed until its provider and replacement requirements are known |
A deliberate CF2 course link should continue to mean “open this existing course.” Do not replace it with a general homepage or an assumed new account destination because the marketing page is being redesigned. A future change to that course route needs its own scope and verification.
Google's site-move guidance recommends mapping old URLs to intended new destinations when URLs change, including relevant asset URLs. This preparation map does not create redirects, change canonical URLs or guarantee a search outcome.
Reconstruct the form dependency
Separate the form's visible questions from its receiving workflow. For a standard HTML form, the action attribute identifies a submission destination, as MDN's form guide explains. That destination alone is not a record of the entire application process.
For F01, the fictional notes contain an address and two visible fields. They do not establish whether a new page can use the receiver. Ask the person responsible for the form to identify:
- The expected fields, required values and validation rules.
- The actual place enquiries are stored and how access is obtained.
- The permitted connection method and any configuration needed.
- The reply owner, notifications and other effects of submission.
- The success and failure states, and how a permitted check will verify them.
Record the approved privacy and consent wording that belongs with the real form. Do not copy unknown scripts or private integration settings into an assistant prompt. If a dependency is unresolved, record the gap; a replacement submit button cannot settle it.
Keep the custom-domain decision explicit
For H01, record who manages the domain and hosting, which hostname and path serve the current page, and who can inspect their configuration. Keep the existing public page and its routes unchanged during preparation.
If a later project includes moving the public address, specify the actual destination, provider requirements, certificate and routing checks, affected links and restoration plan. Inspect the current setup before deciding which changes are needed. The existence of a draft does not establish custom-domain support or a completed connection in any product.
Treat keeping the same public URL and choosing a new URL as different plans. Both need a verified release arrangement. Neither should be silently selected by copying a hostname into a build brief.
Give the assistant a bounded preparation request
Using the fictional inventory, the initial request could be:
Propose a draft page structure for the beginner ink-drawing workshop using C01 and the supplied A01 image. Keep the offer as an enquiry. Omit the undated C02 deadline and unresolved A02 portrait.
Keep the existing A03 download and L02 CF2 course destinations in the link plan. Identify the enquiry section, but list F01's receiving workflow and E01's calendar as unresolved dependencies. Do not invent a working connection or a successful submission.
Return the proposed sections, material used and unresolved decisions. Keep the existing public page, domain, course route and redirect/canonical configuration unchanged.
This request produces a reviewable plan. Building any part of it still depends on the actual tool, account access and supported configuration. It does not require copying the old site's source code or importing a live site.
Use the rebuild preparation worksheet
The rebuild preparation worksheet contains the completed fictional inventory, destination decisions and blank templates. Replace the example with your permitted source material and current observations. Give every unresolved item a responsible person and a concrete next check.
For a ClickFunnels AI project, consult the agent guide for current workflow and access requirements. Keep preparation, a built draft, verified behavior and a public route change recorded as separate results.
Common questions
Is a screenshot enough for an AI-assisted rebuild?
It can communicate visible structure. Supply permitted copy and original assets separately, and record destinations and functional dependencies that the screenshot does not establish.
Can the existing CF2 course stay where it is?
This plan preserves its intentional link and current destination. Any account, content or course-route change belongs to a separately scoped task; no transfer is assumed.
What if a source asset or integration is unavailable?
Mark it unresolved and identify the work it blocks. Continue the independent outline or copy decisions using available, permitted material. Keep the missing item visible in the returned plan.