FlashCrafterOriginal research
Operating-model clarity, overlapping Google Maps results, recurring customer questions, and bounded query estimates across Rohnert Park, Petaluma, and Santa Rosa
Owners of independent car detailing businesses in Sonoma County often frame the market as mobile operators on one side and fixed-location shops on the other. The evidence behind this page does not support a clean split like that. Google Maps results for a general detailing query and a mobile detailing query shared many of the same listings at seven matched coordinates across Rohnert Park, Petaluma, and Santa Rosa, and the provider pages sampled described a mix of mobile, shop, and hybrid logistics.
The central question is how a detailing business should position its operating model when discovery results overlap and customers ask the same cost and value questions whichever label they search under. The defensible answer is to explain your own verified arrangement and your quote inputs clearly. Search positions, ratings, listing names, and approximate query estimates do not prove quality, market share, demand size, or the effect of any marketing change, and this page does not treat them that way.
The Maps and question evidence was retained on 2026-09-09 (report-generation timestamp 2026-09-09T21:11:35.035Z), and the analysis was published on 2026-09-13. Individual capture times are unknown, so cached material may be older. Everything below describes the evidence as of those dates. This is the first publication on this topic, so no before-and-after outcomes exist; that absence is neither evidence for nor against usefulness or impact.
The evidence
Shared Maps place IDs between general and mobile queries ranged from 9 to 31 at seven like-coordinate pairs.
Pack depth varied widely within the paired Maps observations.
One separate Petaluma mobile observation had no selected general-query member at its coordinate.
Total cost, tipping, and value each appeared in every city-and-query context.
Approximate monthly query estimates were small and higher for general queries than mobile queries in each city.
Six sampled provider pages showed differing logistics: customer-location work, a mobile-or-shop choice, recurring schedules, and differing utility language.
| Number | Basis | |
|---|---|---|
| Shared Maps place IDs between general and mobile queries ranged from 9 to 31 at seven like-coordinate pairs. | 9 to 31 shared place IDs per pair | Seven selected like-coordinate general/mobile Google Maps pairs in Rohnert Park, Petaluma, and Santa Rosa, retained 2026-09-09. Shared counts are intersections of nonempty place IDs, not unique verified competitors. |
| Pack depth varied widely within the paired Maps observations. | 9 to 68 listings per pack | Same seven like-coordinate pairs. The 68-listing general pack and the 9-listing mobile pack were both observed. |
| One separate Petaluma mobile observation had no selected general-query member at its coordinate. | 1 unpaired observation of 5 results | A five-result Petaluma mobile Maps sample at 38.210732, -122.609046, retained 2026-09-09 and excluded from the pair table. |
| Total cost, tipping, and value each appeared in every city-and-query context. | 6 of 24 associations each; 6 of 6 contexts each | 24 retained question/query associations across six city-and-query contexts (Rohnert Park, Petaluma, and Santa Rosa, each under a general and a mobile query), after content deduplication. Counts are associations, not searches, people, or popularity. |
In two of the seven pairs, every place ID in the smaller mobile-query pack also appeared in the general-query pack: Rohnert Park at 38.339946, -122.707385 (31 shared of a 31-listing mobile pack) and Petaluma at 38.254102, -122.609046 (9 shared of a 9-listing mobile pack). The other five pairs still overlapped substantially but were not identical, with 14, 14, 17, 15, and 15 shared place IDs. Ordering and composition differed between queries, so overlap does not mean identical visibility.
The deepest pack was the Rohnert Park general-query pack at 38.339946, -122.707385 (68 listings); the shallowest was the Petaluma mobile pack at 38.254102, -122.609046 (9 listings). Because depths were unequal, overlap counts depend partly on how many listings each query returned.
This observation is a reminder that the sample is selected, not a controlled experiment. It describes overlap in the paired observations, not stable visibility, market share, or two verified provider pools.
Duration appeared in 3 of 24 associations, in the three general-query contexts only. Mobile hourly cost appeared in 3 of 24 associations, in the three mobile-query contexts only. Similar wording retained in more than one context counts as a separate association in each. These associations do not show competitor omissions or likely lead volume.
These figures should not be summed as unique people or turned into market size, revenue opportunity, or causal marketing evidence.
This supports an audit checklist for your own page. It does not establish that any competitor offers or omits a given feature.
Method
Seven like-coordinate pairs of Google Maps results were compared, each pairing a general detailing query with a mobile detailing query at the same coordinates in Rohnert Park, Petaluma, or Santa Rosa. Shared counts are intersections of nonempty place IDs.
One additional Petaluma mobile Maps observation (five results, at 38.210732, -122.609046) had no selected general-query member at its coordinate. It is kept outside the comparison as a sampling caveat.
Customer question recurrence was counted across 24 retained question and query associations in six city-and-query contexts (three cities, general and mobile queries), after removing duplicate content. These counts are not searches or people.
Approximate monthly query estimates were recorded separately by city and by general versus mobile intent. The estimate provider's target and averaging window were not retained.
Six provider pages were used only as dated examples of how logistics are disclosed. Current offers, coverage, and suitability on those pages are unverified.
AI assistance was used to organize the admitted evidence, calculate the place-ID intersections, verify recurrence totals, and draft the analysis. No outside browsing, provider contact, or client action was performed.
What it means
General and mobile car detailing searches returned heavily overlapping Google Maps listings at seven matched coordinates in Rohnert Park, Petaluma, and Santa Rosa (shared place IDs ranged from 9 to 31), while six sampled provider pages described mobile, shop, and hybrid logistics. A "mobile" or "shop" label alone does not separate providers in discovery, so the defensible positioning work is stating your own verified arrangement and quote inputs clearly.
For owners
What to act on
Because general and mobile queries shared 9 to 31 place IDs at the seven matched coordinates, and two mobile packs were entirely contained in the general packs, do not rely on a mobile or shop label alone to separate you from other providers. State your own verified arrangement: where work happens, coverage area, customer-site requirements, equipment, weather handling, vehicle custody, drop-off and pickup, scheduling, and personal, fleet, and recurring service. Six sampled provider pages described different logistics, including customer-location work, a mobile-or-shop choice, recurring schedules, and differing utility language. Check your own page against those same topics and publish only what you have currently verified. Total cost, tipping, and value appeared in all six city-and-query contexts. Put your own quote inputs, inclusions, surcharges, and gratuity policy where a customer can find them, without citing a market price, because no normalized quote set exists. Duration questions appeared only in general-query contexts and mobile hourly cost only in mobile-query contexts. If you serve both kinds of customer, give verified timing ranges with the factors that change them, and state your billing basis without implying hourly pricing is standard. The query estimates (40/10, 40/10, and 140/20 for general/mobile) are approximate and lack a target and averaging window. Do not use them to forecast leads or revenue; track your own inquiries by work location, utility constraints, service scope, city, and quote outcome instead.
For customers
What to notice
Searching for "mobile" and searching for a general detailing term surfaced many of the same Maps listings at the sampled coordinates, so a listing's appearance under one query does not confirm that the provider comes to you or that you must go to them. Confirm where the work happens before booking. Ask each provider what your site must supply, what equipment they bring, what happens in bad weather, and how drop-off, pickup, and scheduling work. Provider pages sampled on 2026-09-09 differed on these points, and their current offers are unverified. For total cost, tipping, and value, ask for the quote inputs, what is included, any surcharges, and the gratuity policy. No normalized quote set exists, so a price you see elsewhere is not a reliable benchmark. Ratings, review counts, and result positions do not establish service quality, so use them alongside a provider's own stated scope and logistics rather than in place of them.
The Maps, question, and estimate evidence was retained with a report-generation timestamp of 2026-09-09T21:11:35.035Z. Individual capture times are unknown, and cached material may be older. The analysis was published on 2026-09-13T23:16:47.559Z. All statements describe the evidence as of those dates.
The Maps table compares seven selected like-coordinate general/mobile pairs: two in Rohnert Park, two in Petaluma, and three in Santa Rosa. Shared counts are intersections of nonempty place IDs between the general-query pack and the mobile-query pack at the same coordinates. Pack sizes are the number of returned listings and were unequal across pairs.
One unpaired Petaluma mobile observation (five results at 38.210732, -122.609046, with no selected general-query member at the coordinate) was retained outside the table as a sampling caveat.
Question recurrence was calculated from 24 retained question/query associations across six city-and-query contexts (three cities, each with a general and a mobile query) after content deduplication. Each association was counted separately in each context where similar wording was retained. The counts were not interpreted as searches or people.
Approximate query estimates were reported separately by city and by intent (general versus mobile). The provider target and averaging window were not retained. Provider website statements were used only as dated examples of how logistics are disclosed, not as verification of current offers, coverage, or suitability.
AI assistance was used to organize the admitted evidence, calculate the like-coordinate place-ID intersections, verify recurrence totals, and draft the analysis. No outside browsing, provider contact, or client action was performed.
Individual capture times are unknown; the retained evidence carries a report-generation timestamp of 2026-09-09T21:11:35.035Z, and cached material may be older.
The sample is selected evidence, not a census or controlled intent experiment. Maps result depths were unequal, and one Petaluma mobile point was unpaired.
Place IDs may reflect duplicate or changed identities. Listings and positioned domains do not verify current operating model, locality, service area, capability, availability, or suitability.
Ratings, review counts, and search positions do not establish service quality or causal marketing impact.
No normalized quote set supports price comparisons.
Question associations do not establish unanswered competitor needs, searches, people, popularity, or likely lead volume.
Approximate query estimates do not establish unique audience size, market size, or revenue opportunity; the estimate provider's target and averaging window were not retained.
Current offers on the sampled provider pages remain unverified.
This is a first publication for this topic, so no prior publication outcomes are available. That gap is neither evidence for nor against usefulness or impact.
Where the work happens is not a branding detail for a detailing customer; it determines whether they can book at all. A customer deciding between providers needs to know where work occurs, what geographic area is covered, whether the customer's site must supply anything, what equipment the provider brings, what happens in bad weather, whether the vehicle is left with the business, how drop-off and pickup work, how scheduling works, and where personal, fleet, and recurring service begin and end.
Document each of these for your own business and publish only the details you have currently verified. A statement about water or power at the customer's site, or about a weather reschedule, is only useful if it matches what your crew actually does today.
Six provider pages sampled on 2026-09-09 showed customer-location work, a mobile-or-shop choice, recurring schedules, and differing utility language. That range is a reason to audit your own page against the checklist above. It does not establish that every competitor offers or omits any particular feature, and the current offers on those pages are unverified.
At seven like-coordinate Google Maps pairs, shared place IDs between the general-query pack and the mobile-query pack ranged from 9 to 31. In two pairs, every place ID in the smaller mobile-query pack also appeared in the general-query pack. The other pairs overlapped substantially but were not identical.
Pack depth ranged from 9 to 68 within the paired observations. One separate five-result Petaluma mobile observation, at 38.210732, -122.609046, had no selected general-query member at its coordinate, so it is not in the table.
The sample describes overlap between result sets. It does not describe stable visibility, market share, or two verified provider pools. Listings and domains in the results do not verify a business's current operating model, locality, service area, capability, availability, or suitability, and place IDs may reflect duplicate or changed identities. Treat the table as evidence that the words "mobile" and "shop" do not sort providers into separate groups in discovery, not as a count of competitors.
| City and coordinate | General pack | Mobile pack | Shared place IDs |
|---|---|---|---|
Rohnert Park — 38.339946, -122.707385 | 68 | 31 | 31 |
Rohnert Park — 38.361632, -122.679737 | 20 |
Among 24 retained question and query associations, total cost, tipping, and value each appeared in all six city-and-query contexts, six associations apiece. Duration appeared in the three general-query contexts only, and hourly mobile cost appeared in the three mobile-query contexts only.
Use these associations as a prompt to review your own verified quote factors, inclusions, surcharges, duration guidance, logistics, and gratuity policy. If a customer would reasonably ask what the total will be, whether to tip, and whether the service is worth it, your page should answer those questions from your own practice.
Two limits apply. First, the counts are retained question/query associations, not searches, people, or popularity; similar wording retained in several contexts counts separately in each. Second, no normalized quote set exists, so nothing here supports a market price, a claim that hourly pricing is standard, or a claim that competitors fail to answer these questions.
| Decision | Associations | City-and-query contexts | Bounded implication |
|---|---|---|---|
Total cost |
Approximate general/mobile query estimates were 40/10 for Rohnert Park, 40/10 for Petaluma, and 140/20 for Santa Rosa. The estimate provider's target and averaging window were not retained, so the figures should not be summed as unique people or translated into market size, revenue, or causal opportunity.
Because this is a first publication on the topic, no outcomes from acting on it are available. After publishing changes to your own page, you can track qualified inquiries by requested work location, utility constraints, service scope, city, and quote outcome. That would give you your own evidence about which operating-model details customers actually need, rather than relying on approximate estimates.
| City | General query estimate | Mobile query estimate |
|---|---|---|
Rohnert Park | 40 | 10 |
Questions
Keep reading
Vendor pages change. Figures are as published on the capture date; confirm before deciding.
| Approximate monthly query estimates were small and higher for general queries than mobile queries in each city. |
|---|
| Rohnert Park 40/10; Petaluma 40/10; Santa Rosa 140/20 (general/mobile) |
| Approximate monthly estimates from Google's Keyword Planner tool, retained 2026-09-09. The provider target and averaging window were not retained, and capture time is unknown. |
| Six sampled provider pages showed differing logistics: customer-location work, a mobile-or-shop choice, recurring schedules, and differing utility language. | 6 pages | Six provider pages (On The Spot commercial-service and personal-service pages, The Detail Works Co. mobile-service page, Detailing Paradise hybrid-offer page, Raintree detail-center page, Car Spa mobile-offer page), retained 2026-09-09. Current offers, coverage, and suitability are unverified. |
|---|
20 |
14 |
Petaluma — 38.254102, -122.609046 | 20 | 9 | 9 |
Petaluma — 38.254102, -122.664259 | 20 | 19 | 14 |
Santa Rosa — 38.418744, -122.686369 | 20 | 20 | 17 |
Santa Rosa — 38.418744, -122.741741 | 20 | 20 | 15 |
Santa Rosa — 38.462114, -122.741741 | 20 | 20 | 15 |
Google Maps samples retained 2026-09-09 (individual capture times unknown). Counts are returned listings and shared nonempty place IDs, not unique verified competitors. Pairs use the same coordinates; ordering and composition differed. A separate unpaired Petaluma mobile observation is excluded.
6 of 24
6 of 6 |
Explain quote inputs and total-price components; do not publish an unsupported market price. |
Tipping | 6 of 24 | 6 of 6 | State the business's own gratuity policy clearly. |
Value | 6 of 24 | 6 of 6 | Explain scope and fit; do not claim quality or universal value. |
Duration | 3 of 24 | 3 of 6; general-query contexts only | Give verified timing ranges and the factors that change them. |
Mobile hourly cost | 3 of 24 | 3 of 6; mobile-query contexts only | Clarify billing basis without inferring that hourly pricing is standard. |
Retained 2026-09-09 after content deduplication. Recurrence counts retained question/query associations, not searches, people, popularity, or demand.
Petaluma | 40 | 10 |
Santa Rosa | 140 | 20 |
Approximate monthly estimates retained 2026-09-09 from Google's Keyword Planner tool; provider target, averaging window, and capture time were not retained. Do not sum them as unique searchers or treat them as market size, revenue opportunity, or causal marketing evidence.