← Blog

Build ·

You Built an App With AI. What to Do in the First 30 Days

A week-by-week plan for the month after launch: get indexed, check what crawlers can read, fix page titles, add analytics and find your first ten users.

By , Founder, Baljia AI

Picture the morning after launch. The app works. A few friends said it looks great. The visitor count has not moved since.

That is normal. A live app is an address nobody has heard of, and nothing about building it changed that.

The short answer

Spend the next 30 days on six jobs, in this order: get indexed, check what crawlers can read, give every page its own title, set up analytics, get ten real people through the app, and follow up with your waitlist properly. The first two weeks are settings and checks. The last two weeks are people.

Baljia wrote this post and sells a competing product that also builds web apps. The builder tables below draw on vendor pages. We read each vendor's public pages on October 31, 2026. On November 5, 2026 we re-checked prices and read each builder's blog and docs for growth and marketing features. We did not log in or run these tools.

WeekJobFinish line
1Get indexed, check crawlersSearch Console verified, sitemap sent, your words visible in the page source
2Titles and analyticsEvery public page has its own title, and a signup shows in your reports
3First ten usersTen people finished the core job, and you know where the others stopped
4Waitlist and reviewWaitlist contacted one by one, and a keep, change or stop decision made

This assumes the basics work. If you have not tested phones, forms and links, do that first with our website launch checklist. This plan also skips ads on purpose. Until a stranger has finished the core job, paying for clicks just buys you a faster look at the same problem. That holds even if your builder offers to run ads from the same chat, as Lovable, Base44 and Replit now do.

Week 1: get found, and check what crawlers can read

Day 1: settle your address

Decide now whether you are staying on your builder's address or moving to your own domain. You do not need a custom domain to be indexed, but moving later means Google has to learn the new address. Custom domains are often a paid feature, so check your plan.

Day 2: set up Search Console

Add your site to Google Search Console. A Domain property covers your whole domain but needs a DNS record. A URL-prefix property is simpler if your builder lets you add a tag or file. If DNS sounds foreign, ask your builder: "Which Search Console verification method works on my plan?"

Day 3: send a sitemap

A sitemap is a list of your public pages. Open yoursite.com/sitemap.xml. If you see a list, submit that address under Sitemaps in Search Console. If you get an error, ask your builder to create one that lists every public page and leaves out anything behind sign-in.

Day 4: inspect your home page

Paste your home page address into the URL Inspection box at the top of Search Console. Click Test live URL. If it says the page can be indexed, click Request indexing. Do this for your few most important pages, not every page.

Then wait. Google says crawling can take anywhere from a few days to a few weeks, so a blank report on day 6 is not a failure.

Days 5 to 7: run the source test

This is the check most people skip, and it takes three minutes.

  1. Open a public page in Chrome.
  2. Press Ctrl+U on Windows, or Option+Command+U on a Mac. A page of code opens.
  3. Press Ctrl+F or Command+F and search for your headline.

If your headline is there, anything that reads plain HTML can read it. If the code is short and your words are missing, the words only appear after JavaScript runs in a browser.

That matters less for Google than for others. Google queues pages to render JavaScript, though it says this can take longer than a few seconds, and it also says not all bots can run JavaScript. In December 2024, Vercel reported that the OpenAI and Anthropic crawlers it studied fetched JavaScript files but did not execute them. That finding is old, and Vercel sells hosting for server-rendered sites, so treat it as a reason to test, not a fact about your site.

For Google's own view, go back to URL Inspection and open View tested page after a live test. It shows the HTML and a screenshot of what Google got.

If your words are missing, give your builder this prompt:

Make my public pages (home, pricing, about, blog) send complete HTML
with all the words in the first response, before any JavaScript runs.
Do not change the pages behind sign-in.
Tell me what you changed and how I can confirm it.

Then run the source test again. Pages behind sign-in do not need this. You do not want them crawled.

What to verify on your builder

Builders change how they serve pages, and a feature on a pricing page is not proof of what your site does. So we are not going to tell you how each one renders. We can tell you what each page states, and what to confirm on your own live address.

BuilderWhat its pages stateWhat to verify yourself
LovableAn SEO review that checks pages, sitemap, robots.txt and Search Console and can fix them; Semrush data with no extra fee through November 30, 2026; custom domains on ProWhether its fixes appear in your page source, then the title on each page
ReplitAn SEO Agent with one-click fixes on paid plans; a Lighthouse SEO rating after each publish; meta tags, robots.txt and sitemap.xml by default on new appsWhether its fixes appear in your page source, sitemap, robots.txt
Bolt.newSEO optimization, analytics, custom domains, an SEO/GEO skill; SEO boost and domains are paidWhich of these your plan includes, then the source test
v0Deploy to Vercel, custom domain in docs; SEO not statedTest the deployed address, not a preview
Base44Analytics, an SEO and GEO page with AI Visibility on Pro and up, Search Console connectWhether dashboard changes appear in your page source
EmergentProduction hosting; an Enable SEO toggle that pre-renders pages for crawlersWhether the toggle is on, then the source test, sitemap, title on each page
BaljiaAudits for Google and AI search; applies supported fixes to apps it buildsSource test anyway, and read what it could not verify

Week 2: titles and analytics

Give each page its own title

Click through your public pages and watch the browser tab. If it says the same thing on every page, that is your first fix, and it is an easy one.

Google asks for a distinct, descriptive title on each page and warns against repeated boilerplate. It also asks for a unique description per page. Here is a made-up example:

PageWeakBetter
HomePawRouteMobile Dog Grooming Booking in Tulsa, PawRoute
PricingPawRoutePawRoute Prices: Groom Packages From One Visit
AboutPawRouteAbout PawRoute, a Family Grooming Van in Tulsa

Ask your builder for a table of proposed titles and descriptions, and approve them before it changes anything. Then read them. AI will happily write something false in a meta description, and Google's advice is to review AI output, including metadata, before it goes live.

While you are in there, type yoursite.com/this-page-does-not-exist. You should see a clear not-found page. Some single-page apps show a normal-looking page there with no real error behind it, which Google calls a soft 404. Ask your builder to fix that too.

Set up analytics

Use your builder's analytics if it has them, or Google Analytics if you want more detail. Bolt, Base44, Lovable and Replit state built-in analytics, and Emergent says published apps include its analytics by default. For Google Analytics, you create a property, add a web data stream and put the tag on your site. Enhanced measurement collects page views on its own.

Page views will not tell you much. Add two events, so you can see what people do:

  • Signed up: Google's recommended event name is sign_up.
  • Finished the core job: name it for your app, such as booking_made.

Then test it. Sign up with a fresh email, open the Realtime report, and look for your event. Google says data can take up to 30 minutes to start. Mention analytics in your privacy policy.

From now on, write three numbers down once a week: visitors, signups, and people who finished the core job.

Week 3: get ten real people through it

Stop thinking about marketing for a week. Your job is ten strangers, or near strangers, finishing the one thing your app does. Ten signups does not count. Ten people who got to the end counts.

  1. List 30 names. Past coworkers, customers of a related business, people in groups you belong to, anyone who complained about this problem in public. Our one-day exercise shows how to find people who are asking right now.
  2. Message each one yourself. Skip the launch post. Try this:

Hi [name], this is a promotional note about something I built. You mentioned [the problem] last month, and my small tool is for that. Would you try it for ten minutes and tell me where you got stuck? It is early, and I would value your honest view.

[Your name], [your postal address]. Reply "stop" and I will not write again.

  1. Watch three people use it. Share a screen, ask them to think out loud, and stay quiet. You will want to explain. Do not.
  2. Write down their exact words. The way they describe the problem is your next headline and your next search term.
  3. Fix one thing a day. Only fix what stopped someone. Ignore features they mention in passing.

Your builder may offer to write these for you. Lovable drafts outreach messages that you send yourself, and Replit's docs describe sending email from your Gmail after you approve the drafts. Either way, read each message before it goes, and check it carries the footer below.

If you email strangers about your app, US law applies. Under CAN-SPAM, a commercial email needs clear identification that it is an ad unless the person gave prior consent, a valid postal address and a clear way to opt out. You must honor opt-outs within 10 business days. The sample above has all three.

Week 4: follow up with your waitlist, then decide

A one-line "we are live" blast to everyone is a fast way to waste a waitlist. These people raised their hand, so treat them like people.

  • Send it from your own address, not a no-reply one.
  • Start with the 20 most recent signups, because they remember you.
  • Ask one question: "What made you sign up?"
  • Give one link, straight to the core job.
  • Answer every reply the same day.
  • Follow up once if they do not respond, then stop.
  • Include an ad line unless they gave prior consent, plus your postal address and an opt-out, because this is still commercial email.

The full sequence is in what to send your waitlist. Early replies matter more than sign-ups. They tell you why people wanted this, which is often not why you built it.

On day 30, sit down for 20 minutes and answer five questions:

  1. Are my important pages indexed? Check the Pages report.
  2. Am I getting any search impressions, and for what words?
  3. How many people finished the core job?
  4. Where did the most people stop?
  5. Do I keep going, change who this is for, or stop?

Be honest on the last one. If ten people tried it and nobody came back, more traffic will not help.

Three things that waste the month

Publishing lots of AI pages. Google does not ban AI content, but it penalizes low-value content at scale. A few pages that answer real questions beat fifty that do not.

Rebuilding instead of talking. New features feel like progress. If nobody has finished the core job yet, a new feature is a way to avoid finding out why.

Judging too early. A first week of zero is expected, because Google may not have crawled you yet. Judge by the checks in this plan, not by traffic.

Where Baljia fits

If you built somewhere else, you can do all of this yourself with the steps above, and your builder may already cover part of it. Before you add another tool, check what it now does after launch.

BuilderGrowth features its pages stateWhat to check
LovableGrowth plan, SEO with Semrush, Google and Meta ads with no Lovable fee on spend, drafted posts and outreachPosts and messages are drafts you send, except Google Business Profile posts it can publish after you approve
ReplitSEO Agent on paid plans, analytics, Growth Skills with Apollo cold email, TikTok ads, outreach email from your GmailAsk for drafts first, and confirm which plan each tool needs
Base44Google Ads billed by Base44 with a 15% fee, automatic social posts on Builder and up, Marketing Agent, AI Visibility, marketing emailWhether automatic posting is on, since posts go out unless you cancel them
EmergentEnable SEO toggle, analytics on by defaultMarketing is not stated, so plan the outreach yourself
Bolt.newSEO tools and an SEO/GEO skillMarketing beyond SEO is not stated
v0None statedPlan the marketing yourself

Baljia can help with parts of this too, with limits:

  • It works as an AI employee you message on WhatsApp, Slack or the web.
  • It audits your site for Google and AI search. On apps it builds, it applies supported fixes. On other sites, it prepares instructions for you or your builder.
  • It finds people who need you and sends email outreach, and LinkedIn outreach on Growth and Scale only. Sending limits do not guarantee account safety. LinkedIn can restrict accounts that use automation.
  • Its ads are Meta only. You pay what Meta charged plus a 20% fee on Baljia's managed ad account, or no added fee on an ad account of your own. For Google or TikTok ads, look at the builders above.
  • If you have not built yet, Baljia builds web apps only, and card checkout into your own payment account is not available yet.

See how it works on the web app use case page. For picking a builder in the first place, read how to build an app with AI.

Frequently asked questions

When will Google index my new app?

Often a few days to a few weeks, and Google says indexing is not guaranteed. Submitting a sitemap and requesting indexing for your key pages helps Google find them, but you cannot force the timing.

Why is my AI-built app not showing up on Google?

The usual causes are that it is too new, it was never submitted, a noindex tag or robots.txt is blocking it, or the words are not reaching the crawler. Run URL Inspection on the page to see which one applies.

Do I need a custom domain?

No, not to be indexed. Still, decide early, because moving later means Google has to learn a new address.

Can ChatGPT read my AI-built app?

Maybe, so test it. Run the source test first, then see how to get recommended by ChatGPT for the crawler settings and a 20-minute check.

How do I get my first users with no audience?

Message people one at a time. Start with 30 names who have the problem and ask for ten minutes of honest feedback, because you are after learning before you are after numbers.

Should I run ads in the first month?

Usually not. Wait until strangers can finish the core job without your help, so you are not paying to send people into a problem you could have fixed for free.

Your next step

Run the source test on your own home page now. If you want help with the checks and the outreach that follow, Baljia has a 7-day free trial with no credit card at https://baljia.ai/. The trial does not include LinkedIn outreach, and automations that run on their own start on a paid plan.

Sources