Milestone 1: the agreed work is complete
Start with deliverables you can verify. Has the developer fixed the identified access problem? Are the approved service pages live? Have broken contact links been corrected? Keep a change log with the affected pages, completion dates and the reason for each change.
The date a task is completed is not the date search performance must improve. Ask your provider to separate work delivered from outcomes observed. Both belong in a report, but they answer different questions.
Milestone 2: important pages can be discovered
Check the technical foundations before judging content performance. Google identifies accessible crawling, a working page response and indexable content as minimum requirements. Passing those requirements makes a page eligible; it does not guarantee indexing.
Use Search Console to inspect important pages and investigate unexpected exclusions. Google says recrawling can take days to weeks and that submitting a request does not guarantee immediate inclusion. Repeated requests for the same URL do not speed up crawling. A sitemap helps discovery, especially when many URLs are involved.
Milestone 3: visibility reaches the intended audience
Search Console can show queries, impressions and clicks before a visitor reaches your website. Review whether the growing queries relate to services you actually sell and locations you can serve. More visibility for irrelevant questions is not automatically commercial progress.
Compare equivalent periods and inspect individual service pages, not just a total for the entire domain. Google’s traffic-diagnosis guidance highlights technical issues, algorithm changes, seasonality and changing interest as possible influences. A small movement in position should not trigger a complete strategy rewrite.
Milestone 4: visitors become useful inquiries
Website analytics describes what people do after arrival. Combine that view with your own inquiry records: service requested, suitability, whether the team responded and whether the inquiry became a conversation. Search Console clicks and analytics sessions use different measurement systems, so the totals need not match exactly.
If relevant clicks rise but inquiries do not, review the offer, contact path and visitor questions. If inquiries increase but are consistently unsuitable, review targeting and qualification language. If suitable inquiries go unanswered, the next improvement may be operational rather than another content page.
Agree on review points and decision rules
Build a reporting rhythm that fits the volume of evidence available. A low-traffic service page needs a different interpretation from a busy site with substantial history. At each review, note the baseline, completed changes, observed movement and unresolved questions.
- No discovery: investigate access, indexing and internal links.
- Discovery without relevant visibility: review the topic, page quality and competing results.
- Relevant visibility without clicks: inspect the search presentation and whether the page fits the query.
- Clicks without useful inquiries: test the customer journey and targeting.
- Qualified inquiries without sales: review follow-up and the offer.
Good questions. Clear answers.
Can an SEO company guarantee a number-one position by a deadline?
No. Google explicitly warns against first-place guarantees. Request a documented scope, realistic assumptions and evidence of progress instead.
Should I stop if the first report does not show more leads?
Use the diagnosis above. Check what was implemented and which stage lacks evidence before deciding. Continued spending should have a clear purpose and review process, rather than an indefinite promise.