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.
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketingWrote 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.
[](https://agentmods.dev/rules/thatrebeccarae/claude-marketing/technical-seo-audit)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/technical-seo-audit"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/technical-seo-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/technical-seo-audit"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/technical-seo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.03121 |
| Opus 5 | $0.00037 | $0.01561 |
| Sonnet 5 | $0.00015 | $0.00624 |
| Haiku 4.5 | $0.00007 | $0.00312 |
Grade A, and why
technical-seo-audit scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://example.com/robots.txt How it starts
The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical SEO Audit
Deep technical SEO analysis: crawlability, indexation, Core Web Vitals, site architecture, and performance.
Audit Framework
Phase 1: Crawlability & Indexation
robots.txt Analysis
- Verify file exists at
/robots.txt - Check for unintentional blocks (
Disallow: /on production) - Validate sitemap reference
- Review AI crawler directives (GPTBot, ClaudeBot, PerplexityBot)
XML Sitemap Audit
- Validate sitemap format (XML schema compliance)
- Check for 404, 301, or 5xx URLs in sitemap
- Verify lastmod dates are accurate (not all the same date)
- Confirm sitemap is referenced in robots.txt
- Check sitemap size (under 50MB / 50,000 URLs per file)
- For large sites: verify sitemap index file structure
Indexation Health
- Compare indexed pages (site:domain.com) vs expected pages
- Identify index bloat (thin, duplicate, or low-value pages indexed)
- Check for noindex tags on important pages
- Review Google Search Console coverage report patterns
- Identify orphan pages (in sitemap but no internal links)
Crawl Budget Optimization
- Identify crawl traps (infinite pagination, calendar URLs, faceted navigation)
- Check crawl depth (critical pages should be within 3 clicks)
- Review log files for crawler behavior patterns
- Identify wasted crawl budget on low-value URLs
Phase 2: Site Architecture & Internal Linking
URL Structure
- Consistent URL patterns (lowercase, hyphens, no trailing slashes OR consistent trailing slashes)
- Logical hierarchy reflecting content taxonomy
- No URL parameters where clean URLs are possible
- Proper handling of pagination (rel=next/prev or load-more)
Internal Link Analysis
- PageRank flow: are high-authority pages linking to important content?
- Orphan page detection (pages with zero internal links)
- Broken internal links (404s)
- Anchor text distribution (relevant, varied, not over-optimized)
- Link depth audit (pages more than 3 clicks from homepage)
Navigation & Hierarchy
- Breadcrumb implementation (with BreadcrumbList schema)
- Navigation depth (flatten deep hierarchies)
- Footer link optimization
- Faceted navigation handling (noindex, canonical, or robots)
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.
- 9d ago First seen · 368 lines · 75 tokens per session scan A 50e781a5f2fd
technical-seo-audit is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (133 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 3,121 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.