Issue investigation
Understand a problem, review the affected workflow, and agree on the next work needed.
WebOrbit services
Keep the website you rely on working well.
A live website still needs attention as content, services, and business needs change. WebOrbit helps with issue investigation, updates, reliability work, and taking over an existing project.
A specific fix or ongoing care?
A broken form, a content change, and a recurring support arrangement are different requests. Explain the affected page or workflow, what you expected, and what happened so the first step can be focused.
For ongoing care, agree on the systems covered, who can request changes, and how work will be prioritized. A useful support arrangement makes those responsibilities visible.
Ongoing maintenance
An agreed approach to updates, fixes, checks, and changes over time.
Choose responsibilities you can actually track.
The exact coverage depends on the site and the agreement. Hosting, provider subscriptions, new features, and response expectations should be identified rather than assumed to be included.
- Content changes and adjustments to existing pages or features.
- Investigation and fixes for broken forms, links, or workflows.
- Software updates and checks on the affected experience.
- Performance and reliability improvements.
- Access safeguards and security review work.
- Hosting, account, or project handover support.
Get clarity before promising a fix.
Describe the current experience
Share the public site, the issue or goal, and the tools you know it uses.
Confirm authorized access
Identify who controls the domain, hosting, editing tools, and relevant connected accounts.
Review and prioritize
Assess what can be checked and separate urgent problems from improvements that can be scheduled.
Agree on the next work
Define the scope, access responsibilities, review steps, and ongoing care if needed.
Plan what moves before changing the public site.
A redesign may change the structure, content, or tools behind the website. A migration may move it to a different hosting or editing setup. In both cases, the existing pages and business workflows need a deliberate transition plan.
We can scope the review and transition alongside the build. Start with an inventory of the current public experience and identify which content, links, forms, accounts, and connections need to keep working.
Inventory the public URLs
List existing pages and important downloadable content. Decide which pages stay, move, combine, or retire.
Map links and redirects
Agree on the destination for changed URLs, a redirect plan, and updates to navigation and other links under the business's control.
Carry over the useful content and workflows
Review copy, images, contact information, forms, booking paths, and agreed integrations rather than moving pages without checking them.
Check the transition and ongoing care
Review the agreed launch checks, account access, recovery arrangements, and who handles requests or issues after the change.
Make support terms explicit.
Ask what is covered, how to submit a request, and what happens when a third-party service is involved. New development and ongoing maintenance may need separate scopes.
If your project is already with WebOrbit, use the client portal for project updates and support. For a new request or handover, start with a message about the affected public page or feature. Do not put account passwords or private customer records into the contact form.
Questions before the next step.
Can WebOrbit take over a website built by someone else?
We can discuss a takeover after reviewing the current site, the available access, and the work needed. The review helps define a realistic scope before committing to changes or ongoing care.
Does maintenance include hosting and new features?
That depends on the written scope. Hosting, third-party subscriptions, routine changes, new development, and response expectations should each be identified so you know what is included.
How should I report a website issue?
Describe the affected page or feature, what you expected, and what happened. Existing WebOrbit clients can use their client portal. New requests can start through the contact form without sending passwords or private customer information.
Let's make it work
Tell us what needs attention.
Start with the business problem. We can discuss the right scope together.