You should know when the work will arrive before being asked to wait for results. A useful timeline separates the changes your provider will deliver, the evidence you will review and the decision you will make next.
For a B2B service business, the aim is to reach buyers who need your expertise and help them take a useful next step. Publishing pages, appearing in search and receiving a suitable enquiry are different milestones. A proposal should explain how the work connects them.
Treat a 30-, 60- or 90-day plan as a delivery and review schedule, not a promised result date. First ask what “results” means: a fixed technical issue, a published service page, a sampled AI citation or a qualified enquiry. Each needs different evidence.
This guide explains how to evaluate any provider’s timeline. Our own month-one Setup and 42-day reading appear later as a specific example. For the commitment you are comparing, keep scope and cost, purchase economics and the delivery schedule together.
Separate four kinds of progress
| Progress | What you can inspect | What it helps you decide |
|---|---|---|
| Work delivered | Approved pages, technical changes and proof published, with dates and responsibilities | Did the agreed work ship, and does it answer the buyer’s decision? |
| Search observations | Page access, indexing, relevant search exposure and a recorded sample of AI answers | Are the intended pages being found and represented usefully? |
| Buyer response | Relevant visits, enquiries, fit and sales conversations where recorded | Is discovery reaching people the business can serve? |
| Next decision | The completed work, evidence, unresolved issues and next priority | Should we widen the work, fix a blocker, observe longer or change direction? |
A published page is something you can verify immediately. Its effect takes observation. Google’s SEO Starter Guide says changes can take hours to several months to be reflected, and generally advises allowing a few weeks before assessing them. Google also says some changes will have no noticeable impact. This is guidance for Google Search, not a forecast for AI citations or your business.
AI answers also vary by question, product and time. Record the conditions of a sample before comparing it. Allowing a search crawler access is a technical step; OpenAI’s crawler guidance does not turn it into a date for recommendations or enquiries.
What should be delivered before you wait for an outcome?
Require the proposal to name the deliverable, its owner, the input that starts it and the evidence that will mark it complete. Not every engagement includes every row below. An advisory scope may end with recommendations; an implementation scope needs someone responsible for publishing and checking the change.
| Milestone | Evidence to inspect | Question before marking it complete |
|---|---|---|
| Scope agreed | Priority service and buyer, affected pages or systems, exclusions and named owners | Are we buying advice, a draft or an implemented change? |
| Inputs ready | Required facts, access and proof permissions, with outstanding items recorded | What is missing, who owns it and which work actually depends on it? |
| Work ready for approval | The actual draft or change, its sources and a check against the agreed scope | Can our reviewer assess the work, rather than only a progress percentage? |
| Change published | Live page or system change, publication date and checks of the agreed behavior | Was the approved version published, and does the buyer’s next step work? |
| Observations collected | Source, dates, pages or questions, collection conditions and comparison limits | Is this a technical check, search observation, visit or enquiry record? |
| Review completed | What the evidence supports, unfinished work and the next action with an owner | What justifies continuing, changing the work, investigating or stopping? |
“Published” and “visible in search” are separate states. Google says a recrawl can take days to weeks, and a request does not guarantee inclusion. Repeated requests do not make crawling faster. A live technical check cannot establish that a page is ranking or being cited.
What can change the delivery and review dates?
| Starting condition | What to resolve in the plan |
|---|---|
| Existing site with useful history | Identify the affected pages and comparable baseline. Record work already in progress so later movement is not assigned to the new provider automatically. |
| New site or new service page | There may be no meaningful before-period traffic. Start with publication and access checks, then collect a dated starting record. No history does not justify inventing a baseline. |
| Another team controls implementation | Name the handover, reviewer and publication owner. An accepted recommendation may still be waiting for implementation. |
| Business facts or approvals are missing | List the specific dependency and its effect on the date. Separate client-held and provider-held work; a vague “waiting on access” status is not enough. |
| Several markets, services or site changes | Agree which work can share research and which needs separate review. A larger scope needs a delivery plan, not an assumed multiplier for results. |
| Few enquiries or a long sales cycle | A review may establish delivery and search activity before it can establish qualified demand or sales. Say which decision the available evidence can support. |
A simple site is not automatically a fast-ranking site. A large existing site is not automatically slow. Delivery effort, search processing and the buyer’s decision cycle are different constraints.
A worked sequence: one service page
Illustration, not a client schedule or outcome forecast. A consultancy wants a buyer to understand its compliance advisory service before making an enquiry.
- Agree the job. The scope names the service page, intended buyer, questions to answer and enquiry route. The consultancy supplies approved facts and permissions; the provider owns the draft and implementation.
- Review the actual page. The provider supplies the revised copy and layout, identifies supporting sources and records unanswered questions. A draft is ready for review, not yet a live change.
- Publish and verify. After approval, record the live URL and date. Check that the approved scope, service explanation and enquiry route are present. If publication is delayed, update the observation dates rather than reporting on a change that has not shipped.
- Read the evidence. At the agreed checkpoint, put delivered work beside complete search and enquiry records. If the page is accessible but observations are sparse, record that limit. It is neither a demonstrated commercial success nor proof the work failed.
For an actual published example, inspect the navigation change and search comparison in our hiring guide. It shows why evidence of delivery and evidence of an outcome need separate readings.
What a useful review should put in front of you
The structure below is an illustrative review agenda, not a client report or a set of predicted results. Use it to ask what your provider will bring to the conversation.
| Part of the review | What you should receive |
|---|---|
| The goal and delivered work | The priority, page addresses, change dates and any unfinished dependency |
| The comparison | Source, complete dates, relevant pages, market and filters, with the baseline beside the later reading |
| Discovery and buyer response | Search exposure, sampled AI appearances, referral visits and qualified enquiries kept distinct, where each is available |
| Interpretation | What changed, what may explain it and what the evidence is too limited to settle |
| The next decision | The proposed next work, its reason, who owns it and the next review date |
For examples of the work and evidence behind our approach, read our case studies. For comparing that approach with another provider, use the proposal worksheet.
Use the visibility and enquiry scorecard to gather the records for that conversation, including what the business actually received and whether it fitted the service.
If little has moved, make the next decision useful
Start with delivery. Did the right work go live? Can the pages be reached? Is the intended next step usable? An implementation fault needs fixing, not another month of waiting.
Then check the reading. Are the dates complete, are the measures consistent, and is there enough activity to interpret? A small sample or unchanged data can leave the result unclear. Say what additional evidence would help and set the next review point.
Finally, check the business response. More visibility with the wrong audience may call for a different priority. Suitable enquiries are worth examining even when headline traffic is modest. The next batch should follow what you learn about the buyers and the work, rather than a fixed publishing quota.
| What you find | Useful next decision |
|---|---|
| Agreed work is still undelivered | Resolve scope, responsibility and a revised delivery date. Do not describe unfinished work as a search-engine delay. |
| Published work has a verified fault | Assign and check the fix. Keep the fault and correction dates in the record. |
| The observation window is incomplete or very small | Explain what cannot yet be judged. Agree a bounded next check and its cost, if any. |
| Work is complete but the evidence does not justify more spending | Reconsider the priority, scope or provider, or stop under the agreed terms. Continuing is a decision that needs a reason. |
What our first three months cover
The following is SEO Informatica’s own delivery arrangement, not a market-wide timeline. The proposal names the priority services, market, pages, technical work, fee and responsibilities before we begin. Our starting plan has three months: Setup, then two months of Compound.
| Stage | What we do | What we need from your business |
|---|---|---|
| Before month one | Agree the goal, scope, implementation responsibilities, baseline and reading dates | The priority, relevant constraints and who can approve or implement changes |
| Month one: Setup | Research and write the decision pages, resolve confusing or competing content and implement the agreed technical basics in approved batches | Business facts, access, proof permissions and answers in week one; review each batch before publication |
| Months two and three: Compound | Choose and implement the next useful pages or fixes, strengthen proof, hold one check-in call and provide one plain-language report each month | About ten minutes per review batch and one call a month |
| Before the month-four decision | Review the first reading and the next priorities together | Decide whether the scope and evidence justify continuing, changing direction or stopping under the agreed terms |
Setup runs from approved inputs. If your answers are pending, its clock pauses. If another supplier controls publication or a technical change, the proposal needs to name that dependency. If a delay is ours, the work carries forward at no cost to you.
A new site or rebuild can be included in the plan’s agreed Setup scope. The separately quoted build is another route: the whole setup in one go within 21 business days of approved inputs, with monthly work optional from the month after launch. Compare the scope and cost before choosing between them.
From month four, the plan runs month by month, with 30 days’ notice to continue, pause or stop, no exit fees, and hosting covered while you pause. Delivery dates and review dates belong in the proposal, so you can see how they fit your decision.
How the 42-day reading works
The clock belongs to a published batch. Work still waiting for approval has not started its measurement window.
| Window | What happens |
|---|---|
| The 28 days before publication | Record the baseline for the relevant pages and measures. If comparable history is unavailable, say so and establish a starting record. |
| Day 0 | The approved batch goes live. Record what changed and which pages it affects. |
| First 14 days | Allow time before the comparison window. Check that the work shipped correctly; fix a verified fault as soon as it is found. |
| Following 28 days | Gather the comparison data using the same sources, scope and filters. |
| Around day 42 | Read the completed window against the prior 28 days, allowing for reporting lag. Record what moved, what remains unclear and what to do next. |
This is our review cadence. It does not mean Google has finished processing changes by day 14 or that an enquiry is due by day 42. Search Console API performance data is typically available after two to three days, so the report should identify the complete dates it actually uses.
Keep the comparison useful. A new page may have no meaningful history. Seasonality, other campaigns, changed tracking and overlapping site work can affect the reading. Record those factors and avoid crediting the batch with every movement.
Monthly reports and batch readings serve different purposes. The monthly report keeps delivery, observations and next priorities visible. A batch’s full window may finish between those reports. The first reading is planned before the month-four decision, with the dates agreed in the proposal.
If you want a delivery plan you can assess before committing, request your free Clarity Call. We can discuss the starting problem, work, responsibilities and price directly. If you prefer a written first look, request the free Outside View first.