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
Imagine a business owner opening a local search report and finding that an average reported position of about 3.6 has become 8.6. The larger number looks like a substantial loss of visibility. Before commissioning new pages or changing providers, the owner needs to know what the report compared. A change in the measurement can resemble a change in the business’s fortunes.
In this hypothetical example, the first report sampled nine geographic points for one search query. The second used the same query, kept those points, and added sixteen farther away. At each of the original nine, the reported position remained exactly the same. The weaker positions at the added locations raised the overall average. The business has not lost position at the places measured before; the report now covers more territory.
That finding does not make the wider report useless. The additional locations may be neighborhoods where the owner wants customers, and weak visibility there could deserve attention. It changes the question from recovering an apparent loss to investigating an opportunity. If the business cannot serve those neighborhoods, however, spending money to improve visibility there may accomplish little.
This is where I would begin a local SEO review: establish what an observation actually shows, then decide what it warrants doing. The distinction matters because an owner must allocate money and time before every uncertainty is resolved. A useful report should help that decision by separating a demonstrated problem from a plausible explanation that still needs checking.
“We are not showing up” can refer to an unpaid website result, a business listing in Maps, or local business results within Google Search. These require different investigations. Record the query, the page or business being sought, the date, and the kind of result examined. A website’s absence from the first twenty results inspected establishes an observation within that limit, without explaining the cause.
A geographic ranking grid adds another set of conditions. It samples reported positions for a query at selected locations, so retain the coordinates, tool, and reporting depth when comparing scans. If a business was not found within twenty results, assigning it twenty-one for calculation is a scoring convention. Its actual position has not been measured. Google also cautions that third-party tools have no access to its internal ranking data; a pattern in their observations cannot by itself reveal the ranking mechanism.1
For a missing website page, begin with the exact URL. Google’s minimum technical requirements include crawler access, a successful HTTP 200 response, and indexable content. Meeting them does not guarantee inclusion in the index, Google’s collection of information about pages. An unintended instruction excluding a page from indexing calls for a technical correction before a larger writing assignment.2
Search Console’s URL Inspection tool distinguishes information about Google’s indexed version from a live test of the current page. A successful live test can help check a repair, but it does not establish that the page has entered the index. Conversely, index inclusion does not establish strong visibility for the intended search. Those distinctions determine whether the next question concerns access, indexing, or how the page answers a prospective customer’s need.3
Local business results introduce geographic constraints of their own. Google describes relevance, distance, and popularity as their main factors, explaining prominence as how well known a business is. This guidance does not disclose a complete formula. An accurate statement that a business serves Palo Alto therefore cannot establish where its listing will appear across the city.4
Once the intended destination is identified, examine what a person arriving there can learn. Being based in a city, receiving customers there, visiting their premises, and serving them remotely are different arrangements. A service page should make the relevant arrangement clear enough for someone to decide whether to inquire. A place name becomes useful when it explains what the customer can actually obtain.
Consider a hypothetical provider that visits customers in a neighboring city only on Wednesdays. That schedule affects a booking decision. The page should explain the available service, visiting day, and any limitations the customer needs to know. Depending on how much differs, the information might fit a regional service page or justify a separate city page. The choice should follow the amount of useful information and how readers will find it.
For a remote provider offering the same service through the same process in several cities, one regional explanation may be sufficient. Google’s doorway-abuse policy addresses pages targeting similar searches that send visitors through less useful intermediate destinations, including certain city-targeted pages. It does not prohibit every location page. My practical test is whether the proposed page answers a question the existing pages leave unresolved.5
Business Profile eligibility needs its own assessment. Google generally requires in-person customer contact during stated hours, with specified exceptions, and excludes online-only businesses. Its service-area definition concerns businesses that visit or deliver to customers. Providing a remote service to someone in Palo Alto does not, by itself, satisfy that definition. Website copy cannot establish eligibility by describing a wider area.6
The same attention to meaning helps when old business information remains online. A dated account of a former office can be accurate history. An undated invitation to visit that office can mislead a customer today. The latter deserves correction even if nobody can demonstrate a ranking effect. What matters first is the avoidable journey to premises where the customer will not receive the promised service.
After a repair or revision, the next report still requires interpretation. Search Console records clicks, impressions, click-through rate, and average position within its reporting scope. Click-through rate divides clicks by impressions. These measures describe search activity; an inquiry record is needed to learn whether the resulting prospects want a service the business can provide.7
Suppose a hypothetical page records 200 impressions and twenty clicks during one period, producing a ten percent click-through rate. In a comparable later period, it records 400 impressions and twenty-four clicks, producing a six percent rate. The percentage has fallen while the page has gained four clicks. If additional appearances came from different searches, the total may combine a stable response from the original audience with a lower response from the newly reached audience.
That is an explanation to investigate, not a conclusion supplied by the arithmetic. Compare relevant query groups under consistent page, search-type, country, and device settings, using complete date ranges. Keep the reporting limits visible: Search Console omits some queries for privacy and does not display every stored row. Its geographic grouping identifies the country of origin. A query containing “Palo Alto” does not show that the person searched from Palo Alto.8
Then examine the inquiries separately. If suitable new prospects increased from two to three, the business received one additional prospect. That may be valuable, but the small count offers limited evidence of a lasting trend. Define suitability consistently, separating genuine requests for an offered service from duplicates, spam, and requests the business cannot fulfill. Otherwise, a change in how inquiries are classified can produce another misleading comparison.
The hard part of this work is deciding how to act with incomplete information. A small business cannot suspend every improvement until it has proved what caused each fluctuation. It can, however, choose work whose purpose is clear. Repairing a failed contact form has an immediate justification. Adding an accurate visiting schedule resolves a customer question. Both can be checked directly after publication.
When the problem is weak discovery in an important area, start with a specific service and the page intended to explain it. Check whether the page accurately covers that area, answers the relevant service question, and can be reached through the site’s navigation. If a meaningful answer is missing, add it and record the reason. If the page already provides it, another paragraph containing the city’s name needs a stronger justification.
Agree on what will count as completion before the work starts. For the hypothetical Wednesday provider, that could mean publishing the correct schedule, making it accessible from the main service page, and testing the inquiry route. Subsequent search observations and suitable inquiries answer a different question about performance. Retain the publication date and note other changes, such as advertising or a website move, that could affect interpretation.
My agency, A. Blum Localization Services, is a starting point for discussing whether a website review or content project fits that kind of need. An initial inquiry can identify the decision you are trying to make, so that any proposed scope addresses a concrete problem.
Return to the owner looking at the wider ranking grid. A useful next report would preserve the original nine locations for comparison and assess the additional sixteen separately. It would identify which of those locations matter to the business and connect any proposed work to an observed gap. The owner could then distinguish maintaining existing visibility from pursuing customers in a new area, and decide which deserves the next dollar.
Google documentation checked October 22, 2026. The numerical and service examples in this essay are hypothetical.
Google Search Central: Guidance on using third-party SEO tools, services, and advice. Supports the distinction between external observations and Google’s internal ranking data.
Google Search Central: Google Search technical requirements. Covers crawler access, successful responses, indexable content, and the absence of an indexing guarantee.
Google Search Console Help: URL Inspection tool. Explains indexed information, live tests, and their limits.
Google Business Profile Help: Tips to improve your local ranking on Google. Describes relevance, distance, popularity, and prominence.
Google Search Central: Spam policies for Google web search: Doorway abuse. Describes the policy and its examples; the page-planning recommendation is the author’s judgment.
Google Business Profile Help: Business eligibility and ownership guidelines, and Manage your service areas for service-area and hybrid businesses. Define eligibility and service-area operations.
Google Search Console Help: Performance report: Overview and basic setup. Defines the reported metrics, including click-through rate.
Google Search Console Help: Performance report: Dimensions and data groupings. Explains query omissions, reporting limits, and country grouping.
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.