BluePoint Blog Strategy — Surfer SEO Process
Overview
BluePoint ATM's blog program uses an SEO-first approach built around the Surfer AI content tool. The primary objective is search ranking, not readership — blogs exist to drive organic traffic to the site, where a fraction of visitors will convert into commercial leads. As of Q1 2026, the strategy is producing CTRs well above industry benchmarks, and the client review process is being streamlined to accelerate publishing cadence.
See also: [1] | [2]
The Surfer Workflow
- Topic and keyword selection — The team identifies target keywords based on trending topics in the reverse ATM / ATM space and competitor content analysis (LinkedIn posts, ranking pages).
- Surfer draft generation — Surfer ingests the topic, target keywords, and competitor URLs, then generates a draft optimized to achieve a content score of 80 or higher. The content score is a composite metric designed to outrank the best currently-ranking article for the target keyword.
- Human editorial review — A content editor reads the draft for sense, accuracy, and grammar. The draft is also run through Grammarly.
- Publish — Once spelling and grammar are clean and no factual errors are present, the post is published.
"We're targeting an 80 or higher content score. If we shorten the blog, the score starts to go down."
— Mark Hope, Q1 2026 strategy call
Why Blog Length Is Non-Negotiable
Blog length is dictated by the content score target, not editorial preference. A shorter post will score lower and rank lower. The team does not pad for padding's sake — if a 400-word post could hit 80+, they'd write 400 words. The length requirement is a function of what it takes to outrank existing content.
Client Review Scope
A key process change confirmed in the Q1 2026 review: client review should focus exclusively on factual errors, not stylistic edits.
- If the blog contains no factual inaccuracies, it should be approved as-is.
- Stylistic rewrites, comma changes, and tone adjustments reduce publishing velocity without meaningfully improving SEO performance.
- Clients who over-edit cause publishing delays that undermine the ranking strategy.
"If there's nothing wrong in that blog, let it go. Don't waste so much time on it — we're trying to get the keywords onto the web page."
— Mark Hope
BluePoint (Wade and Mike) had been spending significant time on line-level edits. The agreed new norm is: read for errors, not for prose quality.
CTR Performance
| Metric | BluePoint Actual | B2B Financial Services Benchmark | Agency Target |
|---|---|---|---|
| Click-through rate (CTR) | 15–70% | 3–6% | ~10% |
BluePoint's CTRs are significantly outperforming the closest available benchmark (B2B financial services). Individual posts have recorded CTRs as high as 70% (e.g., "How Reverse ATMs Are Changing Payments" — 132 visits, 70% CTR).
The current constraint is impressions volume, not CTR. "Reverse ATM" as a search category is still low-volume. The strategy is to build ranking authority now so that as search volume grows (analogous to how AI-related searches grew from near-zero to billions), BluePoint is already positioned.
Traffic Intent Model
Not all blog traffic is equal. The team uses a four-type intent framework to set expectations:
| Intent Type | Description | Value to BluePoint |
|---|---|---|
| Informational | Research, curiosity, students | Low (chaff) |
| Commercial | Business model research, comparison | High (wheat) |
| Transactional | Pricing, purchase intent | High (wheat) |
| Navigational | Looking for BluePoint specifically | Moderate |
Informational traffic dominates blog visits (~70–80% of total). This is expected and acceptable — it signals topic relevance to search engines and is necessary to capture the smaller slice of commercial and transactional visitors. Attempting to filter out informational traffic would eliminate the conditions needed to rank at all.
"You have to have the chaff in order to get the wheat."
— Mark Hope
A realistic traffic model: 100 visitors → ~10 commercial, ~10 transactional, ~80 informational.
Blog Images
Stock photography for ATM-related content is limited across all major platforms (iStock, Adobe Stock, Unsplash, Pexels). The team prefers licensed stock over scraped web images due to copyright risk.
Agreed actions:
- Gavin and Raphael (content team) to be briefed on image quality expectations — use fewer images rather than poor ones.
- BluePoint (Mike/Wade) to provide a folder of approved brand images for use in posts.
- Field photos taken on phones are usable and welcome — the team can clean them up with editing tools.
Related
- [3]
- [2]
- [4]
- [5]