Guides / Finipage / Editing pages
How to Edit a Landing Page Made by ChatGPT or Claude
Finipage guide · Edit HTML files without code. Open Finipage
You asked ChatGPT, Claude or Gemini for a landing page, and a few seconds later you had a single file, maybe landing.html, that looks surprisingly finished. Then you look closer. The testimonials quote people who do not exist, the "Get started" button goes to example.com, and the hero photo takes three seconds to appear. The page is a good first draft, and getting it ready to use is mostly a matter of knowing where the weak spots are and who should fix which ones: the AI or you.
What AI-generated pages usually get wrong
The layout is often fine. The problems are in the content and in a few technical shortcuts the model takes to make a page that looks complete on first view.
- Placeholder text. Look for "Lorem ipsum", "Your Company", "Acme Inc.", "[Insert benefit here]", "John Doe", and copy so generic it could describe any business, such as "We deliver innovative solutions tailored to your needs."
- Invented testimonials and numbers. Quotes like "This changed how our team works. — Sarah K., Marketing Director", "10,000+ happy customers", "4.9/5 average rating", or a row of well-known company logos under "Trusted by". The model made these up to fill the design.
- Dummy links.
href="https://example.com",href="#"on every button, amailto:hello@yourcompany.comaddress, and social icons that point totwitter.com/with no account name. - Oversized or borrowed images. Images hot-linked from stock photo sites or placeholder services, or a hero image you added later at 4000 pixels wide and 5 MB. Visitors on a phone connection wait for all of it.
- Tailwind CDN classes. Many generated pages include
<script src="https://cdn.tailwindcss.com"></script>and style everything with class names likebg-indigo-600 text-white px-6 py-3 rounded-lg. Tailwind's own documentation describes this CDN script as meant for development rather than production: it builds the styles in the visitor's browser on every page load, and if the script fails to load, the page shows up unstyled. - Scripts you did not ask for. A mobile menu toggle, a fake countdown timer, a newsletter form that shows "Thanks for subscribing" without sending the address anywhere.
Fake testimonials and numbers must go
This is the one item that is not cosmetic. Publishing reviews or statistics you cannot back up is misleading advertising. In the United States, the FTC's rule banning fake reviews and testimonials took effect in October 2024; in Korea, the Act on Fair Labeling and Advertising and the Fair Trade Commission's guidelines on endorsements cover the same ground, and many other countries have comparable consumer protection rules. Logos of companies that are not your clients can also raise trademark complaints.
For each item, replace the quote with a real one you have permission to use, replace a number with one you can prove, or delete the section. A short line such as "Currently working with early customers in Seoul" is often more convincing than a made-up figure anyway.
Why asking the AI again for every fix backfires
After the first version, the natural move is to keep chatting: "Change the button to green", "Replace the phone number", "Make the heading smaller". This works for one or two rounds, then problems start.
- The model usually rewrites the whole file, and things you did not mention change too: a section disappears, a color shifts, class names get renamed.
- Edits you made by hand in between are lost, because the model works from its own last version, not from your file, unless you paste your current file back into the chat each time.
- Long pages get cut short. You may receive a reply that includes a comment like
<!-- rest of the page unchanged -->, and pasting it over your file deletes the rest of the page.
A better split is to use the AI for structural requests, such as "add a pricing section with three plans" or "rewrite this section for a dental clinic", and to make small changes yourself directly in the file.
A practical editing workflow
- Keep the original untouched. Save the AI's output as
landing-v1-original.htmland edit a separate copy. Once you start editing by hand, stop pasting new versions from the chat over it. - Make a fix list. Open the file in a text editor and search for
example.com,href="#",lorem,your,@andhttp. Every hit is either a real address you need to fill in or something to remove. - Do the structural requests first. If you still need a new section from the AI, ask now, before the manual edits begin.
- Edit text, colors, links and images. A text editor works if you are comfortable reading the markup. A visual editor such as Finipage lets you double-click text to rewrite it, set colors and spacing in a side panel, type link addresses into a Link field, and drag a new image file onto an old one. Finipage does not run the page's JavaScript while you edit, which keeps fake timers and pop-ups out of the way, and it leaves the scripts untouched when you save. Because the Tailwind CDN is itself a script, a Tailwind page may appear unstyled in the editor until you allow scripts in the settings.
- Shrink the images before you insert them. A hero photo resized to 1600 to 2000 pixels wide and saved as WebP or JPG at a quality setting around 75 to 80 usually comes out at a few hundred KB, WebP being the smaller of the two. Neither a text editor nor Finipage compresses images, so do this in an image tool first; image formats and sizes has the numbers for other kinds of images.
- Set the page title and description. AI pages often ship with a title like "Landing Page" or "Modern SaaS Template". This text is what appears in browser tabs and search results.
What to check before you use the page
| Check | How |
|---|---|
| No placeholder text remains | Search for lorem, example, your, acme, TODO |
| Every button and link goes somewhere real | Click each one in a normal browser window |
| Testimonials, ratings and client logos are real | Keep only what you can show proof for |
| Contact details are correct | Phone, email, address and business hours in header and footer |
| Images load quickly | Check file sizes; each should be a few hundred KB at most |
| Language setting matches the content | <html lang="en"> on a Korean page should be lang="ko" |
| Footer year and company name | Generated footers often say 2024 or "Company Name" |
| Layout on a phone | View at about 390 px wide |
For the full pre-launch list, see the landing page checklist. When the page is ready, publishing an HTML page online covers how to give it a public address.
Want to try it on your own file? Open the Finipage editor. It runs in your browser and your file stays on your device.