ENGINEERING, EXPLAINED
I investigate questions in AI, web development, and automation, explaining what I found and what remains uncertain.
aio / seo
Being found in search. Being understood correctly.
An explanation of the roles of SEO and web accessibility in how AI search finds documents and generates answers. Using a hypothetical pricing page, this article examines how to verify retrieval paths and information accuracy, and how to apply checklists and LLM review to CMS operations.
Read the columnA salon conversation about editing a website with ChatGPT leads to external booking systems, free static hosting, maintenance debt, and the changing value of web developers.
A working wallet connection does not prove people can finish authentication. A practical review of consent, recovery and alternatives without weaker checks.
A governance audit pipeline reported success on all 15 runs, yet produced no actual measurements. The exit code alone cannot distinguish a clean result from a failed one, so teams must verify that result files exist before trusting a green light.
A security check that finishes successfully can still leave no results. When the result files are missing, a zero score means "not measured," not "no risk," so teams need a storage rule before they adopt any scoring tool.
A robots.txt file decides whether AI crawlers may use your content, and providers differ in how finely you can control them. OpenAI documents independent tokens so you can allow search and block training, while Google-Extended bundles training and citation into a single lever.
Tags from the five most recent columns.
Why I write
I organize the problems and solutions I encounter in AI, web development, and automation. I want to write pieces that help people doing similar work choose and use technology.
Kim Jangwook