THE RESULT YOU'RE WORKING TOWARD
Done means it works.
The approved hostname reaches the intended site over HTTPS, and existing email remains functional.
Practice project: Harbor Home Care01 / GET READY
Before you start.
- Platform / editor
- Wix Editor, desktop and mobile views
- Access & plan
- Wix demo account. Preview work can start without a custom domain; domains, bookings and other features depend on the selected plan.
- Starting point
- Complete the previous lesson or use an equivalent prepared demo project.
Keep a note of the exact account, project and version you use. Work with demo data and record the expected result before making changes. Never place passwords, verification codes or private customer records in your evidence.
02 / LEARN THE TOOL
Open the official walkthrough.
Use the publisher's instructions and available screenshots to locate the current controls. Then return here for the SETLY exercise and its result checks. These links open on the publisher's website.
Source credit belongs to the named publisher. These are external references, not SETLY recordings or a claim of affiliation. Screen names and plan availability can change.
03 / PUT IT INTO PRACTICE
Your task, step by step.
Use one labelled demo record or project so you can find your work again. Finish each action before continuing; if the screen differs, consult the matching official source rather than guessing.
- 01
Step 1
Identify the domain registrar, current nameservers and existing website host. Export or record current DNS entries, including email-related records.
- 02
Step 2
In Wix, obtain the connection instructions for the exact domain and account. Verify the site's plan supports the intended connection before purchasing anything.
- 03
Step 3
List the exact record changes and rollback values. Get the domain owner's approval before editing live DNS; follow the account-specific values rather than an example IP.
- 04
Step 4
After an approved change, test the apex and www addresses over HTTPS and verify business email still works. Record propagation observations.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If email breaks, compare MX and mail-authentication records against the recorded baseline. Restore unintended changes; do not repeatedly replace all DNS records.
My screen is different from the guide
Check the product, editor, account role and selected project first. Open the credited official instructions for your version. Record the difference and pause any action whose effect you cannot verify.
The screen looks correct, but the result is missing
Inspect the saved record, published page or execution log that should prove the action. A preview, success message or draft is not always evidence that data was stored or a message was delivered. Retest with one unique demo value.
05 / PROVE THE RESULT
Check it before you call it done.
The approved hostname reaches the intended site over HTTPS, and existing email remains functional.
Keep useful evidence
Record the test date, project/version, expected result, observed result and a non-sensitive screenshot or record reference. Mark anything you did not test as untested. Your checkmarks do not certify an untested result.
Download the editable verification checklist ↓Guide status: original written practice exercise with credited external references. SETLY screen recording and independent learner reproduction are not yet complete.