Record a baseline that matches the business question
Choose relevant page groups, queries or inquiry categories and note the data available. Record campaigns, seasonal conditions and site changes that could affect interpretation. Some businesses have too little data for a quick confident comparison. A baseline is not a prediction; it creates a reference for later review and helps identify where the evidence is incomplete.
Use different checkpoints for different claims
A corrected technical issue can be checked after implementation. Search discovery and customer demand follow different processes and may need a longer observation period. Do not convert an implementation date into a guaranteed ranking deadline. Review the quality of incoming inquiries as well as visits, and document alternative explanations before attributing changes to one piece of work.
A practical check before you buy
For each planned action, write one completion check, one observable outcome and one limitation. Agree when each can reasonably be reviewed and what evidence would justify changing the plan.
| Decision | What to consider | What to check |
|---|---|---|
| Completion | Agreed change is live | Inspect the actual page |
| Discovery | Relevant search observations | Use comparable periods |
| Business outcome | Useful inquiries or sales | Record attribution limits |
An illustrative business scenario
A US seasonal service business can record seasonal demand and paid campaigns when comparing organic performance over time.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.