Optimization
Analyse, approve, execute, read back, observe, verify. Then again.
A change that went live has been made. A change that worked has been measured. Signal keeps the two apart in the record, in the dashboard and in every report, so improvement is something shown rather than something claimed.
- Ranked opportunitiesLive
- Signal managed executionLive
- Change and verification recordPartial
The loop
Six moves in every cycle
01
LiveAnalyse
Nightly reads of search, traffic, ads and the public site become ranked opportunities with impact, confidence, coverage, effort and dependency.
02
LiveApprove
Each proposed change is written up with the expected outcome, the access it needs and the approval level it requires under your scope.
03
LiveExecute
The Signal team makes the change in your account or on your site, and records who made it and when.
04
PartialRead back
The live account or page is read again to confirm the change is really there, in the form that was approved.
05
PartialObserve
The data is left to accumulate for the measurement window the change needs. Nothing is called a result early.
06
PartialVerify, then adjust
The observed outcome is compared with the expected one and recorded as verified, failed or rolled back. Either way, the next cycle starts from it.
The status flow
Where a change is, at a glance
- 01ProposedEvidence foundwhat was observed, where, and when
- 02ProposedRecommendationthe change, and why
- 03ProposedExpected outcomewhat should move, and by when
- 04ProposedApprovalwho agreed, under which scope
- 05AppliedAppliedwho changed it, and when
- 06AppliedLive read-backthe change confirmed in the account
- 07WaitingObservation windowenough time for the data to speak
- 08VerifiedVerified / failed / rolled backthe real outcome, compared
Applied is never shown as verified. A change that went live has been made. A change that is verified has been measured against what it was supposed to do, after the observation window, and the comparison is kept.
What the record keeps today
For website fixes, the record already holds the baseline scan, who selected the action, when it was deployed and with what reference, the re-scan it was verified against, and the verdict. The approval step and the observation window are being added to the same record; until then they are tracked by the team in the engagement notes.
Who executes
Managed by people, recorded by the platform
Signal managed execution
With your authorised access and agreed guardrails, the Signal team builds and changes campaigns, keywords, negatives, budgets, targeting, ads, landing pages, tracking and follow-up now. Every change is recorded with what changed, why, who approved it and when it went live.
SignalIQ automated execution
SignalIQ does not change any account by itself. Automated changes are a separate product capability with their own scope, approval, validation, audit history, live read-back and outcome verification gates, and they are not switched on today.
Status today
The capabilities behind this page
Ranked opportunities
LiveSearch and website findings are turned into ranked actions with impact, effort and risk, refreshed nightly.
Signal managed execution
LiveWith authorised access and agreed guardrails, the Signal team makes campaign, keyword, budget, landing page, tracking and content changes now, and records each one.
Change and verification record
PartialWebsite fixes are recorded with who selected them, when they were deployed and a re-scan verdict. An approval step and an observation window are not yet recorded.
Automated Google Ads changes
PlannedSignalIQ makes no changes to any ad account. A test in the codebase fails the build if a write call is ever added. The Signal team makes agreed changes by hand.
Start the first cycle
The free audit is the first analysis. What you approve after that is up to you.