Professional Website
Your goal
Build a Professional Website with AI
Kydro Recommendation
Durable
You won't learn "how to click a builder." You'll learn to decide what your site is FOR — and then make AI build it. You finish with a published site and a Website Blueprint it can be rebuilt from in any tool.
- Human reviewed
- Free options shown honestly
- Never ranked by commission
Before you build the site
This Goal is not a builder tutorial. It's a guide to decisions: from "why does this site exist" to a published site visitors trust.
The most valuable skill you'll take from here is describing a site so precisely that AI can build it — and judging the result like an owner, not a spectator.
You need no coding, no marketing background, no AI experience. Terms like domain, CMS or SEO are explained in plain words exactly where they're needed.
Two questions return throughout: "What is this site for?" and "Would I trust this site?". If you can answer them, the rest is craft.
The need
The path
Structure
The message
The look
The build
Testing
LaunchWhy is it worth 1–2 hours?
Because most sites fail not through looks but through missing decisions: why they exist and what the visitor should do. You'll make those decisions here — before touching any tool.
Every module leaves you wiser, even if you stop halfway. Tools will change; good decisions won't.
At the end you have a Website Blueprint — the document your site can be rebuilt from in any tool, for years.
What will you need?
A description of what you do
2–3 sentences are enough. An idea alone also works — module 1 will sharpen it.
Real material, if you have it
Reviews, numbers, photos of your work. Not required to start — but only real proof goes on the site.
About 1–2 hours of decisions
Not counting generation and publishing time. You can stop and come back to exactly this place.
What will you build?
After this part of the Goal you will have:
- the site's purpose and one primary visitor action
- a chosen building path and tool — with a why and a change condition
- a sitemap and a Homepage skeleton with one CTA
- real copy with proof instead of slogans
- the Website Blueprint — the complete document you can rebuild your site from in any tool
- the skill of keeping AI from making promises on your behalf
Module 1
Define the website you actually need
Most websites fail not through looks but through missing decisions: why they exist and what the visitor should do. This module makes those decisions before anything else exists.
Why this step matters
This module protects you from the most expensive mistake: a beautiful site that serves nothing. Before you pick a tool or colours, you decide what ONE thing the site makes easier for a visitor.
What to prepare
- A description of what you do (2–3 sentences is enough)
- A moment of honesty: what this site is really for
Tips
Write the purpose in one sentence — if it won't fit, it isn't the purpose yet.
Describe the visitor as one person, not a "target group."
1.1
Why would anyone visit your site?
A wedding photographer doesn't need a site "about herself." She needs a site that makes a couple think "she's the one" — and write to her. A website is not a business card or an album. It is the visitor's shortest path to one decision.
Before you pick a tool or colours, you make the decision most people skip: why does this site exist? Write it in one sentence: "This site exists so that [who] [does what]". A plumber: "…so that someone with a burst pipe calls today." An accountant: "…so that a small-business owner books a free consultation."
Answers like "a site for everyone," "to look professional," "it should have everything" don't pass — that's postponing the decision, not making it. The prompt in the resources will interview you and sharpen the answer, but it won't invent your business for you.
Kydro insight
A site "for everyone" convinces no one. One concrete person with one concrete reason to visit — that is a site that works.
Common mistake
"I want a modern site so I look good." Looks are a consequence of this module's decisions — not a substitute for them.
A question for you
Who exactly lands on your site — and what is happening in their life at that moment?
1.2
One site type, one action
The site type follows the purpose, not fashion. Landing page — one page, one offer, one action. Business site — who we are, what we do. Portfolio — the work speaks. Blog — regular content. Shop — selling online. Service or product page — one thing, shown well. Simple web app — when the visitor needs to calculate or check something.
The second decision: one primary visitor action. Call. Write. Book. Buy. Sign up. That action is called a conversion, and the button leading to it — a CTA (call to action). One clear action beats five options "to choose from".
Also write down what the site does NOT need at launch: the "someday" blog, a 200-photo gallery, an English version — all of it can wait. You launch the smallest site that leads to the action.
Kydro insight
A personal trainer whose site has only "Book your first session" gets more enquiries than one with seven tabs. Visitors don't want a tour — they want to know what to do.
Common mistake
Choosing a type by copying a competitor. Their site serves THEIR purpose — which you don't know.
A question for you
If a visitor could do only ONE thing on your site — what would it be?
Kydro Resources
Common mistakes
A site "for everyone."
Why it hurts: It convinces no one because it speaks to no one.
How to avoid it: Describe one person and one reason to visit.
A purpose of "looking professional."
Why it hurts: Looks are a result, not a purpose; a site without an action is a decoration.
How to avoid it: Finish "This site exists so that…" with something concrete.
"It should have everything" at launch.
Why it hurts: Every extra element distracts from the action and delays launch.
How to avoid it: Write the "NOT at launch" list and return to it after publishing.
You can continue if…
- the site's purpose in one sentence
- one concrete visitor
- a site type chosen
- one primary action named
- the "NOT at launch" list written
Website Project Brief
The foundation of the Website Blueprint — the document your site can be rebuilt from in any tool. Sections 1–3 are born now.
Done when: your Website Project Brief holds the site's purpose in one sentence, one concrete visitor, a chosen site type and one primary visitor action.
Module 2
Choose the right building path
"I built it in the wrong tool" is the beginner's most expensive mistake. Here you choose a path from your own answers — and you see tools only once it's clear what you need from them.
Why this step matters
This is the only tool module — deliberately second, not first. Your module-1 answers choose the tool, not a ranking. Good news: every path has a free way to start.
What to prepare
- Your Website Project Brief from module 1
- Whether the start must be free
Tips
Fill the checklist BEFORE looking at tools — the reverse order is choosing with your heart, not your brief.
Don't open "just in case" accounts in three tools; one covers this whole Goal.
The fastest first version: describe your business and have a working site in minutes — with a real free plan to start.
- Beginner friendly
Good to know: Free plan has no custom domain and shows branding. · Limited customization; a young product — features and limits change fast (as of 2026-07-24).
Learning time ~1h
2.1
Five paths, in plain words
There is no single "best website tool" — there are paths with different trade-offs. For each one you get an honest pair: choose it if… / don't choose it if…
AI builder — describe your business, a site appears in minutes. Choose it if the site must be live fast and a template look doesn't bother you. Don't choose it if every detail has to be exactly your way.
Visual no-code builder — you place every element yourself. Choose it if an individual look is non-negotiable and you have time to learn. Don't choose it if the site must be live today.
CMS (content management system) — a home for regular content. Choose it if the site's heart will be a blog or guides. Don't choose it if you need a simple page with one action.
Shop / all-in-one — selling, payments and the site in one place. Choose it if you sell products online now. Don't choose it "just in case" while selling is still a someday plan.
AI coding platform — you describe the behaviour, AI writes the code. Choose it if the site must do something unusual: a calculator, a configurator, a mini-app. Don't choose it if a standard site is enough — it's the longest road to a simple result.
Before comparing anything, meet the two concepts that decide your independence: a custom domain (an address like yourbusiness.com — usually unavailable on free plans) and export (whether the site can be taken to another tool; in many builders — it can't).
Kydro insight
The tool is replaceable. Your Website Blueprint is not. Even if a builder exports nothing, the Blueprint lets you rebuild the site elsewhere in an evening.
Common mistake
Starting with "which tool is best?". The right question is "what does my site require from a tool?".
A question for you
Which requirement from your Brief is non-negotiable — even if the prettiest tool in the world lacked it?
2.2
Seven questions instead of a ranking
Answer the seven questions from the checklist in the resources — self-editing, blog, shop, how individual the look must be, speed, budget, future portability. Mark one requirement as non-negotiable. Only with your answers open the recommendation below.
The recommendation shows the main path for YOUR answers, an example tool and at least one alternative — with the trade-offs stated plainly (prices and limits carry dates, because this market moves fast). Its job: confirm or challenge your pick. The decision is yours, and you record it in the Blueprint with a change condition: "I'll move if…".
Kydro insight
An honest recommendation also says when the alternative is BETTER. If an accountant plans a tax blog, a CMS beats an AI builder — even though the builder ships a site faster.
Common mistake
"I'll take the one with the most users." Popularity measures the tool's marketing, not the fit with your Brief.
A question for you
What would have to happen for you to change paths in six months — and does your choice let you leave without pain then?
Kydro Resources
2.3
Reality Check: who will actually visit?
Before the real work on structure and copy begins — stop for one honest question. Imagine the site already exists, exactly as planned. Who specifically lands on it, and why? Where did they hear about it? What is happening in their day that made them click?
If the answer is foggy ("well… various people…"), go back to module 1 before you invest hours in building. That's not failure — it's the cheapest moment to correct. A site without an answer to this question is a nice place nobody arrives at.
A question for you
Honestly: can you describe yesterday in the life of the person who visits your site tomorrow?
Common mistakes
Picking the tool before the answers.
Why it hurts: You choose by heart and ads, not requirements.
How to avoid it: The checklist always comes before the first look at tools.
"Most popular = right for me."
Why it hurts: Popularity has never read your Brief.
How to avoid it: Compare against your own 7 answers, not user counts.
Ignoring ownership and export.
Why it hurts: In a year you may be locked into a tool you've outgrown.
How to avoid it: Write the change condition into the Blueprint and check export BEFORE launch.
You can continue if…
- 7 answers written
- the non-negotiable named
- path + tool chosen with a why
- the choice's limits known
- the change condition recorded
Decision: building path
Section 4 of the Website Blueprint — the path, the tool and the terms this decision stands on.
Done when: you have 7 written answers, a chosen path and tool with a one-sentence why, you know the choice's limits and the condition under which you'd change it.
Module 3
Plan the structure and user journey
Structure comes before copy and looks — you can't write sections you haven't decided to have. Here you decide which pages exist, why, and how a visitor reaches the action.
Why this step matters
This module turns "which tabs should I have" into "how does the visitor reach the action". A sitemap isn't a table of contents — it's one person's road map.
What to prepare
- Your module-1 Brief (purpose + action)
- Paper or a notes app for the sketch
Tips
Start with one page; add another only when you can finish "this page exists to…".
Sketch the phone version, not the desktop one — that's how most visitors will see it.
3.1
Fewer pages, fuller pages
Five half-empty pages look like an abandoned business. One full page looks like focus. The sitemap (the list of pages and how they connect) should be the smallest possible: one page, three, or five — no more at launch.
For every page, finish the sentence: "this page exists to…". Can't finish it — the page goes. A plumber rarely needs "News"; he needs emergency pricing and a number that works. Navigation (the menu) holds five items at most — the rest can live in the footer.
Kydro insight
Every page ends with a next step. A page without an exit is a dead end — visitors don't go back to the menu, they close the tab.
Common mistake
Copying a big company's structure. A corporation has eight tabs because it has eight departments — you have one purpose.
A question for you
If you had to delete one planned page — which one, and would anyone notice?
3.2
The Homepage in the order of the visitor's decisions
A visitor decides in the order of their questions: Where am I? Is this for me? Can I trust it? What do I do? You order the Homepage sections in exactly that order — that is the user journey, not a list of things you like.
The top of the page (visible without scrolling) answers questions 1–2 and shows the CTA. Trust proofs come before you ask for the action. One CTA, calmly repeated 2–3 times down the page; five different buttons are noise. And the mobile-first rule: design the phone version first, because the thumb and the small screen forgive the least.
Kydro insight
Information hierarchy is politeness: you say the most important thing first, because a visitor gives you seconds, not minutes.
Common mistake
A CTA everywhere — a different button in every section. Everywhere means nowhere.
A question for you
What does a visitor see FIRST on your site on a phone screen — and does it answer their first question?
Kydro Resources
Common mistakes
Seven pages "because that's proper."
Why it hurts: Empty pages damage trust more than their absence.
How to avoid it: Every page must finish "it exists to…".
Designing from the desktop.
Why it hurts: Most visitors arrive on a phone and see something else than you do.
How to avoid it: Sketch and judge the mobile version first.
A page with no next step.
Why it hurts: The visitor doesn't know what's next, so they leave.
How to avoid it: End every page with the CTA or a pointer onward.
You can continue if…
- a sitemap of max 5 pages, each with a purpose
- the Homepage section order set
- one CTA and its place
- the journey from arrival to action described
- the phone version thought through
Website Structure Map
Sections 5–6 of the Website Blueprint: the page map and the Homepage skeleton — input for copy (module 4) and the build (module 6).
Done when: your Website Structure Map holds a sitemap (max 5 pages, each with a purpose), the Homepage section order, one placed CTA and the visitor's journey from arrival to action.
Module 4
Create the message and copy
Copy is the site's most durable asset — it outlives every tool and every redesign. Here you decide what you promise and how you prove it; AI helps write — but is never allowed to invent.
Why this step matters
This is the flagship module: a site convinces with words before it can impress with looks. You'll learn the language of benefits and proofs — and how to keep AI from promising things you haven't done.
What to prepare
- The Brief (module 1) and Structure Map (module 3)
- Real material: reviews, numbers, certificates, photos of work — only what you truly have
Tips
Write to the one person from your Brief — "you," not "our clients."
Before accepting AI copy, find the one claim you CANNOT prove — there always is one.
4.1
A promise you can prove
Visitors don't read — they scan for two things: "what's in it for me" and "why should I believe you." A feature says what you do ("full and simplified accounting"); a benefit says what the client gets ("you sleep well before every tax deadline"). Write benefits.
So you decide the positioning: what I promise, to whom, and what I can prove. A proof is something you can show — a named review, a count of completed jobs, a certificate, a photo of the result.
And when the proof doesn't exist yet, the promise gets a 🟨 [ADD REAL PROOF] marker and waits until it does. Never the other way round.
Kydro insight
A claim without proof isn't neutral — it lowers trust in everything around it. One honest "12 weddings in the 2025 season" beats three empty "years of experience."
Common mistake
Writing about yourself: "We are a dynamic, passionate company…". The visitor asks "what's in it for me?" — and that page never answers.
A question for you
Which ONE proof would convince you yourself, if you landed on your site as a client?
Kydro Resources
You're leaving Kydro now
Open the two approved Master Prompts in the resources. First Strategy & CRO — paste your Brief and Structure Map; its output feeds the second prompt. Then Copywriting — run it once PER PAGE from your sitemap, supplying ONLY true proof. AI is forbidden to invent clients, results, statistics, certificates, reviews or company history — mark every gap with 🟨 [ADD REAL PROOF].
Come back here — screen 4.2 is waiting for you.
4.2
Read it like a stranger
You have AI's draft. Now the crucial part: read it as someone hearing about your business for the first time, with ten seconds to spare. Does the headline say in 3 seconds what this is and who it's for? Is it obvious what to do next?
Run the audit from the resources: cut jargon and hollow words ("comprehensive," "professional," "innovative"), turn features into benefits, test every claim against the credibility checklist. Count the 🟨 markers — that's your honest list of proofs to collect, not a shame. A personal trainer with two real transformations has a stronger page than one with ten promises.
Kydro insight
Copy that survives the stranger's audit is ready for anything — because a stranger is exactly who visits tomorrow.
Common mistake
Accepting AI's first draft whole. AI writes fluently — including when it writes empty sentences.
A question for you
After ten seconds on your page, does a stranger know what they can do — and why with you?
Common mistakes
Slogans without proof.
Why it hurts: They lower trust in the whole page.
How to avoid it: Every claim: a proof or a 🟨 marker.
The page talks about the company, not to the client.
Why it hurts: Visitors can't find themselves in the copy.
How to avoid it: Write in "you"; turn features into benefits.
Letting AI invent.
Why it hurts: A fabricated review or number is lost trust and real risk.
How to avoid it: Supply only true material; gaps → 🟨, never fiction.
You can continue if…
- a 3-second headline
- copy for every mapped section
- one CTA consistent with module 1
- every promise proven or markered
- the copy passed the stranger's audit
Website Copy Draft
Sections 7–8 of the Website Blueprint. This copy becomes the input for the visual direction (module 5) and the Master Build Prompt (module 6) — the more honest now, the better the site later.
Done when: your Website Copy Draft has a headline understandable in 3 seconds, copy for every mapped section, the CTA and trust proofs — and every promise has a proof or a 🟨 [ADD REAL PROOF] marker.
Module 5
Define the visual direction
Looks aren’t decoration — they’re the signal of whether you can be trusted. Here you make a few decisions that will save you a thousand small ones later: how the site looks, and what it will deliberately never look like.
Why this step matters
This module turns “I’m no designer” into a few decisions you can make in fifteen minutes. You’re not designing the site — you’re setting the frame AI will design inside, consistently.
What to prepare
- your module-4 Copy Draft
- A logo and colours if you already have them (not required)
Tips
Stick to 2–3 colours and one typeface — consistency looks more expensive than variety.
Don’t browse inspiration for more than 15 minutes; after that you start copying, not choosing.
5.1
Attractive is not the same as effective
A site with animations, gradients and three typefaces can impress — and sell nothing. A calm, readable, consistent site looks like a company that knows what it’s doing. Looks have one job: not to get in the way of what you wrote in module 4.
You decide the visual tone in three adjectives. An accountant: “calm, orderly, concrete.” A personal trainer: “energetic, direct, human.” Those three words become the instruction for AI — and the filter for every later doubt you’ll have.
Kydro insight
Consistency looks more expensive than variety. Two colours used consistently read as professionalism; six colours read as accident.
Common mistake
Collecting inspiration for hours. After fifteen minutes you’re no longer choosing a direction — you’re copying someone else’s.
A question for you
Which three words describe the impression your site should leave — not how it should look?
Kydro Resources
5.2
A direction, not a catalogue of tastes
The rest follows from the three adjectives: 2–3 colours (one main, one accent, one neutral), one typeface, one photo style. The prompt in the resources proposes three coherent directions from your Brief and your copy.
Now make the decision this module exists for: pick ONE direction and write it down. Not a shortlist, not a blend of two — one, together with its anti-list: what the site deliberately won’t be (“no stock handshakes,” “no pop-ups,” “no three different reds”). From here on, every visual question has an answer you already gave.
Kydro insight
The anti-list protects you twice: from AI adding effects you never asked for, and from yourself next month, when you see a “cool effect” on someone else’s site.
Common mistake
Stock photos posing as your team or your work. It's the same falseness you cut from the copy in module 4 — and an ordinary phone photo of real work beats a perfect photograph of strangers.
A question for you
If someone saw your site for three seconds without reading — what single impression should they take away?
Common mistakes
Six colours and three typefaces.
Why it hurts: The site reads as accidental, and accident reads as unprofessional.
How to avoid it: 2–3 colours, one typeface, consistently.
Stock posing as your team or your work.
Why it hurts: It’s the same falseness you cut from the copy in module 4.
How to avoid it: Real photos or neutral graphics that pretend nothing.
Hunting for the “perfect” look.
Why it hurts: Looks take five minutes to change after launch; having no site costs more.
How to avoid it: Pick a direction in fifteen minutes and move on.
You can continue if…
- three adjectives written
- 2–3 colours chosen
- one typeface
- a photo style and where they will come from
- the anti-list ready
Visual Direction Brief
Section 9 of the Website Blueprint. These few lines will steer every visual decision AI makes in module 6 — and settle every “maybe a different colour?” you’d otherwise revisit for weeks.
Done when: you have three brand adjectives, a colour palette, typography and a photo style — plus the anti-list: what the site deliberately won’t be.
Module 6
Build the website with AI
Everything so far was preparation. Today your Website Blueprint becomes a prompt, and the prompt becomes a working site — a first version, not the final one.
Why this step matters
This is the module where the previous four pay off: the AI prompt assembles itself from your Blueprint. The first version won’t be perfect — it doesn’t need to be. It needs to be YOURS.
What to prepare
- Your Website Blueprint, sections 1–9
- An account in the tool you chose in module 2
- Your phone within reach
Tips
Paste the whole Blueprint in one go — good input is a good first version.
Don’t order fixes mid-generation — wait until the tool finishes.
6.1
Blueprint goes in, a website comes out
You’re not writing a prompt from scratch. You assemble it from what you already have: purpose and visitor (sections 1–2), sitemap and Homepage sections (5–6), copy with proof (7–8), visual direction (9). That is the Master Build Prompt — and that’s why the previous four modules mattered.
Paste it whole as the first message in your module-2 tool and let it finish. One good generation beats ten blind corrections — and in credit-limited tools it costs many times less.
Kydro insight
One sentence worth adding at the end of the prompt: “don’t add sections I didn’t ask for.” AI will happily build a testimonial carousel for reviews you don’t have.
A question for you
Does your Blueprint contain everything a stranger would need to build this site without asking you a single question?
Kydro Resources
You're leaving Kydro now
Open the tool you chose in module 2 and follow its path from the resources: paste the Master Build Prompt whole, generate, wait for it to finish. Then open the preview ON YOUR PHONE — not on your computer. Most of your visitors will see the site there, so that is where you form your first impression.
Come back here — screen 6.2 is waiting for you.
6.2
Judge it as an owner, not a viewer
You have the first version. Before judging “pretty or not,” run three checks. First: count the sections — are they the ones from your map, all of them and only them? A surprise section means AI was guessing; point at it and ask for removal. Second: find your sentences — do you see your module-4 copy, or filler text and invented reviews? Third: scroll on your phone — is the primary action visible without hunting?
Those three checks produce a fix list. Split it in two: “must, before launch” and “can wait.” Most of what irritates you right now belongs to the second.
Kydro insight
The first version isn’t meant to be perfect — it’s meant to be yours. If the sections and copy match, it’s already your site; the rest is polish.
Common mistake
Judging by taste before checking the facts. “Do I like it” is a weaker question than “is my copy in there.”
A question for you
Which of the three checks came out weakest — and would a visitor even notice it?
6.3
One change at a time
Ten fixes in one message end with a site where something broke and you don’t know what. One change, check, then the next. Slower is faster.
Phrase each one as an instruction, not a complaint: not “this section is ugly,” but “make the offer heading smaller and move the button below the text.” Then write every lasting change into the Blueprint — a chat fix disappears with the conversation, a Blueprint fix holds in every future version.
Kydro insight
The Blueprint is your site’s source of truth. The tool merely executes it — which is why changes belong where they’ll survive a change of tool.
Common mistake
Polishing endlessly before launch. An unfinished site serves no one; a published site teaches you from real visits.
A question for you
Which single fix is genuinely required for a visitor to understand the offer and know what to do?
Common mistakes
Ten fixes in one message.
Why it hurts: You can’t tell which one broke something.
How to avoid it: One change, check, next.
Fixes only in the chat.
Why it hurts: They vanish with the conversation and won’t survive a change of tool.
How to avoid it: Write every lasting change into the Blueprint.
Expecting a final site from one prompt.
Why it hurts: It leads to disappointment and quitting after the first result.
How to avoid it: First version plus iteration is the normal process, not failure.
You can continue if…
- the first version exists
- sections match the map
- your copy is inside
- the mobile view checked
- the fix list split in two
- lasting changes in the Blueprint
Master Build Prompt + iteration log
Section 10 of the Website Blueprint. The prompt lets you rebuild the site in any tool; the log tells you what you already changed and why — so you never fix the same thing twice.
Done when: the first version exists and passed three checks (sections from your map, your copy, the mobile view), and you order fixes one at a time.
Module 7
Test before publishing
Find the errors before a customer does. Five deliberate tests — including really sending the form — separate a site you show off from a site that works.
Why this step matters
This module turns fear of publishing into a list of verified facts. You don’t ask “is it good?” — you check five concrete things and then you know.
What to prepare
- The module-6 first version of the site
- A phone that isn’t yours (or a friend for ten minutes)
Tips
A test that found a bug is a successful test — not a failure.
Write down the weakest result immediately; tomorrow your memory will smooth it over.
7.1
Five tests you run before, not after
Test 1 — the form, for real. Send a real message through your own form and check it arrived (spam folder too). A form that looks fine but doesn’t deliver means lost customers you’ll never know about. Test 2 — someone else’s device. Open the site on a phone that isn’t yours. Test 3 — the primary action. Walk the visitor’s path from arrival to the CTA click; count how many steps it took. Test 4 — understanding the offer. Show the site to someone for ten seconds and ask: “what can you do here and who is it for?” If you have to explain — the site isn’t explaining itself yet. Test 5 — links and text. Click every link, read every heading aloud.
Record the results and name the weakest. Then split them the same way you split the fix list in module 6 — and be honest about it: deferring a problem is a decision, hiding it is not.
Kydro insight
A test that found something is a successful test. You want the first failure to reach you — not the customer you care about.
Common mistake
Testing only on your own laptop, where everything always works.
A question for you
What’s the worst thing your site could do to a visitor — and which of the five tests checks exactly that?
Kydro Resources
7.2
Reality Check: would you trust this site?
One question before launch, to be answered honestly. Imagine landing on this site for the first time, knowing nothing about the company. Would you leave your phone number here? Would you pay?
Answer, then decide out loud. YES — you publish, and module 8 starts now. NO — name the ONE thing that made you hesitate, fix only that, and ask the question again. Missing proof sends you back to module 4; an unclear next step sends you to module 3.
This isn’t a step backwards. It’s the last moment when a fix costs fifteen minutes instead of your reputation.
Kydro insight
Hesitation is data. The moment you notice it in yourself, you’ve found exactly the thing a visitor would never tell you about.
A question for you
Honestly: would you leave your details on this site if it weren’t yours?
Common mistakes
A form that looks fine, never actually sent.
Why it hurts: You lose customers you’ll never know about.
How to avoid it: Send a real message and confirm it arrived.
“I’ll fix it after launch.”
Why it hurts: Your first visitors see the version you’re ashamed of.
How to avoid it: Split must from can-wait and fix the first.
Skipping the offer-understanding test.
Why it hurts: You always understand your own site — that proves nothing.
How to avoid it: Ten seconds and one question to a stranger.
You can continue if…
- the form delivered a real message
- the site checked on someone else’s device
- the path to the CTA runs without friction
- a stranger understood the offer
- the weakest result named and resolved
Pre-Launch Checklist
Section 11 of the Website Blueprint. Written results turn “I think it works” into evidence — and give you a ready re-test list after every future change.
Done when: five tests are done, the results are recorded, the form really delivered a message, and a stranger understood the offer without your explanation.
Module 8
Publish, measure and improve
Publishing isn’t the finish line, it’s the start of the loop. Here the site gets a real address, you get data instead of guesses — and you make sure everything you built belongs to you.
Why this step matters
This module turns a project into a working site and protects your independence: your own domain, your own accounts, a copy of the Blueprint outside the tool. A business whose entire existence depends on one builder is more fragile than it looks.
What to prepare
- The tested site from module 7
- An idea for the domain name (2–3 options)
Tips
Register the domain in your own name, not conveniently on an agency’s or a friend’s account.
Keep a copy of the Blueprint outside the tool — the Blueprint IS your site; the builder merely displays it.
8.1
Your address and your ownership
A domain is the address people find you at (yourbusiness.com); hosting is where the site physically sits — in builders usually included in the plan. Choose a name that’s short, easy to dictate over the phone, and hyphen-free if possible. Then publish following your tool’s path from the resources.
Before calling this done, check four ownership items: the domain registered to you (not an agency, not a friend), account credentials saved somewhere that survives changing your phone, whether you can export or move what you have, and a copy of the Website Blueprint outside the tool — a file, a cloud drive, anywhere but the builder.
Kydro insight
The builder displays your site. The domain, the copy and the Blueprint ARE your site. As long as you hold those three, no price change or policy shift at the tool is a catastrophe.
Common mistake
A domain bought conveniently inside the builder without checking whose name it’s in. Recovering your own address can be harder than rebuilding the site.
A question for you
If your tool tripled its price tomorrow — what exactly would you take with you, and how long would rebuilding elsewhere take?
Kydro Resources
8.2
Measure what matters, improve one thing at a time
SEO is helping people who are ALREADY searching for what you do to find your site. Basics are enough at launch: a sensible title and description for every page (prompt in the resources) plus submitting the site to Google Search Console — a free tool that tells Google “this site exists” and shows which phrases bring people in.
Pick 2–3 numbers to watch for 30 days — e.g. visits, form enquiries, the most-viewed page. And write down what you will NOT judge in week one: Google position, visit counts, “did it work.” A site doesn’t attract traffic by existing — link it everywhere you already are: your Google profile, socials, email footer, signature.
Kydro insight
Plan one first improvement before you see any data. A site with a concrete next step stays alive; a “finished” site quietly ages.
Common mistake
Refreshing analytics hourly after launch. One day’s data is noise, not signal.
A question for you
Which single thing on your site would gain most from improvement — and when exactly will you come back to it?
Common mistakes
A domain not in your name.
Why it hurts: You lose control of your own address.
How to avoid it: Verify the registration details before launch.
Judging success after week one.
Why it hurts: Indexing and traffic take time; judging too early ends in abandonment.
How to avoid it: Write the what-I-won’t-judge list and return after 30 days.
The whole business inside one builder.
Why it hurts: A price or policy change becomes your crisis.
How to avoid it: Domain, copy and Blueprint outside the tool.
You can continue if…
- the site is live at its own address
- the domain registered to you
- credentials saved
- a Blueprint copy outside the tool
- titles and descriptions set, the site submitted to Search Console
- 2–3 numbers chosen and the first improvement planned
Professional Website Blueprint (complete)
Sections 12–14 close the Blueprint. From now on this document — not the builder — is your website’s source of truth: you can rebuild the site from it anywhere, and it tells you what to improve next.
Done when: the site is live at its own address, the domain and accounts are yours, basic SEO and analytics work, and you know which 2–3 numbers you watch and what you don’t judge yet.
Your progress
0 / 8
The needThe pathStructureThe messageThe lookThe buildTestingLaunchBuild your personal AI library.
Save useful goals and come back whenever you need them.
Success Tips
Expert recommendations to help you reach your goal faster and avoid common mistakes.
Trust
RecommendedNo promise without proof
A claim you can't show lowers trust in everything else. Mark the missing proofs and go get them.
Building
RecommendedOne change at a time, always through the Blueprint
A chat fix disappears; a Blueprint fix holds in every future version of the site.
Testing
RecommendedSend your own form before a customer does
A form that doesn't deliver means lost customers you'll never know about.
Ownership
Don't leave the domain and content in someone else's hands
The builder displays your site; the domain, copy and Blueprint ARE it.
Questions & answers
What people ask after finishing this goal
The questions that only come up once you have the whole picture.
No. Four of the five building paths need zero code, and on the fifth (an AI coding platform) the AI writes it — you describe what the site should do. The skill you actually need is describing the site precisely — which is what this Goal teaches.
Every path from module 2 has a free way to start. The real threshold is a custom domain: plans that include one start at roughly a few to a dozen dollars per month, and the domain itself is usually a small yearly fee (as of 2026-07-24 — check current prices). Shops and business features cost more.
A domain is your site's address (yourbusiness.com); hosting is the computer the site physically lives on. Builders include hosting in the plan — so usually the only thing you buy is the domain. Without one, the site runs on the tool's address (e.g. yourbusiness.wixsite.com) — fine for testing, weak for a business.
It should be — but check that it's registered to YOU and that you can transfer it to another registrar. Module 8 makes you verify this before launch. The domain is your most valuable address on the internet; don't leave its ownership to chance.
The first version — yes, in minutes. A good site — not without you. AI doesn't know your customer, your offer or your proof; it builds what you describe. That's why modules 1–5 come BEFORE the build: with a good Website Blueprint AI assembles your site, with an empty prompt it guesses.
Don't fix ten things at once. Go back to the Blueprint, find the sentence that was missing or vague, fix it, and order ONE change. If the tool still can't deliver after a few iterations — your Blueprint moves to another tool in an evening.
It depends on the path: some builders have no export (moving = rebuilding), others let you take more. That's why module 2 records your change condition, and the Blueprint is your insurance: it describes the site so precisely you can rebuild it anywhere — export or not.
Often yes — all-in-one builders and CMSs have paid plans with commerce. But if selling online is a real plan (not a "someday" dream), say so in module 2: choosing a path with the shop in mind saves you a migration at the worst possible time.
Usually within days to weeks of submitting it in Search Console (module 8). Appearing ≠ ranking high: position grows with time, content and links. No honest person can promise you a ranking — and this Goal only promises what depends on you.
SEO is helping people who are ALREADY searching for what you do to find your site. At launch the module-8 basics are enough: sensible titles and descriptions, Search Console submission, a page a human understands. Advanced SEO is its own discipline — for later.
Builder forms are safe to run — and everyone gets some spam; most tools filter it. What matters more: module 7 makes you send a REAL message through the form and confirm it arrived. A form that "looks fine" but doesn't deliver means lost customers you'll never know about.
Not just any. Use material you have the rights to: your own photos, licensed stock, AI-generated images. And the module-5 honesty rule: a stock photo must never pose as your team or your work — that destroys trust exactly where the site is supposed to build it.
If you measure traffic or run a form, you collect data — so the site needs a simple privacy policy and consent where the law requires it. Builders ship ready-made components for this. The minimum rule: collect only what you use, and say so plainly.
Less often than you think. A site doesn't rot from standing still — it rots from stale information: prices, hours, offer. Module 8 sets the loop: every so often you look at 2–3 numbers, fix the weakest thing and get back to your life. Daily tinkering is procrastination dressed as work.
Because the layout adapts to the screen — that's responsiveness, and it's supposed to happen. The problem isn't "different", it's "worse": clipped text, buttons you can't tap. That's why module 3 designs phone-first and module 7 tests on someone ELSE's device, not just yours.
That's a normal first week — a site doesn't attract traffic by existing. Check it's in Search Console, link it everywhere you already are (Google profile, socials, email footer), and give it time. Judge by weeks and by your 2–3 module-8 numbers — not by day one.
Decide through the Blueprint, not through mood. If the purpose, visitor and promise in sections 1–7 still hold — improve the weakest section. If the foundation changed (different customer, different offer) — then rebuild, starting from module 1, not from the colours.