SEO Audit
freekmurze/dotfiles
When the user wants to audit, review, or diagnose SEO issues on their site.
Answers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation.
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/google-official-seo-guide .claude/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .claude/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/google-official-seo-guide .agents/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .agents/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/google-official-seo-guide .cursor/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .cursor/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/littleben/awesomeAgentskills.git --path google-official-seo-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/google-official-seo-guide .gemini/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .gemini/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/google-official-seo-guide .github/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .github/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install littleben/awesomeAgentskills google-official-seo-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/littleben/awesomeAgentskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/google-official-seo-guide .opencode/skills/google-official-seo-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-official-seo-guide" agent skill from https://github.com/littleben/awesomeAgentskills/tree/main/google-official-seo-guide into .opencode/skills/google-official-seo-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-official-seo-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
google-official-seo-guideAnswers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation.
The skill is meant to trigger on questions about ranking in Google Search, meta tags and titles, crawling and indexing problems and how Search works, as well as structured data such as VideoObject, BroadcastEvent and Clip, schema.org markup for rich results, sitemaps, robots.txt, breadcrumbs and hreflang. It also covers technical topics like mobile-first indexing, JavaScript rendering, canonical tags, robots meta tags and URL structure, plus Search Console reports, anchor text, spam policies, site migrations and redirects.
Key concepts are the three stages of Google Search, which are crawling, indexing and serving, and principles such as mobile-first indexing, canonical URLs, structured data and the Search Essentials. A short quick reference shows a basic VideoObject JSON-LD example. Detail sits in reference files on APIs, appearance, crawling, fundamentals, guides, indexing, specialty topics and other pages, and the excerpt is cut off after the first example.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit ece600f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are html and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
schema.orguntrusted-site.compartner-site.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Google Search SEO Guide loads about 4.2k tokens when it runs, and up to ~118k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 1,462 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from littleben/awesomeAgentskills at commit ece600f, republished under its MIT licence (© littleben). 1,462 words, ~4,177 tokens.
.claude/skills/google-official-seo-guide/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.Comprehensive assistance with Google Search optimization, SEO best practices, and search visibility improvements based on official Google documentation.
This skill should be triggered when users ask about:
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Video title",
"description": "Video description",
"thumbnailUrl": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"uploadDate": "2024-03-31T08:00:00+08:00",
"duration": "PT1M54S",
"contentUrl": "https://example.com/video.mp4",
"embedUrl": "https://example.com/embed/123"
}Use this for: Adding basic video metadata to help Google understand and display your videos in search results.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Livestream title",
"uploadDate": "2024-10-27T14:00:00+00:00",
"publication": {
"@type": "BroadcastEvent",
"isLiveBroadcast": true,
"startDate": "2024-10-27T14:00:00+00:00",
"endDate": "2024-10-27T14:37:14+00:00"
}
}Use this for: Enabling the LIVE badge on livestream videos in Google Search results.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Cat video",
"hasPart": [
{
"@type": "Clip",
"name": "Cat jumps",
"startOffset": 30,
"endOffset": 45,
"url": "https://example.com/video?t=30"
},
{
"@type": "Clip",
"name": "Cat misses the fence",
"startOffset": 111,
"endOffset": 150,
"url": "https://example.com/video?t=111"
}
]
}Use this for: Manually specifying important timestamps/chapters in your video for the key moments feature.
<!-- Bad: Too generic -->
<a href="https://example.com">Click here</a> to learn more.
<!-- Better: Descriptive and contextual -->
For a full list of cheese available for purchase, see the
<a href="https://example.com">list of cheese types</a>.
<!-- Bad: Too many adjacent links -->
I've written about cheese
<a href="/page1">so</a>
<a href="/page2">many</a>
<a href="/page3">times</a>.
<!-- Better: Spaced out with context -->
I've written about cheese so many times this year:
the <a href="/blue-cheese">controversy over blue cheese</a>,
the <a href="/oldest-brie">world's oldest brie</a>, and
<a href="/boy-and-cheese">A Boy and His Cheese</a>.Use this for: Creating effective internal and external links that help both users and Google understand your content.
<!-- Recommended: Google can crawl these -->
<a href="https://example.com">Link text</a>
<a href="/products/category/shoes">Link text</a>
<a href="./products/category/shoes">Link text</a>
<!-- Not recommended: May not be crawled -->
<a routerLink="products/category">Link text</a>
<a onclick="goto('https://example.com')">Link text</a>
<span href="https://example.com">Link text</span>Use this for: Ensuring your links are discoverable and crawlable by Googlebot.
<!-- Mobile version (https://m.example.com/) -->
<link rel="canonical" href="https://example.com/">
<link rel="alternate" hreflang="es" href="https://m.example.com/es/">
<link rel="alternate" hreflang="fr" href="https://m.example.com/fr/">
<!-- Desktop version (https://example.com/) -->
<link rel="canonical" href="https://example.com/">
<link rel="alternate" media="only screen and (max-width: 640px)"
href="https://m.example.com/">
<link rel="alternate" hreflang="es" href="https://example.com/es/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/">Use this for: Properly configuring separate mobile URLs (m-dot sites) with internationalization support.
<!-- Don't index this page -->
<meta name="robots" content="noindex">
<!-- Don't follow links on this page -->
<meta name="robots" content="nofollow">
<!-- Don't index and don't follow -->
<meta name="robots" content="noindex, nofollow">
<!-- Don't show snippet in search results -->
<meta name="robots" content="nosnippet">Use this for: Controlling how Google crawls and indexes specific pages.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Video title",
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": { "@type": "WatchAction" },
"userInteractionCount": 12345
}
}Use this for: Displaying the number of views/watches for your video content.
<!-- Citing sources with proper attribution -->
<p>
According to a recent study from Swiss researchers,
Emmental cheese wheels exposed to music had a milder flavor,
with the full findings available in
<a href="https://example.com/cheese-study">
Cheese in Surround Sound—a culinary art experiment
</a>.
</p>
<!-- Use nofollow when you don't trust the source -->
<a href="https://untrusted-site.com" rel="nofollow">
Untrusted content
</a>
<!-- Sponsored links must be marked -->
<a href="https://partner-site.com" rel="sponsored">
Partner content
</a>Use this for: Properly linking to external sources while maintaining SEO best practices.
<!-- Ensure same robots meta tags on mobile and desktop -->
<meta name="robots" content="index, follow">
<!-- Use same structured data on both versions -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Corp"
}
</script>
<!-- Ensure images have proper alt text on mobile -->
<img src="product.jpg" alt="Blue ceramic vase, 12 inches tall">
<!-- Use same title and meta description -->
<title>Product Name - Category | Site Name</title>
<meta name="description" content="High-quality product description">Use this for: Ensuring your mobile site is properly optimized for Google's mobile-first indexing.
This skill includes comprehensive documentation organized into the following categories:
Content: Getting started with Google Search Console, monitoring tools, and APIs.
Key Topics:
When to use: Setting up monitoring, accessing Search Console features, understanding available reports.
Content: Visual elements and rich results in Google Search.
Key Topics:
When to use: Optimizing how your content appears in search results, implementing rich results, understanding search UI elements.
Content: How Google discovers, crawls, and accesses web content.
Key Topics:
When to use: Debugging crawling issues, optimizing crawl efficiency, controlling what Google crawls.
Content: Core concepts and essential SEO knowledge.
Key Topics:
When to use: Learning SEO basics, understanding Google Search fundamentals, starting a new project.
Content: Detailed how-to guides for specific SEO tasks.
Key Topics:
When to use: Implementing specific SEO features, solving technical SEO challenges, following best practices.
Content: How Google indexes content and troubleshooting indexing issues.
Key Topics:
When to use: Fixing indexing problems, managing duplicate content, controlling what gets indexed.
Content: Additional topics and specialized information.
Key Topics:
When to use: Understanding policies, avoiding penalties, staying current with Google changes.
Content: Structured data and specialized search features.
Key Topics:
When to use: Implementing video features, adding structured data, enabling rich results, debugging markup errors.
Start with fundamentals.md to understand:
Then review guides.md for practical implementation:
Pro tip: Use the Quick Reference examples above as templates for common tasks.
Focus on these areas:
Common workflows:
Priority reading:
Common tasks:
Explore specialized topics:
Advanced patterns:
To refresh this skill with updated documentation:
© littleben, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 9 other files (references) in google-official-seo-guide of littleben/awesomeAgentskills.
Open the folder on GitHubat commit ece600f
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in littleben/awesomeAgentskills, which our catalogue first saw on October 7, 2026.
Google Search SEO Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Search SEO Guide this skilllittleben/awesomeAgentskills | 189 | 2 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO Auditfreekmurze/dotfiles | 1k | 34 repos | ~2.2k | Automated safety check: Pass | None | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| SEO Setupalisamadiii/Portfolio | 180 | — | ~1.7k | Automated safety check: Pass | None | |
| SEOever-works/ever-works | 162 | 10 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Universal SEO AnalysisAgriciDaniel/claude-seo | 19k | — | ~4.9k | Automated safety check: Pass | MIT |
freekmurze/dotfiles
When the user wants to audit, review, or diagnose SEO issues on their site.
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
alisamadiii/Portfolio
Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).
ever-works/ever-works
Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
littleben/awesomeAgentskills
Shipany AI-powered SaaS boilerplate documentation. Use when working with Shipany framework, Next.js 15, TypeScript, Drizzle ORM, NextAuth, payment…
littleben/awesomeAgentskills
Keeps Agents.md, claude.md and gemini.md identical across a project by scanning folders and copying the newest version over the others, once or continuously.
Works with
Categories
Answers Google Search optimization questions from reference files covering crawling, indexing, structured data, Search Console and site visibility, drawn from Google's documentation. txt, breadcrumbs and hreflang. It also covers technical topics like mobile-first indexing, JavaScript rendering, canonical tags, robots meta tags and URL structure, plus Search Console reports, anchor text, spam policies, site migrations and redirects.
Google Search SEO Guide fits situations like: fixing pages that Google is not crawling or indexing; adding VideoObject or other structured data for rich results; setting up canonical tags, hreflang or sitemaps correctly; understanding how a Search Console report relates to visibility.
Run `npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a claude-code`. Or copy the skill folder (google-official-seo-guide in littleben/awesomeAgentskills) into .claude/skills/google-official-seo-guide in your project. Claude Code loads it when a task matches its description.
Run `npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a codex`. Or copy the skill folder (google-official-seo-guide in littleben/awesomeAgentskills) into .agents/skills/google-official-seo-guide in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add littleben/awesomeAgentskills --skill google-official-seo-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-official-seo-guide, .gemini/skills/google-official-seo-guide, .github/skills/google-official-seo-guide and .opencode/skills/google-official-seo-guide in your project.
SKILL.md names no scripts, command-line tools or credentials: Google Search SEO Guide is instructions for the agent only.
SKILL.md names 3 domains. In commands or code: schema.org, untrusted-site.com and partner-site.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Google Search SEO Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 114k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Google Search SEO Guide: SEO Audit (freekmurze/dotfiles, 1k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars), SEO Setup (alisamadiii/Portfolio, 180 stars) and SEO (ever-works/ever-works, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
littleben (a GitHub user) maintains it in littleben/awesomeAgentskills, which has 189 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on January 17, 2026.
Source: littleben/awesomeAgentskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.