What to set up after your AI agent builds your website

Your AI agent built the pages. You’ve opened the preview, adjusted the heading, and connected your domain.

Before sharing the site, go through the actions a visitor can take. Click the buttons, submit the forms, and check where the data ends up.

A finished-looking website can still have a contact form that only shows a success message locally, or a newsletter field that saves nothing. Those are the parts to verify next.

Choose one main action

What do you want someone to do after visiting?

For a product you haven’t launched, that may be joining a waiting list. For a service business, it may be sending an inquiry. A publication may need a newsletter signup.

Choose the main action before adding features. Make it visible on the page and explain what visitors get by taking it.

If you’re collecting interest before launch, follow the waiting list guide. The same setup applies beyond Lovable: use the script snippet on a regular site or the hosted URL where an embed is easier.

Connect forms to stored data

Submit every form using details you control. Check the stored record, not just the browser’s success message.

Then submit an invalid email, leave a required field empty, and try again with the connection disabled. Visitors need useful errors and a way to retry.

If the agent built a form without a backend, decide whether to finish that backend or use a hosted form service. Sitebase provides contact forms, newsletter signup, and custom forms with submissions managed in the dashboard.

Sitebase is currently in private beta. You can join the waiting list for access updates. Existing beta users can enable these features from their site’s sidebar.

Protect public submission flows

Configure spam protection before sharing a form widely. For Sitebase forms, enable Cloudflare Turnstile and replace the default test keys with real keys for the public domain.

Test on the domain visitors will use. Preview environments and production can have different script policies and domain settings.

Keep private credentials on the server. Public embed keys belong in browser HTML, but email-service secrets and private API tokens don’t.

Check what you’re promising subscribers

Tell people what email they’re signing up for. A launch announcement and a weekly newsletter are different expectations.

If you use double opt-in, test the whole confirmation flow. Submit an address you control, open the confirmation email, follow the link, and check the subscriber’s status.

Know how you’ll export the list and handle unsubscribe requests before sending your first campaign. Sitebase’s newsletter signup documentation covers its capture options.

Install analytics and verify it

Start with pageviews and traffic sources. You need enough information to tell which pages people visit and how they find you.

Place the tracker in the shared layout, visit the published site, and confirm that those pageviews reach the report. If the site uses client-side navigation, test clicks between pages as well as direct page loads.

The Claude Code analytics guide includes an installation prompt you can give your agent. You can adapt it to the agent you’re using.

Add custom events when you have a question that pageviews can’t answer. For a waiting list, that might be whether visitors who reach the signup section finish the form.

Add customer evidence when you have it

If customers have used your product, ask what changed for them. Publish specific quotes with their permission.

Sitebase’s testimonials feature lets you collect quotes and approve them before display. Follow the testimonials guide to test both sides of that flow.

If you don’t have customers yet, explain the product with an honest demo and clear examples. You can add testimonials when real feedback arrives.

Review privacy and availability

Write a privacy notice that reflects the services and data your site uses. Check the requirements that apply to your audience and location, and get qualified advice when needed. Adding a banner alone doesn’t establish compliance.

If downtime would stop inquiries or purchases, set up uptime monitoring. Make sure someone receives and can act on its alerts. Sitebase has a status page and monitoring feature for that workflow.

Make one final pass on the public URL

Open your site in a fresh browser window at a phone-sized width. Start on the homepage and complete the main visitor action.

Check the destination page, validation messages, stored data, and any confirmation email. Read your success message again: does it describe what happened?

Give your AI agent any failures as concrete tasks. “The contact form says sent while offline” gives it something testable to fix. After the change, repeat that flow on the published site.