My Base44 site isn't showing up on Google

Sixty seconds, no AI. Most people are fixed by one of these and never need the prompt below.

1. 1

   Search site:yourdomain.com on Google. If results come back you are indexed, and what you have is a ranking problem — a different and much slower fix. Nothing back, keep going.

2. 2

   Open your domain in a private window. "Server cannot be found" or DNS_PROBE_FINISHED_NXDOMAIN means this is not an indexing problem at all — your domain is not resolving. Go to the domain-not-resolving page. If it used to be on Google and then vanished, this is the most likely cause.

3. 3

   Check which URL you are searching for. A *.base44.app URL and your custom domain are two different sites to Google. Base44's docs say the free URLs "are not intended for long-term, production SEO".

4. 4

   Search Console → URL Inspection → paste the URL → Test live URL → View crawled page. That is the HTML Google actually receives, rather than what you see. If it comes back empty, nothing else here matters until that is fixed.

5. 5

   Dashboard → SEO & GEO → run the scan. It checks the things that silently block indexing: robots.txt, sitemap, custom domain, published state, HTTPS, and whether every page has its own title and description.

6. 6

   SEO & GEO → Advanced Settings → per-page indexing. Confirm the page you are hunting for has not been set to noindex. One toggle, easy to have flipped and forgotten.

7. 7

   Then wait. Google's own words: "Crawling can take anywhere from a few days to a few weeks." Requesting a crawl "does not guarantee that inclusion in search results will happen instantly or even at all", and re-requesting the same URL "won't get it crawled any faster".

Base44 does more of this for you than most platforms. It generates robots.txt and sitemap.xml, adds a self-referencing canonical to every page, and serves crawlers a rendered version of pages that are otherwise client-side rendered.

What it cannot do — what no platform can do — is make Google crawl you. That gap is where this question lives.

The usual causes, in the order they actually occur:

• The site is new. Nothing links to it, so there is no path for a crawler to find it other than the sitemap you have not submitted yet. This is most cases and the fix is patience plus Search Console.
• You are checking the wrong URL. The *.base44.app address and your custom domain are separate sites as far as Google is concerned.
• The pages need a login. A crawler is always signed out. Anything behind auth is invisible, and that is correct behaviour, not a bug.
• Per-page indexing is off for the page you are looking for.
• The domain stopped resolving. Covered on its own page — and it is the answer whenever a site was on Google and then disappeared.

One thing worth being clear about: indexed and ranking are not the same. A site: search that returns your pages means Google has them. If you then cannot find yourself by typing your business name, that is a ranking problem, and no setting fixes it — content, links and time do.

Paste into your Base44 builder chat. The first one only reads — it changes nothing, so it is safe to run on a live app.

Audit this Base44 project for search indexability. The site is live but is not
appearing in Google.

READ ONLY. Do not edit, create or delete any file. Do not run any build or install
step. If something should change, describe it — do not do it.

EVIDENCE RULE — this governs everything below.
Every finding must carry one of:
  [CODE]   a file path and line number in this project
  [LIVE]   a URL you fetched, with the HTTP status code you received
  [UNVERIFIED]  you could not check it from here
You may not report PASS, OK or "looks good" for anything you have not evidenced.
If you cannot verify something, the answer is UNVERIFIED. Never infer that
something works because the code looks like it should.

1. IS IT REACHABLE AT ALL
   - What is the published custom domain, and what is the *.base44.app URL?
   - Fetch the custom domain root. Report the HTTP status code you got.
…

Using the audit you just produced, implement the fixes. The audit was read-only;
this turn is the only one that writes.

Order:
  P0  stops Google crawling or indexing the site at all
  P1  weakens how well a page can be understood or ranked
  P2  worthwhile, not blocking

Implement every P0 and P1 that can be changed safely inside this project.

Do not:
  - modify entity schemas, RLS rules, auth configuration or payment flows
  - delete pages
  - add npm packages
  - rewrite good copy to chase a score, or add keyword padding
  - act on any finding marked UNVERIFIED — list it for me instead

Specifically do NOT touch anything that lives in the Base44 dashboard rather
…

Verify the changes actually took effect. Do not trust the previous turn's report.

PART 1 — RE-CHECK FROM OUTSIDE
Fetch each of these fresh and report the raw result, not your expectation:
  - the custom domain root: HTTP status code
  - /robots.txt: full contents
  - /sitemap.xml: URL count, and the status code of a random sample of 5
  - the three most important routes: <title>, meta description, canonical,
    any robots meta tag, and whether the body text is present in the response

For each, say PASS or FAIL against what the fix turn claimed. Where they
disagree, the fetch wins — say so plainly and explain what is actually there.

PART 2 — WHAT I STILL HAVE TO DO MYSELF
List, with the exact screen and value:
  - anything that needs the Base44 dashboard (SEO & GEO, indexing, domains)
  - anything that needs Google Search Console
Do not describe these as done. You cannot do them.
…

• Google Search ConsoleAdd and verify your property. Everything else starts here.
• Build and submit a sitemapGoogle's own guide, including how to submit it.
• Ask Google to recrawl your URLsURL Inspection vs sitemaps, quotas, and realistic timings.
• Base44 — getting your app found in searchWhat the platform does automatically and what it leaves to you.