How do I make a new page match the rest of my AI-built site?

Name one existing page as the visual reference and tell the builder to reuse the same header, footer, colors, fonts, buttons and spacing. Also tell it not to create duplicate versions of shared site elements. The prompt above includes those safeguards.

Will adding a page change my existing pages?

It should not, but broad instructions can cause an unnecessary site-wide restyle. This prompt limits the work to one new page and requires the builder to check that existing pages, forms and account areas are unchanged.

Should every new page appear in the main menu?

No. Important service and information pages often belong in the main menu, while confirmation, private or highly specific pages may belong in a footer or direct link. Choose the place that helps the intended visitor without overcrowding the navigation.

Getting Started

Add a second page that matches your site

Add one more page to a working site without making it look or behave like a separate mini-site.

Time: ~20 minutes Difficulty: Beginner Works with: Base44 / Lovable / v0

When to use this

When your first site already works and you need one more page without making it look or behave like a separate mini-site.

Before you start

A working site with at least one page whose design you want to keep.
The new page name, its purpose, and the label visitors should see in the menu.
The real text and real images you want on the page. If the images are not ready, use clearly labelled placeholders rather than invented photos.
A reference page from your existing site that has the right header, footer, spacing, buttons and mobile behavior.
A decision about where visitors should find the new page: the main menu, footer, an existing button, or more than one of these.

The prompt

Add a new page called [PAGE NAME] to this existing site. Its purpose is [WHAT THIS PAGE HELPS A VISITOR UNDERSTAND OR DO]. The menu label should be [NAVIGATION LABEL], and the main action on the page should be [PRIMARY ACTION].

Use [REFERENCE PAGE] as the design reference. Reuse the same header, footer, navigation, colors, fonts, button styles, content width, spacing rhythm, corners and mobile menu. Do not create a second version of shared site elements and do not restyle any existing page.

Build the new page with these sections in this order: [SECTION NAMES AND WHAT EACH SHOULD CONTAIN]. Use my real wording wherever I provide it: [PASTE REAL CONTENT]. Keep any missing image as a labelled placeholder for [REAL IMAGE NEEDED]. Do not add stock photography or generate fake examples, customers, products, food, places or results.

Add the page to [MAIN MENU / FOOTER / EXISTING BUTTON OR LINK]. Make the current page clear in the navigation. Check that every new link opens the intended destination and that the browser Back button behaves normally.

Give the page one clear main heading, a unique browser title and a short search description based on [PAGE TOPIC AND AUDIENCE]. Use a short readable page address based on [PREFERRED PAGE ADDRESS]. Add the page to the site's list of public pages for search engines, but keep it out if [THIS PAGE SHOULD BE PRIVATE].

Make the page comfortable to use on a phone, including readable text, tap-friendly buttons and no sideways scrolling. Preserve all existing forms, logins, payments, tracking and connections. The visual feeling should remain [THREE BRAND ADJECTIVES].

When finished, tell me where you linked the page, what information is still a placeholder, and which existing pages you checked to confirm nothing else changed.

Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.

Build it on

Start free with Base44 Read Review: Base44

Start free with Lovable Read Review: Lovable

Start free with v0 Read Review: v0 by Vercel

How we make money

What this creates

One complete new page using the site's existing design
The right menu, footer or button links to reach it
A matching phone layout with the same shared header and footer
A unique browser title, search description and readable page address
A clear list of any text or images the owner still needs to supply

Check it worked

Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:

The new page appears wherever you asked visitors to find it
Opening it feels like moving to another page of the same site, not a different template
The logo, menu and footer still lead to the same places as before
The page is easy to read and use on your phone without zooming or scrolling sideways
Every new button opens the destination you named
Existing pages, forms and account areas still look and work as they did before

Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.

Next steps

Connect the new page from the right places

When the page exists but visitors could still miss it

Review the existing site and add natural links to [PAGE NAME] from [RELEVANT EXISTING PAGES OR SECTIONS]. Use descriptive link wording that tells visitors what they will find. Do not add the link everywhere and do not change the page content.

You'll know it worked when: A visitor can reach the new page from each relevant place without the site feeling crowded with repeated links.

Tighten the phone version

After opening the new page on a real phone

Improve only the phone layout of [PAGE NAME]. Fix [DESCRIBE WHAT FEELS WRONG], keep the desktop version unchanged, preserve the site's existing mobile menu, and test every button and form on a narrow screen.

You'll know it worked when: The new page is comfortable to read and use one-handed, with no sideways scrolling or covered controls.

Make the page easier to find in search

Once the final wording is on the page

Review only [PAGE NAME] for search basics. Give it one accurate main heading, a unique browser title and description using [TOPIC PEOPLE SEARCH FOR], descriptive image text where real images exist, and useful links to [RELATED PAGES]. Keep the writing natural and do not repeat keywords unnaturally.

You'll know it worked when: The page has its own accurate search title and description, and its links help visitors continue to relevant pages.

Watch out for

A copied page can keep the wrong details. Check headings, contact details, buttons and search descriptions for text inherited from the reference page.
A matching appearance can hide duplicate site parts. If the builder creates a second header or footer instead of reusing the current one, later edits will drift. Ask it to reuse the shared version.
Adding a menu item can break the phone header. A crowded desktop menu may wrap or hide controls on a small screen. Test the real menu, not only the new page body.
Changing a page address later can break saved links. Choose a short stable address now; if it must change later, automatically send the old address to the new one.
A placeholder must look like a task, not a finished image. Label what real image belongs there so a generic or invented picture is not mistaken for final content.

Platform notes

<ul><li>Base44: Base44 can create the page, connect it to existing navigation and manage the public page from the same app. Explicitly tell it to reuse current shared elements and to keep private pages out of public navigation.</li><li>Lovable: Lovable handles page additions well when you name a reference page or attach a screenshot. Publishing uses a saved version of the project, so publish an update after the new page is approved or the live site will still show the older version.</li><li>v0: v0 can add a page inside the existing project, but navigation, page information for search engines and deployment should all be requested explicitly. Check the deployed version as well as the preview.</li></ul>

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Related playbooks

Related prompts

Last reviewed: 2026-07-27