Case study · Cosmetic dermatology · Beverly Hills and New York
A content engine that turns every video into pages that rank.
Dr. Jason Emer is one of the most recognized cosmetic dermatologists in the world. We rebuilt jasonemermd.com, then built the engine behind it: every new video becomes a blog post, a landing page, and search-ready copy, drafted by AI, approved by the practice, live within twenty minutes, and submitted to Google. Underneath, the website intake now runs into Salesforce.
By the numbers
The engine
From one video to a page that ranks, in seven steps
Dr. Emer films constantly. Before, each video lived on YouTube and nowhere else. Now every one becomes a set of pages on his own site, and his team only has to say yes.
The guardrails
- Quotes only what Dr. Emer said in the video
- Never names or identifies a patient
- Never promises a result
- Nothing goes live without a person approving it
A new video goes up
The engine checks Dr. Emer’s YouTube channel every hour and registers anything new.
The transcript is pulled
Captions come down with the video, along with its thumbnail and any before-and-after frames.
AI drafts the whole package
One draft per video: a blog post, a treatment landing page, a YouTube title, description, and tags, and a Google Business post, all written from what Dr. Emer actually said.
Thumbnails and hero art are made
Face detection and background removal cut Dr. Emer out of the frame and set him into branded templates for results, education, and Q&A.
The practice approves it
Every package lands in a review hub. Nothing publishes until a person approves it, and change requests are rewritten field by field.
It goes live in 20 minutes
Approved pages publish with their meta title, description, and schema written for them, and the sitemap updates itself.
Google is told
New pages are submitted to Google Search Console for indexing, and a monitor flags anything approved that is not live within 26 hours.
What one video becomes
Six pieces of search-ready content, every time
Blog post
Written from the transcript, with Article schema and its own hero image.
Landing page
A treatment page with MedicalProcedure, Physician, and VideoObject schema.
YouTube copy
A search-first title, description, and tags for the video itself.
Google Business post
Drafted with every package for the practice’s map listings.
Thumbnail and hero
Branded art built from the video and approved brand assets.
Metadata
Title, description, canonical, and social tags, generated for every page.
The migration
1,574 pages moved without losing a ranking
The old WordPress site carried years of treatment pages, articles, galleries, and patient stories. We moved every one to a fast new build, kept their addresses, redirected the ones that changed, and cut the image weight by almost three quarters.
- 8,858 media files moved to fast storage
- 5,143 images converted to modern formats
- Breadcrumb and page schema on every route
- A sitemap that adds approved pages automatically
Search Console
Every problem Google reported, worked through by hand
A migration this size shakes loose years of old errors. We pulled every issue Google Search Console reported and resolved them one batch at a time, with the evidence kept for each.
Salesforce and intake
The website now feeds Salesforce directly
We merged the website into the practice’s Salesforce: consultation handoffs, phone verification, and payment records are Salesforce objects now, moved by automated flows, so the team works from Salesforce records instead of an inbox. The paid consultation flow on the right was rebuilt end to end and validated before launch.
What we fixed
- Intake is carried through the policy and checkout steps instead of being lost between them
- Duplicate payments are blocked
- Every payment return is verified against Salesforce before a patient sees "confirmed"
- Consent boxes are never pre-checked
- Free consultation requests land in Salesforce as leads, with bot and spam protection in front
Choose a consultation
Free request or paid consultation, by team and treatment.
Intake, saved as they go
Encrypted drafts mean nothing is lost if a patient steps away.
Sign the financial policy
An e-signature with a signed proof on the record.
Verify their phone
A text code confirms the number before any payment.
Pay a secure deposit
Salesforce generates the payment link, and the site checks the result with Salesforce before confirming.
Hand off to a coordinator
A handoff record is created in Salesforce and assigned to the coordinator team.
Built to be trusted
Safe by default, because it is a medical practice
- Bot protection and spam checks on every form
- Intake drafts encrypted, phone and policy proofs signed
- Test builds can never touch live payments or the live Salesforce
- 80+ automated checks that verify redirects, pages, and flows before release
- AI never names a patient, never promises results, and only quotes what Dr. Emer said
Where it stands
The engine is running. The results publish here as they land.
New videos keep turning into pages every week. We publish outcomes with the practice’s sign-off, the same standard we hold for every case study on this site.