Replit makes it easy to build and deploy an app, often with the Replit Agent writing a React + Vite frontend for you. You connect a custom domain, launch, and then nothing shows up in Google. Search Console reports pages as "Discovered – currently not indexed," and links shared on social media show only a generic title.
If your frontend is a client-side rendered single-page app, the server sends nearly empty HTML for every route:
<div id="root"></div>
<script type="module" src="/assets/index-xyz.js"></script>
Your browser runs the JavaScript and builds the page. Crawlers that don't run JavaScript (link previewers, most AI crawlers) see nothing. Google does render JavaScript, but in a separate, deferred step, so new or low-authority sites can sit unindexed, and route-specific titles set only in JavaScript may not be used.
If your Replit app is a server-rendered app instead (for example Express templates, Flask/Django templates, or Next.js), this specific problem may not apply. The test below tells you which case you're in.
curl as Googlebot:
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://www.yourdomain.com/ | grep -i -E "<title>|<h1|id=\"root\""
An <h1> with your real text is good news. Only id="root" and a generic title means crawlers are getting a shell.
Google Search Console: verify your domain, open URL Inspection, paste a page URL, then Test live URL and View tested page. Look at the screenshot and HTML. Also check the Pages report for "Crawled – currently not indexed" and "Duplicate without user-selected canonical," both common on SPAs where every route shares one title.
Free scan: the CrawlFixer checker shows the raw vs. rendered difference, plus missing title, description, canonical, social tags, robots.txt, and sitemap. No signup.
www or bare) and redirect the other, so Google doesn't split signals between them.robots.txt and sitemap.xml. In many SPA setups, unknown paths fall through to index.html, so /sitemap.xml returns your app's HTML instead of XML. Fetch both with curl and make sure they're the right content type.1. Edge prerendering (no rewrite). Put a prerendering layer in front of your Replit deployment. Crawlers get fully rendered HTML; people get your app unchanged. Google calls this dynamic rendering and accepts it when content matches. With CrawlFixer, you add www CNAME customers.crawlfixer.com and enter your Replit app address as the origin. Details in Connecting your domain. Free *.replit.app addresses can't be connected directly; you need your own domain.
2. Build-time prerendering. Snapshot static routes to HTML during the build. Works for a few marketing pages, not great for dynamic data.
3. Switch to SSR. Next.js, Remix, or Astro. The most thorough fix, and the most work.
Whichever you choose, also give each route a unique title, meta description, and canonical in the HTML crawlers receive, and submit your sitemap in Search Console.
Run the free scan on your Replit app's URL. If crawlers get an empty root div, start a free 7-day trial with no card. After that it's $12/month per site, or $49/month for up to 10 sites on the agency plan.
Related: Lovable site not indexed by Google · Why your Bolt.new site isn't on Google · React SPA SEO without Next.js
CrawlFixer is not affiliated with Replit or Google.