---
title: Surfer SEO Optimization in Blog Workflow
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-03-19-content-call-131308273.md
tags:
- surfer
- seo
- content-marketing
- blog
- workflow
- internal-links
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Surfer SEO Optimization in Blog Workflow

Surfer is the SEO optimization layer in the [[wiki/knowledge/content-marketing/blog-production-sop|Blog Production SOP]]. It sits between the initial Claude draft and the final review pass, handling keyword scoring, internal linking, and content health metrics.

## Role in the Workflow

Surfer is **Step 2** of the four-step blog production process:

1. Draft in Claude (Team Project)
2. **Optimize in Surfer** ← this step
3. Final review in Claude
4. Deliver as Google Doc

The Claude draft enters Surfer as raw content. The optimized, linked output exits as a `.docx` file for upload back into Claude.

## What to Do in Surfer

### Opening a Content Editor Session

1. Log into Surfer and navigate to the correct client site (each client has a dedicated site in the account).
2. Go to **Create Content → Content Editor**.
3. Select **New Content**, enter the target keyword from the brief, and paste the Claude draft into the editor.

### Keyword Color Coding

Surfer highlights keywords throughout the document using a traffic-light system:

| Color | Meaning |
|-------|---------|
| **Green** | Keyword used at the recommended frequency |
| **Yellow** | Keyword present but underused — add more instances |
| **Red** | Keyword overused — reduce occurrences |

Aim to move all primary and secondary keywords to green before exiting Surfer.

### Adding Internal Links

Use Surfer's internal link suggestions to add links throughout the post. Do **not** manually copy-paste the content out of Surfer to add links — the links must be added inside the editor so they are preserved when the document is exported.

> **Important:** Copying plain text out of Surfer strips all hyperlinks. Always export as `.docx` to preserve link formatting.

### Checking the Health Score

The Surfer health score is a composite SEO quality metric. Improve it by:
- Addressing keyword gaps (yellow/red terms)
- Adding recommended headings or sections
- Incorporating internal links

For clients who track SEO metrics (e.g., Brian at Citrus America), note the final health score and target keyword — these should appear at the top of the delivered Google Doc.

## Exporting from Surfer

When optimization is complete, export the document as a **`.docx` file**. This format:
- Preserves all internal links and formatting
- Can be uploaded directly to the client's Claude Team Project for final review
- Can be opened in Google Docs or Word without reformatting

Do not export as PDF — PDFs cannot be edited by account managers during their review pass.

## Access and Seat Limits

Surfer seats are limited (currently **5 users**). Current seat holders include Gavin, Karly, Raphael, and Sebastian. Account managers who need to view scores but not edit content may be accommodated via a shared "Team" viewer account — see [[wiki/knowledge/tools/surfer-access|Surfer Access & Seat Management]] (pending research by Mark).

If you need Surfer access and do not have a seat, contact Mark before attempting to share credentials.

## Common Mistakes to Avoid

- **Copying instead of exporting** — always use the `.docx` export; copy-paste loses links
- **Skipping the health score** — the score is a client-visible deliverable for SEO-focused clients
- **Leaving red keywords** — over-optimized terms can hurt rankings; reduce usage until green
- **Forgetting the target keyword** — it appears in the top-left of the Surfer editor next to the client name; record it before closing the session

## Related

- [[wiki/knowledge/content-marketing/blog-production-sop|Blog Production SOP]]
- [[wiki/knowledge/content-marketing/claude-team-projects-for-content|Claude Team Projects for Content]]
- [[wiki/knowledge/content-marketing/client-writing-guides|Client Writing Guides]]
- [[wiki/meetings/2026-04-05-content-call-blog-sop-revision|Content Call — Blog SOP Revision (2026-04-05)]]