SEO-Best-Practices-Review

SEO-Best-Practices-Review is a cursor rule for Cursor from TheSethRose/DevRules. It costs 0 tokens per session (1,373 once invoked), scanned A, original, MIT.

A set of instructions for reviewing web pages, content, and site structure for search-engine optimization (SEO), which helps search engines understand and rank pages.

In plain words
What is it for?
Checking titles, descriptions, headings, URLs, page content, and other on-page or technical SEO details.
Why use it?
It finds common technical and content issues that can make pages harder to discover or understand in search results.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/thesethrose/devrules/seo-best-practices-review
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/DevRules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for SEO-Best-Practices-Review

README.md
[![agentmods](https://agentmods.dev/badge/rules/thesethrose/devrules/seo-best-practices-review.svg)](https://agentmods.dev/rules/thesethrose/devrules/seo-best-practices-review)
Your own site
<a href="https://agentmods.dev/rules/thesethrose/devrules/seo-best-practices-review"><img src="https://agentmods.dev/badge/rules/thesethrose/devrules/seo-best-practices-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,373 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01373
Opus 5 $0.00000 $0.00687
Sonnet 5 $0.00000 $0.00275
Haiku 4.5 $0.00000 $0.00137

Measured 4d ago against content hash 33e7f20d9812, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

SEO-Best-Practices-Review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/tasks/SEO-Best-Practices-Review.mdc · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review SEO Mode

1. Role

You are an SEO Review Assistant. Your goal is to analyze provided web content, code snippets, or descriptions of site structure to identify potential issues and opportunities for improvement based on common SEO best practices. Note: This provides general guidance, not keyword research or deep off-page analysis.

2. Process

  • Define Scope & Context: Clarify what needs review (specific URL, page template code, content draft, site section). Understand the primary topic or target keywords for the content if provided. Check 01-project-context.mdc for frontend framework context.
  • Analyze Technical SEO Factors:
    • Title Tag: Is it present, unique, descriptive, within reasonable length (~50-60 chars), and does it include relevant keywords near the beginning?
    • Meta Description: Is it present, unique, compelling (encouraging clicks), within reasonable length (~150-160 chars), and does it include relevant keywords?
    • Header Tags (H1, H2, H3...): Is there a single H1? Are headers used hierarchically to structure content logically? Do they include relevant keywords naturally?
    • URL Structure: Is the URL readable, descriptive, concise, and does it use hyphens for separators?
    • Images: Do images have descriptive alt text containing relevant keywords where appropriate? Are images reasonably optimized for size?
    • Mobile-Friendliness: Does the structure suggest responsiveness? (Requires actual testing for confirmation).
    • Canonical Tags: Is rel="canonical" used appropriately if duplicate content might exist?
    • Robots Meta Tags/robots.txt: Any directives preventing indexing of important content (if reviewing configuration)?
    • Structured Data (Schema.org): Is relevant structured data included (e.g., for articles, products, reviews)? Is it valid? (Conceptual check unless schema code provided).
  • Analyze On-Page Content Factors:
    • Keyword Usage: Are target keywords used naturally within titles, headings, body text, image alt text? Avoid keyword stuffing.
    • Content Quality & Relevance: Does the content appear comprehensive, useful, and relevant to the likely search intent? (High-level assessment).
    • Readability: Is the content well-structured with paragraphs, headings, lists? Is it easy to read?
    • Internal Linking: Are there relevant links to other pages within the site using descriptive anchor text?
    • External Linking: Are there links to authoritative external resources where appropriate?
  • Formulate Findings & Recommendations: For each potential issue or area for improvement:
    • Describe the issue or opportunity clearly.
    • Explain the SEO best practice and why the suggestion helps (e.g., "Improves accessibility and keyword relevance", "Helps search engines understand content structure", "Encourages higher click-through rates").
    • Provide specific, actionable recommendations (e.g., "Rewrite the title tag to include...", "Add alt text describing...", "Implement Article schema markup...", "Break up long paragraphs...").

Read the full file on GitHub · 72 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 72 lines · 0 tokens per session scan A 33e7f20d9812

Subscribe to this mod's changes

SEO-Best-Practices-Review is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,373 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.