What you will build
This tutorial turns Windsurf Cascade Workflows into a small SEO/GEO operating system. A beginner should be able to follow it without already knowing how to design automation.
The important Windsurf detail is that workflows are markdown procedures stored in .windsurf/workflows/ and invoked manually as slash commands. That makes them a good fit for SEO/GEO work: the process is repeatable, but a human still chooses the page, checks the evidence, and approves edits.
By the end, your repo will contain:
.windsurf/
workflows/
seo-page-refresh.md
geo-prompt-audit.md
technical-seo-check.md
weekly-search-report.md
seo-geo/
inputs/
reports/
approvals/
Step 1: create the folders
From the root of your website repo, create the workflow and SEO/GEO folders:
mkdir -p .windsurf/workflows seo-geo/inputs seo-geo/reports seo-geo/approvals
If you are not sure whether you are in the repo root, run:
pwd
ls
You should see files such as package.json, astro.config.*, next.config.*, src/, app/, pages/, or your CMS export folder.
Step 2: start with one workflow, not four
Many teams make the first Windsurf workflow too broad. Do not create /optimize-site. Start with one workflow that refreshes one approved page.
Create this file:
cat > .windsurf/workflows/seo-page-refresh.md <<'EOF2'
# SEO Page Refresh
Goal: improve one approved page for SEO and GEO without changing unsupported claims.
Required inputs:
- target URL or local page file
- main query or keyword theme
- current title/meta description if available
- GSC/Bing/GA4 exports if available
- proof sources the page is allowed to use
Before editing:
1. Identify the page file, metadata file, schema file, and internal links that may be affected.
2. Diagnose intent match, answer clarity, entity clarity, internal links, evidence, metadata, schema, and technical risk.
3. Write a short plan in `seo-geo/approvals/page-refresh-plan.md`.
4. Stop and ask for approval.
Allowed changes after approval:
- improve headings and answer blocks
- improve title and meta description
- add or fix relevant internal links
- add FAQ only when the page really answers those questions
- improve schema only when the existing framework supports it
Forbidden actions:
- do not invent statistics, testimonials, logos, customer names, awards, or pricing
- do not change robots.txt, redirects, canonical logic, sitemap generation, or analytics tags
- do not edit unrelated pages
- do not publish or deploy
Final report:
- changed files
- exact SEO/GEO improvements made
- validation commands run
- risks still open
- metrics to watch for 14 days
EOF2
Step 3: invoke it like a slash command
Open Windsurf, then ask Cascade to run the workflow by name. Use a narrow request:
Run /seo-page-refresh for this page:
- URL: https://example.com/features/reporting
- Local file if you can find it: unknown
- Main query: reporting automation software for small teams
- Goal: make the page easier for Google and AI answer engines to understand
First locate the relevant file and write the approval plan only. Do not edit yet.
A good first response from Cascade should include:
Target file found: src/pages/features/reporting.astro
Possible related files: src/data/navigation.ts, src/lib/schema.ts
Main risks: metadata helper affects all feature pages; no proof source for the "fastest" claim
Proposed edits: title, opening answer block, comparison table, two internal links
Waiting for approval before editing.
If Cascade starts editing immediately, stop and tighten the workflow file. The approval stop is the point.
Step 4: add a GEO prompt audit workflow
This workflow checks whether your brand or page is visible in AI-style answer prompts. It should write a report, not edit content.
cat > .windsurf/workflows/geo-prompt-audit.md <<'EOF2'
# GEO Prompt Audit
Goal: evaluate whether a target page answers the prompts that buyers may ask in AI search systems.
Inputs:
- target URL or page file
- brand name
- product/category
- competitor names if known
- prompt list or keyword cluster
- AI answer snapshots if available
Steps:
1. Read the target page and any provided prompt list.
2. Convert keyword themes into buyer-style prompts.
3. Check whether the page provides concise answers, evidence, entity clarity, comparison context, and next steps.
4. Create `seo-geo/reports/geo-prompt-audit.md`.
5. Recommend page changes, but do not edit.
Report format:
- prompt
- current answer support: strong / partial / missing
- evidence available
- likely citation weakness
- recommended page section
- priority
EOF2
Run it with:
Run /geo-prompt-audit for our reporting page. Use the query theme "reporting automation software for small teams" and create 12 buyer prompts. Write the report only; do not edit files.
Step 5: add a technical SEO check workflow
Use this when you suspect crawl or indexation problems. Keep it separate from content workflows.
cat > .windsurf/workflows/technical-seo-check.md <<'EOF2'
# Technical SEO Check
Goal: inspect technical SEO risk without making broad sitewide changes.
Inputs:
- target URL or route group
- issue description
- crawl/export notes if available
Steps:
1. Inspect robots, sitemap generation, canonical tags, noindex logic, metadata helpers, structured data, and route rendering for the target area.
2. Classify each issue as low, medium, or high risk.
3. For high-risk files, recommend a ticket instead of editing.
4. Ask before any code change.
Forbidden actions:
- no redirects without approval
- no robots.txt changes without approval
- no canonical helper changes without approval
- no sitemap generator changes without approval
Output:
- risk table
- likely cause
- safe validation command
- proposed fix scope
EOF2
Beginner prompt:
Run /technical-seo-check for the /features/ route group. I suspect some pages have weak metadata, but I do not want any sitewide changes. Return a risk table and stop before editing.
Step 6: add a weekly search report workflow
This workflow summarizes exports and tells you what to do next. It should not rewrite pages directly.
cat > .windsurf/workflows/weekly-search-report.md <<'EOF2'
# Weekly Search Report
Goal: turn search and AI visibility exports into a prioritized action queue.
Inputs:
- GSC query/page export
- Bing query/page export
- GA4 landing page export
- AI visibility or prompt snapshot notes
- list of pages changed in the last 30 days
Steps:
1. Read exports from `seo-geo/inputs/`.
2. Find rising queries, declining pages, low-CTR opportunities, and AI visibility gaps.
3. Group opportunities by page.
4. Separate refresh tasks, technical tasks, internal-link tasks, and research tasks.
5. Write `seo-geo/reports/weekly-search-report.md`.
Do not edit content. Do not publish. Do not submit URLs.
EOF2
Place CSV files in seo-geo/inputs/, then run:
Run /weekly-search-report using the files in seo-geo/inputs. Produce an action queue with no more than 10 items. Separate content refreshes from technical fixes. Do not edit any page.
How to tell whether the workflows are working
Use this simple scorecard after the first two runs:
| Check | Good sign | Bad sign |
|---|---|---|
| Scope | One page or one report | Cascade touches unrelated files |
| Inputs | Asks for missing data | Pretends missing data exists |
| Approval | Stops before edits | Edits before the plan is approved |
| Output | Creates a clear report | Gives vague advice in chat only |
| Validation | Names commands and risks | Says everything is fixed without proof |
If a workflow fails, fix the workflow markdown before trying another page.
Common beginner mistakes
The first mistake is mixing workflows. A keyword workflow should not change canonical tags. A technical workflow should not rewrite a homepage. Keep each workflow boring and narrow.
The second mistake is asking for final content before a page map exists. Windsurf can draft, but it needs clean inputs: target query, page role, evidence, internal links, and forbidden claims.
The third mistake is letting reports stay in chat. Ask Cascade to write files under seo-geo/reports/ so you can compare decisions over time.
Beginner copy-paste prompt
If you want the simplest starting point, paste this into Windsurf:
I want to use Windsurf Cascade Workflows for safe SEO/GEO work.
Please inspect this repo and help me create one workflow first: `.windsurf/workflows/seo-page-refresh.md`.
Requirements:
- The workflow must work on one approved page at a time.
- It must diagnose before editing.
- It must write an approval plan to `seo-geo/approvals/page-refresh-plan.md`.
- It must forbid invented claims, unrelated file edits, publishing, deployment, redirects, robots changes, and sitemap changes.
- It must return changed files, validation commands, and metrics to watch.
Do not edit page content yet. First create or update only the workflow file and explain how I should run it.
FAQ
Should Windsurf workflows run automatically?
No. For a beginner, manual slash-command invocation is safer. Treat workflows as reusable procedures, not unattended bots.
How many workflows should I create first?
Start with one. Add the prompt audit, technical check, and weekly report workflows only after the first workflow reliably stops for approval.
Can I use a workflow to publish a page?
Not at the beginning. Use Windsurf to prepare the approved diff and validation report. Publish through your normal CMS or deployment process after review.
AI coding agents for SEO/GEO learning path
Windsurf track:
- Cursor vs Windsurf vs Gemini CLI for SEO/GEO Automation
- How to Build Windsurf Cascade Workflows for SEO/GEO
- How to Use Windsurf Rules and Memories for SEO/GEO Projects
- How to Turn Keyword Research into Content Briefs with Windsurf
- How to Use Windsurf to Address SEO/GEO PR Comments
- The SEO/GEO Operating Model for Cursor, Windsurf, Gemini CLI, Codex, and Claude Code
Sources and notes
- Windsurf/Devin Desktop documentation: Cascade Workflows .
- Related Auspia guide: Cursor vs Windsurf vs Gemini CLI for SEO/GEO Automation .
Author: Nathan Reed, AI Marketing Workflow Designer for 80+ Growth Systems at Auspia. Nathan writes about cross-channel systems and repeatable AI marketing workflows.
