UrgisoftAI-built apps

AI-built apps ยท November 2026

Fix Lovable SEO: why Google does not show your Lovable app, and seven fixes

Short answer: first find out what search engines really see. A Lovable app can be missing from Google for plain reasons (it is not public, Google was never told about it, every page carries the same title) or for a deeper one: an older Lovable app is a page that builds itself in the visitor's browser, and a reader that does not run that code gets an almost empty page. Four free checks, about ten minutes, tell you which it is. Being listed is the part you can fix; how high you rank is a separate, slower question.

Four checks: what do search engines see?

Do these on the live address people visit, not inside the builder.

  1. Ask Google what it has. Search for site:yourdomain.com. No results: Google has not listed the site at all. Only the home page: it has not found, or not kept, the other pages. Every result with the same title: see cause 3 below.
  2. Read the page the way a simple reader does. Open the live address and press Ctrl+U ("View page source"). Search that text for a sentence you can see on the page. If the sentence is not there and the body is little more than <div id="root"></div>, the words are added later by code in the browser. Do this for an inner page too, not just the home page.
  3. Look through Google's own eyes. In Google Search Console (free), paste a page's address into the box at the top. It says whether the page is on Google and, if not, why. "Test live URL" then shows the page as Google fetched it: check that your text and your own title are in it.
  4. Ask for a page that does not exist. Open yourdomain.com/this-page-does-not-exist, press F12, open the Network tab and reload. The first line shows a number. 404 is right. 200 with a "not found" message on the screen is cause 6.

Seven causes, and the fix for each

  1. The app is not public. Lovable's own page on search says only publicly published apps can appear in results; an unpublished project, or one whose access is limited to chosen people, never does.
    Fix: publish it and open its access to everyone. A page behind a sign-in screen is not listed either: search engines do not log in. Put what should be found (the home page, prices, the help pages) outside the login.
  2. Google was never told the site exists. A new address with no links pointing to it can wait a long time to be found. Lovable's page says a new project gets a robots.txt file but not always a sitemap, the list of your pages that search engines read.
    Fix: open yourdomain.com/sitemap.xml. If nothing is there, ask Lovable to create one that lists every public page with its full address, then add the site to Search Console and submit the sitemap there. Lovable can connect Search Console for you from its chat. Check yourdomain.com/robots.txt too: a line Disallow: / shuts every search engine out.
  3. Every page has the same title and description. Lovable says the starting title and description of a project are generic. If nobody changed them, every page tells Google the same thing, and Google's guide asks for a unique, descriptive title and description on each page.
    Fix: give each important page its own title (what the page is, then your name) and its own one-sentence description. Also give each page its own share title, text and picture, or every link shared on LinkedIn, WhatsApp or Slack shows the same card: Lovable notes that most of those preview readers do not run a page's code.
  4. The page is empty until its code runs (older Lovable apps). Check 2 shows this. Lovable says apps created from May 13, 2026 are built so the server sends the finished page. Older ones (React + Vite) are single-page apps: on Lovable's hosting, search engines and AI search readers that Lovable has verified are handed a ready-made copy, and every other reader gets the bare app. Google does run a page's code, but as a separate, later step that can sit in a queue, and its guide warns that not every reader on the web runs code at all.
    Fix: Lovable offers an upgrade of an existing project to the newer setup; by its own description the live site does not change until you publish again, so test the upgraded app before you do. If you would rather not upgrade, make sure at least the title, description and main heading of each page are right in what Search Console shows (check 3).
  5. You moved the app to another host. Lovable's page promises the ready-made copy for projects on Lovable's hosting. The same older app on Vercel, Netlify or your own server is a plain single-page app there unless you add that step yourself.
    Fix: add pre-rendering to the build (each public page is saved as finished HTML when the app is built) or move the public pages to a setup that renders on the server. Google's guide calls both a good idea for visitors and for search engines, and calls serving a special copy only to search engines a workaround, not a long-term answer. Moving a Lovable app to Vercel or Netlify: the steps, and six errors that stop it.
  6. Missing pages answer "200 OK", or addresses use a #. In a single-page app the server sends the same file for every address, so a mistyped or deleted page still answers as a real page (check 4). Google calls this a soft 404, and it fills the index with empty pages. Addresses like yourdomain.com/#/pricing are a second trap: Google's guide says to use real paths, not the part after a #, to load different pages.
    Fix: Google gives two ways for the not-found screen: send the visitor on to an address where the server really answers 404, or have the not-found screen add <meta name="robots" content="noindex">. And use normal paths (/pricing) for pages.
  7. Two addresses, or a tag that points the wrong way. If the app answers on more than one address, search engines have to guess which is the real one. And one wrong line in the page's head can tell them to skip a page: a leftover noindex, or a canonical tag (the line that names a page's one true address) that names the home page on every page.
    Fix: connect your own domain in Lovable and set it as the primary domain; Lovable says other connected domains then redirect to it. In the page source (check 2) search for noindex and for canonical: there should be no noindex on a page you want found, and each page's canonical should be its own address. Google's guide says the canonical is best set in the page's HTML, not changed later by code.

What Lovable can fix for you, and what it cannot

Lovable has a built-in check, included on all plans by its own page: in Analytics, the SEO & AI tab, "Run SEO scan". It looks at the sitemap, robots.txt, titles and descriptions, structured data, page structure, picture descriptions, canonical tags and indexing, and offers "Try to fix" for most findings. Run it first; it is the cheapest step on this page.

What it cannot do: make a new site rank. After the fixes, ask Google to index your most important pages in Search Console, and give it time: listing can take days or weeks (one of our own new pages was listed a day after we asked, others were still waiting), and ranking for a busy search takes much longer and needs pages worth finding. Speed counts as well: why a Lovable or Bolt app is slow on phones, with our demo shop measured before and after.

Before you ask the AI to "fix the SEO"

  1. Name the cause, not the wish. "Fix my SEO" makes the AI guess, and it tends to add tags without checking what was wrong. "Every page has the same title; give each of these pages its own title and description" tells it what to do.
  2. Check the result on the live address. Publish, then repeat checks 2 and 3. A title that changes only after the page's code runs may still be missing for readers that do not run code.
  3. Change one thing at a time and note the date. Search Console's numbers arrive a couple of days late; if you change five things in one day you will not know which one helped.

Sources, read November 22, 2026: Lovable's documentation on search (docs.lovable.dev/features/seo) for what Lovable builds, serves to verified readers, checks and fixes; Google Search Central's JavaScript SEO basics and dynamic rendering pages for how Google reads pages built by code. Both change; check them for your own case. This is a checklist from engineering practice, not a study: we have not counted how often each cause happens in Lovable apps, and nobody can promise a ranking. Other pages on this site: not sure what is broken? A ten-minute check. A blank page after publishing. Login and Supabase errors. Six security checks. Stripe payments not working. Lovable to WordPress. Convert a Lovable app to iOS. Urgisoft is not affiliated with Lovable, Google, Vercel or Netlify.

Want it fixed for you?

We fix the technical side in your Lovable app's own code: titles and descriptions per page, the sitemap, missing pages that answer as real ones, the wrong tag in the head, and pre-rendering when the app lives on another host. Then we show you the page a search engine receives, before and after. We do not promise rankings; nobody honestly can. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from $150. No fix, no charge. We work through GitHub or as a collaborator you invite; we never ask for your password, and we ask you to replace any key we could see once the work is done.

See the gig on Fiverr