BluepointATM State Pages Optimization

Overview

BluePoint ATM is building out a 50-state service area page structure to capture local search traffic and reinforce geographic presence. As of the February 2026 marketing review, 10 state pages exist (Colorado plus 9 others). Several issues were identified that need to be resolved before the remaining 40 pages are built out and the section is added to site navigation.

Related: ^[1] | ^[2]

Issues Identified

1. Missing Mid-Page Phone Number

Problem: The CallRail local phone number only appears once on state pages. As users scroll, it disappears from view, undermining the local presence signal.

Fix: Add a second phone number section mid-page, modeled after the "lady with phone" image block on the main BluePoint website. This keeps the CallRail number visible as users scroll and reinforces that BluePoint has a local presence in that state.

Rationale (from Wade): The goal isn't necessarily to drive more phone calls — it's the visual effect of a local number. Prospects should feel like they're dealing with a local company.

2. Text Inconsistency Across State Pages

Problem: 9 of the 10 state pages contain outdated copy. Only the Colorado page has the correct, current text.

Fix: Standardize all 9 remaining state pages to match the Colorado page copy exactly.

3. Mobile Hero Image Disappears

Problem: The hero image on state pages features a reverse ATM graphic, but the ATM disappears when the page is viewed on a mobile device (the image collapses as the viewport narrows).

Fix: Update the hero image CSS/layout so the reverse ATM graphic remains visible at mobile breakpoints.

4. Service Area Page CTA Is Too Vague

Problem: The interactive state map on the Service Area page uses the CTA "Select your state," which doesn't tell users what they'll get when they click.

Fix: Replace with more descriptive text. Suggested direction:
- "Click on your state to see our local service offerings"
- "Select your state to find your local service center"

Wade and Mike took this as an action item to draft options and send to Karly for implementation.

Sequencing

These fixes must be completed before:
1. Adding the Service Area page to the main site navigation
2. Building out the remaining 40 state pages

Future SEO Strategy: City-Level Pages

Mark proposed extending the state page structure down to the city level to capture hyper-local search traffic.

Concept: After state pages are complete, create individual city pages (e.g., "Reverse ATMs in Ann Arbor, MI") optimized for local search queries. Each city page would:
- Rank for "[product] in [city]" searches
- Present BluePoint as a local provider
- Include a contact/quote form that tags the lead with the originating city

Precedent: Mark showed an example from another client with state → city page hierarchies, where clicking a city on a state map loads a dedicated city page. BluePoint doesn't need to go that deep immediately, but the architecture supports it.

Mike's response: "That makes sense to optimize it for location." No immediate commitment; team will think about it.

Action Items

Notes

• The state map on the Service Area page will show states in a lighter color until a page is built and linked for that state — this provides a natural visual indicator of coverage as pages are added.
• Wade raised the question of whether to mark unbuilt states as "no service" for authenticity. Karly's view: no harm in building all 50 states, even if BluePoint doesn't have active customers there yet.