← Changelog
🔁 Standing implementation report

Transition plan · Build Your Home

The 301 strategy for promoting the Build Your Home microsite onto novafurnishing.com, if and when that happens. At v0.1 we're a standalone microsite at a separate domain (e.g. nova-build.vercel.app) so there are no legacy URLs to migrate from yet. This page lives at /redirect-plan/ and is noindex.

Current state at v0.1. This is a brand new microsite, not a rebuild of an existing path on novafurnishing.com. No old URLs to redirect away from. The plan below is the playbook we'd run if we ever promote the experience to a path under the main domain.

Possible promotion paths

Three scenarios where we'd execute redirects:

  1. Promote to a path on novafurnishing.com. Move the live URL from nova-build.vercel.app (or wherever we ship to) to novafurnishing.com/build-my-home. The microsite becomes a permanent landing page accessible from the main nav.
  2. Replace a legacy promo page. If Nova already has a "buy 3 special" or seasonal promo landing page, replace it with this experience and 301 the old URL.
  3. Sunset the microsite. If we wind down this experiment, redirect the standalone URL to the most relevant category on the main site (e.g. /collections/sofa) rather than leaving a dead page.

Redirect master plan (template)

To fill in when we know the target architecture. Both source and destination paths need to be confirmed before any deploy.

Source URLDestination URLTypeNotes
nova-build.vercel.app/→novafurnishing.com/build-my-home301Main entry point
nova-build.vercel.app/changelog/→novafurnishing.com/build-my-home/changelog/301noindex on both ends
nova-build.vercel.app/seo-report/→novafurnishing.com/build-my-home/seo-report/301noindex on both ends
nova-build.vercel.app/redirect-plan/→novafurnishing.com/build-my-home/redirect-plan/301noindex on both ends
Legacy promo path (if any)→novafurnishing.com/build-my-home301To confirm with Nova

Pre-promotion checklist

If we promote this onto novafurnishing.com, run through these before flipping DNS or rewriting routes:

  1. Update canonical URL in index.html from https://novafurnishing.com/build-my-home (placeholder) to the final destination.
  2. Update OG and Twitter card URLs to point at the destination.
  3. Add the destination URL to Google Search Console as a property and submit the new sitemap.
  4. Cross-link from main site nav. Decide where the entry lives (homepage hero CTA, promotions menu, etc.).
  5. Run a 301 audit. Crawl every internal link and confirm nothing 404s. Use a free tool like Screaming Frog free tier or `curl -I` against the top 20 paths.
  6. Confirm analytics still fire. The GTM container should pick up the new domain. Add a property to GA4 if needed.
  7. Confirm WhatsApp deep-link still works. The wa.me/6589537580 link is path-agnostic, so it's fine, but test once on mobile.
  8. Keep the old domain alive for 30 days minimum serving 301s before letting it expire. Search engines need time to refresh.

What NOT to do

Common 301 pitfalls we want to avoid:

  1. Don't 302 (temporary) when you mean 301 (permanent). Search engines don't transfer ranking signal on a 302.
  2. Don't chain redirects. A → B → C loses signal. Always rewrite to the final destination in one hop.
  3. Don't redirect to the homepage as a catch-all. If a specific source page existed, redirect to the closest specific destination, not the root.
  4. Don't forget the www vs apex decision. Pick one canonical host and 301 the other to it.