SEO
gridaco/grida
SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.
When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes…
Install Page Metadata
$ npx skills add kostja94/marketing-skills --skill page-metadata -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kostja94/marketing-skills page-metadata --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/kostja94/marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/on-page/metadata .claude/skills/page-metadata && 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 "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .claude/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadataType 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 kostja94/marketing-skills --skill page-metadata -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kostja94/marketing-skills page-metadata --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo/on-page/metadata .agents/skills/page-metadata && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .agents/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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 kostja94/marketing-skills --skill page-metadata -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kostja94/marketing-skills page-metadata --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo/on-page/metadata .cursor/skills/page-metadata && 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 "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .cursor/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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/kostja94/marketing-skills.git --path skills/seo/on-page/metadata--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 kostja94/marketing-skills --skill page-metadata -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kostja94/marketing-skills page-metadata --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo/on-page/metadata .gemini/skills/page-metadata && 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 "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .gemini/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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 kostja94/marketing-skills page-metadataInstalls 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 kostja94/marketing-skills --skill page-metadata -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo/on-page/metadata .github/skills/page-metadata && 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 "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .github/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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 kostja94/marketing-skills --skill page-metadata -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kostja94/marketing-skills page-metadata --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo/on-page/metadata .opencode/skills/page-metadata && 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 "page-metadata" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/on-page/metadata into .opencode/skills/page-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "page-metadata", 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.
Facts
- Skill name
page-metadata- GitHub stars
- 1k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 846 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes…
- Works in 7 steps: Discover and classify pages → Establish intent and page identity → Route specialist work → …
- Wants a full-page metadata audit
- SKILL.md covers Ownership and boundaries, Required inputs and evidence, Lifecycle and Other technical metadata, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Page Metadata is an agent skill from kostja94/marketing-skills. When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes, build validation, rendered HTML, production verification, localization, or post-release observation. Also use for "metadata audit," "sitewide meta optimization," "metadata implementation," "meta robots," "hreflang," "viewport," or "charset." For an isolated title, description, heading, Open Graph, or Twitter Card task…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Technical SEO, Keyword research and Internationalization. It works with X (Twitter). The repository describes itself as: Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context… The licence is MIT.
When your agent uses it
- Wants a full-page metadata audit
- Implementation across discovery
- Build validation
- Production verification
Example prompts
- “metadata audit,”
- “sitewide meta optimization,”
- “metadata implementation,”
- “/page-metadata”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8dd89c5. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developers.google.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Page Metadata loads about 1.9k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 846 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from kostja94/marketing-skills at commit 8dd89c5, republished under its MIT licence (© kostja94). 846 words, ~1,903 tokens.
Download SKILL.mdSave it as
.claude/skills/page-metadata/SKILL.md (or your agent's skills folder).- name
- page-metadata
- description
- When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes, build validation, rendered HTML, production verification, localization, or post-release observation. Also use for "metadata audit," "sitewide meta optimization," "metadata implementation," "meta robots," "hreflang," "viewport," or "charset." For an isolated title, description, heading, Open Graph, or Twitter Card task, use its specialist skill directly.
- metadata.version
- 2.0.0
SEO On-Page: Page Metadata
Orchestrates the complete metadata lifecycle. It owns scope, routing, implementation, validation, and delivery; specialist skills own their individual writing and tag rules.
When invoking: On first use, briefly state the scope and which specialist skills are needed. Then work from current production evidence and the real source of truth rather than producing a detached copy sheet.
Ownership and boundaries
| Concern | Owner |
|---|---|
| Lifecycle, page inventory, implementation, validation, delivery | page-metadata |
<title> writing and review | title-tag |
| Meta description writing and review | meta-description |
| H1-H6 writing and hierarchy | heading-structure |
| Open Graph | open-graph |
| X/Twitter Cards | twitter-cards |
| Canonical URL | canonical-tag |
| Localization | localization-strategy, translation |
| Post-release query and CTR observation | google-search-console |
This skill may check H1 and body coverage to confirm that metadata promises are fulfilled. It must not rewrite H1-H6; route that work to heading-structure. It may report keyword cannibalization, but must not merge pages, change page roles, delete URLs, or redistribute target keywords.
Required inputs and evidence
Read root contextus.md when present and load only relevant modules. Otherwise use project documentation and verified product facts. Establish:
- Target site, locales, environment, and release scope.
- Page inventory from production navigation, footer, contextual links, index or hub pages, robots.txt, sitemap, production URLs, and application routes. A sitemap is evidence, not a complete inventory guarantee. For very large generated page families, inspect the template and representative examples instead of enumerating every URL.
- Page type, unique job, primary search intent, target query evidence, audience, and page-specific facts.
- Current production output: title, description, H1, canonical, robots, hreflang, OG, Twitter Cards, HTTP status, and server-returned HTML.
- Actual maintenance source: framework metadata API, layout template, route module, static HTML, JSON/YAML, CMS fields, server injection, or proxy layer.
Never infer current production metadata from source code alone. Deployment and production may differ in either direction.
Lifecycle
1. Discover and classify pages
- Build a URL-to-page-type map and select representative samples for repeated page families.
- Identify missing, duplicate, stale, inherited, fallback, or cross-locale metadata.
- Detect template-generated brand suffixes before writing titles so the suffix is not duplicated.
- Flag old brand names, parent-product language, obsolete features, or copied sibling-page claims.
2. Establish intent and page identity
- Confirm what the page alone can promise and prove.
- Use verified product facts and current page content; do not invent differentiators.
- Apply the Swap Test: if a title or description could be moved unchanged to a sibling page, it lacks page-specific information.
- Report potential cannibalization with affected URLs, overlapping intent, and evidence. Stop at reporting.
3. Route specialist work
- Use title-tag for title decisions and meta-description for descriptions.
- Use heading-structure only when headings need actual edits; otherwise check semantic alignment.
- Use open-graph and twitter-cards for social metadata. Social copy may differ from SEO copy, but page identity and claims must remain consistent.
- Use canonical-tag, localization-strategy, and translation when applicable.
4. Localize by market
- Research query language and intent for each locale; do not translate and truncate source metadata.
- Preserve product and brand terminology intentionally through a terminology source when one exists.
- Confirm each locale URL, canonical, hreflang set, and
og:localerelationship. - Treat missing or materially non-equivalent locale pages as an implementation issue rather than fabricating parity.
Show full SKILL.md (324 more words)Show less
5. Implement at the source of truth
- Edit canonical code or CMS fields, not generated output.
- Preserve URL and page identity unless a separate migration task changes them.
- Account for layout inheritance, route precedence, template interpolation, CMS fallbacks, and automatic brand suffixes.
- Keep title, description, social metadata, canonical, robots, and hreflang internally consistent without forcing identical strings.
6. Validate before release
Run relevant lint, typecheck, tests, and production build. Then start or preview the built application when practical and inspect the initial server response HTML for representative URLs and locales. A browser DOM snapshot alone is insufficient when crawlers may receive different HTML.
Check:
- exactly one effective title and one intended description;
- no empty, placeholder, duplicate, or doubly suffixed output;
- title and H1 serve the same page intent without needing identical wording;
- H2/body content substantiate the metadata promise;
- canonical, robots, hreflang, OG, and Twitter tags resolve to intended absolute URLs;
- HTML escaping, locale output, images, and status codes are correct.
7. Verify production and observe
- Recheck representative production URLs after deployment using raw response HTML.
- Use platform preview/debug tools where available for social tags; cached previews may require refresh.
- Use google-search-console after recrawl to observe query mix, impressions, title/snippet behavior, and CTR. Do not promise a ranking or CTR lift.
Other technical metadata
robotscontrols page-level indexing/snippet behavior; robots.txt controls crawling. Use indexing and robots-txt for strategy.viewportnormally useswidth=device-width, initial-scale=1.- Declare UTF-8 early in the document head.
- Hreflang annotations must use valid language or language-region codes, include self and reciprocal references, and align each locale with its own canonical URL. Use HTML, sitemap, or HTTP headers consistently.
Deliverable
Provide scope and evidence, affected URLs or families, their true maintenance source, before/after metadata where useful, unresolved blockers, any cannibalization report, build/HTML/locale/production verification, and a post-release observation plan.
Primary references
Related Skills
- title-tag, meta-description, heading-structure
- open-graph, twitter-cards, canonical-tag
- localization-strategy, translation
- indexing, robots-txt, google-search-console
© kostja94, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/seo/on-page/metadata of kostja94/marketing-skills.
Open the folder on GitHubat commit 8dd89c5
Compare with similar skills
Page Metadata 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 |
|---|---|---|---|---|---|---|
| Page Metadata this skillkostja94/marketing-skills | 1k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SEOgridaco/grida | 2.7k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Business Website Setupsickn33/agentic-awesome-skills | 47k | 1 repos | ~6.2k | Automated safety check: Pass | MIT | |
| SEO Persona Intent Mappinghashgraph-online/awesome-codex-plugins | 1.3k | — | ~561 | Automated safety check: Pass | MIT | |
| Content SEOjdevalk/skills | 105 | — | ~2.3k | Automated safety check: Pass | MIT | |
| SEO Specialistborghei/Claude-Skills | 886 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Business Website Setup
sickn33/agentic-awesome-skills
Website page register: URL, title, meta description, search intent, NAP block, schema type, canonical, indexability and Core Web Vitals target.
SEO Persona Intent Mapping
hashgraph-online/awesome-codex-plugins
Map SEO personas, search intent, funnel stage, expected content format, CTA, device context, and localization needs into actionable organic search plans.
Content SEO
jdevalk/skills
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness…
SEO Specialist
borghei/Claude-Skills
SEO covering technical SEO, content optimization, link building, keyword research, and search analytics.
SEO Optimizer
aiskillstore/marketplace
Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements.
More from kostja94/marketing-skills
All 102 skills in this repoGrokipedia Recommendations
kostja94/marketing-skills
When the user wants to add recommendations, links, or content to Grokipedia.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
Analytics Tracking
kostja94/marketing-skills
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions).
Brand Visual Generator
kostja94/marketing-skills
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics).
Canonical Tag
kostja94/marketing-skills
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals.
Content Strategy
kostja94/marketing-skills
When the user wants to plan content for SEO, create content calendar, or build topic clusters.
Related
Works with
Categories
Questions about Page Metadata
What does Page Metadata do?
When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes…. Page Metadata is an agent skill from kostja94/marketing-skills. When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes, build validation, rendered HTML, production verification, localization, or post-release observation.
When should I use Page Metadata?
Page Metadata fits situations like: wants a full-page metadata audit; implementation across discovery; build validation; production verification.
How do I install Page Metadata in Claude Code?
Run `npx skills add kostja94/marketing-skills --skill page-metadata -a claude-code`. Or copy the skill folder (skills/seo/on-page/metadata in kostja94/marketing-skills) into .claude/skills/page-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Page Metadata in Codex?
Run `npx skills add kostja94/marketing-skills --skill page-metadata -a codex`. Or copy the skill folder (skills/seo/on-page/metadata in kostja94/marketing-skills) into .agents/skills/page-metadata in your project. Codex loads it when a task matches its description.
Can I use Page Metadata in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kostja94/marketing-skills --skill page-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/page-metadata, .gemini/skills/page-metadata, .github/skills/page-metadata and .opencode/skills/page-metadata in your project.
What does Page Metadata need to run?
SKILL.md names no scripts, command-line tools or credentials: Page Metadata is instructions for the agent only.
Does Page Metadata access the network?
SKILL.md names 1 domain. As links in the text: developers.google.com. This is read from the text; nothing was executed.
Is Page Metadata safe to install?
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.
What licence does Page Metadata use?
Page Metadata is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Page Metadata use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Page Metadata?
Skills that share tags, products or a category with Page Metadata: SEO (gridaco/grida, 2.7k stars), Business Website Setup (sickn33/agentic-awesome-skills, 47k stars), SEO Persona Intent Mapping (hashgraph-online/awesome-codex-plugins, 1.3k stars) and Content SEO (jdevalk/skills, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Page Metadata?
kostja94 (a GitHub user) maintains it in kostja94/marketing-skills, which has 1,025 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 6, 2026.
Source: kostja94/marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.