Replit site not showing on Google: what to change
Most Replit sites built by Agent are React apps that render in the browser, so the HTML Google first receives can be an almost empty shell with generic tags. On top of that, the replit.app address keeps working after you connect a custom domain, so Google may index the wrong one. Publish on your custom domain, make titles, descriptions and a canonical link to that domain appear in the served HTML, add sitemap.xml and robots.txt, then submit the sitemap in Google Search Console.
What you'll see
Searching for your business name returns nothing from your site, or returns the something.replit.app address instead of your own domain. Search Console, if set up, lists pages as Discovered or Crawled but not indexed, or says Google chose a different canonical.
Why it happens
1. Content and tags are added by JavaScript
A Vite React app serves one index.html and builds the page in the browser. Google can render JavaScript, but it does so later and less reliably, and tags set only by script may be missed. Replit’s own SEO guide recommends Static deployments for content-heavy sites because they serve ready-made HTML.
2. The replit.app copy competes with your domain
After connecting a custom domain the replit.app URL usually stays reachable. Without a canonical tag pointing at your domain, Google sees two copies of the same site and may pick the one you did not want.
3. Basic SEO files and tags were never added
Agent does not always create a sitemap, a robots.txt, unique page titles or meta descriptions unless asked. Every page sharing one generic title gives Google little reason to rank any of them.
How to fix it
- Open your site, choose View Page Source (not Inspect), and search for title, description and canonical. What you see there is what Google receives before rendering. If it is generic or missing, that is the first fix.
- After publishing, look at the SEO rating Replit shows in the Publishing pane. On paid plans, open the Growth pane and use Run scan with Agent in the SEO Rating card to get a list of issues and fixes.
- Ask Agent to add a unique title and meta description per page, Open Graph tags, and a canonical link that uses your custom domain, output in the served HTML rather than only set by script.
- For a content site with no server logic, switch to a Static deployment so each page is served as pre-rendered HTML.
- Ask Agent to generate sitemap.xml listing your custom-domain URLs and a robots.txt that links to it. Check both load in the browser.
- Verify your custom domain in Google Search Console, submit the sitemap under Sitemaps, and use URL Inspection on the homepage to request indexing.
Prompt to paste into Replit
Optimize this site for search on my domain https://example.com. Give every page a unique title and meta description, add Open Graph and Twitter tags, a lang attribute, and a canonical link pointing at the https://example.com version of each URL. Make sure these tags are in the HTML the server sends, not only added by JavaScript. Generate sitemap.xml and robots.txt for https://example.com and add JSON-LD for my business.
How to check it's fixed
- View Page Source on two or three pages shows a distinct title, description and a canonical URL on your custom domain.
- Search Console reports the sitemap as read successfully, and URL Inspection shows Google’s chosen canonical is your domain.
What a QAlaunch scan shows for this
- Missing or duplicate titles and meta descriptions in the rendered HTML.
- A canonical tag that points to replit.app, or no canonical at all.
- A robots noindex tag left on the page.
- It reads the page as a browser does and cannot tell you whether Google has indexed it; Search Console is the place for that.
See exactly what a full report contains in the sample report.
Frequently asked questions
Can I redirect replit.app to my custom domain?
Replit’s docs do not describe a built-in permanent redirect from the replit.app address. A canonical tag on every page pointing at your domain is the dependable way to tell Google which copy to index.
Does Replit’s SEO rating mean Google will rank me?
No. The rating comes from a Lighthouse audit of technical basics. It helps you fix obvious problems, but ranking still depends on your content, links and competition.
How long until my Replit site appears on Google?
A new site often takes days to weeks. Submitting a sitemap and requesting indexing in Search Console helps Google find it; neither guarantees a date.
Rather have a QA engineer test it by hand?
If this is a site you're launching or handing to a client, I'll go through it by hand, including the Replit-specific issues a scan can't reach, like logged-in flows.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fixes
- Replit custom domain not working: verifying, failed and SSL fixes
- Replit app slow to load: cold starts and how to fix them
- Replit app stops when I close the tab: how to keep it running
- Replit works in dev but not in production: the real causes
- Replit deployment failed health check: how to get it to publish
More for Replit: all Replit fixes · Replit testing
Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: Replit docs: improve SEO · Replit forum: SEO for Replit-hosted websites · Replit forum: SEO best practices on Replit