WebforAI: One Landing Page for Three Industries, From Plan to Production in a Day

Challenge

WebforAI prepares a company’s official information so that AI can read and cite it accurately. The main domain webforai.kr carried a clinic-only landing, and as separate services for companies and local businesses appeared, the top level needed a landing that routes three industries from one screen. Three conditions applied: keep the clinic landing alive on a subdomain, keep the contact form that the company homepage borrows from this domain working, and break none of the URLs already in circulation.

Approach

1. A plan and a decision list. One page covered who the site is for, the first-screen sentence, the three destinations, the contact path, and the measurement and indexing policy. Screen copy used only approved sentences, and anything new was listed separately for approval. Ten open decisions were written down with a recommendation for each.

2. Five drafts, four rejections. A light gradient with three rows, a dark three-panel layout, oversized typography, and an enterprise hero were rejected in turn. The fifth draft took a video of a real service’s new homepage as the reference and copied its structure as is: a warm off-white canvas, a centered headline, an aurora gradient card that fills the screen, and three tabs on the card that act as the industry selector, each changing the color and the card. The industry word in the headline rotates with the tabs.

3. Product screens as the visuals. The visuals inside the cards are the actual screens of each service, not diagrams. The clinic tab carries the header, score rings, and item rows of the AI answer readiness report in their real structure, the local business tab shows the confirmation step of the shop website builder, and the company tab shows an AI chatbot citing the official answer hub as a source. Layers are separated by shadow only, with a single accent color. The five-step section below follows the same rule: a title, one short line, and a product screen fragment per frame.

4. A static build with a publishing gate. The site is static with no external packages so it can move to any host. The build fails if it finds banned terms, em dashes, emoji, a missing Naver verification tag, broken links, or a wrong industry destination. The three destinations live in one config file, so a new address later means changing one line.

5. The switch. The company guide page is served from the same build by host-based routing, 13 legacy URLs redirect permanently to the clinic landing, and only the one contact endpoint is forwarded to the previous project. After a local preview review and verification on the project URL, the domain moved. The post-switch checklist ended with a real submission through the company homepage’s contact form.

Result

Plan to production took one day. webforai.kr now routes three industries, and the clinic landing runs unchanged at infinith.webforai.kr. Neither the company homepage’s contact form nor any circulated URL broke. The rejected drafts, the feedback, and the deployment procedure are documented in the repository so the next person does not repeat the same judgments.