Article by Ardan Michael Blum CEO at A. Blum Localization Services. The Palo Alto SEO agency provides search engine optimization consulting, website reviews, service-page writing, content strategy, and localization planning.
Navigation: Index of Blog Posts
Revised October 22, 2026
Consider a hypothetical consultancy whose owner has noticed fewer suitable inquiries. Website visits appear much the same, so the owner wonders whether the home page needs a rewrite. That is a plausible place to look, but the concern reaches beyond the words on the screen. Somewhere between finding the business and discussing an assignment, fewer people seem to be arriving. A useful website review begins by locating what has changed closely enough to decide what deserves attention.
I would first ask what “fewer inquiries” means. It might mean fewer messages received, fewer requests that fit the service, or fewer prospective clients proceeding after a conversation. Each description points toward different evidence. A change in prices or availability also matters: people may still be contacting the business while fewer of those conversations lead to work. Before comparing periods, the owner and reviewer need to agree on what they are counting.
The records themselves deserve examination. If the owner counts inquiries by reading an inbox, that count depends on messages reaching the inbox and being recognized there. The website can invite contact, accept a submission, and display a confirmation while a later part of the process needs attention. I would want to understand how an attempted inquiry becomes something the business can answer.
Where the agreed review includes checking the contact route, a clearly labeled test can help follow that sequence. The reviewer and owner can establish what the sender sees, whether the submission or its notification reaches the intended destination, and whether the submission appears in the record used to count inquiries. The test should remain identifiable so that nobody mistakes it for a prospective client. Its purpose is to examine a particular route under known conditions.
Suppose, in this hypothetical review, the test appears among the form’s stored responses, but the notification goes to an old inbox that nobody responsible for inquiries now monitors. The submission is stored, yet its notification has not reached the inbox where the owner expects to receive it. A reviewer can describe that discrepancy precisely. The next work concerns the notification destination and the stored responses, with responsibility for making any change agreed separately.
The stored records may also help establish whether earlier messages await attention. Their dates matter. An inquiry submitted three weeks ago remains an older inquiry even if the owner discovers it today. Counting it as new would make the subsequent report misleading. Correcting the contact route and recovering overlooked correspondence could improve the owner’s handling of requests without establishing that more people have become interested in the service.
After a correction, another labeled test can check whether the intended recipient now receives the notification. That establishes something useful about the revised route. It cannot reconstruct every earlier attempt, particularly if the available records begin after the suspected problem. The review should leave the owner with a clear account of the observed failure, the correction made, and any historical question the records cannot answer.
A working contact route can still ask for more than the reader is prepared to provide. Imagine that the consultancy’s service page invites a preliminary question, while its form requires a detailed project specification. Someone who wants help deciding what work is needed now faces a demand to define that work before making contact. The invitation and the form describe different starting points for the relationship.
The business may have a sound reason for asking detailed questions. A brief can reveal whether a request falls within its services and give the person replying enough information to prepare a useful response. If the business can consider only projects that have already been defined, its invitation should explain that. Making the requirement visible helps prospective clients judge whether they are ready to inquire.
For a consultancy that helps clients define the problem, however, a finished specification may ask the reader to supply part of the work they hope to commission. Such a reader might be able to describe the difficulty and its consequences while remaining uncertain about the cause. Requiring a diagnosis at that stage can obscure the distinction between asking whether the service fits and beginning the substantive assignment.
The decision concerns which information is needed before an initial response. The owner might retain a question about the problem while moving a detailed request for proposed deliverables to a later conversation. Another business might keep the full brief and revise its invitation. Either decision should follow the service offered and the information needed to assess fit. The observed mismatch justifies examining those requirements; it does not reveal how many people abandoned the form.
The service page should also make the next step understandable. A reader considering a website review may need to know whether the assignment produces written findings, revised copy, or implementation work under an agreed scope.
The inquiry process does not settle every question about how people reach the business. Returning to the hypothetical consultancy, suppose that visits to an informational article have increased while visits to the relevant service page have fallen. The stable overall total had concealed a change worth investigating. Discovering a notification problem would not explain why the service page receives fewer visits. Those two observations need to be assessed separately.
The source of those visits helps determine which records to examine. For unpaid website results in Google Search, Search Console reports appearances and clicks, which can be grouped by page or search query. A decline in newsletter visits would require different records. Search clicks, website visits, and inquiries describe different events; their connection has to be established rather than assumed. Search Console alone cannot tell the owner which visitors became suitable prospective clients.1
A comparison also needs appropriate dates and enough context to interpret them. A changed page address may warrant checking old links, while a seasonal service may require a longer view of demand. Google’s guidance on investigating search traffic drops describes technical problems and changing search demand among the possible explanations. The timing of a redesign or other change can suggest what to investigate, without establishing that it caused the decline.2
Some checks answer narrower questions directly. A page loading in a browser does not establish that Google has indexed it. Search Console’s URL Inspection tool distinguishes information about the indexed version from a live test of the current page; a successful live test does not guarantee inclusion or appearance in search results.3
The recommendations should show what each finding permits the owner to do. In the hypothetical consultancy, an outdated notification destination calls for a specific correction. The mismatch between the invitation and form requires a decision about the information needed at first contact. The decline in service-page visits calls for further examination of the relevant traffic. These findings differ in both their certainty and the work needed to address them.
A useful recommendation names the affected page or process, records the observation, and explains the proposed action. It should also make dependencies visible. A writer cannot accurately describe a service until the owner confirms what it includes. A change to a notification destination may require someone with appropriate access. Recording these details helps the owner distinguish work that can proceed from work waiting on information or a decision.
Verification continues after implementation. The revised invitation can be compared with the form’s requirements, and the corrected notification route can be checked. Assessing the effect on suitable inquiries takes different evidence. The record should preserve when changes were made and separate test submissions and recovered older messages from new inquiries. If the business also changes its offer, a later increase cannot simply be credited to the website revision.
The owner who initially considered rewriting the home page now has more immediate decisions to make. The outdated notification address can be corrected, and the invitation can be aligned with the kind of inquiry the business is prepared to receive. The service-page traffic decline remains a separate question. A home-page rewrite may eventually be justified, but its purpose must become as specific as the problems the review has already made visible.
These principles guide my work at A. Blum Localization Services. The SEO Consulting and Website Review service page explains the assignments available, possible deliverables, and how a written scope is agreed.
Google Search Console Help: Performance report overview and basic setup. Describes the search-result metrics and reporting dimensions used in the discussion.
Google Search Central: Debugging drops in Google Search traffic. Covers possible explanations, comparisons, and changes in search demand.
Google Search Central: How Google Search works, and Search Console Help: URL Inspection tool. Distinguish crawling, indexing, and serving results, and explain the limits of indexed information and live testing.
This article provides general information about search, business representation, and website review. It does not provide legal advice or promise rankings, traffic, or commercial outcomes. Advice for a particular business depends on its operating facts, permissions, and applicable requirements.
Disclosure: AI tools assist with research, summaries, drafting, and editorial review. Their use varies by article and stage of the writing process. Ardan Michael Blum writes, revises, and updates the content, shapes its arguments and interpretations, and makes the final editorial decisions.
See detailed Legal, Privacy and Accessibility information.
Navigation: Index of Blog Posts