Surfer SEO Content Optimization Workflow
Overview
Rather than writing new blog content from scratch, an often faster and higher-ROI approach is to improve existing articles using Surfer SEO's auto-optimize feature. A single session can take an article from an uncompetitive score to above the top-ranked competitor, making it eligible to rank.
This workflow was demonstrated live during a [1] using a Cordwainer article on "Sundowning" as the example case.
Why Optimize Existing Content First
- New articles take time to index and build authority; existing pages already have some history.
- Many published articles are severely underscored (e.g., score of 24) simply due to thin content or missing keyword coverage — not because the topic is wrong.
- Surfer shows the top competitor score for any keyword. If you can exceed it, you should outrank them.
- The process is fast: a full optimization pass can be completed in under an hour per article.
Workflow
1. Identify Target Articles
- Pull the site's existing blog or resource articles.
- Prioritize articles that already receive some organic traffic but rank poorly (e.g., position 15–30).
- Focus on articles tied to core service keywords.
2. Set Up Surfer SEO
- Create a Surfer site for the client domain if one doesn't exist yet.
- In Surfer, open Content Editor and paste the article URL along with the target keyword.
- Surfer will load the article and display:
- Current content score (e.g., 24)
- Top competitor score for that keyword (e.g., 66)
- Average score across ranking pages (e.g., 56)
Rule of thumb: Score above the top competitor to have a strong chance of ranking.
3. Auto-Optimize
- Click Auto-Optimize in the Surfer content editor.
- Surfer's AI will rewrite and expand sections to hit keyword targets, add missing terms, and improve structure.
- Watch the score climb in real time. The Sundowning article went from 24 → 76 in a single pass, exceeding the top competitor's score of 66.
4. Add a Q&A Section
- After auto-optimization, append an AI-generated Q&A section to the bottom of the article.
- Prompt an LLM (e.g., ChatGPT): "Create a concise Q&A section for this article" — then paste the article content.
- Keep answers short and direct; avoid long-form answers that bloat the page.
- Paste the Q&A into the Surfer editor to capture any additional score gains.
5. Add Internal Links
- In Surfer, use the Internal Links tool and select the client domain.
- Insert 2–3 relevant internal links into the article.
- This improves site structure and passes link equity to other pages.
6. Clean Up and QA
- Review the auto-optimized content for accuracy, tone, and brand fit.
- Remove any HTML artifacts or formatting garbage that Surfer may introduce (visible as stray dots or broken markup).
- Run through Grammarly for a final polish pass.
7. Publish
- Hand the finalized content off to the site editor (e.g., Raphael for Cordwainer) with instructions to update the existing article — not create a new one.
- The editor cuts, pastes, and publishes the improved version.
Supplementary Website Fixes (Content Pages)
While reviewing articles, also address cosmetic and UX issues that undermine credibility:
- CTA button text: Change "RSVP" to "Learn More" on blog posts — users cannot RSVP to an article.
- Incorrect images: Remove placeholder or irrelevant images (e.g., a trophy image on a care article).
Example: Cordwainer "Sundowning" Article
| Metric | Before | After |
|---|---|---|
| Surfer Content Score | 24 | 76 |
| Top Competitor Score | 66 | 66 |
| Estimated Rank Position | ~21 | Competitive |
The article went from well below average to the strongest piece on that keyword in a single optimization session. See [2] for broader SEO context.
Key Principles
- Improve before you create. Existing content is an underutilized asset.
- Score above the top competitor, not just the average. The average score gets you average rankings.
- Q&A sections add value. They target long-tail and conversational queries and are easy to generate with AI.
- Delegate the publishing step. The strategist runs the optimization; a site editor handles the WordPress update.
Related
- [2]
- [3]
- [4]