Core maintenance
WordPress/core software updates, routine compatibility checks and maintenance work appropriate to the active website plan.
Support should be specific enough to understand: what is maintained, how requests are handled, what counts as a routine update and when a change becomes a new project.
The exact included work is controlled by the signed client agreement. This page explains the categories, not an unlimited-work promise.
WordPress/core software updates, routine compatibility checks and maintenance work appropriate to the active website plan.
Backup and recovery responsibilities are defined for the selected hosting/support scope instead of being left implicit.
Active website plans can include routine text changes, image swaps and minor content edits. New pages, features and redesign work are scoped separately.
Investigate broken links, form issues, redirect problems and other website-path failures that fall within the supported site.
Review obvious performance regressions, oversized media and front-end issues that materially affect the supported website.
Help maintain the measurement setup included in the project and investigate tracking issues when they relate to the supported implementation.
Routine care keeps an existing site healthy. A new calculator, customer portal, booking system, major page group or full redesign is product work and should be scoped as such. That distinction protects both the client and the quality of the website.
Public site unavailable, critical form/payment path failure, or a serious production issue affecting the primary customer journey.
Handled according to the support terms and access available for the client account.
Major feature or important page malfunctioning but the site remains generally available.
Triaged ahead of routine content work.
Text edits, image swaps, normal content updates, small visual corrections and noncritical questions.
Scheduled through the normal support queue.
New page groups, new integrations, major redesigns, custom software or substantial feature expansion.
Scoped and approved separately before implementation.
The project should leave behind clear account ownership, a known hosting environment, analytics access, documented integrations and an agreed request path.
See how SkyReelz plans around domains, DNS, email, old URLs, analytics and third-party tools before launch.
No. SkyReelz does not use vague “unlimited” language. Included maintenance and content work follow the active agreement; larger changes are scoped separately.
Active clients use the support/request process provided for their account. That keeps requests documented and connected to the correct client/project.
Only when a signed agreement includes that commitment. We define support expectations in the client scope rather than publishing a guarantee that may not apply to every plan.
Usually not. Minor edits to existing pages may be included; new pages, major sections, integrations and redesign work are treated as new scope.
When self-editing is part of the project, yes. We can provide appropriate access and training while retaining a controlled technical administration layer.
The completed site can be transferred to you according to the agreement, or SkyReelz can remain involved through an optional month-to-month care or growth arrangement.
If you want SkyReelz to stay involved, we scope the ongoing responsibility clearly instead of leaving it implied.