Ask for an explanation of the problem before comparing deliverable counts. A useful proposal connects evidence, recommended changes, and business outcomes without promising rankings.
You are buying decisions as well as implementation. Before agreeing to a partnership, ask the provider to show a sample audit, identify who will make changes, and explain how you will verify completion. Separate website work, GBP management, content, and reporting so a broad service label does not hide important exclusions.
5 signals that separate diagnostic work from surface-level optimization
- Crawl and index analysis: Ask for examples showing whether Google can access and index important pages, with rendered-content checks where JavaScript may affect availability.
- Citation audit with discrepancy report: Ask how records on Neustar and Foursquare will be reviewed, corrected, and tracked without assuming every mismatch causes a ranking loss.
- Competitor GBP teardown: Compare accurate categories, services, and visible information. Website schema and rich results are separate checks, not a way to reverse-engineer Google's local scoring.
- Baseline traffic attribution: Ask how GA4, call tracking, and DNI would measure organic inquiries, including privacy requirements, implementation costs, and gaps in keyword-level attribution.
- Lakewood intent mapping: Compare service needs and genuine customer geography using available query and inquiry data, rather than assuming every neighborhood needs its own page.
Request an example of a site-speed waterfall, GSC indexing findings, and a link review with plain-language priorities. A backlink toxicity score by itself does not establish a Google penalty. The useful question is whether the provider can explain impact, dependencies, and verification. Before paying for fixes, check that you own the relevant accounts and that the proposal identifies which findings are confirmed, suspected, or outside scope.








