Case · Pilot · Aug 2026 – present
Beyond Dental Clinic, Gwacheon — website SEO/GEO and a new blog
A website built in 2023, made readable to search engines and AI through code, with its design left as it was.
The clinic is owned by our founder. We use it as our pilot site and say so openly. This page describes our work only. It does not promote the clinic or its treatments, and we do not publish search rankings or AI recommendation results.
1. Audit & diagnosis
The website was built in 2023. Generative engine optimization (GEO) was first proposed only at the end of that year, so clinic websites of the time were designed for people: photos and layout came first, and machine-readable structure was not on the checklist. This site had good photography and design, but most headings and much of the text were images, leaving little for a machine to read.
Before changing anything, we measured the following and recorded it as a baseline.
| Area | Finding |
|---|---|
| SEO | No heading tags (H1–H3) and no image alt text on any of nine pages. One-word page titles. No internal links between treatment pages. A duplicate page |
| Indexing | Sitemap unread by search engines for 11 months. Old http copies and an empty layout page mixed into the index |
| AEO | No text that answers questions directly, such as definitions or FAQs |
| GEO · E-E-A-T | No page showing who wrote the information. Credentials worded differently from the documents; superlatives |
| Structured data | Classified as a generic Organization, not a dental clinic. No dentist or treatment data |
| Consistency | Address written differently even within the site. Name and categories differed across website, maps and Google Business Profile. Former clinic names still live elsewhere |
| AI access | Some AI crawlers blocked by the hosting platform’s firewall, which the site cannot change |
| Measurement | No analytics; no way to count clicks that lead to enquiries |
2. Fixes & improvements
Four rules: keep the design · fix it in code inside the site builder (header code, code widgets, page settings) · check every change on the live page · nothing that is not true.
SEO — a sign search engines can read
- H1–H3 heading structure on home and eight treatment pages, desktop and mobile. Image headings kept and wrapped in heading tags; new heading images made in the original typeface, colour and size
- Alt text on main pages, describing what each photo shows
- New titles and descriptions for nine pages, written after reading each page. One site title, letter for letter, across website, maps and blog
- Two-way internal links between related treatment pages
- Sitemap resubmitted, indexing requested page by page, empty pages excluded, main-address issues resolved
<!-- Design unchanged: an image heading wrapped in a heading tag -->
<h2><img src="…/title-gum-treatment.png" alt="Gum treatment · periodontal curettage"></h2>
AEO — a help desk that answers questions
- A one-paragraph definition at the top of treatment pages
- FAQs published as text, not images, and repeated in structured data — screen and data match exactly
- The page says who provides the treatment
- Directions as an address / subway / bus table — the same text lived in four places on the site, and all four now match
GEO — a source AI can trust and cite (E-E-A-T)
| Element | What we did |
|---|---|
| Experience | Blog articles start from real clinical records |
| Expertise | A new page for the lead dentist: education, training, specialist certification; certificates as reduced copies with personal details hidden |
| Authority | Papers, lectures, society roles, co-authored textbooks; the website profile and the blog author page link to each other |
| Trust | Credentials corrected against documents and undocumented claims removed; superlatives and comparisons removed; industry relationships listed openly |
Structured data — clinic, person and posts in one graph
Organization→Dentist: phone, opening hours by day, address, area served, legal name, external profiles- Former clinic names and opening month, so records under old names join the same clinic
- The dentist’s
Personand the clinic point at each other; every blog post names the dentist as author and the clinic as publisher; books asBook - Page-level data:
MedicalWebPage→MedicalCondition→MedicalTherapy, FAQs, breadcrumbs - Zero errors in Google’s Rich Results Test, with person and clinic linked
{ "@type": "Dentist", "@id": "https://beyonddh.com/#dentist",
"employee": { "@id": "…#person" } }
{ "@type": "Person", "@id": "…#person",
"worksFor": { "@id": "https://beyonddh.com/#dentist" } }
{ "@type": "BlogPosting",
"author": { "@id": "…#person" },
"publisher": { "@id": "https://beyonddh.com/#dentist" } }
Consistency — the same clinic everywhere
- Address unified in 44 places on the site
- Clinic name matched letter for letter on website, maps, blog and Google Business Profile; inaccurate profile categories removed and description rewritten
- A list of outside pages still showing former names, with correction requests
Blog — a channel AI can read
- A blog open to the AI crawlers the website blocks: blog.beyonddh.com
- Six series planned first, so search engines and AI read the articles as connected topics; three articles and an author page published
- Written house rules: tone, formats AI can quote, disclosure of industry relationships, medical advertising law. Clinical claims are checked against published sources before use
3. Measurement & upkeep
- Baseline comparison — the same measurements, taken again the same way
- GA4 — website and blog in one property; phone, KakaoTalk and booking clicks as events; clinic-internal traffic excluded
- Weekly Search Console reports — every Monday: queries, pages and index status against last week, with alerts when a top page slips
- Weekly AI-answer monitoring — the same questions to Claude, ChatGPT and Gemini every week. We record how the clinic is described, find the source of anything inaccurate and fix it
We do not publish rankings or visibility results here, because they could work as advertising for the clinic.
How we work
A dentist decides what is true and what gets published; AI agents handle diagnosis, code and cross-review. Every change is logged and checked again on the live page after publishing.