AI app builders make it easy to launch a good-looking site in an afternoon. What they don't always produce is a site search engines can read properly. Weeks later, the site still doesn't show up for its own name, or only the home page is indexed, and nobody knows why.
The causes are usually technical, not about keywords or content, and they're fixable. Here are the ones that come up most, roughly in order of how much damage they do.
Content that only exists after JavaScript runs
Many AI-built sites are single-page apps. The server sends an almost empty HTML file and JavaScript builds the page in the browser. Google can render JavaScript, but it does so in a separate, delayed step, and errors or slow scripts can leave pages half-read. Many other crawlers, including social media link previews and some AI search tools, don't run JavaScript at all and see a blank page.
Check by viewing the page source (not the inspector) on a key page. If your headline and main text aren't in that HTML, crawlers that don't run JavaScript can't see them.
The fix is to render pages on the server or generate them at build time. Frameworks such as Next.js, Astro or Remix do this by default. For a small marketing site, moving it to one of them is often simpler than patching a single-page app.
The same title and description on every page
A common pattern: one title tag set in the main HTML file, shared by every route. Search engines then see dozens of pages that all claim to be the home page.
- Give every page its own title, under about 60 characters, that says what the page is about.
- Write a unique meta description for each important page. It doesn't affect ranking directly, but it's often the text shown in results.
- Use one h1 per page that matches the page's topic.
- Add Open Graph tags so links shared on social media and in chat apps show the right title and image.
No sitemap, or a wrong one
A sitemap lists the pages you want indexed. AI-built sites often have none, or one that lists localhost or preview URLs because it was generated during development.
- Serve a sitemap at /sitemap.xml with the full production URL of every public page.
- Generate it from your routes or content so new pages are added automatically.
- Reference it in robots.txt and submit it in Google Search Console.
- Leave out login pages, dashboards, thank-you pages and anything behind auth.
A noindex tag or robots rule left from development
Preview environments are often set to stay out of search results, which is right. The problem is when that setting ships to production. One line in robots.txt, a meta robots tag or an HTTP header can quietly keep the whole site out of Google.
# robots.txt that blocks everything: fine on staging, fatal in production
User-agent: *
Disallow: /Search Console's URL Inspection tool tells you whether a page is allowed to be indexed and, if not, exactly why.
Duplicate versions of the same site
If your site loads at both www and the bare domain, or at both http and https, search engines may treat them as separate copies. The same happens with a preview domain that's publicly reachable.
- Pick one canonical domain and permanently redirect (301 or 308) every other version to it.
- Add a canonical link tag on each page pointing at its preferred URL.
- Keep preview and staging domains out of the index.
Links search engines can't follow
Generated code sometimes navigates with a click handler on a div or button instead of a real link. Visitors can click it, but crawlers follow href attributes, so the pages behind those buttons may never be discovered. Use proper anchor tags for navigation, which your framework's link component does for you.
Pages that say "not found" with a 200 status
In a single-page app, a missing page often shows a "not found" message while the server still returns a 200 OK status. Search engines call these soft 404s and may index junk URLs. Return a real 404 status for pages that don't exist.
Slow, heavy pages
Speed affects both rankings and whether visitors stay. Large images, big JavaScript bundles and slow servers are common in AI-built sites. Our guide to Core Web Vitals covers what to measure and fix.
Then give it time
After fixing these, request indexing for your key pages in Search Console and watch the Pages report. New sites often take days to weeks to be crawled and indexed, so steady progress there is the signal to look for, not instant rankings.
Deeraf's Tech Check covers technical SEO, speed and conversion on your key pages, and the fixes can be done in a fixed-price Build Sprint.