Attors Technologies provides website care for businesses that need planned updates, monitoring and a clear route for support. We agree the platform, coverage and responsibilities around your site's real operation.
Website maintenance is recurring work that keeps an existing site manageable. A specific fault or larger technical improvement may need a separate, defined engagement.
For a working website that needs a planned update cycle, monitoring and an agreed route for routine issues.
For an identified issue or a bounded improvement that needs investigation and a clear delivery scope.
Maintenance brings repeatable checks and ownership to an existing site. We begin by understanding the platform and the customer actions it must keep supporting.
Review Your Maintenance NeedsOutdated components accumulate risk. We review dependencies and plan supported updates with appropriate compatibility checks.
A backup file alone does not prove recoverability. We confirm coverage, retention and scoped restoration tests.
A working homepage can hide a broken enquiry path. We identify the critical journeys that need checking.
Scattered messages make responsibility unclear. We agree an intake route with useful issue information.
Uncontrolled live edits can cause regressions. We use appropriate testing and keep a change record.
Hosting, plugins and custom code may have different owners. We map escalation routes and access responsibilities.
Coverage depends on the platform and its operating model. WordPress maintenance differs from managed platforms where the provider controls core infrastructure.
Define Your Website CoverageInventory the platform, hosting, extensions, custom code, access and known issues before accepting ongoing maintenance.
Review supported updates, dependencies and testing needs. Confirm appropriate backup and rollback options before applying changes.
Agree what is backed up, where copies are stored, retention and restore-test responsibilities. Identify gaps affecting recovery.
Set the agreed checks for availability and important website functions, with a clear alert recipient and response boundary.
Review reported problems, reproduce them where possible and explain the fix, dependency or separate scope required.
Handle agreed minor content or configuration changes within the defined allowance and approval process.
Test the pages, forms or purchase steps included in coverage after relevant maintenance changes.
Record completed work, exceptions and outstanding risks so your team can see what needs attention.
The service makes completed work and remaining responsibilities visible. Your agreement sets the frequency and depth of each item.
An inventory of the supported platform, dependencies, access owners and initial issues.
Included tasks, service windows, allowances, exclusions and escalation responsibilities.
A record of scoped updates, testing and any deferred changes requiring action.
Documented backup coverage and results of the restoration checks included in the plan.
Agreed checks and alert routing with an identified response owner.
Reported issues, investigation findings, completed fixes and unresolved dependencies.
A scoped summary of completed care, exceptions and recommended priorities.
Relevant access ownership and operational notes when the support arrangement changes.
An existing website is reviewed before recurring responsibilities are accepted. Serious baseline issues may need a separate stabilization task.
Explore Our Full ProcessIdentify platform, hosting, custom code, key journeys and current issues.
Set tasks, service windows, escalation and safe collaborator access.
Review backup coverage and establish the checks required for planned changes.
Apply approved updates or fixes with suitable checks and a change record.
Assess incoming problems within the agreed scope and route supplier dependencies.
Summarize work, deferred risks and changes in the site's support requirements.
Maintenance reduces avoidable risk but cannot remove every failure. Testing, recovery options and supplier boundaries need to match the website's importance to the business.
A typical WordPress recovery needs both files and its database, not just exported pages.
Identify storage locations, available versions and who can retrieve the backups.
Confirm whether staging is available and suitable for the planned change.
Prevent test activity or an old restore from unintentionally replacing current business records.
Document support availability and severity handling without assuming round-the-clock coverage.
Record where hosting, DNS, platform or extension support must be involved.
Identify subscriptions, unsupported dependencies and limits on routine updates.
Agree who approves disruptive work and larger repairs outside maintenance scope.
Start with the website URL, platform, hosting details and the issues your team encounters. Do not send passwords through the enquiry form; access is arranged through an appropriate process later.
Onboarding depends on site complexity, access, documentation and existing faults. Routine scheduling and incident response follow the agreed coverage; urgent resolution times are not promised before the support requirements are understood.
Platform complexity, critical functions, service windows, maintenance frequency and included changes determine pricing. Hosting, premium licenses, major development and incident recovery are clarified separately.
Name someone who can approve changes, explain customer impact and coordinate access with hosting or other suppliers.
The care agreement defines covered systems, allowances, response expectations, exclusions, reporting and the process for ending or changing support.
Practical answers about coverage, backups, updates and responsibilities.
Yes, subject to an onboarding review. We assess access, code or platform condition, licensing and known issues. Unsupported components or undocumented custom work may require stabilization before we accept ongoing care.
We review the platform and required tasks before confirming coverage. Managed platforms control some infrastructure themselves, while WordPress and custom websites can require different update and backup responsibilities. The agreement names what Attors can maintain.
No. Recovery depends on completeness, usable versions, storage access and the website's dependencies. For a typical WordPress site, both files and the database matter. The support plan specifies backup coverage and any restore testing.
No such coverage is implied by this page. Service windows, issue priorities and response expectations are agreed in writing. Resolution also depends on the fault and any hosting or platform supplier involved.
Minor updates can be included within a defined allowance. New features, substantial design changes, integrations and larger development tasks are separately scoped. Your care agreement explains how requests are assessed.
We assess the issue and use the agreed recovery or rollback approach where appropriate. Relevant functions are tested again after the correction. The plan must account for recent orders or other live data before restoring an older backup.
Not automatically. A suspected security incident needs a separate assessment and may involve the hosting provider or specialist incident response. Routine care does not guarantee immunity from compromise or include unlimited forensic work.
Yes. Your business retains ownership of its website and supplier accounts. We use appropriate authorized access and document responsibility for subscriptions, backups and operational notes during onboarding and handover.
Explore selected website projects for examples of our engineering work. Project inclusion does not imply a current maintenance contract, continuous monitoring or a particular service-level commitment.
