IQDeskLovable → WordPress Open the converter

Guide

Lovable Site Not Showing in Google: How to Fix It

If your Lovable site is not showing in Google, the cause is almost always one of four things: the pages have not been crawled yet, the live domain is not the one you published, the pages have no unique titles and descriptions, or a staging copy is blocking indexing. Start by searching site:yourdomain.com to see what Google already has. Then work down the checks below in order, from fastest to slowest. Most fixes take minutes; getting indexed afterwards takes days.

First, find out what Google actually has

Before changing anything, measure. Two checks tell you where you stand.

Search site:yourdomain.com in Google. If nothing comes back, no page of the site is indexed. If the homepage comes back but inner pages do not, crawling works and the problem is on the individual pages.

Then open Google Search Console, add the domain, and use the URL Inspection tool on your homepage. It tells you whether the URL is indexed, whether Google could fetch it, and what HTML Google received. That last part matters a lot for Lovable apps, as the next section explains.

A new site is simply not indexed yet. Google needs days to weeks after it first finds a domain. If the site went live this morning, there may be nothing to fix.

  • site: search — quick count of what is indexed right now.
  • URL Inspection — per-page verdict plus the rendered HTML Google saw.
  • Age — a domain live for under a week usually has nothing indexed yet.
  • Coverage report — look for pages marked as excluded and read the reason given.

Check what the crawler receives

Lovable apps built from 13 May 2026 use TanStack Start and are server-rendered. Every visitor and every crawler gets full HTML. If your app is one of these, rendering is not your problem.

Apps created before that date are React + Vite and render in the browser. On Lovable hosting, Lovable prerenders them on request for verified search engines, link-preview bots and AI crawlers. Google gets HTML; third-party SEO scanners see an empty app shell. So a scanner reporting "no content" is not proof that Google sees nothing.

The real risk is an older app moved off Lovable hosting. That prerendering is part of Lovable hosting. Host the same build on a plain static host and the HTML a crawler receives is an empty root element unless you add prerendering yourself.

Confirm with the Search Console URL Inspection tool: open the live test and look at the rendered HTML. If your headings and body copy are there, the crawler is fine. If it is an empty shell, read Is Lovable good for SEO? and Lovable hosting.

Check the domain and the published version

A surprising number of "not indexed" cases are the wrong URL being indexed, or none at all.

Make sure the domain you are searching for is the domain that serves the site. If you bought a custom domain but the live site still runs on the Lovable preview URL, Google will index that preview URL instead. Point the custom domain at the project and check it loads over HTTPS.

Pick one canonical host and redirect the rest. www.example.com and example.com should not both serve the site independently. The same goes for http:// and https://.

Publishing matters too. Changes made in the Lovable editor are not live until you publish. Open the live URL in a private window and confirm you see the current content, not an older version.

Submit a sitemap in Search Console if you have one, and use URL Inspection then Request Indexing on your most important pages. That nudges the queue; it does not guarantee anything.

  1. Open the live site in a private browsing window and confirm it is the current build.
  2. Check the address bar: is it the custom domain or the Lovable preview URL?
  3. Try the other variant (www or no www) and confirm it redirects rather than serving a second copy.
  4. In Search Console, confirm the property matches the domain you expect to rank.
  5. Request indexing for the homepage and two or three key pages.

Check titles, descriptions and thin pages

Google indexes pages it can tell apart. If every route shares one title from index.html, your pages compete with each other and many get dropped as duplicates.

Newer Lovable apps have file-based routes in src/routes with a head() per route holding title, description and JSON-LD. Fill those in, one per page. Older React + Vite apps have pages in src/pages and routes in src/App.tsx, and per-page meta is not handled for you. Setting it needs extra work in the code; check Lovable's documentation for the current approach.

Thin pages are the other common cause. A page with a heading and two lines of text gives Google little reason to index it. Pages built mostly from images, icons or decorative blocks look empty in HTML even when they look full on screen.

Check for an accidental noindex as well. Look in the page source for a robots meta tag, and open /robots.txt on the live domain to confirm it does not disallow everything.

  • One title per page — unique, specific, under about 60 characters.
  • One description per page — written for the result snippet, not keyword stuffing.
  • Real text — each page needs enough HTML copy to describe itself.
  • No stray noindex — check the page source and /robots.txt.
  • Internal links — every page should be reachable from the navigation or another page.

If the site is already in WordPress

Moving to WordPress changes which settings can hide a site. The most common one is a single checkbox.

Go to Settings → Reading. If "Discourage search engines from indexing this site" is checked, uncheck it. Staging installs often ship with it on, and it quietly follows you to launch if you copied the site over.

Check your SEO plugin next. Yoast, Rank Math and SEOPress each have per-page indexing controls, and a page set to noindex there will not appear no matter what else you do.

Then check URLs. If slugs changed during the move, old indexed URLs now return 404. Redirect them. Slugs are edited per page, and the structure sits under Settings → Permalinks.

Finally, confirm the homepage is set under Settings → Reading → "Your homepage displays". A site with no front page set will not rank for your brand name.

Why WordPress often fixes this for good

A WordPress site serves plain HTML to everyone. There is no prerendering layer to depend on and no difference between what a browser and a crawler receive. For an older React + Vite Lovable app, that removes the whole category of rendering problems.

It also puts the controls in one place. Titles, descriptions, slugs, redirects and the indexing checkbox all live in the admin, so a non-developer can fix a page without a rebuild and a redeploy.

Our converter turns a Lovable export into a WordPress block theme: templates, header and footer template parts, one pattern per page, theme.json with your palette and fonts, and your images copied into the theme. Per-page titles and descriptions from TanStack Start heads are written into Yoast, Rank Math or SEOPress, and redirects from public/_redirects are carried over. Conversion, review and the theme download are free, and you can compare the converted site against the original in WordPress Playground first. What converts and what does not is listed on supported features.

Be realistic about timing. Fixing indexing does not produce rankings the same week. Google has to recrawl, re-evaluate and rebuild its picture of the site. Make the fixes, request indexing, then check back in two weeks.

FAQ

How long does it take for a new Lovable site to appear in Google?

There is no fixed time. A brand new domain usually takes days to a few weeks before anything is indexed, and longer for every page. Submitting a sitemap and requesting indexing in Google Search Console helps Google find the pages sooner, but it does not guarantee indexing.

Why does an SEO checker say my Lovable page is empty?

Lovable apps created before 13 May 2026 render in the browser. On Lovable hosting they are prerendered on request only for verified search engines, link-preview bots and AI crawlers, so third-party SEO scanners receive an empty app shell. Use the URL Inspection tool in Google Search Console instead, since it shows the HTML Google actually received.

Does moving a Lovable site to WordPress get it indexed faster?

It removes rendering as a cause, because WordPress serves full HTML to every visitor and crawler. It also gives you per-page titles, descriptions, slugs and redirects in one admin area. Google still needs time to crawl and index the pages after the move.

Which WordPress setting hides a site from Google?

Settings then Reading contains a checkbox labelled "Discourage search engines from indexing this site". Leave it checked while you build on a staging site, and uncheck it before launch. Also check your SEO plugin, because Yoast, Rank Math and SEOPress can each set a single page to noindex.

My homepage is indexed but my other pages are not. What now?

That usually means the inner pages are duplicates, thin, or not linked from anywhere. Give each page a unique title and description, add enough real text to describe what the page is about, and link to it from the navigation or another page. Then request indexing for those URLs in Search Console.

Keep reading