Editor Basics

Landingsite is an AI-powered website builder. Instead of dragging and dropping elements or editing code, you tell the AI what you want and it builds your site for you.

How the AI Editor Works

The editor uses a chat-based interface on the right side of the screen. You type instructions in the chat box, and the AI makes changes to your website in real time. There is no left-side editing panel — the AI chat is the primary way you edit your site.

Two Ways to Edit: Chat and Inline Text

The AI chat is the main way to edit your site. For quick text changes, you can also edit text directly on the page: click the text edit button in the editor toolbar, then click the text you want to change and type the new text.

For anything beyond text — images, buttons, layout, new sections, or styling — describe the change in the AI chat.

There is also no separate Assets, Media, or Files sidebar in the current AI editor. To upload a logo or other image, use the chat composer on the right: click the attachment button next to the message box or drag the file into the chat, then tell the AI where to place it.

If you need the current logo file from a site that is already live, open the public page in a normal browser tab, right-click the logo, and save the image. If right-click does not download the file cleanly, open the logo image in a new tab first and save it from there.

For logos, a PNG is usually the easiest format to work with, especially if you want a transparent background. A practical starting size is roughly 250 to 500 pixels wide. If an upload gives you trouble, try a smaller file size (for example, under 2 MB).

If app.landingsite.ai opens but the sign-in screen never gets past a loading state, the problem is often something on your device or network blocking Landingsite’s secure login service rather than a problem with your website itself.

Common causes include:

VPN security features or web protection tools
antivirus or HTTPS-inspection software
browser privacy/security extensions
company or school network filters

Try these checks in order:

Temporarily disable VPN filtering, threat protection, or web-shield features and reload the page.
If you use a VPN, test both with it fully off and fully on.
Open https://clerk.landingsite.ai directly in your browser. If that page will not load, something on the device or network is blocking the login service.
Try a different network or device, such as your phone on mobile data.

If sign-in works on another device or network, ask your IT team or security software to allow clerk.landingsite.ai.

Important: Landingsite can use an attached logo as a reference, but it does not currently have a separate logo-only editing workflow where you can open one existing logo and generate controlled variations of that exact file inside the editor. If you need several close variations, the most reliable workflow today is either:

ask the AI to generate a fresh logo using very specific instructions and your current logo attached as a reference, or
create the variations in a dedicated image tool first, then upload the final logo into Landingsite

Logo looks white, missing, or the wrong color

If your logo looks fine in one place but shows up white, washed out, or the wrong color in the header or footer, the issue is often a theme/style rule rather than the uploaded image file itself.

Try this first:

Ask the AI to remove any styling or CSS classes that are forcing the logo to appear white or recolored.
Refresh the preview and check the header/footer again.
If it still looks wrong, download the logo image you want to use, attach that exact file in the AI chat, and ask the AI to use this uploaded file as the logo everywhere on the site.
Publish again after the logo looks correct in preview.

Changing the dashboard thumbnail

If the website itself is live but the thumbnail card in your dashboard looks broken, outdated, or shows the wrong image, you can usually change it yourself:

Go back to your dashboard.
Find the website card.
Click the three-dot menu on that card.
Choose Change thumbnail.
Pick the image you want the dashboard to use.

If you already changed the thumbnail and the dashboard card still looks wrong afterward, refresh the dashboard first. If the live website is correct but the dashboard thumbnail still will not update, contact support with the website URL and a screenshot of the card.

Instead, tell the AI exactly what you want changed in the chat. For example:

change the headline at the top to "Serving Denver homeowners since 2008"
replace the hero image with a photo of a modern kitchen
update the About section to mention we are family-owned

After the AI makes the change, review the preview and publish again if you want that update to go live.

What You Can Ask the AI to Do

Write or rewrite text on any section of your page
Change colors, fonts, and layout styles
Add new sections (hero, features, testimonials, pricing, etc.)
Add images — upload your own or let the AI find one for you
Add social media icons with links (e.g., “Add a Facebook icon linking to my page”)
Add embed codes for third-party widgets or tools
Add or remove pages (on the Pro plan)
Add DNS records like TXT records for domain verification (e.g., Google Search Console)
Create, inspect, disable, or replace promo codes for products you sell through a connected Stripe account (React websites).
Send invoices and recurring invoices to your clients, with automatic reminders (React websites, Pro plan, connected Stripe account).
Answer questions about your website traffic, such as “where did my visitors come from last week?” (React websites). See Website Analytics.

About Advanced Edit

You make all changes to your site through the AI chat.

To undo a change, ask the AI to reverse it, or use the Versions tab to restore an older saved version of the site.

If the Versions tab says there are no saved versions yet, that usually means the website has not recorded any AI-chat edits into version history yet. After you make changes through the AI chat, new saved versions should start appearing there.

Restoring an older version does not refund credits from earlier AI edits.

If you need something highly specific, describe the change in the chat as clearly as possible and review the result before publishing.

Legacy (HTML) Sites

As of May 19, 2026, all new Landingsite websites are built with the React builder described throughout this documentation. Sites created before then are legacy HTML sites that use an older editor and can look or behave differently. Some accounts contain a mix of both, so the editor may differ from site to site.

This documentation describes the React builder by default. Anything that only applies to older sites is called out in a Legacy (HTML) sites note like the one below.

Tips for Getting Good Results

Be specific. Instead of “make it look better,” try “change the hero background to dark blue and make the heading white.”
Describe the kind of change you want. If you want a more professional redesign, mention the layout, spacing, typography, button style, color palette, and tone you want the AI to aim for.
One change at a time. The AI handles focused requests more accurately than long lists of changes.
Start with a broad design direction, then follow up with smaller requests. A good pattern is to first ask for the overall redesign, then separately ask for a stronger hero section, better spacing, new testimonials, cleaner mobile layout, or other focused improvements.
Expect a separate mobile cleanup pass after larger redesigns. Landingsite sites are responsive by default, but bigger visual changes can still leave mobile details needing follow-up — especially navigation menus, spacing, alignment, and button layout on smaller screens.
Ask for mobile fixes one at a time. Requests like clean up the mobile navigation menu, tighten the mobile spacing, or make the buttons fit better on phones usually work better than a long mixed desktop/mobile request.
Break long prompt documents into parts. If you have a long brief, start with your brand/style rules and overall page structure first, then send each section in priority order instead of pasting everything at once.
Use exact text for tiny corrections. For spelling, accents, or punctuation changes, paste the exact old text and exact new text you want. For example: change every instance of "Jedah" to "Jëdah" exactly.
Review as you go. After each edit, check the preview to make sure it looks the way you want before moving on.

Example prompt for a bigger visual refresh:

Redesign this website to look more modern and professional for my industry. Use a cleaner layout, better spacing, stronger headings, consistent button styling, and a more polished color palette. Keep the branding focused on trust and professionalism.

If the AI says it made a text change but you still see the old version, refresh the preview and publish again if needed.

Settings Fields vs Visible Page Content

Some settings fields give the AI background context, but they do not always rewrite the visible text on your live page by themselves.

For example, updating your business description in the AI Project Instructions field helps guide the AI, but it will not necessarily replace the text visitors see in your About section or update your page SEO automatically.

On React websites, the page name shown in the page dropdown also follows that page’s meta title. There is not a separate manual page-name field in the current editor, so if you want the page label to change, ask the AI to update that page’s title/meta title.

If you want the live page content to change, ask the AI editor to update that exact section, then publish again.

Global Header and Footer Content

Many themes use a shared header and shared footer across the whole website. If you edit something inside that shared area — like a phone number, navigation link, or button — the change usually applies to every page that uses that same header or footer.

That means you generally cannot keep one phone number in the global header on most pages and a different phone number in that same global header on just one page.

If you need page-specific contact details, the practical options are:

keep the shared header/footer content the same site-wide, then add a separate text block, button, or call-to-action on the specific page that needs a different number, or
remove the number from the shared header/footer entirely and place page-specific contact info directly inside each page instead

A useful AI prompt is:

keep the global header phone number unchanged, but add this different phone number to the Apply Now page only as a separate button or text block near the top of the page

Favicons on Newer Site Layouts

Some websites do not show the same older Settings → Branding path for favicon management.

If you do see a visible favicon or site-icon field in settings, you can use that and then publish again.

If you do not see that field, the practical fallback is:

Create or prepare your favicon image (a small square PNG usually works best).
Attach that image in the AI chat.
Ask the AI to use this image as the favicon.
Publish the site again.

If the favicon is still missing on the live site after publishing, check the live site in an incognito window first before assuming the upload failed.

Publishing Your Website

Your edits are saved automatically, but your website is not live until you publish it. There are two ways to publish:

Click the Launch button at the top right of the editor.
Click the blue “Yes, continue” button when the AI chat prompts you to publish.

Until you publish, your site is only visible to you in the editor. After publishing, anyone with your domain or subdomain URL can see it.

If the publish confirmation button seems stuck but your public site is already loading normally, the publish may have gone through anyway. Fully close and reopen the browser or app, then sign in again and check the live site in a normal browser tab.

Can I Build Before Paying?

Yes. You can build and preview a website before paying.

You only need a paid plan when you want to publish the site to a custom domain. Once a site is published, it becomes live and publicly accessible.

Adding Embeds and Third-Party Code

If you have embed code from another service (like a booking widget, video player, or chat tool), paste it into the AI chat and ask it to add it to your site. The AI will place it directly into the page for you.

Video, Sliders, and Interactive Widgets

Landingsite does not currently include native video file upload/hosting as a built-in editor feature. For videos, upload them to a service like YouTube or Vimeo first, then paste the embed code into the AI chat and ask the AI to place it on the page.

For sliders, carousels, before-and-after comparisons, and other interactive widgets, Landingsite does not currently have a dedicated built-in block for every use case. In those cases, use a third-party embed or custom script and place it with the AI.

Layout Flexibility

The AI can handle many custom layout requests, including things like:

Centered logos
Right-aligned navigation
Badges, reviews, or contact details placed in specific areas
Custom section arrangements

The more specific your prompt is, the better the result tends to be.

Uploading Your Own Images

You can upload your own images through the AI chat. Just attach or describe the image you want to use, and the AI will add it to your site. You are not limited to stock photos — use any images you have the rights to.

The most reliable workflow today is to upload the exact final image files you want placed on the website and tell the AI exactly where each one should go.

Important: if you want the website to use the real photos from your business, do not rely on the AI to pull them from Google, Google Reviews, Facebook, or another third-party listing automatically. In those cases, the AI may fall back to stock imagery or choose the wrong location entirely.

If an image upload is blocked by the automated content filter but the file is legitimate business content or artwork, contact support for a manual review. False positives can happen.

If image uploads fail with a network error

If the editor accepts the file selection but the upload fails with a generic network error, the issue is often outside the browser.

Landingsite first asks its API for a temporary upload URL, then your browser sends the file directly to Landingsite’s storage provider. If that second step is blocked, the upload will fail even though the editor itself is working normally.

Common causes include:

company or school firewalls
VPNs or antivirus tools that inspect HTTPS traffic
browser extensions or network filters blocking cloud storage domains

Try these checks:

Test one small image from a different device or network, such as your phone on mobile data.
Temporarily disable VPN filtering, antivirus web shields, or privacy extensions and try again.
If uploads work elsewhere but not on your normal machine or network, ask your IT team to allow r2.cloudflarestorage.com.

If the same files upload successfully from another network, you do not need to clean up partial uploads inside Landingsite. The failed transfer usually never reached storage in the first place.

For the most accurate result:

Save the exact photos you want to your computer.
Upload those files directly into the AI chat.
Tell the AI which section each photo should replace.

Important: uploaded images work best as assets to place on the site. The AI is less reliable when you ask it to treat an uploaded screenshot or photo as a broader reference for recreating a layout or for making precise asset swaps across a section. If you need a very exact result, break the work into smaller steps and attach the exact image that should replace each current image.

Collaboration Invites

If someone invites you to collaborate on a Landingsite website, you need to be logged into a Landingsite account that uses the same email address the invitation was sent to.

If you click the invite link and nothing happens:

Go to app.landingsite.ai.
Sign up for a free account with the invited email address, or log out and back in with that exact email.
Open the invitation link again.

If you normally sign in with Google, make sure you use Continue with Google for that same invited email address.

If the invitation has expired, was sent to the wrong email, or no longer opens correctly, the website owner needs to send a fresh invite from their Landingsite account. Support cannot manually re-open an old invite on your behalf.

What collaborators can and cannot do

Collaborators can still help edit the website, but some account-level actions require a higher role.

In practice:

Editors can usually build and change the website content
Owners or admins are the ones who can manage paid actions like buying a domain for that website

If checkout tells you to create a website, upgrade, or take some other step that does not match what you are already looking at, first confirm you are signed into the account that owns the website or has admin access to it.

Support and Feature Requests

Always send support questions, bug reports, and feature requests to support@landingsite.ai. See Support and Feature Requests for what to include.

Important Notes

Landingsite builds websites and landing pages with built-in services such as forms and payments. It is not a general-purpose backend or database builder for custom applications.
React websites support product sales through a connected Stripe account, including product management, shopping carts, and promo codes. Start with Start Selling for setup, shipping, orders, and subscriptions.
Built-in selling uses Stripe Checkout. Follow Start Selling to connect your merchant account and check payment readiness.