Why your Base44 app isn't showing up on Google, and how to fix it

A Base44 app that isn’t on Google almost always fails one of six checks: it isn’t on a custom domain, it isn’t published, the pages sit behind a login, something is sending noindex, Google hasn’t been told the pages exist, or crawlers are getting a summary instead of your content. Work through them in that order. The first four take a few minutes each.

The wider picture of how Base44 handles search lives in the Base44 SEO guide. This post is the fix list.

Before anything: how long has it been?#

Base44’s SEO documentation says a new or moved app can take “anywhere from a few days to a few weeks” to be indexed. If you published yesterday, submit your sitemap and wait. If it’s been three weeks and a site:yourdomain.com search still shows nothing, something below is wrong.

1. Is the app on a custom domain?#

Base44 builds its SEO setup for custom domains and says free base44.app URLs “are not intended for long-term, production SEO.” They can still be indexed, but you’re competing without llms.txt, social previews or any domain history of your own.

Custom domains need the Starter plan or higher. If you connected one recently, check two things:

• The domain loads your app over HTTPS, and www redirects to the root (Base44 always does this, and there’s no setting to reverse it).
• Your old base44.app address now sends noindex, so Google moves its attention to the new domain:

curl -sI https://yourapp.base44.app/ | grep -i x-robots-tag

If the base44.app copy still has no noindex header and declares itself canonical, you have two copies of the site competing. We saw this on 3 of 46 apps in our crawler test. Republish, and if it persists, ask Base44 support to confirm the custom domain is set as primary.

2. Is it published, and is the live version the one you think?#

Search engines only see the published app. Changes in the editor, in the Code tab or through GitHub sync go live only after you click Publish. Open the live domain in a private window and confirm the page exists there.

3. Are the pages behind a login?#

Base44 always excludes login-required pages from indexing. If your whole app requires login, crawlers can’t open a single page, and there’s nothing to index.

The usual fix is a public landing page with login only for the private areas. Ask the AI chat something like Make the Home, Pricing, About and Blog pages public. Keep login required for the dashboard and account pages. Then check a public page in a private window: if it redirects to a login screen, so will Googlebot.

4. Is something sending noindex?#

Three places can hide a noindex:

1. Per-page indexing toggles. In SEO & GEO → Advanced Settings, a page with its toggle off gets noindex and drops out of the sitemap.
2. The main SEO toggle. If Enable SEO for this app was switched off and then back on, Base44 warns that any page set to noindex while SEO was off is hidden again the moment you re-enable it. Set the pages you want back to Indexable first.
3. A header. Check the live response for an x-robots-tag:

curl -sI https://yourdomain.com/pricing | grep -i x-robots-tag
curl -s https://yourdomain.com/pricing | grep -io '<meta[^>]*robots[^>]*>'

Neither command should print noindex on a page you want in Google.

5. Has Google been told the pages exist?#

Base44 serves a sitemap at /sitemap.xml, but Google won’t necessarily go looking for it. Verify the domain in Google Search Console, submit the sitemap, and request indexing for the three or four pages that matter most. The Search Console guide walks through the verification tag, which goes into index.html from the Code tab.

Then open the sitemap and read it:

curl -s https://yourdomain.com/sitemap.xml | grep -o '<loc>[^<]*</loc>'

Two things commonly go wrong. Pages that show records (products, posts, listings) aren’t listed at all, because Base44’s sitemap only contains page files. And login, password-reset and admin pages often are listed: they were 21% of all sitemap URLs in our test. The sitemap guide fixes both.

6. What does Googlebot actually get?#

This is the Base44-specific check. Base44 serves recognized crawlers a pre-rendered copy of each page from a cache, and never renders while a crawler waits. When a page has no cached render, crawlers get a hidden, auto-generated summary block (seo-snapshot): your page name, a stock description of the app, and a list of links. Google can’t rank a page for anything when that’s all it sees.

Test your own pages with Googlebot’s user agent, which is what Base44 uses to decide:

UA='Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)'
for p in / /pricing /about /blog; do
  printf '%-10s ' "$p"
  curl -s -A "$UA" "https://yourdomain.com$p" | grep -q 'id="seo-snapshot"' && echo summary || echo rendered
done

Pages that print summary have no cached render, and asking again won’t get them one: in our tests, pages requested every 10 seconds for four minutes stayed on the summary. In our first test, 31% of inner pages were still summary-only after two passes.

What Search Console’s status is telling you#

“Crawled, currently not indexed” is the one to look at hardest on Base44. If the crawl that produced it got the summary block, Google saw a page name and a stock description that’s nearly identical on every page of your site. Fixing the content does nothing until crawlers get the rendered page.

When the pages that matter are dynamically loaded#

If the pages you need indexed show dynamically loaded content (product pages, directory listings, blog posts stored in your app’s data: anything that isn’t written into the page’s source code), you’re facing all three weak spots at once: missing from the sitemap, a shared title, and the least likely to have a render ready. Requesting those pages yourself won’t get them rendered. The two fixes are a pre-rendering service in front of the domain, so every page is rendered before crawlers ask, or exporting the app to a stack with server rendering. The Base44 SEO guide compares them.

What to do next#

1. Run checks 1 to 4 now. They’re quick and they cover most cases.
2. Verify the domain in Search Console and submit the sitemap.
3. Run the Googlebot loop on your key pages, twice.
4. Come back in a week and read the Pages report for the statuses in the table.