The short answer: expect stages, not one finish date
SEO does not switch on at a predictable moment. A useful page must be accessible, discovered, crawled, selected for indexing, matched to searches, shown often enough to generate data, clicked and then persuasive enough to create an enquiry.
For a service business starting with little non-brand visibility, 90 days is a sensible first learning window—not a promise of first place. The first month should prove foundations and initial discovery; the second should reveal relevant impressions and emerging pages; the third should concentrate effort on demonstrated winners and expose weak tactics.
Days 1–14: prove access and measurement
Confirm important pages return correctly, use self-canonicals, appear in the sitemap, receive internal links and are not blocked from crawling. Verify the stored enquiry and lead event separately from email clicks or button taps.
Google says a recrawl request can take from a few days to a few weeks and does not guarantee inclusion. Repeated requests do not make crawling faster, so use this period to improve page value and discovery rather than repeatedly pressing the same button.
Weeks 2–4: look for discovery and query fit
The useful signals are indexed priority pages, first non-brand impressions, relevant query themes and accurate local-profile coverage. A new page appearing for imperfect long-tail searches can be a better early signal than an arbitrary headline position.
If a page is still not indexed after 7–14 days, inspect the response, canonical, robots rules, sitemap, internal links, duplication and usefulness. Fix the cause before requesting another crawl. A submitted sitemap is discovery help, not ranking or indexing proof.
Days 30–60: separate visibility from persuasion
At this stage, compare the same queries, landing pages, devices and locations. Rising impressions with weak click-through rate point toward title, description or intent mismatch. Clicks without qualified enquiries point toward offer clarity, proof, friction or poor query quality.
Search Console data is assigned largely to canonical URLs and can omit anonymised or lower-volume query rows. Use trends in impressions and clicks, not one average-position number, and keep Maps grids separate from organic web performance.
Days 60–90: move effort to proven clusters
Strengthen the service or problem cluster already earning relevant impressions: improve decision support, add verified case evidence, link related pages, and promote the most useful asset to relevant local or industry sources.
Merge or clearly separate pages competing for the same intent. Stop directory, outreach or publishing tactics that show no leading indicator across two comparable review cycles. The goal of month three is not maximum output; it is a smaller number of stronger bets.
Why one business moves faster than another
Existing demand, site history, competition, technical condition, content quality, reputation and the relevance of external references all change the learning speed. A recognised firm with useful proof and an established site starts from a different position than a new domain with no references.
The query matters too. A specific service-and-problem search may become visible before a broad head term. Local visibility also varies by searcher location, so one map check beside the business cannot represent an entire service corridor.
What can be verified quickly
Technical corrections, published copy, canonical tags, sitemap entries, structured data, internal links, conversion storage and profile accuracy can be verified immediately or soon after release. These are completed inputs, not acquisition outcomes.
A supplier should distinguish built, deployed, crawled, indexed, shown, clicked and converted. A dashboard task marked complete proves only the task; it does not prove that a search engine accepted the page or that a prospect enquired.
What should never be guaranteed
No supplier controls Google’s crawl timing, competitor improvements, demand, distance or ranking systems. Guarantees of a fixed position by a fixed date usually hide a weak definition, an irrelevant keyword or a tactic that creates long-term risk.
Reasonable commitments are operational: a defined release cadence, quality gates, transparent link records, matched weekly reporting, budget limits, response times and decision rules. Outcomes can be targeted and measured without pretending they are purchased.
A 30/60/90-day decision table in words
At day 30, require clean crawlability, accurate measurement, stronger commercial pages, a truthful local entity and first discovery evidence. If nothing moves, recheck intent, technical access and competitor gaps before increasing volume.
At day 60, require relevant impressions or local visibility on at least part of the matched set. If impressions rise, improve the pages and snippets earning them. If they remain flat, narrow toward stronger commercial long-tail needs and acquire better evidence or references.
At day 90, require a clear classification for every tactic: scale, maintain, revise or stop. Rankings and enquiries may still be developing, but the programme should know which clusters are earning attention, which pages persuade and which activities are waste.
Questions to ask in every weekly review
Which priority pages were crawled or indexed? Which non-brand queries and pages changed on a comparable date range? Did matched Maps coverage change at the same grid points? Were any genuine enquiries stored, and which landing path preceded them?
What was published, promoted or corrected—and what provider or user-facing evidence proves it? What will receive more effort next week, what will be changed and what will stop? A useful review ends with decisions, not a larger activity count.