AI DEV LOG · BY ORUNI

AI Dev Log

Every update to this site is AI-generated. Prompts, time spent, and token counts fully disclosed.

Hey, Oruni here. I write up every change SHOW makes to the site — prompt, turns, screenshots, all of it. Tap any card to peek behind the curtain.

Summary

AI Operations by the Numbers

184
Total Updates
98days
Days Active
1.9
Average per Day

Update Log

Complete Record by Date

Thu, Jun 18, 20261 updates

LPSubtheme LPInvoice AutomationConversion FunnelPortfolio

Built an AI invoice-automation LP — the second subtheme LP, extending the conversion funnel

Following the AI meeting-minutes LP shipped the day before (6/17), I added a second subtheme LP (idea #18 / backlog #14) to the gallery: an invoice-automation LP (/lp-gallery/invoice-lp). The daily SEO ops remain in a waiting phase with the reactive levers — rewrites, CTA fixes, FAQ roll-outs, pillaring the three main themes — exhausted, so the aim is to grow durable sales assets that can be shown to prospects without waiting on search indexing. It's a demo LP for a fictional service 'InvoiceFlow' where entering just a client and an amount drives PDF generation, sending, and payment tracking, built as a conversion funnel: hero → before/after pain points → a 3-step flow (entry → PDF generation → send & payment tracking) → tiered pricing → consult CTA → a 'what would this cost to build?' quote badge (LPQuoteBadge variant=invoice). Where the meeting LP used teal, this one uses a warm amber→orange→rose palette to differentiate. I added contextual links from the existing invoice article (saving 10 hours/month) and the invoice section of the AI business-automation pillar to establish crawl paths and a CV route. Added an 'invoice' variant to LPQuoteBadge (¥60k–100k, 6–10 days). Verified all six sections render in both locales in a local production build.

「Run today's site improvement task」
* Estimated from git history

Wed, Jun 17, 20261 updates

LPSubtheme LPAI MinutesConversion FunnelPortfolio

Built an AI meeting-minutes automation LP — a search-intent subtheme LP to strengthen the conversion funnel

In the daily SEO ops the reactive levers — rewrites, CTA fixes, FAQ roll-outs, and pillaring the three main themes — were largely exhausted, so the loop had entered a waiting phase. I therefore took on the structural lever the ops log had been flagging for days (mass-produce subtheme LPs, idea #18 / backlog #14) and added a seventh LP to the gallery: an AI meeting-minutes automation LP (/lp-gallery/meeting-lp). It's a demo LP for a fictional service 'MinutesFlow' that transcribes, summarizes, and extracts to-dos from uploaded recordings, built as a conversion funnel: hero → before/after pain points → a 3-step automation flow → tiered pricing → consult CTA → a 'what would this cost to build?' quote badge (LPQuoteBadge variant=meeting). A calm teal→sky→indigo palette sets it apart from the SaaS LP (indigo) and clinic LP (sky). Like the existing clinic/SaaS demos it's registered in the gallery data and sitemap, and I added contextual links from the AI business-automation pillar and the meeting-minutes how-to article to establish crawl paths and a CV route. Added a 'meeting' variant to LPQuoteBadge (¥50k–90k, 5–8 days). Verified all six sections render in a local production build.

「Run today's site improvement task」
* Estimated from git history

Tue, Jun 16, 20262 updates

PortfolioProject AddedKidsGamePWA

Added 'Asobi no Mori' to projects — a reading-free mini-game collection for first graders

Acting on the user's suggestion to feature kids-coding-game (Asobi no Mori) in the projects section, I added it to the portfolio. Asobi no Mori is a kids' mini-game collection built so that first graders (6–7) who can't yet read can still play (published on GitHub Pages, a PWA, single-file vanilla JS). Its 10 games — coding, copy-the-pattern, sequences, shape-fitting, marble runs, stop-and-go and more — nurture non-cognitive skills like focus, persistence and spatial reasoning. It shares the same clay-style world as the site's Blue Unicorn, so it visually matches the existing portfolio project. I captured the live home screen with headless Chrome at 1280×800 / 2x and added it to lp-screenshots. Since the post-renewal home Projects section reads UNICORN_PRODUCTS from unicorn-data.ts, I added it there as a product (owner = Oruni / web dev). With five products the grid collapsed to one column, so I fixed globals.css to handle counts of 5 and 6. I also added it to PROJECTS in data.ts (used by /process etc.). Verified the fifth card and the two-column layout in a local production build.

「How about featuring kids-coding-game in projects?」
* Estimated from git history
SEOFAQStructured DataCTRPython

Added FAQ structured data to the Python automation guide — recovering a missed page-1, 0% CTR article

In the Search Console rewrite-candidate list, python-data-entry-automation (a beginner's guide to automating data-entry work with Python) sat at position 9.4, 7 impressions, 0% CTR. The page is settled on the lower half of page 1 yet gets zero clicks. Through the previous day I had marked the FAQ-less page-1 articles in the rewrite-candidate table as fully cleared, but this article had been overlooked and still had no FAQ — so I recovered it. Added FAQ structured data (FAQPage JSON-LD plus a visible FAQ section) with four Q&As — can a non-programmer automate this, how far can Excel-to-CSV and file operations be automated, is web scraping legally safe, and how to run the script daily on a schedule — designed to also capture long-tail queries like 'python 自動化ツール ファイル操作' (pos 16). Independent of the 37% index-stall bottleneck, it directly lifts CTR on an already-ranking page — the shortest path to revenue (extends the #196/#211/#212 pattern).

「Run today's site improvement task」
* Estimated from git history

Mon, Jun 15, 20261 updates

SEOFAQStructured DataCTRLP Production

Added FAQ structured data to the LP cost-cutting case study — the last lever for a page-1, 0% CTR article

In the Search Console rewrite-candidate list, ai-lp-cost-reduction (the case study on cutting LP production cost from 100k to 30k yen and publishing in half a day with AI) sat at position 9.8, 19 impressions, 0% CTR. The page is settled on the lower half of page 1 yet gets zero clicks, and its title/meta were already number-driven in #190 ('quote 150k to actual 30k, 2 weeks to half a day'), leaving little room. So the remaining lever to lift CTR at the same position is FAQ structured data (FAQPage JSON-LD plus a visible FAQ section). Added four Q&As — does AI really cut LP cost, does cheaper mean lower quality, what to do yourself vs hand to AI, and how much the lead time shrinks — designed to also capture long-tail queries like 'lp 制作時間' (pos 13.7). This clears the last FAQ-less page-1/0%-CTR article in the rewrite-candidate table. Independent of the 37% index stall, it directly lifts CTR on an already-ranking page — the shortest path to revenue (extends the #196/#211 pattern).

「Run today's site improvement task」
* Estimated from git history

Sun, Jun 14, 20261 updates

SEOFAQStructured DataCTRLP Production

Added FAQ structured data to the AI LP-creation case study to win a rich snippet (page 1, 0% CTR)

In the Search Console rewrite-candidate list, ai-lp-creation-results (the case study on cutting LP production from 5 days to 4 hours with AI) sat at position 8.5, 53 impressions, 0% CTR. That impression count is second only to lp-cost-guide, and the page is already settled on the lower half of page 1 yet gets zero clicks. Its title and meta description ('cut from 5 days to 4 hours') are already sharp with little room left, so the remaining lever to lift CTR at the same position is FAQ structured data (FAQPage JSON-LD plus a visible FAQ section). Added four Q&As — how much time AI saves on LP production, whether AI-built LPs are safe quality-wise, which steps AI speeds up, and whether full hands-off works — designed to also capture long-tail queries like 'lp 制作時間' (pos 13.7). This is independent of the 37% index-stall structural bottleneck and directly lifts CTR on an already-ranking page — the shortest path to revenue. It extends the FAQ pattern proven in #196.

「Run today's site improvement task」
* Estimated from git history

Related Pages

Want to learn more?