Written by Ari Rosenberg
Why Base44 Apps Don't Show Up in Google or ChatGPT
If your app doesn't appear in Google and ChatGPT has never heard of it, the cause usually isn't your content. It's that search engines and AI assistants are being handed a page with nothing on it. Here's the 30-second test, and what to do about it.
The 30-second test
Open your app in Chrome. Right-click anywhere on the page and choose View Page Source. Don't use Inspect — that shows the finished page after your browser has done its work, which is not what a crawler sees.
Now press Ctrl+F (Cmd+F on a Mac) and search for a sentence from your own page. Your headline works well.
You find it
Good. Search engines and AI assistants can read your page.
You don't
They can't. Whatever they're getting, it isn't your content.
When I ran this on my own site, every page returned the same thing: a list of my page names, the same repeated sentence under each one, and a line saying the site requires JavaScript. None of my actual copy was there. Not my headline, not my services. Google and ChatGPT were being handed a directory of page names and nothing else.
Why this happens
Apps built this way assemble the page inside your visitor's browser. The page arrives as a mostly empty container plus a set of instructions, and those instructions run on the visitor's device to build what they see. For a person with a browser this takes a second and works perfectly. It's a normal way to build modern web applications.
The problem is that not every visitor is a person with a browser.
When Google's crawler visits, it can run those instructions. It queues the page, loads it properly, and eventually reads the result. Slower than ideal, but it gets there.
The AI crawlers don't do this at all. The bots behind ChatGPT, Claude and Perplexity fetch the raw page and move on. They don't run the instructions and they don't come back for a second look. Vercel studied hundreds of millions of real crawler visits and found no evidence of any major AI crawler executing page code — GPTBot and ClaudeBot even download the code files sometimes, then never run them.
So there's a gap that catches people out: your app can be in Google and completely absent from AI assistants, because the two look at it with very different eyes.
What the platform does, and how it still fails
Base44 knows about this and ships a fix: the platform prepares a complete version of each page behind the scenes and serves that to crawlers, with real headings and real content. It works — when it's switched on and has actually run for your app. There are three ways it quietly doesn't.
The main SEO switch is off
In your app dashboard, under Marketing then SEO & GEO, there's a master toggle called Enable SEO for this app. Turning it off doesn't only stop the platform writing your meta tags — it also stops the engine that writes your real content into the page for crawlers. People switch it off deliberately, usually to control their own tags, without realising what else goes with it.
The prepared version never got made
Base44's documentation says that when a rendered version isn't ready for a page, the platform falls back to a generic outline of your app so crawlers receive something. That fallback is what I was looking at: a list of my page names and nothing else. No dashboard warning tells you this is happening. The only way to know is to look at the page source yourself.
Pages are individually hidden
There's a per-page indexing toggle in Advanced Settings. Worth knowing: if the master SEO switch was ever off, pages can end up marked as not indexable, and the moment you switch SEO back on they stay hidden from search. Check every page you care about after re-enabling.
Where I am with it, honestly
I'm writing this in the middle of the problem rather than after it. On my own site the master SEO switch is on, every page is set to indexable, and repeated publishes haven't produced a rendered version. Meanwhile another app on the same account renders perfectly, and the failure follows my app to its free address as well as its custom domain — so it isn't the domain, and it isn't the platform in general.
That leaves the prerender job for this specific app, which is a support question rather than a settings question. If you're staring at the same fallback page, that's the ticket to raise, and asking whether the job is running, failing or timing out gets you further than another pass through the settings checklist.
What to do, in order
- 1
Run the test above on your homepage and two or three other important pages. Write down which fail.
- 2
Publish on a custom domain. The SEO features are built and supported for apps on your own domain — a free address is fine while building, not for being found.
- 3
Check the master switch: Dashboard, Marketing, SEO & GEO, Advanced Settings. Enable SEO for this app should be on.
- 4
Check each page's indexing toggle in the same place. Anything you want found should be set to indexable.
- 5
Publish again, wait a day, and re-run the test. Publishing is what triggers the prepared version to refresh.
- 6
Still failing? Contact support with the evidence and ask specifically about the prerender job for your app. This is their feature not working, not something you can prompt your way out of.
- 7
Verify in Google Search Console. Submit your sitemap and use URL Inspection on a page that was failing. Free, and the only way to see what Google actually did.
Two things the platform won't do for you
Write your descriptions. Left alone you get something generic. Mine described my business by the number of page types in the app, which is not a sentence I'd want a potential client to read. Set them by hand on the Meta tags tab.
Write a useful llms.txt. This is a plain text file telling AI assistants what your site is about. The automatic version lists your pages by name — "About page", "Blog page" — which teaches an assistant nothing. Replace it with a real description of what you do and who you serve.
The bigger point
Getting your app visible is the floor, not the finish line. Once crawlers can read your pages they still have to find something worth reading: specific answers, real numbers, named people, honest comparisons. That's what gets a page quoted in an AI answer, and it's the same thing that gets it ranked in Google. But none of it counts for anything while the page arrives empty. Fix that first.
Common questions
Will Google eventually find my app anyway?
Probably. Google runs the code on your page, so it can usually reach your content in the end. AI assistants won't. If your goal includes showing up in ChatGPT, Claude, Gemini or Perplexity, waiting isn't a strategy.
Does asking the AI builder to add meta tags fix this?
No. Tags added that way get applied inside the visitor's browser after the page loads, which is exactly the part crawlers skip. Your browser tab will look right and the page source won't change. Use the Meta tags tab in the dashboard instead.
Do I need a paid prerendering service?
Almost certainly not. Those services work, but Base44 does this natively now. Pay for a second one only after you've confirmed the built-in one isn't working for your app and support can't fix it.
Does this affect link previews on WhatsApp and Facebook?
Yes, the same way. Social platforms don't run your page code either, so when the prepared version is missing, shared links show generic previews instead of your title and image.
Should I move off Base44 because of this?
That depends on what your app does, not on this issue. Base44 is a good fit for apps with real functionality — portals, booking, dashboards, internal tools. For a straightforward brochure website, a platform like Wix handles all of this without you having to think about it. I build on both.
If you need a hand with this
Want me to check it for you?
I'm a Base44 Specialist Partner and a Wix Legend Partner, and I run this test on every app I touch. If your app isn't showing up and you'd rather someone just looked, book a free 15-minute call and I'll tell you what's wrong with it — whether or not you hire me to fix it.