Building a Personal Website Without Code: A Step-by-Step Plan

A tool-neutral, seven-step plan for building a simple personal site with a site builder, from planning pages and writing content to connecting a domain.

tomyl.ink · Last reviewed October 24, 2026 · 5 min read

You do not need to write code to build a good personal website. Hosted site builders, blogging platforms and similar tools let you pick a layout, type your words into boxes and publish. What they cannot do is decide what your site is for or write it for you.

This guide is a tool-neutral plan. It works whichever service you use, and it focuses on the decisions that make a simple site clear, findable and easy to maintain. For the specific buttons and settings, rely on your chosen tool's own help pages.

Step 1: Decide what the site is for

Mozilla's beginner web development course starts with planning before any building: what the site is about, what information it presents, and what it should look like in simple terms. It also advises keeping things simple for a first site.

Write one sentence that finishes "Someone who visits my site should be able to..." For example, imagine a hypothetical landscape photographer named Dana: "Someone who visits my site should be able to see my best work and book a session." That sentence will settle a lot of later choices, including which pages to cut.

Step 2: Plan a small set of pages

Most personal sites need only a handful of pages. A common starting set:

Home: your name, what you do, and one clear next step.
About: a short bio in plain language, with a photo if you are comfortable sharing one.
Work, projects or writing: a curated selection, not everything you have ever made.
Contact: how to reach you. A contact form or a dedicated email address avoids publishing your personal inbox.

A one-page site that stacks these as sections is also fine. Sketch the pages on paper first; Mozilla's course recommends rough sketches even for simple pages, and notes that professional teams usually start that way too.

Step 3: Write the words before you choose a design

Templates look best with real content in them, so write first. A few habits from the W3C's Web Accessibility Initiative (WAI) and from Google make pages clearer for everyone:

Give each page a short, descriptive title that distinguishes it from your other pages. WAI suggests putting the unique part first, such as "Projects - Dana Ruiz" rather than "Dana Ruiz - Projects."
Use headings to break pages into sections. WAI notes that good headings provide an outline of the content.
Write link text that describes where the link goes. WAI advises against vague text such as "click here" or "read more."
Write a short summary for each page. Google says a good meta description is short, unique to one page and includes the page's most relevant points. Many builders have a field for it, often in page or search settings.

Step 4: Choose a template and check the features you need

Most builders offer templates. Pick one for its structure and readability, not its demo photos. Before you commit, look for these features in the tool's documentation:

Custom domain support, so your site can live at your own domain name.
Editable page titles and descriptions for each page.
A field for image alternative text.
A mobile preview. Google uses the mobile version of a site's content for indexing and ranking, which it calls mobile-first indexing, and it very strongly recommends having a mobile-friendly version.
A way to export or back up your content, in case you ever change tools.
Multifactor authentication for your account login, which CISA lists among the core steps everyone should take to stay safer online.

If a tool lacks something that matters to you, it is easier to switch now than after twenty pages.

Step 5: Use images and fonts you have the right to use

Mozilla's course points out that most images on the web are copyrighted, and that many fonts are licensed in ways that limit how you can use them. Your safest options are your own photos, images you have permission to use, and images or fonts offered under a license that allows your use. If a template includes sample images or fonts, check the tool's documentation for how you are allowed to use them.

When you add images, write alternative text. Google's SEO Starter Guide describes alt text as a short but descriptive piece of text that explains the relationship between the image and your content. WAI adds that purely decorative images do not need alternative text. Our guide, Accessibility Basics for Personal Sites: Simple WCAG Checks, covers this in more detail.

Step 6: Connect your domain and publish

Your domain registration and your website are separate things. ICANN, which coordinates the domain name system, compares a domain name to a street address: you still need a building there, meaning a hosting service or site builder, before anything appears. Some services sell both; others expect you to bring a domain you registered elsewhere.

Connecting the two usually means changing a few settings at your registrar or letting the builder do it for you. Follow the builder's own help page for the exact records, since they differ between services. Then, before you announce the site:

Open every page on your phone and on a computer.
Click every link and submit your contact form once to make sure it arrives.
Read each page aloud. Typos and awkward sentences stand out when spoken.

Step 7: Help people find it

Google's SEO Starter Guide says you usually do not need to do anything except publish, and that Google primarily finds pages through links from other pages. Link to your new site from your profiles and email signature. After a while, search for site: followed by your domain to see whether Google has found it.

Sitemaps are optional for most personal sites. Google's documentation says you might not need one if your site is small, about 500 pages or fewer, and well linked internally. Google also notes that some content management systems create one for you automatically. If you want more detail, Google's Search Console includes a URL Inspection Tool that shows how Google sees a page.

Key takeaways

Start with one sentence about what visitors should be able to do, then plan only the pages that serve it.
Write your content before choosing a design, with descriptive titles, headings and link text.
Check that a builder supports a custom domain, editable titles, alt text, mobile layouts, export and multifactor login.
Use only images and fonts you have the right to use, and add alt text to meaningful images.
Publishing and linking from your profiles is usually enough for Google to find a small site.

Sources

Spotted something out of date? Let us know.