Agent skill · Audited from source
seo-auditing
skill · spencerpauly/awesome-cursor-skillsCC0-1.0 licenceAudited 29 Oct 2026 · source 94fd3401595c
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 94fd3401595c and found no filesystem, network or shell access and no hard-coded secrets. What it does: Audit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals.
Cite
Cite this page
ModelsAtlas. “seo-auditing (spencerpauly/awesome-cursor-skills)”. Retrieved 29 Oct 2026. https://modelsatlas.com/skills/spencerpauly/seo-auditing
Trust audit
Audit 0.4.1 · source read 29 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 94fd3401595c · 29 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherspencerpauly GitHub userOwner of the repository this skill is read from
- Source folderspencerpauly/awesome-cursor-skills/resources/seo-auditingThe exact folder we audited
- LicenceCC0-1.0As the repository states it
- Commit pinned for this verdict94fd3401595cA new audit runs when the source changes
- Repository statusNot archivedLast push 88 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Audit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals.
---
name: seo-auditing
description: Audit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals.
user-invocable: true
---
# SEO Auditing
Check and fix technical SEO issues in a web project.
## Audit Checklist
### 1. Meta Tags
Every page must have:
```html
<head>
<title>Page Title — Site Name</title>
<meta name="description" content="155 chars max, compelling summary" />
<link rel="canonical" href="https://example.com/page" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
</head>
```
Check for:
- [ ] Unique `<title>` per page (50-60 chars)
- [ ] Unique `<meta description>` per page (120-155 chars)
- [ ] Canonical URL set (avoids duplicate content)
- [ ] No `noindex` on pages that should be indexed
### 2. Open Graph & Social
```html
<meta property="og:title" content="Page Title" />
<meta property="og:description" content="Description for social sharing" />
<meta property="og:image" content="https://example.com/og-image.png" />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />
```
- OG image should be 1200x630px
- Test with https://developers.facebook.com/tools/debug/ and https://cards-dev.twitter.com/validator
### 3. Structured Data (JSON-LD)
Add schema markup for rich search results:
```html
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title",
"author": { "@type": "Person", "name": "Author Name" },
"datePublished": "2026-04-10",
"image": "https://example.com/image.jpg"
}
</script>
```
Common types: `Article`, `Product`, `FAQPage`, `Organization`, `BreadcrumbList`
Test with: https://search.google.com/test/rich-results
### 4. Sitemap
`/sitemap.xml` should:
- List all indexable pages
- Include `<lastmod>` dates
- Exclude pages with `noindex`
- Be under 50MB / 50,000 URLs per file
- Be referenced in `robots.txt`
### 5. Robots.txt
`/robots.txt` should:
```
User-agent: *
Allow: /
Disallow: /api/
Disallow: /admin/
Sitemap: https://example.com/sitemap.xml
```
- Not block CSS/JS files (search engines need them to render)
- Not block pages you want indexed
### 6. Performance (Core Web Vitals)
| Metric | Good | Needs Work |
|--------|------|------------|
| LCP (Largest Contentful Paint) | < 2.5s | > 4.0s |
| INP (Interaction to Next Paint) | < 200ms | > 500ms |
| CLS (Cumulative Layout Shift) | < 0.1 | > 0.25 |
Key fixes:
- Compress and lazy-load images
- Preload critical fonts and CSS
- Avoid layout shifts from dynamic content
- Use `next/image` or equivalent for automatic optimization
### 7. Crawlability
- [ ] All important pages are reachable from internal links
- [ ] No orphan pages (pages with zero internal links)
- [ ] No redirect chains (A→B→C should be A→C)
- [ ] 404 pages return proper HTTP 404 status
- [ ] No broken internal links
### 8. Accessibility (SEO Signals)
- [ ] All images have `alt` text
- [ ] Heading hierarchy is correct (one `h1`, then `h2`, `h3` etc.)
- [ ] Links have descriptive text (not "click here")
- [ ] Language attribute set: `<html lang="en">`
## Quick Automated Check
```bash
# Check robots.txt
curl -s https://example.com/robots.txt
# Check sitemap
curl -s https://example.com/sitemap.xml | head -20
# Check meta tags
curl -s https://example.com | grep -E '<title>|<meta name="description"|<link rel="canonical"'
# Check HTTP status codes
curl -o /dev/null -s -w "%{http_code}" https://example.com/page
```
## Tips
- Run Lighthouse in Chrome DevTools → check SEO score
- Google Search Console is the source of truth for indexing issues
- Mobile-friendliness is a ranking factor — test on mobile viewports
- Page speed directly affects rankings — optimize Core Web VitalsExcerpt, first 3,870 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 94fd340
git clone https://github.com/spencerpauly/awesome-cursor-skills git -C awesome-cursor-skills checkout 94fd3401595c
The author documents no install command, so this uses the repository directly. Our verdict covers commit 94fd3401595c only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
94fd3401595c
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about seo-auditing
What does the seo-auditing skill do?
Is seo-auditing safe to install?
What can seo-auditing access on my machine?
How current is this page?
Sources
- github.com/spencerpauly/awesome-cursor-skills/tree/main/resource — the audited source at commit 94fd3401595c and every finding aboveObserved · 29 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the seo-auditing skill do?
- Is seo-auditing safe to install?
- What can seo-auditing access on my machine?