After your SEO website goes live, the work does not stop at launch. Dobble treats SEO as a long-term strategy, not a one-off website task. The launch is the point where the technical foundation, site architecture, content structure and tracking are put into the live environment, then refined over time through ongoing SEO activity.
Before launch, Dobble develops and tests websites in a secure staging environment where possible. This allows the website to be reviewed, refined and approved before it is deployed. Once launch is approved, Dobble performs final testing, deploys the website to the live environment and completes relevant launch tasks such as analytics setup, sitemap submission, indexing checks and technical verification.
After launch, the focus moves into ongoing SEO implementation. Dobble’s SEO engagements run over 24 months and include a structured roadmap informed by market research, keyword clustering, search intent, site architecture and technical performance. This may include content writing, editing and publishing, on-page optimisation, technical refinements, internal linking, performance improvements and expansion of service or location pages where appropriate to the strategy.
Dobble does not guarantee rankings, traffic, leads or revenue, because SEO outcomes depend on competition, search engine changes, website quality, content, technical performance and user behaviour. Instead, progress is assessed through practical indicators such as work completed, website performance, keyword visibility, organic search trends and sustainable improvement over time.
Handover depends on the project and agreement. Dobble primarily builds websites using its proprietary Genesis CMS. Clients who request CMS access can be provided with a limited user account containing the permissions required to manage approved website content. Access levels are assigned at Dobble’s discretion to help protect the integrity, security and functionality of the website. Where requested, Dobble can also provide basic training and documentation for common content management tasks.
It is important to separate content ownership from platform ownership. Clients retain ownership of content they provide, including logos, branding, text, images and other business assets. Dobble retains ownership of its proprietary website source code, Genesis CMS software, frameworks, development tools, templates, source files and related intellectual property. Clients are granted a licence to use the website and Dobble’s proprietary CMS while their SLA remains active and their account is in good standing.
Maintenance and aftercare may also include hosting, security monitoring, backups, uptime monitoring, domain management or email support, depending on the client’s agreement. Where Dobble manages hosting infrastructure, it aims to maintain 99.9% monthly uptime for websites and hosting services managed on its infrastructure, subject to exclusions such as scheduled maintenance, emergency maintenance, third-party outages, DNS issues, client-side connectivity problems, force majeure events and issues caused by client changes or third-party systems.
For hosting, maintenance, domain and email clients, Dobble provides support 24 hours a day, 7 days a week. Emergency support is available, with response times typically within 4 hours. If a client is outside an SLA, emergency work is charged on an ad hoc basis, with quotes, predictions or capped timing supplied before work begins where applicable.
SEO reporting is available, but scheduled monthly SEO reports are not a standard inclusion unless specifically agreed in the client’s package or proposal. Clients may request an SEO report during their engagement, which can outline work completed, website performance, keyword visibility and other relevant SEO metrics. Additional reporting frequency or customised reporting can be arranged where agreed.
Dobble’s aftercare is designed to keep the website structured, maintained and aligned with long-term search performance. The aim is to support gradual, measurable improvement through a Search-First Strategy, rather than treating launch as the end of the project.