Article Growth

Personal Website Checklist: What to Prepare Before the Build

Everything to gather before a personal website build starts, from verified facts and photo rights to domain ownership, contact routes and the final pre-launch checks.

In this note

A preparation and launch checklist for a professional's personal website, grouped by goals, content, images, accounts, contact paths and launch.

7 min read
A consultant reviews printed headshots, a portfolio folder and notes at a desk before a website project.

Published by

VSN Editorial

Date

Oct 14, 2026

Read time

7 min read

Personal website projects rarely stall because of design or code. They stall because a photo is missing, a credential needs confirming, nobody can find the domain login, or the person whose name is on the site has no time to review the copy. A short personal website checklist, worked through before the build starts, removes most of those delays.

Below, the checklist is grouped into the order you will need things. Tick off what you have, note what you still need to find, and share the list with whoever is building your site.

1. Goal and audience

Start with a short note your builder can refer back to when choices come up.

  • The main reader: clients, event organisers, recruiters, investors or media.
  • The one action you want them to take: book a call, send an enquiry, download a speaker sheet.
  • Two or three sites of people in your field that you like, and what you like about them.
  • Anything you do not want, such as certain colours, styles or topics.
  • The markets and languages you work in.

Before you start, decide where the checklist lives. A shared folder with subfolders for facts, photos, accounts and approvals works well, and it becomes your master record after launch. Name files clearly, for example “bio-long-approved” or “headshot-2026-rights-confirmed”, so nobody uses the wrong version.

If the reader and action are not clear yet, decide them first. Every later decision depends on them.

2. Facts, proof and permissions

Your site will make claims in your name. Gather the evidence now so nothing has to be softened at the last minute.

  • Current title and organisation, spelled exactly as you want them shown.
  • Career history with dates you are confident about.
  • Qualifications, memberships and certifications, with a document or public link for each.
  • Selected projects or clients you have written permission to mention.
  • Publications, talks, podcasts and media appearances, with links.
  • Any award, with the awarding body, year and whether it was personal or team.
  • Short, medium and long bio drafts, if you have them.

If you do not have a bio yet, our guide on how to write a professional bio explains how to build one from these facts.

If you cannot show it, do not claim it. Your website should survive a reader who checks.

— VSN Editorial

Keep the evidence itself private. Your builder needs to know a qualification is real, but your certificates, ID documents and contracts do not belong on the website or in an email thread. Share public links where they exist, and keep originals in your own folder.

3. Photos and visual material

  • Recent, high-resolution photos of you, ideally several poses and backgrounds.
  • Confirmation that you own the photos or have the photographer’s permission to use them.
  • Event photos only where you were actually present and permitted to use them.
  • Logos of organisations only where you have permission to display them.
  • Any brand colours or fonts you already use on LinkedIn, slides or business cards.

If you plan to use AI-assisted portraits, approve the reference photos yourself and check that the results look like you and do not suggest settings, events or credentials that are not real.

4. Domain, hosting and accounts

This is where projects most often lose a week.

  • Domain name chosen, ideally your name, and registered in your name.
  • Login details for the domain registrar available to you (do not email passwords; share access through the provider’s user or delegate features where possible).
  • Hosting account in your name, or a decision on who will set it up.
  • Professional email address on your domain, if you want one.
  • Accounts for any booking, newsletter or CRM tool you plan to connect.

Keeping these in your own name means you control renewals and can change suppliers later without losing your address.

5. Contact paths

  • The email address or form destination that enquiries should reach.
  • A booking link and the meeting types you offer, if any.
  • Social profiles you want linked, and any you do not.
  • Whether you want a downloadable contact card or a QR code for events.
  • Who replies to enquiries, and how quickly you can realistically respond.

6. Technical basics to confirm with your builder

You do not need to do these yourself, but ask whether they are included.

  • Pages work well on a phone and with keyboard navigation.
  • Each page has a title and description for search results.
  • Social share previews show the right image and text.
  • A sitemap is created.
  • Relevant structured data is added. Google documents ProfilePage structured data for pages focused on a single person or organisation, such as an “About me” page.
  • You receive admin access and source files at handover.

7. Before you launch

Run this final pass on the working site, ideally on your phone and a laptop.

  1. Read every page aloud and check names, titles, dates and numbers.
  2. Click every link and button, including the booking and contact routes.
  3. Submit the contact form and confirm the message arrives where expected.
  4. Check each photo appears correctly and loads quickly.
  5. Share a page link in a private message to see the preview.
  6. Ask one trusted person to review it as a stranger would.
  7. Update your LinkedIn and email signature with the new address after launch.

If you are still deciding whether you need a site at all, see our comparison of a personal website vs a LinkedIn profile.

Common gaps that delay a launch

Even well-prepared projects stall on a few predictable items. Check these early.

The approver is too busy. The person whose name is on the site must approve every factual line. If that is you, block review time in your calendar for each round before the project starts, and agree a turnaround you can keep.

Permissions arrive late. Client names, logos, event photos and quotes from other people all need permission. Ask for it at the start, because replies can take weeks. If permission does not come, describe the work without the name.

The domain is locked somewhere else. An old supplier, a former employer or a relative may have registered your name years ago. Find out who controls it and how to transfer it before the build depends on it.

Translations are not ready. If the site is in two languages, the second version needs its own approved text. A translation nobody has reviewed is a risk to your credibility.

The contact route has no owner. Decide who reads enquiries and books calls. A beautiful site with an unanswered inbox does more harm than no site.

Clearing these before design starts usually saves more time than any other step in the project.

Key takeaways

  • Write down the reader and the one action before anything else.
  • Gather proof and permissions for every claim, photo and logo.
  • Register the domain and hosting in your own name.
  • Test every contact route and preview before launch.

Questions people ask

How long does it take to prepare content for a personal website?

It depends on how much material you already have. Professionals with a current bio, good photos and a list of work can be ready quickly; others need time to collect proof and permissions. Starting this checklist early shortens the project.

Can my builder register the domain for me?

They can help, but the registration should be in your name with an email address you control. That way renewals and transfers stay in your hands.

What if I do not have professional photos?

You can arrange a short shoot, use good-quality recent photos you own with some finishing, or consider approved AI-assisted portraits based on your own reference photos.

Do I need a privacy policy on a personal website?

If your site collects personal data, for example through a contact form, booking tool or newsletter sign-up, you will usually need to explain what you collect and why. The rules depend on where you and your visitors are, so check what applies or ask a qualified adviser.

VSN’s Authority Profile service works from exactly this kind of brief: your facts, approved images and owned accounts. Once your checklist is in progress, see the Authority Profile packages or share your brief with us.

Filed under Growth

Keep reading

Related notes