Project kickoff and first version of the site (approximate date, recalled — no technical evidence exists for this stage).
The project in three acts
Context
A years-long relationship, not a single delivery
Monono Café is a specialty coffee shop in Querétaro. Its website started around 2022–2023 and went through at least two different stacks and a hosting change before landing, since July 2025, under verifiable version control.
The 2022–2025 stage is documented here as it's recalled, with no technical evidence to back it up — unlike the rest of the case, which is verified against the current repository's commit history and Google Search Console.
The challenge
A lost version and a database that kept falling asleep
At some point between 2023 and 2025 the site was redesigned in Astro, but that version was never pushed to a repository. When hosting changed, the code was lost entirely, and the previous HTML, CSS, and JavaScript version had to be recovered.
Once under version control, two more problems showed up: the site had Google indexation issues (detected in September 2025), and months later, the owner's event-management admin panel started failing because Supabase's free tier was pausing the database from inactivity.
Solution applied
Recovery, technical SEO, and a custom tool for the owner
Recovery and version control
- Site recovered under Git after the Astro version was lost (Jul 2025)
- Automatic deploys on Vercel on every push to the repository
Technical SEO and local positioning
- SEO optimization with local Querétaro keywords and Search Console verification
- Diagnosis and fix of Google indexation issues (Sep 2025)
- JSON-LD structured data and crawl optimization for AI crawlers (Aug 2026)
Custom system and availability
- Event-management system on Supabase with a live preview for the owner (Dec 2025)
- GitHub Actions keep-alive workflow to stop Supabase's free tier from pausing the database (Jul 2026)
Migration to Astro (Aug 2026)
- Technical evaluation of Next.js vs Astro to decide the target stack
- Full frontend migration to Astro, now live in production
Verified results
Impressions accelerating since the indexation fix
The chart shows a single continuous growth phase: no data is available before September 2025 in this Search Console property, which coincides with an indexation issue being fixed. Since then, impressions show a sustained acceleration trend through August 2026.
Organic clicks 706 Sep '25 – Aug '26 (~11 months)
Impressions 19.4K accelerating trend
Avg. CTR 3.6% Google Search Console
Avg. position 4.6 First page on Google
Project timeline
From lost code to a real pipeline
2022
2023
Initial connection to Google Search Console (recalled, not verifiable).
Site redesign in Astro. That version is lost after a hosting change, since it was never backed up to a repository (recalled).
2025
The HTML/CSS/JS site is recovered under Git version control — initial commit of the current repository.
Google Search Console verification and SEO optimization with local Querétaro keywords.
Diagnosis and fix of Google indexation issues — coincides with the start of the real historical data available in Search Console.
Supabase integration: a custom event management system with a live preview, built for the owner's own use.
2026
It's discovered that Supabase's free tier was pausing the database from inactivity; fixed with a GitHub Actions keep-alive workflow. Styles migrated to Tailwind.
JSON-LD structured data, crawl optimization for AI crawlers, clean URLs on Vercel, and Google Analytics 4 installed.
Full frontend migration to Astro, now live in production. Next.js and Astro were evaluated; Astro won as a content-driven site where SEO comes first and extra JS adds nothing.
Frequently asked questions
What you want to know about the Monono Café project
What technology powers the Monono Café site today?
The current site is built with Astro and TypeScript, styled with Tailwind CSS, with an event-management admin panel backed by Supabase and continuous deployment on Vercel connected to a GitHub repository. The frontend migration to Astro was completed on August 22, 2026; every change goes live automatically.
Why did the site move back to Astro after already losing a version built on it?
There was an Astro redesign at some point between 2023 and 2025, but that version was never pushed to a repository and was lost entirely when hosting changed. The site was recovered in HTML/CSS/JS and placed under version control on July 22, 2025. In August 2026, Next.js and Astro were formally evaluated for the project's next stage, and Astro won again: it's a content-driven site where SEO comes first, and the extra JavaScript Next.js brings isn't needed. This time the migration was versioned from the first commit.
What are Monono Café's verified organic results?
According to Google Search Console, over the ~11 months of history available in the current property (Sep 10, 2025–Aug 20, 2026): 706 organic clicks, 19,400 impressions, an average CTR of 3.6%, and an average position of 4.6. Impressions show a month-over-month acceleration trend. This period predates the August 22, 2026 migration to Astro, so it doesn't reflect its impact yet.
What problem did the Supabase GitHub Action solve?
Supabase's free tier pauses the database after inactivity, which took the owner's event-management panel offline. In July 2026, a GitHub Actions workflow was added that pings the database periodically to keep it always active.
Why was Astro chosen over Next.js for the frontend migration?
Both options were evaluated. Next.js pays off when a site needs complex client-side interactivity, but Monono Café is fundamentally a content site: storefront, menu, events, and business info. Astro ships static HTML by default and only loads JavaScript where it's actually needed, which favors local SEO and load times. The migration was completed on August 22, 2026 and is already live in production.
