3Edit Web Builder iconVibe coding guide

SEO for vibe-coded websites

Help search engines find and understand your site.

Built your website with AI? A practical SEO checklist that works with any tool, from titles and sitemaps to what search engines see in your page source, and how 3Edit helps.

About 9 minutes to readLast updated

By Humayun Rashed, founder of 3Edit

Why AI-built sites often struggle in search

An AI agent can build a good-looking site in an afternoon, but looking good and being easy to find are different jobs. Search engines read your pages’ code and settings, which you may never see when you build by chatting.

The same few things come up again and again on AI-built sites, and none of them is hard to fix once you know to look:

  • Every page has the same title, or a placeholder left over from the first build, so search engines can’t tell the pages apart.
  • The words load late. Some sites send an almost empty page and fill it in with JavaScript, which makes search engines work harder to see the content.
  • Nobody told the search engines. There is no sitemap, and the site was never added to Google Search Console or Bing Webmaster Tools.
  • Addresses changed without a plan. The site moved from a temporary address to its own domain, or pages were renamed, without redirects.
  • Images arrive heavy and unlabelled, with no alt text and files far bigger than the screen needs.

The SEO checklist

These checks work with any tool. Each links to the official advice behind it.

CheckWhat to doOfficial advice
A unique title on every pageWrite a title for each page that describes that page, not the whole site.Google: title links
A unique description on every pageGive each page its own short summary of what is on it.Google: snippets
One clear H1Use one main heading per page, then smaller headings in order. Google says heading order doesn’t matter for Search, but a clear structure helps readers and screen readers.MDN: heading elements; Google: SEO starter guide
Readable addressesUse words, not long ID numbers, in your page addresses.Google: URL structure
A sitemapPublish a sitemap listing your pages, and submit it in Search Console and Bing Webmaster Tools.Google: sitemaps
A robots fileUse robots.txt to tell crawlers which addresses they may visit. To keep a page out of Google, use noindex instead: robots.txt isn’t meant for that.Google: robots.txt
Google Search ConsoleAdd and verify your site, submit your sitemap, and watch for problems.Google Search Console
Bing Webmaster ToolsAdd and verify your site for Bing too, and submit your sitemap there.Bing Webmaster Tools: getting started
Content in the page HTMLCheck your main words appear in the page source, not only after JavaScript runs. The next section shows how.Google: JavaScript SEO basics
Canonical addresses and your domainTell search engines the preferred address of each page, especially after you connect your own domain.Google: canonical URLs
Structured dataDescribe products, articles and FAQs with structured data, then test it in the Rich Results Test. It can help, but rich results are never guaranteed.Rich Results Test; Google: structured data policies; schema.org
A share pictureSet an og:image for each page, so it has a picture of its own when it is shared.The Open Graph protocol
Alt textDescribe each meaningful image in a few plain words.Google: image SEO
Image size and speedServe images no bigger than they are shown, then test the page in PageSpeed Insights and fix what it suggests.PageSpeed Insights; web.dev: images
A real 404 pageA page that doesn’t exist should answer with a 404 status, not a normal page that says “not found”.Google: soft 404s
Redirects when pages moveWhen you rename or move a page, redirect the old address to the new one with a permanent (301 or 308) server-side redirect.Google: redirects

See your page the way a search engine first does

Google processes JavaScript pages in three phases (crawling, rendering and indexing), and its JavaScript SEO guide says server-side rendering or pre-rendering is still a great idea. The easiest way to see what your server sends is a two-minute check:

  1. Open a page of your live site, right-click an empty part of the page and choose View page source.
  2. Use your browser’s Find to search the source for a sentence you can see on the page, such as a product name or a heading.
  3. If you find it, the words are in the page’s HTML. If you don’t, they load later with JavaScript, so ask your AI agent to render that content on the server.
  • Why View page source and not the Elements panel? Chrome’s DevTools docs explain that HTML is the initial page content, while the DOM in the Elements panel is the live, current content after scripts have run.

After launch: measure, then improve

SEO takes time, and nobody can promise a position: in Google’s own words, “No one can guarantee a #1 ranking on Google.” What you can do is make your site easy to find and understand, then keep an eye on it.

  • Check Search Console now and then for pages that aren’t indexed and for errors, and fix them one by one.
  • Retest speed in PageSpeed Insights after big changes, especially new images.
  • Redirect before you rename. Whenever you change an address, set up the permanent redirect at the same time.
  • Keep each new page complete: its own title, description, H1 and share picture, from the day it goes live.
  • Test before launch, too. See how to test a vibe-coded app before launch and the security basics.

How 3Edit helps with SEO

Click SEO in a Web Builder project to open the SEO & Media panel, with the tabs “Overview”, “Meta”, “Media”, “Identity” and “Ads”.

  • Meta, page by page. Each page has a “Page Title”, “Meta Description”, “OG Title”, “OG Description”, “Keywords”, “Canonical URL” and “Hide from Search Engines”, with a “Search Preview”, and “Fill with AI” drafts them for you.
  • Identity for the whole site. “Site Name”, “Tagline”, “Logo”, “Favicon”, a “Default Social Share Image” (1200×630 recommended), your social links, “Website Schema” with “Generate Schema”, and a “Google Search Console” verification field: “Paste only the content value from your Google verification meta tag.”
  • Media, image by image. Each image has “Alt Text”, “Title”, “Caption” and a “Loading Strategy” (lazy or eager), and “Generate SEO Fields with AI” fills them in.
  • Applied to your site. “Apply SEO to Site” writes your saved settings into the site, and publishing applies them automatically.
  • Store and blog starter kits. Every product and blog post has its own “SEO title” and “Meta description”. The product importer and the blog writer fill them in, and you can edit them. Blog posts also have “Canonical URL”, “Hide from search engines (noindex)” and “Image alt text”.
  • A sitemap and robots file. The starter kits include an automatic sitemap, split into parts for large stores, and a robots file that keeps admin and checkout pages out of search.
  • Structured data in the kits. Product data with price and availability, BlogPosting, BreadcrumbList on blog posts, and FAQPage when a post has FAQs. Product data never invents ratings or reviews.
  • Content on the server. Product pages and blog pages load their content on the server. The shop and category pages load their product lists in the browser.
  • Your own domain. With a custom domain connected, canonical addresses, sitemap links and social links use your domain, and 3Edit’s managed addresses redirect to it with a permanent 308 redirect.
  • Ads and analytics, with consent. The “Ads” tab sets up Google Tag Manager, Google Analytics (GA4), Google Ads and the Meta, TikTok, LinkedIn and X pixels, with a cookie banner (“Accept”, “Reject”, “Cookie settings”), so trackers load only after consent.
  • For stores. The ecommerce admin’s SEO page has Google and Meta site verification tags, product feeds for Google, Facebook and Instagram, and a blog RSS feed.
  • Yours to check. Add your site to Bing Webmaster Tools, test image sizes and speed in PageSpeed Insights, check your 404 page and redirects when pages move, and fill in the Meta tab for each new page an agent builds. Read more on the Web Builder page.

About the author.

Written by Humayun Rashed, founder of 3Edit. He also runs 3Edit’s free in-person AI website building and vibe coding course in London.

Questions people ask.

Yes, if the content is there to find. Google processes JavaScript pages in three phases, crawling, rendering and indexing, and still recommends server-side rendering or pre-rendering. Check that your main words appear in View page source.

It helps. A sitemap lists your pages so search engines can find them. Submit it in Google Search Console and in Bing Webmaster Tools.

One clear H1 per page is good practice: MDN advises using only one, and it helps readers and screen readers. Google says the number and order of headings doesn’t matter for Search, so focus on clear headings rather than rules.

Not necessarily. Google does not guarantee that structured data will show up in search results. Test your pages in the Rich Results Test, and use structured data that matches what is on the page.

No. robots.txt tells crawlers which addresses they may visit, but Google says it isn’t a way to keep a page out of Google. Use noindex for that.

3Edit gives you the tools: the SEO & Media panel for titles, descriptions, share images, alt text and site schema, and publishing applies your saved settings. The store and blog starter kits add sitemaps, a robots file and structured data. Nobody can guarantee rankings, so check the rest of this list too.

When you connect a custom domain, canonical addresses, sitemap links and social links use your domain, and 3Edit’s managed addresses redirect to it with a permanent 308 redirect.

Start vibe coding today.

Download 3Edit for Mac or Windows and build your first professional website in minutes.

Download now
macOSWindows