Measure, prioritise, implement and report honestly

• 1. Connect: Website, Search Console, Analytics and relevant advertising or local sources.
• 2. Understand: Goals, offering, priority pages and existing measurement quality.
• 3. Improve: Small, verifiable changes with clear boundaries for risk and publication.

Onboarding that does not feel like work

For each connection, customers see why it is needed, what access is requested and what happens automatically afterwards. We do not request systems or permissions that are unnecessary for the chosen package.

• Clear progress and next step
• OAuth where possible instead of separate keys
• Minimum permissions per source
• Immediate verification that data is actually arriving

Prioritise customer value

We prioritise problems that block indexing, conversion or relevant visibility. A technical error across all service pages matters more than dozens of cosmetic warnings.

• Impact on revenue goals or discoverability
• Number of important URLs affected
• Quality of evidence and measurability
• Implementation risk and reversibility

Only an update worth reading

A small traffic increase or a single keyword movement does not trigger an email. Material conversion growth, sustained strategic rankings or work verified as live can do so.

• Complete comparison weeks
• Fresh source data
• No duplicate conversions
• No repetition of previously reported work
• Direct link to evidence

From the first connection to a repeatable working rhythm

Onboarding begins with four practical decisions: which business goals matter, which data sources they require, which URLs take priority and who may approve different types of changes. We request only the access needed for the chosen service and explain which data each connection reads or uses. A connection is only ready when the correct organisation, property or advertising account has been selected and current data is demonstrably arriving. A successful login without a verified source is not completed onboarding. Missing access remains visible as one concrete action with an owner, consequence and recovery path.

The baseline measurement is followed by a short cycle of selection, implementation, verification and reprioritisation. Not every channel needs to be active from day one. If conversion measurement is still unreliable, for example, technical repairs can proceed while performance comparisons are deliberately postponed. In each cycle we choose work that can actually be completed with the available access and capacity. This prevents the customer journey from feeling like a long questionnaire and avoids artificial pressure to activate every possible integration immediately. Each next step should explain why it is needed now and which decision or implementation it enables.

• First confirm goals and primary conversions in plain language
• Connect only relevant data sources and verify the correct account selection
• Record priority pages, owners and publication boundaries
• Equip the first worklist with evidence and acceptance criteria
• Base the next cycle on new information, not a fixed task volume

Which actions need approval, and how is a change reversed?

Changes agreed in advance with limited risk can be implemented within a clear set of rules without requesting permission again for every small item. For example, repairing a broken internal link when its destination and context are unambiguous. New commercial claims, pricing information, major template changes, tracking changes, advertising budget increases and actions with broad customer impact require explicit approval from the designated owner. Decision rules are recorded at the start and remain visible to the customer. Automation therefore means recurring work runs smoothly, not that unclear or major decisions are made without oversight.

Every change with substantial reach has a recovery path. We retain the previous state or a verifiable diff, record when the change went live and identify which signal would trigger a rollback. For a technical incident, we first assess the impact on visitors, measurement and indexing; then we restore or pause within the agreed authority. A failed publication is not hidden inside a general progress score. Customers receive a factual explanation of the impact, recovery, remaining uncertainty and any further decision. This keeps speed, ownership and safety within the same working method.

• Pre-authorised: small, reversible and within recorded rules
• Explicit approval: new claims, budget, broad publication or high technical risk
• Always record: owner, time, change evidence and recovery path
• When uncertain: pause and make the required decision visible

You receive an update only when there is something real to report

A customer update is useful when important work has gone live, a reliable complete measurement shows a relevant change, a blocker has consequences or a customer decision is needed. The message starts with what it means for the business, then states what changed, which evidence is available and what comes next. A green arrow, a single moving keyword or a general list of checks is not a reason for a separate email. When there is nothing decisive or demonstrable, information remains in the dashboard so useful messages do not get lost among routine updates.

A valid work update might read: ‘The incorrect canonicals on three priority pages have been fixed and verified live; Search Console still needs to reprocess the change.’ This example distinguishes completed work from an effect that is not yet known. A brief movement at a single measurement point is not presented as growth. Performance updates identify the source, period, comparison baseline and relevant limitations. Customers then see one concrete next step, or that no action is needed. This keeps reporting readable, personally relevant and useful for decisions without wrongly treating silence as a lack of progress.

• Send an email: important work live, relevant development or a decision needed
• Do not email: noise, incomplete periods or the same result repackaged
• Always include: meaning, evidence, limitation and next step
• Use the dashboard for details that need no separate attention

Frequently asked questions