Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cj-teaches.dev/llms.txt

Use this file to discover all available pages before exploring further.

I was going to write this tutorial with a basic SEO skill I wrote and have used at work. However, I recently discovered the claude-seo plugin by Agrici Daniel and was completely blown away by its capabilities. The plugin runs 18 sub-agents in parallel running 25 sub-skills, and is kicked off with a single skill. It’s awesome. Improving the SEO (Search Engine Optimization) and GEO (Generative Engine Optimization) of your tutorials helps them reach a wider audience and perform better in search results. In this tutorial, you use the claude-seo plugin to audit a tutorial for SEO issues. Feel free to use your own tutorial file instead of the provided demo.

​
Prerequisites

Before starting, install the claude-seo plugin:

Install claude-seo

The claude-seo plugin must be installed and available in Claude before running this tutorial.

​
Set up the tutorial file

1

Create a working directory

In your terminal, create a directory for this tutorial and download the demo tutorial file:
mkdir -p seo-tutorial
cd seo-tutorial
curl -O https://raw.githubusercontent.com/cjobermaier/public-resources/main/seo-your-tutorials/demo-tutorial.md
Open demo-tutorial.md in your editor to skim the file before running the audit. It contains a realistic-looking tutorial with intentional SEO issues seeded throughout.
2

Launch Claude Code from this directory

Start Claude Code from inside seo-tutorial/:
claude
Later commands reference demo-tutorial.md as a relative path, so Claude must be running from this directory.

​
Run the SEO check

The /seo skill audits your file for SEO issues and returns findings across several categories: page title and meta description, heading structure, link text quality, and AI/LLM visibility signals. Each finding includes what to change and why.
1

Run the SEO audit

The /seo skill accepts a subcommand and a target. Use page to analyze a single file, or audit to analyze an entire site.Run page against the demo file:
/seo page demo-tutorial.md
Claude scans the file and returns a scorecard followed by a prioritized issue list. The exact output varies, but the structure looks similar to the following:
Overall Score: 38/100

On-Page SEO:     32/100  ███░░░░░░░
Content Quality: 48/100  █████░░░░░
Technical:       45/100  ████░░░░░░
Schema:           0/100  ░░░░░░░░░░
Images:         N/A
You also see a prioritized list of issues with explanations and suggested fixes:Prioritized Action Plan
#ActionPriorityExpected Impact
1Add React 19 version note or expand with React 19 patternCriticalAccuracy + E-E-A-T + recency signal
2Add description to frontmatter (157 chars)CriticalDirect CTR improvement in SERP
3Revise title to 50–60 chars, drop “A Guide to”HighCTR + keyword matching
4Fix both vague anchor text linksHighCrawlability + topical relevance signal
5Add author bio + publication/updated datesHighE-E-A-T — foundational for technical content
6Add OG/Twitter card metadataHighSocial sharing CTR
7Expand content to 1,000+ words (add useRef for values, useImperativeHandle)MediumCompetitive depth; passes thin-content threshold
8Add TechArticle JSON-LDMediumStructured signals to Google + AI systems
9Add canonical declarationMediumLink equity consolidation
10Remove ## Introduction heading; merge with openingMediumCleaner structure, no duplicate framing
11Add one diagram (parent→forwardRef→DOM ref chain)MediumUX + image SEO surface

​
Implement improvements

You have two approaches depending on how much control you want:
  1. You can review the findings and choose which ones to apply.
  2. You can ask Claude to apply all the improvements at once.
Working through each finding with Claude gives you more control over the result.

​
Work through each item

Use this approach when you want to review changes before committing to them, or when working on real content where some suggestions may not fit your audience.
1

Ask Claude to work on findings with you

Lets work through each of the findings together in priority order.
2

Claude shows you the first finding and suggests a fix

Tell Claude which priority levels to apply:
  ---
Finding C1 — Missing meta description

The frontmatter currently only has:

---
title: A Guide to Using React Refs
---

I'd add a description field. Here's a draft (157 chars):

▎ "Learn how to use React refs with useRef and forwardRef. Covers attaching refs to DOM elements, forwarding refs through custom components, and when to use refs vs.
▎ state."

Does that description look right to you, or would you like to adjust the focus or phrasing before I write it to the file?
Work through each finding with Claude, deciding which ones to apply and how to implement them.
3

Re-run the audit to verify

/seo page demo-tutorial.md
Confirm the items you applied are resolved. The issues you skipped will still appear.

​
Apply everything at once

1

Apply all improvements

Ask Claude to apply every finding from the audit:
Apply all the SEO improvements from the audit to demo-tutorial.md that you can 
automatically fix.
2

Re-run the audit to verify

Run the audit again to confirm the Critical and High issues are resolved:
/seo page demo-tutorial.md
The score jumps significantly. Medium and Low issues may still appear — that’s expected. Decide which remaining items are worth addressing.

​
Next steps

You downloaded a demo tutorial with seeded SEO issues, ran /seo page to get a scored audit with a prioritized action plan, and applied targeted improvements to titles, descriptions, headings, and links. Then you re-ran the audit to verify the score improved.
Found an issue with this tutorial? Open a GitHub issue.