You built your app with Base44. It looks great. And nobody is coming.
Where are the customers? Ads cost money, and posting on X every day becomes a second job. Search can bring visitors without ad spend, but a new site starts with no articles for Google to find. Base44 will build a blog if you ask for one in chat, but the articles still have to come from somewhere.
This guide fixes that, step by step. You paste one prompt into Base44, connect it to TalkGenAI, and publish your first article. Each article takes up to 5 minutes to write. A blog is no guarantee of traffic, so we also show how to check that search engines can read your pages.
Key takeaways
- One prompt is enough. Base44 built the webhook receiver, the
/bloglist, a page for each post, a sitemap and structured data from it, and tested its own endpoint. - Skip Base44's first secret form. TalkGenAI only creates the secret after you enter your site address.
- Publish your Base44 app again after adding the secret. We did, and the live endpoint then started checking signatures. We did not test skipping this step on Base44, but on Lovable the first test failed until we republished.
- Check the page source. On our demo site, the article text, headings and structured data were all in the raw HTML, for a normal browser and for a Googlebot user agent alike.
- Two things were missing on our demo site: a canonical link and a
robots.txt. We show how to ask Base44 for both. - Start with drafts, so you read each article before it goes live.
We tested every step on a throwaway demo site. That demo site was also built with Base44, and the article you will see was written by TalkGenAI. Where something went wrong or was missing in our test, we say so, because those are the parts that will save you time.
What you need
- A Base44 account and a new app (an empty one is fine).
- A TalkGenAI account.
- A few minutes while Base44 builds the receiver. In our run it took about four minutes.
How it works
TalkGenAI writes an article and sends it to your site as a signed message (a webhook). Your Base44 app checks the signature, saves the post, and shows it at /blog/your-article. The signature means nobody else can post to your blog.
Step 1: Paste the setup prompt into Base44
In TalkGenAI, open Integrations, choose Custom site, click Add Site, and open "Setup prompt for your AI builder". Copy it and paste it into the Base44 box on the home screen ("Describe the app you want to build"). This is the full prompt:
Add a blog to this site that receives articles from TalkGenAI by webhook.
1. Create a POST endpoint at /api/talkgen-webhook.
2. Read the RAW request body. Verify the header X-TalkGen-Signature equals "sha256=" + hex(HMAC-SHA256(secret, X-TalkGen-Timestamp + "." + rawBody)) using the env var TALKGEN_WEBHOOK_SECRET. Compare in constant time. Reject (401) if the timestamp is older than 5 minutes.
3. Event "ping": answer 200 {"ok":true}.
4. Events "article.published" / "article.updated": JSON body has title, slug, html, excerpt, meta_description, category, status ("draft"|"publish"), images[0].url + alt, schema.article, schema.faq, job_id, existing_id. Upsert the post by job_id (idempotent), store it, show only status "publish" posts publicly. Sanitize the html before rendering it. Put schema.article and schema.faq in the page as JSON-LD.
5. Answer 200 {"id": "<your post id>", "url": "<public post URL>"}.
6. Add a /blog list page and /blog/[slug] page, and add the posts to sitemap.xml.
Base44 may ask a few optional questions about your design, such as what kind of site the blog is joining. We clicked Skip all.
When it finished, Base44 summarised what it had built: an editorial home page, a /blog archive, article pages, a signed webhook that checks the signature and rejects old timestamps, a sanitiser for the article HTML, and Article and FAQ structured data. It also tested its own routes and sitemap. The home page it designed for us:
Base44 will ask you for a secret called TALKGEN_WEBHOOK_SECRET right away. Click Skip. You do not have the secret yet, because TalkGenAI only creates it in Step 3. Base44 itself warned that, without the secret, deliveries get an error until you add it.
Step 2: Publish your app and copy the address
Click Publish in Base44, then Publish again in the popover. Your endpoint address is your app address plus /api/talkgen-webhook, for example:
https://your-app.base44.app/api/talkgen-webhook
Our test used the free address Base44 gives you. The Publish popover and the "app is live" window also offer a custom domain. We did not test one.
You can check the endpoint is alive before doing anything else. A request with no signature should be refused, not ignored. On our app it answered {"error":"webhook secret is not configured"} with HTTP 500, which is the expected answer before the secret exists.
Step 3: Add the site in TalkGenAI
In TalkGenAI, go to Integrations, choose Custom site, click Add Site, paste your endpoint address, give the site a name, and click Create connection.
TalkGenAI now shows your signing secret. It is shown only once, so copy it. Do not paste it into the Base44 chat or into any public file.
Step 4: Add the secret to Base44
Go back to Base44 and type: Add a secret named TALKGEN_WEBHOOK_SECRET. Base44 opens a private form. Paste the secret there and click Submit Secrets.
Step 5: Publish again
After you save the secret, publish your app again. In our run, an unsigned request to the live endpoint changed from "webhook secret is not configured" (HTTP 500) to "missing signature headers" (HTTP 401) once the new version was live. That is the answer you want: the live site now has the secret and is checking signatures.
We republished before sending the first test event, so we do not know whether Base44 would have worked without it. On Lovable, skipping it made the first test fail with HTTP 500, so we recommend you do it too.
Then go back to TalkGenAI and click I saved it, test and continue. TalkGenAI sends a test event right away. Ours passed on the first try:
TalkGenAI then asks how to publish: as a draft, or live. Choose Save as a draft for your own site, so you read each article before it goes out. We chose Publish live for the demo, so you can see the result.
Step 6: Write and publish your first article
In TalkGenAI, open Create Article, enter a topic, choose the length, and generate. We used a short article, 736 words. Not sure what to write about? Pick topics by the job your customer is trying to get done, as we explain in SEO for SaaS: pick keywords by the job. When the article is ready, click Publish to my site and choose your Base44 site.
TalkGenAI warned us that this connection was set to publish live, so the article went public with no review.
Step 7: Check that it worked
Open /blog on your site. Your article should be listed, and its own page should open.
Check that search engines can read it. Some sites built with AI tools send search engines an almost empty page that fills in only in the browser. We checked the raw page our demo site returns, once with a Googlebot user agent and once with a plain one. Both returned the same page (31,492 bytes). It contained the title, the meta description, one h1, four h2 headings, 23 paragraphs (about 4,800 characters of visible text), and two blocks of structured data (BlogPosting and FAQPage). The sitemap listed the article too.
That is what we saw on our demo site. It does not guarantee Google will index or rank a page, and we do not promise that. The structured data is also what AI assistants such as ChatGPT, Claude and Gemini can read when they look at a page. We can't promise they will cite you. For more on how AI assistants choose what to quote, see LLM SEO: what actually gets cited by ChatGPT. You can run the same check yourself: view the page source of one article and look for your headline and text in it.
Two things we found missing. The post page had no canonical link tag, and /robots.txt returned a 404 (not found). Neither stops the blog from working, but you can ask Base44 to add both. We did not run this prompt, so read what it builds:
On every /blog/[slug] page add a <link rel="canonical"> with the full address of the page. Add a /robots.txt that allows all crawlers and points to /sitemap.xml.
Then connect Google Search Console, so you can see which pages get clicks and decide what to write next: Google Search Console + AI agent: what to write next.
If something goes wrong
- Test event says HTTP 500 or "webhook secret is not configured": the secret is missing on the live site. Add it (Step 4) and publish again (Step 5).
- 401 or "Invalid signature": the secret in Base44 does not match the one TalkGenAI gave you. Remove the connection in TalkGenAI and add it again to get a new secret.
- The article is not on your blog: check whether it was sent as a draft. Only posts marked "publish" are shown.
- Slug rejected: slugs may contain only letters, numbers and hyphens.
Other ways to add a blog to Base44
You can ask Base44 to build a blog by hand and write the articles yourself. That gives you full control, but you write and maintain the content. You can also use a hosted blog service that connects to your site. The approach in this guide is for when you want articles to arrive on their own and you are happy to run the blog on your own app.
Questions
Do I need a custom domain? The steps work on the address Base44 gives you, and that is all we tested. Base44 offers a custom domain from the Publish popover. We did not test one or check how it affects search.
Does this use Base44 credits? Building the receiver is a normal Base44 request. We did not measure how much it used, or whether incoming webhook requests count, so check the usage page in your Base44 workspace.
Can I edit an article after it is published? The setup prompt tells Base44 to match posts by their ID, so a re-sent article should update the same post and not make a copy. We tested this on Lovable, not on Base44. To refresh older posts later, see How to update old blog posts.
Will this make my site rank on Google? No tool can promise that. A blog gives you pages to be found, and the quality of the writing matters. We only checked that your pages can be read.
Does it work with Lovable or other builders? Yes for Lovable, we have a step-by-step guide: Lovable SEO: how to add a blog that brings visitors to your app. Any site that can receive a signed webhook can use the same connection. If your site runs on Webflow, Framer, Wix, Shopify or WordPress, see our guides for Webflow, Framer, Wix, Shopify and WordPress.
Related guides
- Lovable SEO: how to add a blog that brings visitors to your app
- SEO for SaaS: pick keywords by the job, not competitors
- LLM SEO: what actually gets cited by ChatGPT
- Google Search Console + AI agent: what to write next
- How to update old blog posts: which ones, what to change
- AI Overviews SEO: how to get cited by Google
- All TalkGenAI guides
The short version
- Paste the setup prompt into Base44 and skip the secret form.
- Publish, and copy your endpoint address.
- Add the site in TalkGenAI and copy the secret.
- Add the secret in Base44.
- Publish again, then send the test event.
- Write your first article and publish it.