Revised proposal · Version 2 · Prepared for Sherry Xiao
A complete rebuild of soaplakeresort.com on Wix — planned, built and tested entirely off to one side, while your current site stays online and taking bookings every single day of peak season. Nothing changes on your live domain until you have seen the new site and approved it.
Where this landed
Three things you told me reshaped this proposal, so I want to reflect them back before quoting anything.
Your contractor is mid-build on the Solstice foundation and automations. I will not touch that site or interfere with their deliverable. My scope is the resort site alone, built to connect cleanly to whatever structure Solstice lands on.
Spa serves resort guests in peak season and opens to the public in shoulder and off-season. That is a rhythm, not a permanent split — so the resort site gets built to shift emphasis by season without a rebuild each time.
Rooms hand off to Wyndham; everything else routes to Solstice. That makes the resort site's job precise: attract, qualify, and hand off cleanly. Every page gets designed against that one job.
One correction to my earlier note. I originally suggested a 4–5 day fast-track. Having mapped your full page inventory — 26 pages including six accommodation pages, eight venue and facility pages, and the blog — I would rather quote six days honestly than five days optimistically. Because your live site stays up throughout, the extra day costs you nothing in bookings.
The part you were right to worry about
Most migrations go wrong because someone rebuilds the site people are already using. I don't do that. Two tracks run in parallel, and they only meet once — at a switch you control.
The green line is your revenue. It is never cut, never paused, never redirected mid-build. If the new site isn't right on review day, we simply don't switch — and you have lost nothing but time.
You are in peak season. A half-finished site on your live domain — even for a few hours — costs real room nights and burns paid ad clicks that land on broken pages.
This approach means the worst possible outcome of the project is that you decide not to switch. There is no scenario where guests hit a construction site.
Your first question, answered properly
Ranking value is not stored in WordPress. It lives in your domain, your backlinks, your content, and your URL paths — and all four survive a migration intact. What causes real, permanent loss is sloppy execution: changed URLs with no redirects, dropped metadata, thinned content. So those are the things this plan attacks directly.
| Asset | What happens to it | Risk if mishandled |
|---|---|---|
| URL paths | Mapped 1:1 before a single page is built. /accommodations/, /essence-spa/, /venues/, /offers/ and every venue page keep their exact paths. |
The single largest cause of traffic loss in a platform migration. |
| Trailing slashes | WordPress serves /venues/; Wix serves /venues. Every affected path gets an explicit 301 so neither version 404s or loops. |
Missed by most migrations. Silently kills a share of your inbound links. |
| Titles, meta descriptions, H1s | Exported from SiteSEO and transferred verbatim first, then improved only where there is a clear gain. | Rewriting these during a migration makes ranking changes impossible to diagnose. |
| Legacy & duplicate URLs | /large-infrared-spa-the-essence-retreat/ and /home-new/ are consolidated with permanent 301s to their canonical pages. |
Duplicate pages split your ranking signals between them. |
| Structured data | Hotel, LocalBusiness and Breadcrumb schema (JSON-LD) rebuilt on Wix and validated in Google's Rich Results Test. | Losing schema costs rich results in hotel and local search. |
| Images | Migrated at original resolution with alt text preserved, then compressed and served through Wix's CDN. | Image search traffic and page speed both suffer if this is done lazily. |
| Google Search Console | New sitemap submitted and the old one retired on switch day; index coverage watched daily for the first week. | Google can take weeks longer to recrawl if it is not told the site changed. |
| Google Ads final URLs | Every final URL and sitelink audited and updated the same day, including the held Solstice Journey campaign destination. | Ads pointing at dead URLs get disapproved and waste spend immediately. |
An honest expectation. Even a clean migration usually shows mild ranking movement for two to four weeks while Google recrawls and re-establishes the pages. That settles. Permanent loss comes from bad redirect mapping, not from the platform — which is exactly why the redirect map is built first and tested before the switch, rather than patched afterwards.
Included after launch: 30 days of monitoring on rankings, index coverage and 404 logs, with fixes to any redirect or crawl issue found in that window at no extra cost.
Your second question, answered properly
You said the business is starting to grow and you need to make changes. That is a requirement I build around, not something to solve afterwards.
Rooms, suites, cottages, cabins, venues and packages are built as Wix CMS collections rather than hand-placed text. Changing a rate, swapping a photo or updating amenities means editing a field in a list — the layout cannot break, because you are not touching it.
Add a new room type or a new venue and its page builds itself from the template.
You receive short Loom walkthroughs recorded on your actual site, covering the edits you will genuinely make: updating rates, swapping images, editing a package, adding a seasonal offer, and publishing.
Full owner access, in your own Wix account. No agency lock-in, no dependency on me to change a price.
The same Wix Editor you already know.
The resort site is built in the standard Wix Editor — the same interface your Solstice site runs on. Nothing new to learn, one consistent way of working across both properties, and anyone on your team who can edit Solstice can edit the resort site too.
That is a deliberate choice, not a limitation. The CMS collections, the seasonal spa toggles and the room and venue templates described above are all built with standard Wix tools, so everything I hand over stays fully editable by you long after the project closes.
Booking flow
Every accommodation page carries a clear, persistent booking action that passes to your Wyndham system, including a sticky booking bar on mobile. Each room type is linked to its correct Wyndham destination and tested individually before launch.
The resort site teases rather than duplicates: short, high-intent blocks for Solstice BioSpa and retreats that route to the Solstice site. No competing spa content, no keyword cannibalisation between your two domains.
Essence Retreat is positioned as an Historic Inn guest amenity on the resort site — a reason to book a room, not a spa competing for public search traffic. Naming standardised to "Essence Retreat" throughout.
Designed for your seasonal swing. The spa modules on the resort site are built as CMS-driven blocks with a visibility toggle. In peak season they read as a guest amenity. In shoulder and off-season you switch them to public-facing messaging and day-pass promotion without a developer, and without a rebuild. That is the flexibility your seasonal model actually needs.
Scope
A fixed price is only fair to both of us if the boundary is written down. This is the boundary.
Timeline
Your live site is earning throughout every one of these days.
Full crawl and inventory of the WordPress site. Every URL, title, meta description and H1 exported. Redirect map drafted. Wix workspace and CMS collections set up for rooms, venues and packages. Nothing on your live site is touched.
Homepage, accommodations, venues and offers built on the staging URL. Content migrated into CMS collections. Responsive behaviour set for desktop, tablet and mobile. Brand look carried across and tightened — this is a rebuild, so the design is reconstructed rather than copied pixel for pixel.
Wyndham handoffs wired and tested per room type. Solstice teaser blocks and Essence Retreat page built. Historic Inn buyout enquiry page created. Forms connected and test submissions verified.
Redirect map loaded in full. Metadata and schema applied and validated. Speed and mobile pass. Cross-device and accessibility QA. The complete staging site is sent to you for review — this is your decision point.
Your revisions applied. On your written go-ahead, the domain is pointed at the new site at your chosen low-traffic hour. Redirects, forms, booking handoffs, Search Console and Google Ads destinations re-verified live. WordPress kept intact as a 30-day rollback. Loom training library delivered.
Days run from the morning after access is provided. The only thing that moves this timeline is waiting on access or on review feedback — both of which I will flag the moment they become blocking.
Investment
Why this differs from my first note. My earlier message quoted $850 on a 4–5 day fast-track. Once I mapped the real page count and added the things that were missing — the parallel staging build, Google Ads URL updates, Search Console handling and 30 days of post-launch monitoring — that number no longer covered the work. I would rather quote what the job actually takes than discover it halfway through and start negotiating. The scope above is what $1,100 buys, in writing.
To begin
Asking for all of it once, so I am not coming back to you piece by piece mid-build. Please create accounts for me rather than sharing your own passwords — it is safer for you and you can revoke access in one click at any time.
A new Administrator account at soaplakeresort.com/wp-admin — not your own login.
Add me as a contributor, or I can build in my agency workspace and transfer full ownership to you at handover.
Wherever soaplakeresort.com is registered. Needed only on switchover day.
Owner or full access to the soaplakeresort.com property.
Editor access, so tracking is reconnected the moment we switch.
Standard access to audit and update final URLs and sitelinks.
The correct booking link or property code for each room type.
Logo files and original photography if you have them — otherwise I will extract from the existing site.
Your preferred low-traffic hour and day for pointing the domain across.
A quick number, so we confirm the 15-post allowance is right before we start rather than after.
Next
If anything above should be scoped differently — a smaller first phase, a different sequence, a narrower starting point — say so and I will restructure it. And if a short call is easier than typing, send me a time that suits you and I will work around your schedule.