Discovered – currently not indexed: a Lovable-site fix guide

Why Google finds your Lovable pages but refuses to index them, and the practical fixes that move them into the index.

By Fellow Lovable vibe coder · 7 min read

"Discovered – currently not indexed" is the single most common status Lovable users see in Google Search Console. Google knows the URL exists. It just decided — for now — that the page is not worth crawling or storing in its index.

This is not a technical block. Robots.txt is not blocking you. There is no noindex tag. Google saw the URL, weighed it against its crawl budget, and chose to skip it.

Why this happens to Lovable sites specifically

Lovable apps ship as React SPAs built with Vite. When Googlebot first discovers a URL, it does a cheap fetch of the raw HTML before deciding whether to invest the more expensive JavaScript render. On an unprerendered Lovable site, that raw HTML is almost empty:

<!DOCTYPE html>
<html>
  <head><title>My Lovable site</title></head>
  <body>
    <div id="root"></div>
    <script src="/assets/index.js"></script>
  </body>
</html>

Google's heuristics see nothing distinguishable here from thousands of other empty shells, so the URL gets parked in "Discovered" and deprioritized.

The five most common root causes

1. Empty pre-render HTML

Crawlers fetch the SPA shell, see no content, and decide the page is low value. Prerendering (Encited) or SSR fixes this immediately.

2. Thin or templated content

Pages with under ~300 words of unique content, especially if many pages share the same layout and boilerplate, look like template spam to Google.

3. New domain with no authority

Fresh domains have no backlinks, no history, no trust signal. Google crawls them sparingly until they prove themselves.

4. No internal links to the page

If a URL only lives in your sitemap but nothing on the site links to it, Google treats it as orphaned and low priority.

5. Duplicate or near-duplicate pages

Multiple pages targeting the same intent with shuffled wording (common with AI-generated programmatic SEO pages) get deduplicated and dropped.

The fix, in order

Step 1 – Confirm what Google actually sees

In Search Console, run URL Inspection → "Test live URL" → "View crawled page" → "HTML". If the body is just an empty <div id="root"></div>, the problem is rendering, not content.

You can also reproduce it from any terminal:

curl -A "Googlebot" https://your-site.com/some-page | grep -i "<h1\|<p>"

Step 2 – Serve pre-rendered HTML

Add a prerendering layer (Encited is the no-code option) so that Googlebot, Bingbot, GPTBot and friends get fully rendered HTML with real headings, paragraphs and links instead of the SPA shell. This alone resolves a large share of "Discovered – currently not indexed" cases on Lovable projects.

Step 3 – Make each page substantially unique

Aim for 600+ words of content that only exists on that URL.
Unique <title> and meta description per route.
One clear H1 that matches the URL's intent.
Avoid shared boilerplate that dominates the page body.

Step 4 – Link the page internally

From your homepage, navigation, or a related-content section, link to the page with descriptive anchor text. Pages that only appear in sitemap.xml behave like orphans to Google.

Step 5 – Request indexing, then wait

After fixing the above, click "Request indexing" in URL Inspection. Then leave it alone. Re-requesting daily does not speed things up — Google decides on its own schedule, usually within 1–3 weeks for new Lovable domains.

The shortest path out of "Discovered – currently not indexed" on a Lovable site is: prerender, then de-template the content, then internally link it.