How to preview a site rebuild before you commit to it
Short answer: To preview a rebuild, make a quick copy of three page types from your current site in a new builder, score it against your old pages, and decide before you spend real money. Ploy, a software subscription where an AI agent builds and hosts websites, can read your public address and rebuild pages for you to review, and nothing goes live until you approve. Treat the result as a preview, not a finished migration, because imports can miss dynamic features.
You are not sure a rebuild is worth it and want to see what your own site would look like before you commit money or a launch date.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A good preview answers five questions before you commit: does the new look suit you, does the structure make sense, which pages and features would not carry over, what would it cost and how long would it take, and what would happen to your search traffic. You can get rough answers to all five for little or no money by building a small copy of your own pages. The key rule is that a preview stays private and is never mistaken for the real site.
This guide gives a step-by-step way to do that, with options from a paper sketch to an AI import such as Ploy, a scorecard with pass and fail rules, and the redirect and indexing checks that stop a preview turning into a mess. Prices are as of November 2026, so check each vendor page.
This page may contain affiliate links from which Blur Studio earns commissions.
What a preview is for, and what it is not
A preview is a cheap test. It tells you whether to go on. It is not a launch plan and it is not proof that every feature will work. Ploy's own docs describe an import as a rebuild, not an identical copy, and say forms, plugins, shortcodes, embeds, interactions, custom code, private pages and live data may need separate work. Plan for that gap from the start, and do not promise a client or a boss a finished site because the preview looked good on three pages.
Options, from least to most effort
| Option | What you get | Cost (as of November 2026, check the vendor page) |
|---|---|---|
| Paper or Figma sketch (Figma is a design drawing tool) | Layout and page list only, no real build | Free, your time |
| Framer free plan | Framer is a design-first website builder. You rebuild pages by hand. Free plan has a Framer address and no custom domain | Free $0. Basic $10 a month and Pro $30 a month billed yearly ($15 and $45 billed monthly) |
| Webflow Starter | Webflow is a visual website builder. Starter has a webflow.io address, 2 static pages and no custom domain. Webflow says you cannot import code or sites | Starter free. Basic $15 a month and Premium $25 a month with yearly billing (monthly billing costs more, check the page) |
| Lovable | Lovable is an AI builder that makes apps and sites from chat | Free plan with daily credits. Pro $25 a month (check the page for yearly billing) |
| Ploy import | AI agent reads your public address and rebuilds pages on its own design system | Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote |
| Freelancer mockup | A designer builds a sample homepage | Quote or hourly rate |
Only an AI import starts from your real content. With the others you copy by hand, which is slow but costs nothing. For prices and limits of the Ploy plans, see the Ploy pricing guide.
Step 1: take a snapshot of what you have
Before any preview, write down what exists. This protects you later, whichever tool you pick.
- Page list. Download your sitemap or export a page list from your current platform. Ploy's migration-readiness docs (updated 10 November 2026) tell you to save the old sitemap URL list as your redirect map.
- Top pages. In Google Search Console (Google's free report on how your site appears in search), which pages bring the most clicks over the last 90 days? Those must keep their addresses.
- Features. List every form, booking widget, chat box, shop, login and embed.
- Three page types. Pick one of each: a home page, a service or product page, a content page such as a blog post.
- Screenshots. Capture each on desktop and phone. This is your baseline for comparing.
Step 2: build the preview copy
With Ploy, the route is short. Check that your site loads without a login, because the import needs a public address. Start on the Free plan, enter your address in setup, and choose one goal only, since each extra goal can start a chat that spends credits. If you chose to migrate, Ploy's docs say it inventories the site, shows a plan and waits for your approval, and large sites are done key pages first. Per Ploy's docs, its Agent can publish your first page once to your free ploy.build address, and your real site does not change. To keep even that unpublished, ask the Agent before it builds. Read Ploy site migration for the detail.
Ploy's migration docs say imports use AI credits, and larger sites use more. Ploy does not publish a price per action, so check Settings, then Organization, then Usage after the first run. Ploy's docs also list a free website migration cost calculator. You can also compare against the typical range in how much a website migration costs.
With another tool, rebuild the same three pages by hand, using the style note from matching your current website style.
Step 3: keep the preview out of Google
A preview that gets indexed can split your traffic or confuse customers. Do these checks.
- Ploy previews. Ploy's docs recommend adding a noindex directive (a tag telling search engines not to list the page) on staging or test pages, for example a test page published to Preview only. Its first page also goes once to a ploy.build address, so do not share or link that address from your real site.
- Google's rule. Google's noindex guide says the rule goes in a meta tag or an X-Robots-Tag header, and the page must not be blocked by robots.txt, otherwise Google never sees the noindex and the page can still appear in results.
- Preview address. Ploy's docs say your Preview address is your site name with staging- in front, such as staging-your-site.ploy.build, and that a preview-only publish does not update the live site. On the Free plan, pages on the ploy.build Production and Preview addresses show a small Made by Ploy badge.
- Private pages. Ploy's docs say private pages live under /private and are never published, but they are not password protected, so do not store anything secret there.
- Hide what you do not want. Ploy lets you right-click a page in the Pages panel and choose "Hide from published site" (changelog, 26 October 2026).
- No real forms. Ploy's docs say submissions from the editor preview or the preview address are saved and emailed like live ones. Do not send test leads to your real sales inbox, and do not tell customers to use a preview form.
Step 4: score the preview
Use a score for each row, from 0 to 2: 0 fails, 1 needs fixing, 2 is good. The weights below are my suggestion, so adjust them to your business.
| Row | Weight | Pass looks like |
|---|---|---|
| Look and feel | 2 | You would be happy to show it to a customer |
| Facts correct | 3 | Every price, address and claim matches. One error scores 0 |
| Structure and navigation | 2 | Same or better page list, clear menu |
| Phone view | 2 | No sideways scroll, buttons easy to tap |
| Features carried over | 3 | Forms, booking and embeds work or have a clear plan |
| URLs | 3 | Top pages keep their addresses or have a 301 plan |
| Cost and time | 2 | Credits used and hours needed fit your budget |
Worked example with made-up numbers. A small consultancy scores look 2 (weight 2, gives 4), facts 2 (6), structure 2 (4), phone 1 (2), features 0 (0, the booking widget did not copy), URLs 2 (6) and cost 2 (4). Total 26 of a possible 34. Decision rule: go ahead if the total is at least 75 percent and no weight-3 row scores 0. Here 26 of 34 is 76 percent, but features scored 0, so the rule says fix the booking widget first, then re-score.
Step 5: plan the URLs before you plan the look
The most common rebuild mistake is changing addresses without redirects. Google's site move guidance says to use permanent server-side redirects (301 or 308), go straight to the final destination, avoid long chains, and keep redirects for generally at least one year. It also says to expect temporary ranking fluctuation, and that medium-size sites can take a few weeks or more for pages to move.
For Ploy, the docs say prerendered pages drop the trailing slash by default, so an address ending in /about/ redirects to /about. Redirect each changed or removed address to its closest match using Path routing, and contact support at support@ploy.ai before migration day if you need more than 20 rules. Read how to keep SEO rankings when you rebuild and how to redirect old links after a redesign.
If the preview passes: switching without a big bang
Ploy's docs describe three ways to go live: move the whole domain, move one path at a time while the old site serves the rest through an "Everything else" route to the old host, or, for WordPress, a plugin called Ploy Connect that needs a paid plan. A path-by-path move lets you launch the best pages first and keep the risky ones on the old site. For the DNS part, follow the custom domain DNS and SSL guide. Ploy says DNS changes can take up to 24 hours, so do not judge the switch in the first hour.
Common ways a preview misleads you
- Judging on the homepage alone. Homepages get the most polish. Service and content pages show the real gaps.
- Counting credits as the whole cost. Your time fixing misses, plus a plan fee once you connect a domain, is usually the larger cost.
- Forgetting the people who edit the site. If staff cannot update the new version, the rebuild fails later. Have one editor try a text change during the preview.
- Treating a good score as a launch date. The scorecard says whether to continue. A launch still needs the redirect map, analytics checks and a rollback plan.
Who should skip this approach
- Your site is a store, a membership site or a booking system. The pages that matter are the live ones, and a preview of the static pages hides the real work. Ploy's own Webflow comparison page concedes that Webflow suits heavy programmatic SEO and ecommerce.
- Your pages are behind a login. The import cannot read them.
- You already know you will rebuild and have a designer. Skip straight to a written brief and a staging site.
- The site is tiny. If you have five pages, a hand-built copy in any builder teaches you as much as an import.
How I'd approach this
Preview in this order: inventory, three page types, privacy checks, scorecard, URL plan. Only then talk to a designer or pay for a plan. If you want the AI route, start Ploy on the Free plan, run the import on one page set, and stop when the scorecard says stop. If you also want a second view, build the same three pages in Framer or Webflow free and compare. Do not buy anything until you have scores for at least one real preview.
First-week plan. Day one: export the page list and screenshots. Day two: pick three page types and confirm the site loads without a login. Day three: build the preview and turn on noindex. Day four: score it with the table above and list what did not copy. Day five: decide using the rule: go ahead at 75 percent or more with no weight-3 zero, otherwise fix and re-score once, then stop. If the preview shows your old site needs more than a refresh, such as a custom app, a client portal or a finished version of a half-built site, I build that custom version and look after it afterwards: see what it includes.
You may also want what to do if rankings drop after a migration before you start.
You may also want refreshing an old website without starting over.
For a closer look, see testing a new product line page before a full rebuild.
Questions people ask
How do I see what my website would look like redesigned?
Rebuild three page types, home, service and content, in a free tier of a builder or with an AI import, keep it private, and compare to screenshots of your old pages. Score it on look, facts, structure, phone view, features, URLs and cost before you commit.
Will a preview change my live website?
Not with Ploy: its docs say nothing changes live until you approve a migration, and the first page goes once to a ploy.build address. Still add noindex to test pages and do not link to the preview address from your real site.
Can I import my site into Webflow or Framer?
Webflow says on its pricing page FAQ that you cannot import code or sites, and Framer has no official HTML export. You rebuild by hand in both. Check each vendor page for current details.
Will my Google rankings drop if I rebuild?
Google says to expect temporary fluctuation during a move, and recommends 301 or 308 redirects kept for at least a year. Keeping your addresses the same and redirecting any that change reduces the risk. See rankings dropped after a migration.
How much does a Ploy preview cost?
As of November 2026, Ploy's pricing page shows Free at $0 with 500 AI credits a day up to 2,000, Starter at $50 a month and Pro at $300 a month. Imports use credits and Ploy publishes no per-action price. Check ploy.ai/pricing.
What does not carry over in an import?
Ploy says forms, plugins, shortcodes, embeds, interactions, custom code, private pages and live data may need separate work. Make a list of these on your site before you start.
Should I show the preview to customers?
No. Show it to your team or client only. A private preview can still be indexed if noindex is missing, so add noindex and keep the address out of your real site's links.
When is a full redesign better than a preview?
When the site is a store or booking system, when brand work is needed, or when your preview scores below 75 percent after one fix round. Then brief a designer using what the preview taught you.
More in this topic: Websites: launching, refreshing and previewing a site (7 guides) →