SEO for Non-Coders Who Vibe-Code Apps

Most AI-built apps ship as a blank page to a search engine. What that means, how to check whether yours does, and the small set of fixes that decide whether you are findable at all.

By · · 12 min read

Illustration for SEO for Non-Coders Who Vibe-Code Apps

There is a specific disappointment that arrives a few weeks after launching an app you vibe-coded: you search for it, and it is not there. Not ranked badly. Absent.

Usually that is not a ranking problem, and no amount of keyword advice will touch it. It is that search engines received a blank page, because of how apps built this way are put together.

The Launch Readiness Checklist, which covers the technical groundwork this post explains alongside the security and performance items
The Launch Readiness Checklist, which covers the technical groundwork this post explains alongside the security and performance items

Why your app might be invisible

AI builders produce what is called a single-page app. The file a visitor's browser downloads first is nearly empty, something close to an empty div, and the text appears a moment later once JavaScript runs and fetches your content.

People never notice, because it happens in a few hundred milliseconds.

Search engines are a different matter. Google can run JavaScript, but it does so in a second pass that may come days later and is not guaranteed. Other engines and most AI assistants do far less, and some read only the initial file. If that file is empty, what gets stored is an empty page.

Here is how to check yours, without any tools. Open your site, right-click and choose View Page Source. That shows the file as delivered, before JavaScript runs. If you can find your headline and your actual sentences in there, you are fine. If you see a short file with some script tags and no readable content, that is what a search engine receives too.

The fix, and why it is a platform decision

What you need is for the server to send finished HTML. The two common approaches are server-side rendering, which builds each page when requested, and prerendering, which builds the pages ahead of time and serves them as files.

For a mostly static site such as a landing page, a blog or a catalogue of tools, prerendering is simpler and faster, because the page is already sitting there as a file.

This is the one item in this post you may not be able to solve by prompting, because it depends on what your platform supports. It is worth finding out early. A beautiful app that search engines cannot read will only ever grow through links you place yourself, which is a much harder business than being found.

If your platform genuinely cannot do it, the usual workaround is to put your marketing pages and blog on something that can, and keep the app itself on the platform. Search engines only need to read the pages you want found.

The four tags that matter

Once your content is actually in the HTML, a small set of tags does most of the remaining work. AI builders typically write one set for the whole site and leave every page identical, which is nearly as bad as having none, because it makes your pages indistinguishable.

Title. The clickable line in results. Roughly 60 characters, different on every page, leading with the words someone would actually type. Not your brand name first.

Meta description. The grey text underneath, around 150 characters. It does not affect ranking directly, but it decides whether anyone clicks.

Canonical. Tells search engines which address is the real one when a page can be reached several ways. The usual silent problem: your site answers on both example.com and www.example.com, and they are treated as two competing copies.

One H1 per page, saying what the page is. Generated apps often have several, or none, because headings get used for styling.

The test is quick: visit three different pages and compare their titles in the browser tab. Identical titles mean you have one page as far as a search engine is concerned.

Telling search engines what exists

Two files, both of which an AI builder can generate.

A sitemap is a list of every address you want found. Submit it once in Google Search Console and it tells engines what to look for rather than leaving them to discover it by following links.

A robots.txt says what crawlers may fetch. The failure to know about is a line that blocks everything, which gets left behind after a staging site goes live. If your pages vanish from search suddenly, check this file first, because it is a one-line mistake that removes an entire site.

While you are there, set up Search Console itself. It is free, and it is the only place that tells you what search engines actually think of your site: which pages they stored, which they refused and why. That last part turns "we are not showing up" into a specific, fixable reason.

What actually gets you found

The technical groundwork gets you eligible. It does not get you traffic. Being honest about that saves months.

Pages rank when they answer a question better than the pages already answering it. For an app, that generally means written pages around the app rather than the app screen itself: explaining the problem your app solves, the comparisons people search before choosing, the specific questions your customers email you.

One good page beats twenty thin ones, consistently and by a wide margin. The twenty-thin-pages approach is what AI content generators make easy, which is precisely why it no longer works.

Give each page a stable, readable address. /invoice-generator will still make sense in two years; /page-12 never did.

The order to do this in

  1. View source on your home page. If your text is not there, solve that first; nothing else matters until it is.
  2. Give every page its own title and description.
  3. Check your canonical, and pick one of www or non-www.
  4. Generate a sitemap and check robots.txt is not blocking you.
  5. Set up Search Console and read what it says about your pages.
  6. Only then write content, and write fewer, better pages.

Steps one through five are an afternoon and are mostly permanent. Step six is the ongoing work, and it is the part that actually produces visitors.

Frequently asked questions

Why does my app not appear in Google at all?

Most often because the HTML sent to the crawler contains no content, which is normal for a single-page app. Right-click your page, choose View Page Source, and look for your own sentences. If they are missing, search engines received an empty page and stored one.

Does Google run JavaScript on my site?

It can, in a second pass that may be delayed by days and is not guaranteed for every page. Other search engines and most AI assistants do much less. Relying on that pass means accepting slower indexing and poorer coverage than sending finished HTML.

What is the difference between prerendering and server-side rendering?

Prerendering builds each page ahead of time and serves it as a ready file, which suits content that changes rarely. Server-side rendering builds the page when it is requested, which suits content that is personalised or changes constantly. Both send real HTML, which is the part that matters here.

Do meta descriptions improve my ranking?

Not directly. They are the text shown under your title in results, so they influence whether someone clicks rather than where you appear. A clear, specific description is still worth writing, because clicks are the point of ranking at all.

How many pages should I write?

Fewer than you think, and better. One page that genuinely answers a question will outperform twenty shallow pages on related terms, and thin pages can hold back the whole site. Write for questions your actual users ask rather than for a keyword list.

Sources and further reading

Browse all tools