Honest about staying
A small working site is a small working site. Migration is the bigger invoice, which is why the recommendation has to be worth trusting.
Keep it running, or move it somewhere with a future.
Weebly still runs plenty of working sites, and most of what I am asked for now is a careful move off it. I will do either – including telling you to stay put if the site is small and doing its job.
Weebly was one of the original drag-and-drop site builders, and for a long time it did its job well: a small business could get online in an afternoon, with hosting, security and updates handled by somebody else. A great many perfectly functional sites were built on it and are still running.
Since the Square acquisition, development attention has clearly shifted towards Square’s own commerce products. That is not a reason to panic, and I am not going to dress it up as one – existing sites continue to work. It is a reason to make a deliberate decision about where your site lives over the next few years, rather than drifting.
The constraints are the familiar ones for a hosted builder. Layout control ends where the theme ends. Custom functionality means embedded code sitting on markup you do not own. Technical SEO control is narrower than on an open platform. And leaving is a rebuild, because there is no export that produces a working site elsewhere.
So the honest position is this. If your site is a few pages, it works, and it brings in the enquiries you need, staying is fine and I will say so. If it is central to your business, or you are finding things you want to do that the platform will not allow, the question is when to move rather than whether.
Broken layouts, forms that stopped delivering, mobile problems and content restructuring on an existing site.
A working site again without committing to a rebuild you may not need yet.
Embedded HTML, CSS and JavaScript to push past theme limits, with the fragility stated up front.
The behaviour you want, with honest expectations about how long it will hold.
Titles, descriptions, URL settings and structured data set up within what the platform exposes.
The available controls actually used, which on most of these sites they are not.
A full catalogue of every page, URL and asset, with traffic data attached to each.
You know exactly what you have, which is useful whether you move or not.
Content moved, design rebuilt, forms recreated and every URL mapped and redirected before launch.
A site you own, on a platform with an active future, keeping the visibility you have.
A straight comparison of staying versus moving, with costs over three years both ways.
A decision made on arithmetic rather than on anybody’s roadmap announcement.
Mostly about not rushing you into a migration you do not need.
A small working site is a small working site. Migration is the bigger invoice, which is why the recommendation has to be worth trusting.
Every page, URL and asset catalogued first, with traffic attached – useful whichever way you decide.
Built from a crawl of the live site and verified on staging, because this is where migrations lose traffic.
The existing site stays live and taking enquiries until the new one is signed off and DNS is cut over.
Embedded code on a platform you do not control is fragile. You hear that before it is written, not when it breaks.
What you own, what you rent, and what leaving costs – while the information is still useful.
Almost always about the same decision.
A site built years ago that still works, where nobody is sure what happens next.
Something straightforward elsewhere that simply cannot be done here.
Where the site now matters commercially and its limits have started to cost real money.
Catalogues or fulfilment that have outgrown what the built-in tools handle.
Recommendations from a consultant that cannot be implemented on the platform.
Years of subscription with no asset at the end of it.
Plenty of small businesses across Bangalore built on this platform in its busier years, and many of those sites are still quietly working. What has become harder is finding anyone who will look at one – most agencies will only quote for a migration, because that is the larger job.
I will do either. If your site is small and working, the useful deliverable is often just an inventory and a straight answer, which costs very little. If moving is right, it gets done properly, with every URL mapped rather than the handful someone remembers.
I work with businesses across Bangalore and India, and with clients in the UK, USA, Canada, the UAE and Singapore.
Sites most agencies will not quote for.
Know what you have before deciding anything.
Every URL mapped, nothing dropped.
India, the UK, USA, Canada, the UAE and Singapore.
Serving Chennai, Bangalore, India, Canada, UK, USA, Dubai, Singapore.
Small businesses, mostly, which is who it was built for.
Typically needs: Presence, contact details and enquiries from nearby searches.
How I help: Local information made consistent, enquiry paths tested, and an honest read on whether to move.
Typically needs: A modest catalogue and straightforward payments.
How I help: Store review against current needs, and migration to WooCommerce where it has been outgrown.
Typically needs: Events, notices and membership information on a small budget.
How I help: Content tidied and a low-cost path forward that does not assume a rebuild.
Typically needs: Credibility and a clear way to get in touch.
How I help: Service pages structured properly, with enquiry delivery verified end to end.
Typically needs: Notices, admissions information and staff details.
How I help: Content structure that non-technical staff can keep current, wherever the site ends up.
Typically needs: A site now central to the business, on a platform they do not own.
How I help: Full inventory, rebuilt design, mapped redirects and coverage monitored after launch.
Same discipline as any migration: the inventory and the redirects are the job.
I crawl and inventory the site – every page, URL, image and form – and pull traffic data so we can see what actually matters rather than guessing.
You get: A full inventory with traffic attached, and a straight answer on whether to move.
Why it matters: You cannot decide sensibly about a site nobody has catalogued.
The new site is planned: structure, what carries over, what gets improved, and what goes because nothing has visited it in years.
You get: A sitemap, a content plan and a fixed quote.
Why it matters: Copying everything wastes the one good opportunity to remove what is not working.
Design: carrying the existing look across or improving it, phone width first, built against your real content.
You get: Designs for the key page types, approved before building.
Why it matters: Leaving a hosted builder means rebuilding the design, and that gets scoped honestly rather than assumed.
The new site is built on WordPress, content migrated, forms recreated and integrations reconnected, on staging while the current site stays live.
You get: A complete site on a staging URL, with the old one still serving visitors.
Why it matters: No window where a customer cannot reach you.
The redirect map is built from the inventory, every old URL pointed at its new equivalent, chains flattened and the map tested on staging.
You get: A verified redirect map covering every URL the old site had.
Why it matters: Missing redirects are the single reason migrations cost visibility.
Launch at a quiet hour, analytics and Search Console reconnected, and coverage monitored while Google reprocesses the site.
You get: A live site you own, logins in your name and indexation watched afterwards.
Why it matters: A migration is finished when the index has caught up, not on launch day.
The platform as it stands, and where sites go next.
Depending on whether you are staying or moving.
The basics exist – page titles, descriptions and some URL control – and on most of these sites they have never been touched. Configuring them properly is cheap and often the single best thing that can be done without moving anywhere.
The ceiling is lower than an open platform: limited control over markup, no server-level configuration and constrained performance tuning. If your SEO work has run into those, that is a real reason to move rather than a preference.
Builder-generated markup is harder for anything automated to read cleanly. Within the platform, the moves that help are the simple ones: state the facts directly, use real headings, and keep business details identical wherever they appear.
The practical reasons, rather than the adjectives.
Most agencies will only quote for the migration, because it is the bigger job. If yours needs a two-hour fix, that is what you will be offered.
The platform’s shifted focus is a real fact and not an emergency. Your site works. The point is to decide deliberately rather than be frightened into it.
Every URL inventoried, mapped and tested before launch. Visibility lost in a move is a planning failure, not bad luck.
A complete record of your pages, URLs and traffic is useful whichever decision you make, and it costs a fraction of a rebuild.
Tell me what you need. I reply within one working day, and the first conversation costs nothing.