Skip to content
Base44 SEO Journal

How to connect a Base44 app to Google Search Console

Verify a Base44 app in Google Search Console with the HTML tag in index.html, submit the sitemap, and read URL Inspection correctly on a Base44 site.

8 min read

To connect a Base44 app to Google Search Console, add a URL prefix property, paste Google’s verification meta tag into your app’s index.html from the Code tab, publish, click Verify, and submit sitemap.xml. It takes about five minutes. Reading the results correctly takes one extra piece of knowledge about how Base44 serves crawlers, covered at the end.

This is one step in the Base44 SEO checklist. Do it once your custom domain is live, since that’s the address you want Google to index.

Before you start

  • Your app should be on its custom domain and published. You can verify a free base44.app URL too (Base44’s docs confirm both work), but it isn’t the address you’ll want ranking.
  • Decide which address is canonical. Base44 redirects www to the root domain and has no setting to reverse it, so the root is your main address.
  • You’ll need access to the app’s Code tab.

Verify with the HTML tag

These steps follow Base44’s SEO documentation.

  1. Go to Google Search Console, sign in, and click Add property.
  2. Choose URL prefix and enter your full URL, including https://.
  3. On the Verify ownership page, expand HTML tag and copy the meta tag. It looks like <meta name="google-site-verification" content="..." />. Don’t edit the content value.
  4. In your Base44 app editor, click Dashboard, then the Code tab, then index.html.
  5. Paste the tag anywhere inside <head>.
  6. Click Save, then Publish.
  7. Back in Search Console, click Verify.

If it fails, check the live site. The preview doesn’t count:

curl -s https://yourdomain.com/ | grep -o '<meta name="google-site-verification"[^>]*>'

Base44’s docs list three causes of failure: the tag isn’t in the live <head>, it doesn’t match exactly, or the URL in Search Console doesn’t match the published app’s protocol and subdomain. Leave the tag in place after verifying, or the property can lose its verified status.

Submit the sitemap

In Search Console, open Sitemaps, enter sitemap.xml, and click Submit. Base44 serves it at https://yourdomain.com/sitemap.xml on custom domains.

Look at what you submitted before you rely on it. Base44’s sitemap lists page files only, so records such as individual products or posts aren’t in it, and it often includes login, password-reset and admin pages. In our test of 47 Base44 sites, 21% of sitemap URLs were utility pages like those. The sitemap guide covers removing them and adding records.

Request indexing for key pages

Open URL inspection, paste the full URL of an important page, and click Request indexing. Google treats the request as a hint and makes no promise about timing. Do it for your homepage and the three or four pages you most want found. Repeating the request doesn’t move you up the queue.

Read URL Inspection correctly on Base44

URL Inspection shows two different things, and on Base44 they disagree.

  • The indexed result (what you see first, and View crawled page) is what Googlebot fetched and stored.
  • Test live URL fetches the page now, using a user agent called Google-InspectionTool.

Base44 pre-renders pages for crawlers it recognizes by user agent. In our tests Google-InspectionTool wasn’t one of them: it always received Base44’s hidden, auto-generated summary block (seo-snapshot) instead of the rendered page, even where Googlebot’s user agent got the full render. Google’s Rich Results Test uses the same user agent, so it has the same blind spot.

So when Test live URL shows your page with a heading like “Pricing | YourApp”, a stock description of your app and a list of links, you’re looking at the summary Base44 serves when it isn’t pre-rendering. Googlebot may well have received the full page. Check View crawled page → HTML on the indexed result, and search it for a sentence that only appears in your real page copy.

To see what Base44 sends Googlebot right now, use Googlebot’s user agent directly:

UA='Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)'
curl -s -A "$UA" https://yourdomain.com/pricing | grep -c 'id="seo-snapshot"'
# 0 = rendered page, 1 = generated summary

Add Bing Webmaster Tools too

Base44’s docs recommend Bing Webmaster Tools alongside Search Console, “because many AI assistants rely on both Google and Bing.” In Bing Webmaster Tools you can import a verified site from Search Console, or verify with Bing’s own meta tag in index.html the same way. Then submit the same sitemap.xml.

The Search Console connector inside Base44

Base44 also has a Google Search Console connector that lets you query your search data from the AI chat or dashboard. It’s useful once the property exists. It doesn’t replace verifying the property in your own Google account.

What to do next

  1. Verify the property and submit the sitemap today.
  2. Request indexing for your top pages.
  3. After a week, open the Pages report. If pages sit in “Crawled, currently not indexed”, work through why a Base44 app isn’t showing up on Google.

Found something wrong or out of date? Base44 ships changes every week and we'd rather fix a guide than let it rot.

Frequently asked questions

Where do I put the Google verification tag in Base44?
In your app's index.html. Open your app's Dashboard, click the Code tab, open index.html, paste the meta tag inside the head section without changing its content value, click Save, then Publish. Verification only works once the tag is on the live site.
Should I use a Domain or URL prefix property for Base44?
Base44's docs describe the URL prefix method with an HTML tag, which needs no DNS changes. A Domain property covers every subdomain and protocol but needs a DNS TXT record. If you manage your domain's DNS yourself, a Domain property is the more complete choice.
What sitemap URL do I submit for a Base44 app?
https://yourdomain.com/sitemap.xml. Base44 generates and serves it automatically on custom domains. If you replaced it with a sitemap served from a backend function, submit that function's full URL instead.
Why does the Search Console live test show different content from my page?
The live test fetches with Google-InspectionTool. In our tests Base44 served that user agent its auto-generated summary block even when Googlebot's user agent got the full render. Check View crawled page on the indexed version for what Googlebot actually stored.
Can I connect Search Console to Base44 itself?
Yes. Base44 has a Google Search Console connector you can use from the AI chat or your app dashboard to query your search data inside Base44. It doesn't replace verifying the property in your Google account.

Read next

Keep going