How working with Viresto goes: from the first conversation and audit to implementation, reports and handover.
With a short conversation: goals (leads, a market, a launch), audience and regions, the current state of the site and constraints — budget, timing, who makes the changes. Then we review the site from the outside and suggest a format: a one-off audit or monthly support. You receive a proposal with scope, timeline and price before paying anything.
Not for an initial review: indexing, speed, structure, markup and AI visibility can be assessed from public data. A full audit needs read access to Search Console, Yandex Webmaster and analytics. CMS or server access is needed only if we implement changes ourselves; permissions are kept minimal and revoked after the work.
At the start both sides name a person responsible on the client's side and an approval process. Typically, technical fixes that do not affect design or copy follow the agreed plan, while changes to copy, structure and prices go ahead after the client confirms. All changes are logged in the report so it is clear what changed and when.
Usually a kick-off meeting, then a monthly call on the report and meetings on key decisions: restructuring, launching new sections or language versions. Day-to-day questions are handled by email or messenger. If the client prefers a different rhythm, it is agreed at the start; meetings should not replace the work itself.
Diagnostics and groundwork: a technical audit, checking and setting up analytics and goals, demand research, fixing critical indexing errors, a plan for priority pages and, in packages with GEO, a baseline measurement of visibility in AI answers. The month ends with a report of issues found, what has already been fixed and a plan for the next two months.
Yes, and it is often the best option: the client's experts know the product, prices and customers' real questions. We prepare the page structure, a list of questions and requirements for facts and headings, then edit the text for search and AI systems. That way the copy contains experience that is hard to get from outside.
Usually not. Most tasks can be solved on the current platform — WordPress, Tilda, Bitrix or a custom site. Switching CMS is justified if the platform does not let you control key things (URLs, canonicals, redirects, meta tags, speed) and fixing it costs more than moving. A migration is a separate project with a redirect map; otherwise traffic can be lost.
Yes. Tasks are handed over as technical specifications: what to change, where, why and how to verify the result — with a priority and acceptance criteria. We check the implementation before and after release. We adapt to the team's process: issue tracker, Git, sprints.
Agree the plan: which tasks come first, who owns each one and by when. Start with blocking errors — indexing, canonicals, redirects, availability — then pages for demand and content. After implementation, verify the changes and compare metrics with the baseline after 4–8 weeks. An audit without implementation changes nothing.
Yes; the procedure for pausing and terminating is set out in the contract, usually with a notice period. When we finish, we hand over everything prepared: reports, documentation of changes, the access we were given and a plan for further work, so that you or another contractor can continue without losses.
Nothing found.
