by /
Definitive Guide · Personal Brand Ops
From One Email to a Live Personal Brand Site: The Exact Playbook
Someone replies “I’d love a personal website — here’s my domain.” That one line should trigger a complete, repeatable sequence: pull everything we already know about them, build their entity home, find out who their registrar is, hand them the exact DNS record to paste, and reply in plain language with one thing for them to do. This is that sequence — the SOP an agent (human or AI) follows every time, so the answer is always a finished site, not a scheduling email.
Most “can you build me a site?” requests die in back-and-forth. Someone asks, we ask for assets, they go quiet, and three months later nobody has a site. The fix isn’t working harder — it’s having a playbook so complete that the first reply already contains the finished site. Here’s the whole thing, start to live.
The trigger
“I would love to have a personal website. I have the domain [name].com.”
Nine words. Everything below is what happens next — ideally before they’ve finished their coffee.
The eight steps
1
Read the whole thread — not just the last message.
Who is asking, which domain do they actually control, and what do they want the site to do? People change their mind mid-thread (a
Who is asking, which domain do they actually control, and what do they want the site to do? People change their mind mid-thread (a
.com they lost becomes a .nl they own). Get the person, the live domain, and the goal straight before touching anything.2
Pull everything we already know.
Before asking them for anything, mine what exists: their brand audit and score, any bio, their business website, LinkedIn and socials, photos they’ve already sent. Most of the time we’ve already scored them — the site is 80% writable from that. Verify the load-bearing facts (degree, employer, numbers) against primary sources; an authority site with a wrong credential is worse than no site.
Before asking them for anything, mine what exists: their brand audit and score, any bio, their business website, LinkedIn and socials, photos they’ve already sent. Most of the time we’ve already scored them — the site is 80% writable from that. Verify the load-bearing facts (degree, employer, numbers) against primary sources; an authority site with a wrong credential is worse than no site.
3
Build the entity home.
One page that answers “who is this person?” in their words — hero with a real photo, the method or idea they own, proof (real testimonials, real citations), where their work shows up, and one clear next step. Add
One page that answers “who is this person?” in their words — hero with a real photo, the method or idea they own, proof (real testimonials, real citations), where their work shows up, and one clear next step. Add
Person schema with sameAs to every profile, alumniOf, and worksFor so Google and the LLMs can build their Knowledge Panel from a home they control. Follow the Personal Brand Score rubric.4
Identify the registrar — look, don’t assume.
Run a live lookup on the domain to see where DNS actually lives:
Run a live lookup on the domain to see where DNS actually lives:
dig +short NS theirdomain.nl
dig +short A theirdomain.nl
The nameservers tell you the registrar/DNS host — domaincontrol.com is GoDaddy, transip.* is TransIP, siteground.net is SiteGround, and so on. This decides which instructions they get. Never guess the registrar from the email.5
Generate the exact records for THAT registrar — and protect their email.
Default to the A-record method: point
Default to the A-record method: point
@ and www to the fleet IP and leave the nameservers alone, so mail (MX), calendar and everything else keep working. Use a nameserver switch only when we’re taking over the whole zone. Give them the specific values to paste — not “update your DNS.”
The rule that prevents disasters: if the domain also runs their email, changing nameservers can silently kill their inbox. One A-record change moves the website and nothing else. Ask about vanity email before any nameserver move.
6
Make sure the registrar how-to exists — write it if it doesn’t.
Link them to a screenshot-level guide for their exact registrar. We keep one for GoDaddy and one for TransIP. If the person’s registrar isn’t covered yet, that’s the signal to create the guide — then it’s ready for the next person on that host. The library grows itself, one request at a time.
Link them to a screenshot-level guide for their exact registrar. We keep one for GoDaddy and one for TransIP. If the person’s registrar isn’t covered yet, that’s the signal to create the guide — then it’s ready for the next person on that host. The library grows itself, one request at a time.
7
Reply with the finished thing and one action.
The reply shows them their live (or preview) site, then gives them exactly one job: paste this value here, click Save. Everything technical stays on our side. Warm, plain language, no jargon. For an external person, the email is drafted for the human to send, never auto-sent.
The reply shows them their live (or preview) site, then gives them exactly one job: paste this value here, click Save. Everything technical stays on our side. Warm, plain language, no jargon. For an external person, the email is drafted for the human to send, never auto-sent.
8
Provision, then verify with your own eyes.
Map their domain to the site on our end, confirm HTTPS issues automatically once DNS resolves, publish the pages, set them as the site owner, and load the live URL with a cache-buster to confirm it’s really up. Then log it and write the meta article — the next build starts smarter.
Map their domain to the site on our end, confirm HTTPS issues automatically once DNS resolves, publish the pages, set them as the site owner, and load the live URL with a cache-buster to confirm it’s really up. Then log it and write the meta article — the next build starts smarter.
Why it works
Because the marginal cost of completeness is near zero. The same energy it takes to write “sure, send me some photos and I’ll get started” can instead produce a built site, a verified set of DNS records, and a one-click instruction — if the playbook is standing and the assets already exist. The person experiences it as magic: they sent nine words and got a website. What actually happened is that the work was staged, the facts were checked, and the reply carried the finished product.
“The answer is the finished product, not a plan to build it.”
— the standard every one of these builds is held to.
Keep reading
- How to point your TransIP domain to your new website
- Changing domain DNS nameservers in GoDaddy
- The Personal Brand Score — the rubric every entity home is built against
Dennis Yu
Dennis Yu is co-author of the #1 best-selling book on Amazon in social media, The Definitive Guide to TikTok Ads. He’s on a mission to create one million jobs through hands-on digital training, and his team turns a person’s scattered authority into a home they own — documenting every step openly so anyone can follow the same playbook.
Dennis Yu
Dennis Yu is the CEO of Local Service Spotlight, a platform that amplifies the reputations of contractors and local service businesses using the Content Factory process. He is a former search engine engineer who has spent a billion dollars on Google and Facebook ads for Nike, Quiznos, Ashley Furniture, Red Bull, State Farm, and other brands.
Dennis has achieved 25% of his goal of creating a million digital marketing jobs by partnering with universities, professional organizations, and agencies. Through Local Service Spotlight, he teaches the Dollar a Day strategy and Content Factory training to help local service businesses enhance their existing local reputation and make the phone ring.
Dennis coaches young adult agency owners serving plumbers, AC technicians, landscapers, roofers, electricians, and believes there should be a standard in measuring local marketing efforts, much like doctors and plumbers must be certified.