Symptoms are typed literally. Pages missing from the index, a sitemap that will not process, duplicate parameters: somebody describing that behaviour has a defined problem and no interest in a general service page.
Only the prepared look up migration planning. A team assembling a checklist weeks before a replatform is exactly the client worth having, and reaching them then avoids the version of the conversation that begins with a traffic collapse.
Framework names qualify ruthlessly. A single-page application, a headless setup or a specific commerce platform brings enquiries where the rendering problem is already understood by both sides.
Large sites have their own vocabulary. Whoever is responsible for hundreds of thousands of pages looks up log file analysis, faceted navigation and index bloat, and that work is priced very differently from a small business site.
The score is both a trap and a doorway. Everybody searches for the number the tool shows; writing honestly about which part of it moves revenue and which merely turns a dial green separates you from anybody selling a percentage.
Cases carry this service. Crawl budget before and after, pages indexed, load time, a six-month curve: technical work is invisible until somebody shows the graph, and that is what a marketing director forwards internally.
The panic search happens on a Monday. Traffic halved over the weekend, or a release went out on Friday: a page describing how a first triage works, and what can be established in the first hours, catches somebody who will pay for speed.
International setups have their own vocabulary. Hreflang conflicts, country targeting, duplicate pages across regions and consolidated domains bring a buyer with real budget and very few places to look.
Structured data gets looked up by its result. Somebody after review stars, event listings or product snippets describes the feature rather than the specification, and a page in that language reaches them before any documentation does.
Say how you work with an in-house team. Whether you raise tickets, join their sprint, write the code or hand over a specification decides whether a technical audit ever gets implemented, and buyers who have been burned ask this first.