AI Engineering line, station 3 of 8
Run and Grow Your Site
Give your live site its own domain, e-mail that lands in the inbox, analytics, search, ads that pay, nightly reports that run themselves, and a monthly routine that keeps it safe and cheap.
- 6lessons
- 2.5 hto read and do
- Beginnerlevel
- 6podcast episodes
Tools you'll use in this course
The lessons open these with a template ready. They work for your own job too, no course needed.
About this course
A site on a vercel.app address is a start. A site people find, trust and come back to needs more: its own domain, e-mail from that domain that does not land in spam, analytics and Google Search Console so you know who comes and how they found you, ads if it should earn money, and reports that tell you every night how it is doing. This course walks you through each of those, the same way Kolom itself is run: DNS at Cloudflare, e-mail through Resend, Google Analytics, Search Console and AdSense, and scheduled jobs in Supabase.
You keep working on Mangrove Kitchen, the recipes-and-offers site for Mangrove Market (the fictional grocery chain used across Kolom) that you launched in Build and Launch a Site with AI. By the end it lives at its own domain, sends sign-in mails and a weekly offers e-mail from its own address, shows up in Google search with a sitemap, can show ads with consent handled, and e-mails its owner a short report every night.
As before, you write no code by hand. You buy and point a domain, copy DNS records between dashboards, ask your AI agent for small changes, paste the SQL it writes into Supabase, and check each result. The last lesson is the owner's routine: logs, rollbacks, backups, costs, key rotation, and when to call an engineer.
What you will be able to do
- Buy a domain, move its DNS to Cloudflare and point it at Vercel with the right records and proxy setting
- Send e-mail from your own domain with Resend, with SPF, DKIM and DMARC passing and Supabase sign-in mails sent through it
- Set up Google Analytics and Search Console, publish a sitemap and read the first reports
- Apply for AdSense, publish ads.txt, handle consent, and place ads without hurting the site
- Schedule a nightly report and owner alerts with pg_cron and pg_net calling a protected route with a secret
- Run a monthly owner routine: logs, rollbacks, backups, costs and free-tier limits, key rotation, and when to call an engineer
Syllabus
6 stops, about 2.5 h in total. Each stop fills in when you complete the lesson.
Your own domain, with DNS at Cloudflare
Mangrove Kitchen works at mangrove-kitchen.vercel.app, but nobody remembers that address. In this lesson you buy a domain, let Cloudflare run its DNS, and point it at Vercel so the site opens at its own name over HTTPS.
DNS and domainsRunning a website
E-mail that arrives: Resend, SPF, DKIM and DMARC
Sign-in links, the weekly offers e-mail and your own reports are only useful if they reach the inbox. This lesson sends Mangrove Kitchen's mail from its own domain through Resend, with the three DNS checks that keep it out of spam.
E-mail deliverabilityDNS and domainsRunning a website
Analytics, Search Console and your sitemap
You can't grow what you can't see. This lesson connects Mangrove Kitchen to Google Analytics and Google Search Console, publishes a sitemap so Google finds every recipe, and shows you how to read the first reports without drowning in numbers.
Web analyticsSEO basicsRunning a website
Earning with ads: AdSense, ads.txt and consent
Ads can pay some of your site's bills, but only after Google approves the site, and only if visitors don't leave because of them. This lesson walks you through getting Mangrove Kitchen ready, applying, publishing ads.txt, handling consent and getting paid.
Ads and consentRunning a websiteSEO basics
Reports and alerts that run themselves
You shouldn't have to open five dashboards to know how your site did yesterday. This lesson sets up a nightly report e-mail for Mangrove Kitchen, sent by a scheduled job, through a route that only answers when it gets the right secret.
Scheduled jobsRunning a websiteE-mail deliverability
Keep it healthy, safe and cheap
A live site needs a little care every week and a short review every month. This lesson gives you the owner's routine for Mangrove Kitchen: where to look when something breaks, how to roll back, backups, costs, key rotation, and when to call an engineer.
Running a websiteApp security basicsScheduled jobs
Capstone: Run Mangrove Kitchen like an owner
A realistic project with a rubric and a model answer.
Final exam and certificate
10 questions drawn at random, 70% to pass.
Capstone project
Run Mangrove Kitchen like an owner
Mangrove Kitchen is live on a vercel.app address, and Imran wants it ready for real visitors before the festival rush. Give it its own domain with DNS at Cloudflare, send sign-in mails and a weekly offers e-mail from that domain through Resend with SPF, DKIM and DMARC passing, connect Google Analytics and Search Console with a submitted sitemap, publish ads.txt and a consent setup if you apply for ads, and schedule a nightly owner report e-mail with pg_cron and pg_net calling a route protected by a secret. Finish with a one-page owner's runbook: where the logs are, how to roll back, how backups work on your plan, what each service costs, when keys get rotated, and the signals that mean it is time to call an engineer. Your own site of the same size works too.
You will hand in
- The site live on its own domain over HTTPS, with www and the bare domain both reaching it
- Sign-in mails and one other e-mail sent from your domain, with SPF, DKIM and DMARC shown as passing
- A sitemap at /sitemap.xml submitted in Search Console, and Google Analytics receiving visits
- A scheduled nightly report e-mail, with the route protected by a secret and the schedule written in UTC
- A one-page owner's runbook covering logs, rollback, backups, costs, key rotation and when to call an engineer
Check what you know
Already know some of this? Answer 6 quick questions, one from each lesson, and we will mark the lessons you can skim. It takes about 3 minutes and nothing is graded.
Questions
Do I need to finish Build and Launch a Site with AI first?
It helps, because this course starts from a site already live on Vercel with a Supabase database. If you have a live site built another way, most lessons still apply; the scheduled reports lesson assumes Supabase.
How much will a domain and these services cost?
A domain costs a yearly fee that depends on the ending (.com, .net, a country ending) and the registrar. Cloudflare, Resend, Google Analytics, Search Console and AdSense all have free plans or are free. Once a site earns money, check whether your hosting plan allows commercial use: Vercel's Hobby plan, for example, is for personal, non-commercial projects. Prices and limits change often, so read each pricing page.
Will ads really make money?
Only with steady traffic. Earnings depend on how many people visit, where they live and what the pages are about, and many small sites earn little. Google also has to approve the site first. The lesson covers how to apply, how payment works and how to keep ads from driving visitors away.
Is this how Kolom runs?
Yes. Kolom's domain is on Cloudflare, it is hosted on Vercel, sends e-mail through Resend, uses Google's tools for search and ads, and e-mails its owner a nightly report from a scheduled database job. The lessons teach the same setup on a smaller site.
Is there an exam and a certificate?
Yes, and both are free. The exam mixes scenario questions with practical tasks such as matching DNS records to their purpose or ordering the steps to verify an e-mail domain. You pass with 70% on the questions and an average of 70% on the tasks.
Is it really free?
Yes. Every lesson, podcast episode, exercise, quiz and final exam is free, so you can finish the course without paying. The labs and their templates for real work are free too. Plus and Premium add the verifiable certificate, every lab challenge, weekly extras and a mentor on top, and they never lock the tools or the courses.
How long does it take?
Each lesson shows an honest time for reading and doing. Most people finish a course in two to four weeks at three or four hours a week.