SEO on AI-built sites
A site the Studio builds for you is real code, and every page a visitor is served carries a real head: canonical, social cards, robots, pixels. Here is what is in it, how the share image is chosen, and the two limits worth knowing.
What every built page carries
Every built page a visitor is served gets a full head: a canonical for its own address, og and Twitter card tags so links preview as cards in Slack, iMessage, and X, the favicon set, a robots line, your tracking pixels, and any custom head code you pasted in settings.
The robots line follows publish state: index on a published site, noindex on a draft. So a draft is reachable at its address but tells search engines not to list it, and publishing is what opens the door.
The build's own tags always win. Whatever a page already declares, its title, its description, an og:image it set itself, is left exactly as written and never doubled. The platform fills gaps; it does not overrule your site.
How the share image is chosen
When a link to a built page is shared, the preview image falls back in order: the page's own og:image if it set one, else the site's OG image, else the logo. The favicon is never used as a share image.
A site with no image anywhere in that chain shares as a bare title and link. The fix is one setting: give the site an OG image, or at least a logo, and every shared link starts previewing as a card.
The sitemap
The live sitemap at /sitemap.xml lists one URL per page the build wrote, read from the built site itself. Search engines get the real map of your pages with nothing to configure.
Two honest limits
First: sites generated before 2026-08-16 share one title across all their pages, because those older projects were generated without per-page names in their route list. Rebuilding does not fix this; only generating the site again does, since a fresh generation rewrites the files that carry the titles. Sites generated from now on title each page after its own name.
Second: the description is per-site rather than per-page on built sites, even on new builds. Every page of a built site carries the site description, so write that one description to represent the whole business.
When it does not work
Shared links show no image: nothing in the fallback chain exists yet. Set a site OG image and share the link again. Some chat apps cache previews, so a fresh paste may take a moment to update.
Every page shows the same title in search: the site was generated before 2026-08-16. Ask for the site to be generated again; a rebuild alone will not change it.
You expected a different description on each page: on a built site the description is per-site by design. Make the one description count.
Pages carry noindex: the site is in draft. Publish it and the robots line flips to index.
You changed a head setting and the live page has not moved: a fresh build can take up to a minute to reach every visitor, because the edge serves the previous version that long. Reload after a minute before treating it as a failure.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.