Surfer SEO Optimization Process for Blog Content

Surfer's Content Editor is the SEO optimization step in the team's standardized blog production workflow. It sits between the initial Claude draft and the final Claude review, and is used specifically to improve content scores, add internal links, and prepare the document for final delivery.

For the full end-to-end workflow this step belongs to, see ^[1].

Role of Surfer in the Workflow

Surfer is an SEO tool only — it is not the final delivery format. Final blog posts are delivered as Google Docs. Surfer's job is to:

• Score the draft against the target keyword
• Surface missing or overused keywords
• Generate internal links automatically
• Provide a health score to report to SEO-conscious clients (e.g., Citrus America)

Step-by-Step Process

1. Navigate to the Client's Surfer Workspace

• Log into Surfer using your assigned credentials (see Access section below)
• Select the correct client site (e.g., "Citrus America")
• Go to Content Editor

2. Create a New Content Document

• Click New Content
• Enter the target keyword from the content brief
• Choose Write Yourself (do not use Surfer AI to generate — the draft comes from Claude)

3. Paste the Claude Draft

• Copy the full draft from the Claude Team Project
• Paste it into the Surfer Content Editor
• Review the content score and keyword highlighting:
• 🟢 Green = keyword used at recommended frequency
• 🟡 Yellow = keyword underused
• 🔴 Red = keyword overused

4. Optimize the Content

• Adjust keyword usage to move highlighted terms toward green
• Use Surfer's internal link suggestions to add relevant links throughout the post
• Insert [Image Placeholder] notes at appropriate locations in the body (these will be visible to reviewers and can be acted on before publishing)

5. Export as .docx — Critical Step

Do not copy-paste from Surfer back to Claude. Copying loses all hyperlinks and formatting.

• When optimization is complete, export the document as a .docx file
• This preserves internal links, formatting, and structure
• The .docx file is then uploaded back into the Claude Team Project for final review

What to Note for Delivery

For clients who require SEO reporting (currently: Citrus America / Brian), record the following before leaving Surfer:

• Surfer health score
• Target keyword (visible in the top-left of the Content Editor, next to the client name)

These are added to the top of the final Google Doc so the client can see them without needing Surfer access.

Access

The team subscription supports approximately 5 users. Additional users should coordinate with Karly or Mark before attempting to create new logins.

Common Mistakes to Avoid

• Do not share Surfer links with clients or AMs for review. Not everyone can view Surfer consistently, and the interface is not client-friendly. Always convert to Google Doc.
• Do not copy-paste from Surfer into Claude. Always export .docx and upload the file to preserve links.
• Do not use Surfer AI to write or rewrite content. The draft originates in Claude with the client knowledge base loaded; Surfer is for optimization only.

Related

• ^[1] — Full Claude → Surfer → Claude → Google Doc workflow
• ^[2] — How to set up and use Claude Team Projects with client knowledge bases
• ^[3] — Final delivery format and ClickUp handoff