Guides optimization of meta tags beyond title, description, Open Graph, and Twitter Cards. Covers hreflang, robots, viewport, charset, and metadata completeness.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpage-metadataExecute the skills CLI command in your project's root directory to begin installation:
Fetches page-metadata from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate page-metadata. Access via /page-metadata in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides optimization of meta tags beyond title, description, Open Graph, and Twitter Cards. Covers hreflang, robots, viewport, charset, and metadata completeness.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for language/locale and indexing goals.
Identify:
Three non-negotiables: (1) Self-referencing tags (each page links to itself), (2) Symmetric annotations (every version lists ALL others), (3) Valid ISO 639-1 or language-region codes (en, en-US, zh-CN).
Implementation methods: HTML <link> in head, XML sitemap (xhtml:link), or HTTP headers. For SPAs/JS-rendered pages, use sitemap-based hreflang as backup. See rendering-strategies for SSR/SSG/CSR.
Canonical alignment: Canonical URL must match the same regional version hreflang refers to. Misalignment causes Google to ignore hreflang.
x-default: Fallback for users whose language/location doesn't match any version. Point to default locale or language-selector page.
export const metadata = {
alternates: {
languages: {
'en-US': '/en/page',
'zh-CN': '/zh/page',
'x-default': '/en/page',
},
},
};
<link rel="alternate" hreflang="en" href="https://example.com/en/page" />
<link rel="alternate" hreflang="zh" href="https://example.com/zh/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/page" />
Page-level control for indexing and link following. See indexing for which page types typically need noindex.
| Directive | Effect |
|---|---|
noindex |
Exclude page from search results |
nofollow |
Do not pass link equity through links on the page; does NOT prevent indexing |
noindex,follow |
Exclude from SERP; allow crawlers to follow links (most common for thank-you, signup, legal) |
noindex,nofollow |
Exclude + block link flow (login, staging, test pages) |
Crawl vs index vs link equity: robots.txt = crawl control; noindex = index control; nofollow = link equity only. See robots-txt, indexing.
<meta name="robots" content="noindex, follow">
Next.js: metadata.robots = { index: false, follow: true }. Default is index: true, follow: true.
<meta name="viewport" content="width=device-width, initial-scale=1">
Required for mobile-friendly pages; affects Core Web Vitals and mobile search. For full mobile-first indexing and mobile usability requirements, see mobile-friendly.
<meta charset="UTF-8">
Place in <head>; first child of <head> recommended.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added page-metadata from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
page-metadata reduced setup friction for our internal harness; good balance of opinion and flexibility.
page-metadata reduced setup friction for our internal harness; good balance of opinion and flexibility.
page-metadata fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added page-metadata from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: page-metadata is the kind of skill you can hand to a new teammate without a long onboarding doc.
page-metadata is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
page-metadata has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: page-metadata is focused, and the summary matches what you get after install.
We added page-metadata from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 46