Website Care in Kufstein
You run a website for your business in Kufstein, but handover, access, or the last updates are no longer fully traceable. I start with a stock-take and derive clearly bounded local maintenance tasks from it.
Missing access credentials, unknown hosting contracts, or undocumented add-ons make even small changes harder.
During the stock-take, existing information is gathered and open responsibilities are named before I take on any maintenance tasks.
For smaller business sites, this is often updated hours or service information, form tests, and bounded fixes on existing pages.
Technical issues get described as concrete tasks. That doesn't create a general commitment to run the whole operation.
I check the available access, domain and hosting setup, contact paths, and visible dependencies of the existing solution.
The result separates necessary fixes from worthwhile updates and topics that call for a bigger rebuild.
Text within existing pages, contact details, and manageable technical fixes can be agreed as individual tasks.
New page types, fundamental navigation changes, or additional systems belong in their own project instead.
Maintenance only covers named websites, access, and tasks. Other topics get rescoped before work starts.
Legal advice, open-ended editorial work, and search engine rankings stay excluded.
If a topic moves outside the agreed area, it gets reassessed before further work.
A redesign is more appropriate once the old page structure blocks new services or the technical base can't reasonably be extended further.
Ongoing maintenance isn't quietly expanded at that point. A relaunch gets a new page plan and its own approval.
Yes. First I document access, structure, key content, and functions. Only then can a takeover be scoped sensibly.
I check available access, hosting setup, contact functions, system status, and known issues. That produces a prioritized task list.
Yes, if they're on existing pages and clearly described. New content areas are planned separately.
You describe the change you want; I check whether it fits the agreed area. Otherwise it gets its own scope before we start.
Yes. When individual fixes aren't enough anymore, the maintenance task ends and a standalone relaunch project gets planned.
Tell me the address of the existing site along with known access or open changes. That's what's needed to prepare the local initial check.