Build the navigation around customer tasks
Choose a design that suits your content, then build the service, contact and trust pages first. Write navigation labels in customer language. Use reusable sections and a consistent type scale rather than recreating layouts page by page.
Set up pages around the customer journey
Define what someone needs to do after arriving: request a quote, review a portfolio or buy a product. Create those paths before choosing elaborate page layouts. Use the design tools to set consistent type, spacing and buttons. Draft content with real prices, scope or service examples where appropriate. Put important public pages in navigation or link them from another relevant page.
- Create the core pathsBuild the service, portfolio or purchase sequence
- Set the public addressVerify SSL, metadata and URL mappings
- Try the customer taskCheck phones, forms and production visibility
Connect the domain and configure search settings
Confirm where the domain is managed and follow the connection steps shown in Squarespace. Keep any existing email records in place. Set descriptive SEO titles for important pages, add meaningful image text, and inspect the generated sitemap after publication.
Connect your domain and prepare search settings
Confirm the live primary domain and SSL. Edit SEO titles and descriptions for core pages and set readable slugs. Review image descriptions for informational images and check how social previews look when sharing a page. Open the automatically generated sitemap on the live domain. If you replace an existing site, document old paths and configure URL mappings for addresses that have moved.
Test the published experience
Open the site on mobile, submit an enquiry and check where it arrives. Verify redirects if replacing a site. Test the canonical hostname and remove any launch restrictions that should no longer apply. Measure contact or purchase completions separately from general visits.
Check forms, accessibility and mobile layouts
Publish to a preview environment while reviewing forms and shopping or booking flows. Confirm submissions reach the right account and the confirmation instructions make sense. Test the live navigation on a phone and keyboard. Review text on images for contrast and verify that image crops preserve essential content. After launch, connect Search Console and check a few important URLs.
A photographer’s launch example
A portrait photographer builds a portfolio, a packages page and a booking page. The packages page answers travel and delivery questions and links to booking. After switching domains, the photographer redirects the old packages URL and tests both booking and a callback request on a phone.
Before launch, review which pages must be public and which areas belong behind restricted access. An unlinked page can still be accessible by its exact address, so use the relevant visibility and indexing controls for material that should be private or excluded. Document who can publish, update domains and change payment information. When possible, get one person who did not build the site to complete the most important task using a small phone and a realistic network connection.
| Check | Expected result | Action if it fails |
|---|---|---|
| Primary domain | A single preferred HTTPS hostname | Correct domain connections and redirects |
| Forms and booking | A confirmed request with clear next steps | Review recipients, scheduling settings and consent |
| Sitemap | Public, intended pages listed | Review page visibility and published status |
Common questions
Can I redesign before changing the domain?
Yes. Keep your public site operating while you review the new design. Schedule the DNS change after confirming redirects and critical forms.
Should I add a third-party sitemap plugin?
Squarespace generates a sitemap. Test its live output and its coverage before introducing a second source.
What is the safest way to rename a published page?
Record the old URL and create a mapping to the new path. Update navigation and internal links, then check both URLs in a signed-out session.
What to check next
- NavigationUse customer language rather than internal labels
- DomainsKeep existing mail DNS records
- LaunchVerify enquiry delivery and sitemap URLs




