Guides / Finipage / Putting it online

Landing Page Checklist: What to Check Before Going Live

By the Qorlize team · Last reviewed November 11, 2026

Finipage guide · Edit HTML files without code. Open Finipage

Putting a one-page site live takes a minute. Finding out a week later that the phone number had a typo, or that the "Book a call" button pointed to #, takes longer and costs visitors. Go through this checklist before you share the address. It is grouped by area, so you can split it with a colleague.

Search and sharing basics

Page title. The text in <title> appears on the browser tab and as the blue headline in Google results. Templates often ship with "Landing Page" or "Untitled". Write your business name plus what you offer. Google trims long titles by display width rather than a fixed count, so staying under about 60 characters keeps it whole in most results. In Finipage this is the Title field in the document section of the properties panel.
Meta description. The one- or two-sentence summary search engines may show under the title. Aim for around 150 characters and say plainly who the page is for. Google sometimes writes its own snippet instead, but a clear description is what it uses most often. It sits next to the title in Finipage's document panel.
Favicon. The small icon on the browser tab. Without one, browsers show a generic page icon and usually request /favicon.ico anyway, which turns into a stream of 404 entries in your server logs. Adding it means a line in <head> such as <link rel="icon" href="favicon.png">.
Share image (og:image). When someone pastes your link into KakaoTalk, Slack or Facebook, the preview card uses the og:image meta tag. Without it you get a blank card or a random image from the page. Use a 1200 by 630 pixel image and a full address beginning with https://, not a relative path.

The favicon and og:image tags have no editing panel in Finipage, so add them in a text editor such as VS Code or Notepad, then confirm they are there with Finipage's HTML source view. Adding a favicon and link preview walks through the exact tags and how to test the preview card.

Content and copy

Leftover placeholder text. Search the page for "Lorem ipsum", "Your Company", "John Doe", "example.com", "123-456-7890" and "Feature title". Templates and AI-generated pages are full of these. Press Ctrl+F in the browser for each one.
Contact details. Check the phone number, email, address and business hours against an official source, not your memory. Check the footer too; it is often filled in by a different person, or not at all.
Spelling and numbers. Read the page once out loud, slowly, with extra attention to prices, dates and percentages. A wrong number does more damage than a typo. A second reader catches what you will not.
Dates that will go stale. A "2024 promotion" banner or a copyright year that is three years old makes the page look abandoned.

Text fixes in Finipage are a double-click on the text, then Esc when done. If you would rather fix it in the source, search for the exact sentence in your text editor. Editing an AI-generated landing page covers this in more detail.

Links and buttons

Click every link and every button, not a sample of them. Things to look for:

Buttons whose target is # or empty. They look fine and do nothing.
Section links such as #pricing that no longer match the id of the section, often after a section was renamed or deleted.
mailto: links. Click one and confirm your email program opens with the right address. Remember that many visitors on desktop have no mail program set up, so show the address as text as well.
tel: links. Write the number without spaces or with hyphens only, for example tel:+82-2-1234-5678, and test it on a phone, where it should open the dialer.
Links to social profiles, booking pages and maps that still point to the template author's accounts.

In Finipage, selecting a link shows its address in the Link field, which is built for https:// addresses and #section anchors. For mailto: and tel: links, look them up in the HTML source view and change them in a text editor if needed.

Images

File size. A photo straight from a phone or a stock site is often 3 to 8MB. Aim for a few hundred KB or less per image, and well under that for small icons. Resize photos to roughly the width they are displayed at (1600 pixels is plenty for a full-width banner) and compress them with an online image compressor or your image editor's export-for-web option. WebP and well-compressed JPEG both work. Finipage does not crop or compress images, but once you have a smaller version you can swap it in by dragging the file onto the old image.
Alt text. Every meaningful image should have an alt attribute that says what it shows, for example alt="Team of four at the Seoul office". Screen readers read it out, and it appears if the image fails to load. Purely decorative images can use an empty alt="". Alt text is added in a text editor.
Broken images. If an image shows on your computer but not online, the path is usually the problem. See why images don't show in an HTML file.

Mobile and browsers

Phones first. For a small business page shared through messengers and social media, phone visitors are often the majority. Check text size, button size and sideways scrolling, as covered in how to check your page on mobile. Finipage's 390px and 768px preview widths are a fast first pass.
Several browsers. Open the page in Chrome, Safari (on an iPhone if you can), Edge and Firefox. In Korea, add Samsung Internet. You are looking for fonts that fall back to something unexpected, layouts that collapse, and sticky headers that cover content.

Forms and legal pages

Forms need somewhere to send data. An HTML form on its own does not deliver anything. It needs a server or a form-handling service behind its action address. Finipage does not process form submissions, so if your template has a contact form, connect it to a form service or replace it with a clear email address and phone number. Submit a test entry and confirm it arrives. Contact forms on a static HTML page compares the ways to receive submissions.
Privacy policy. If you collect names, emails or phone numbers, most countries expect you to say what you collect, why, and how long you keep it. In Korea the Personal Information Protection Act requires a published privacy policy. Link it from the footer and next to the form.
Business information. Some countries require online sellers to show their registered business details. In Korea, the Act on the Consumer Protection in Electronic Commerce asks for items such as the business name, representative, business registration number and mail-order business report number. Check what applies to you.

If your template includes a login form, remove it before the page goes live. A one-page site has no account system behind it, so the form does nothing, and a password field on an unfamiliar page can look like phishing to visitors. On a page served without HTTPS, browsers also flag password fields as not secure.

When everything above is ticked, the next step is putting the HTML file online, and later connecting your own domain.

Want to try it on your own file? Open the Finipage editor. It runs in your browser and your file stays on your device.