FREEFirst project with us? Your landing page design is on the house.See the offer

Process

You built your site with AI. Here is what is left

You built your marketing site with an AI tool. Here is what still needs doing before real visitors arrive, from redirects and forms to speed and ownership.

By Abdul QuadirUpdated 2026-10-267 min read
TL;DR
  • AI tools build pages quickly. The work around the pages often still needs doing before real visitors arrive.
  • Start by checking that Google can read your content, and add redirects if you are replacing an older site.
  • Test every form from a phone and confirm the lead reaches the place your team really reads.
  • Check speed on a real phone, plus accessibility, tracking, consent, security headers and private keys.
  • Make sure your team can edit the site, and name one owner for it after launch. Nobody can promise rankings.

The short answer

An AI tool can get you a good looking marketing site quickly, and that is useful. We use AI tools in our own work too. What it may not finish is the work around the pages: redirects from any old site, titles and meta, schema, sitemap and robots, tracking and consent, forms that really deliver leads, speed on a real phone, accessibility, editing without a developer, security headers and a clear owner after launch.

If your AI-built website is not ranking, start with one question: can Google read your content? Then work down this list. Google says appropriate use of AI is not against its guidelines, so the tool itself is rarely the issue.

Can search engines read your site?

Many generated sites are JavaScript apps. The first HTML can be nearly empty, with the content added in the browser. Google can usually handle this, because it runs JavaScript in a later rendering step. But its JavaScript SEO guide still recommends server-side rendering or pre-rendering, and notes that not all bots can run JavaScript.

  • Quick test. View the page source, not the inspector. Is your headline there as text?
  • See what Google sees. Use the URL Inspection tool in Search Console. It shows index status, and a live test shows a screenshot of the rendered page.
  • Sitemap. Add one listing only your real, final URLs, then submit it. Google says a sitemap helps discovery but does not guarantee indexing.
  • Robots and noindex. Make sure a setting from your preview stage did not go live. Google says robots.txt is not a way to keep a page out of Google. For that, use noindex or a password.

A new domain can also take time. Few links and little history are normal at the start, and no checklist changes that overnight.

Redirects from any old site

If you are replacing an older site, this comes first. Your old URLs may have links and rankings. If they turn into 404 pages, you lose that work. List every old URL, match each one to the closest new page, and add permanent redirects. Google treats a permanent redirect as a signal that the new page should be the canonical one.

A tool cannot add redirects for URLs it does not know about. Take the list from your old sitemap and Search Console. Our free redirect map tool turns that list into a file you can use. Brand new domain with no old site? Skip this one.

Titles, meta and schema

  • Titles. Each page needs its own title that says what the page is. Look out for one site name repeated everywhere, which can happen in JavaScript apps.
  • Meta descriptions. Write one per page. Google mostly builds snippets from the page content, and uses your description when it fits better, so the page text matters too.
  • One clear H1. Check headings run in order. Generated pages sometimes choose headings for their size.
  • Social images. Paste a link into a chat app and see what shows up.
  • Schema. Add markup for your organisation, FAQs and breadcrumbs where they fit. Google says it must be a true representation of the page, and it does not guarantee rich results. Read generated schema closely. Check any ratings, addresses or founders it lists against the facts.

Tracking and consent

Without tracking, you cannot tell which pages bring leads. Set up analytics, then define the events that matter, such as a form sent or a call booked. Trigger each one yourself and check that it arrives.

Consent comes with it. Rules differ by country, and this is not legal advice, so ask a lawyer about your own case. In practice, decide whether tags wait for consent, make Accept and Reject both easy to use, and test that the choice really changes what loads. Google's consent mode changes how its tags behave, but it does not save choices, so you still need your own banner or consent tool. Make sure your privacy page names the tools you really use. A generated privacy page may not.

Forms that really deliver leads

A form can show a success message and still lose the lead. This is the most expensive thing to get wrong, and the easiest to miss.

  • Test from a phone. Send a real message through every form, then find it where your team actually reads leads.
  • Keep a second copy. Notification emails can land in spam. Save leads to a sheet or CRM as well.
  • Check the failure path. If the send fails, the visitor should see that and have another way to reach you.
  • Stop spam on the server. Add a hidden trap field, a limit on requests and length limits on fields. Checks in the browser alone are easy to skip.
  • Escape what you store. If leads go to a spreadsheet, a submitted value can act as a formula unless you escape it.

On this site, our form route accepts same-site requests only, has a trap field, caps field length and limits requests per IP address.

Speed on a real phone, and accessibility

A site that feels instant on your laptop may be slow on a mid-range phone on mobile data. Test on a real one, and run PageSpeed Insights, which shows real-user data when there is enough of it, plus a lab test. The Core Web Vitals targets are LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less. Usual fixes: smaller images, less JavaScript, fewer outside scripts and fonts that load early.

For accessibility, WCAG is the standard to work towards. Start with what you can test today:

  • Use the whole site with only a keyboard. Can you reach every link and see where you are?
  • Check text contrast, including over images.
  • Give images useful alt text, and give every form field a label.
  • Try the reduced motion setting on any animation.

Automatic tools catch only part of this, so have a person test it too.

Editing without a developer

Ask this before launch: can your marketing team change a headline, publish a post or add a page without prompting a tool and hoping nothing else moves? If each edit means regenerating code, small changes get slow or risky, and someone has to check the whole page again.

A CMS fixes most of this. Blog posts, case studies and landing pages live as content, and your team fills in fields inside a design that stays put. Also check who holds the code, whether you can export it, and whether you can roll back a bad change.

Security headers and secrets

Automated scans look for easy targets, and small marketing sites count. Check these first:

  • Secrets. Search the code sent to the browser for private API keys. Anything there is public. Move it to the server and replace the key.
  • Data access. If the tool added a database, confirm a stranger cannot read your leads.
  • Headers. Add a Content-Security-Policy, which mainly helps against cross-site scripting, along with Strict-Transport-Security. Use frame-ancestors to stop other sites framing yours, unless you need that.
  • Dependencies. Generated projects can pull in many packages. Keep them updated, and remove what you do not use.

Test headers after you add them, because a strict policy can block your own analytics or embeds.

Who owns it after launch

This is the gap that shows up last. A site is a running thing. Forms break when a key expires, tracking drifts, a package needs a patch and your offer changes. Put a name next to each of these:

  • Domain, DNS and hosting logins, held in company accounts
  • Lead delivery, checked on a schedule
  • Analytics and consent
  • Search Console, and who reads it
  • Updates, backups and rollback
  • Who fixes it when it breaks on a Friday

That can be someone on your team or a partner. Our guide to website care plans helps you decide whether you need one.

What to do next

Go through the list in order, and fix what could lose you leads or traffic first: redirects, what Google can read, and forms. You may well keep the site you built. Our website launch checklist has the full run of checks, and our free tools cover redirects, AEO checks and cost.

Would you rather hand this part over? See our AI-built site rebuild service, or send us your site and we will tell you what we would fix first. We cannot promise rankings, and nobody honestly can.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Core Web Vitals, AEO

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Common causes are content that only appears after JavaScript runs, missing redirects from an old site, weak titles, a leftover noindex tag or a young domain with few links. Use the URL Inspection tool in Search Console to see what Google sees.

Yes. The tool is rarely the problem. Run the checks in this guide first: redirects, titles, schema, sitemap, tracking, forms, speed, accessibility, editing, security and ownership.

Often no. Many gaps can be fixed in place. A rebuild makes sense when the content only exists after JavaScript runs and cannot be changed, or when your team cannot edit the site without help.

Google says appropriate use of AI or automation is not against its guidelines, and that it rewards quality however content is made. Using AI mainly to manipulate rankings breaks its spam policies. Nobody can promise rankings.

Send a real message from a phone, on each form. Confirm it reached the place your team actually reads, then have someone other than you reply to it. Repeat after any change.

Name one person or partner. They own the domain, hosting, form delivery, tracking, updates and fixes. It can be someone on your team, a freelancer or an agency, as long as everyone knows who it is.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.