Web & Content Platform
A large share of your visitors are no longer people but AI crawlers. A site that cannot be read is a site that does not exist.
Built on the premise that an AI crawler reads the page before a human does.
What usually goes wrong
Invisible to search
A client-rendered site means the crawler never reads the body text, and without structured data nothing gets cited.
Every edit needs a developer
Publishing one reference means emailing the agency that built the site.
Slow and inaccessible
Mobile LCP is over four seconds, and accessibility costs points in public tenders.
How we approach it
- 01Rendering strategyKey pages are served as static or server-rendered HTML. We do not ship client-only rendering.
- 02Structure for machinesSchema.org, llms.txt, and question-form H2 headings followed by a direct answer, so there is a unit an AI can quote.
- 03Content independenceA headless CMS lets your team publish references, insights and job posts without a developer.
- 04Performance and accessibility budgetLCP 2.5s, INP 200ms and CLS 0.1 are fixed as release criteria, with KWCAG items checked.
What you receive
| Responsive site | Desktop, tablet and mobile, in Korean and English |
|---|---|
| Headless CMS | Content type design, permissions, preview |
| SEO and AEO setup | Meta, OG, canonical, sitemap, hreflang, Schema.org and llms.txt |
| Analytics and conversion design | GA4 with server-side events and six defined conversions |
| Legal notices and accessibility | Privacy policy, terms of use, separated consent, KWCAG checklist |
How it runs
| Strategy and IA | 2 weeks | Personas, sitemap, message |
| Content | 2 weeks | Copywriting - in practice the critical path |
| Design | 2 weeks | Design system, home and inner page concepts |
| Build | 3 weeks | Markup, CMS integration, localisation |
| QA and launch | 2 weeks | Performance, accessibility and SEO checks, deployment |
Frequently asked
How does answer-engine optimisation differ from SEO?
SEO competes for the click in a results page. AEO is about being quoted accurately inside the answer an AI produces. A question-form subheading followed by a two or three sentence direct answer becomes the unit that gets quoted.
Do we really need llms.txt?
It is not an official standard and it does not feed into ranking directly. But it costs almost nothing to produce and has an indirect effect on the chance of being cited, so we recommend it as a low-cost, low-risk item.
Can we publish content ourselves?
Yes. References, insights and job posts are created and edited in the CMS, checked in preview and then published. No development release is involved.
What structure do you recommend for multiple languages?
A subdirectory such as /en/. Domain authority stays in one place and hreflang handling is simpler. English should be written as separate copy rather than translated line by line.
How far do you go on web accessibility?
Alternative text, keyboard access, contrast ratio and focus indication are checked against the core KWCAG items during development. Private sites in Korea are also covered by anti-discrimination legislation.
How is the performance target guaranteed?
LCP 2.5s, INP 200ms and CLS 0.1 at the 75th percentile of real user data are release gates, and a release is held if they are not met.
A 30-minute call first
We do not quote a rate before the scope is defined. We map your current flow on a call and reply with a draft architecture and a staged cost range within a week.