Guides
Guides for people who own the website, not the code
Straight answers for owners and operations leads on taking over a site from another team, rebuilding it, and keeping it running. Each guide starts with the short answer and ends with what it doesn’t cover.
-
GuideTakeover8 min read
How to take over a website from an agency without losing access
What to check first, the order to move accounts in, and what to do when your developer has stopped answering.
Read the guide -
ChecklistTakeover7 min read
Website handover checklist: accounts, code, data, domains
What to collect from an agency or freelancer before the contract ends, from the domain and DNS to backups, analytics and API keys. And how to check you really have each one.
Read the checklist -
GuideRebuild without losing what works8 min read
Rebuilding a website so Google can follow the move: what to carry over
Page addresses, redirects, titles and sitemaps: what has to survive a rebuild, what launch day looks like, and what a normal few weeks after it look like.
Read the guide
Topics
Five topics we write about
-
ATakeover
Getting a site back from another team, and keeping it alive
For when an agency is winding down, a freelancer has gone quiet, or nobody quite knows how the system works any more.
-
BRebuild without losing what works
Replacing an old platform without throwing away what it earned
When to rebuild, what to carry over, and how to move without losing search visibility, orders or data on the way.
-
CRunning a product with a team
What ongoing development should look like from the owner’s chair
Choosing between an agency, a freelancer, in-house hires or a dedicated team, and what a weekly report should tell you.
Related service: Support and maintenance
-
DIntegrations inside the system
Connecting the shop, the warehouse, the carriers and the spreadsheets
How order sync, shipping and quoting connections work, and where they tend to break.
Related: Integrations · Online shops · Logistics
-
ESearch, AI visibility, AI in the product
Being found by search engines and AI assistants, and using AI where it pays
What assistants read on your site, and where adding AI to an existing product makes sense.
Every guide is written by the Smartunex engineering team. Outside facts link to their primary source, and each guide ends with what it doesn’t cover. If you find a mistake, write to contact@smartunex.com and we’ll fix it.
Have a question these guides don’t answer?
Tell us about your site or system and what is bothering you. A person from the team will read it and reply.
We reply within one business day, Tallinn time (EET), usually within a few hours. No obligation.