$ ~/registry/skill/microsoft-plugins-power-pages-skills-add-seo

SKILL

add-seo

Name: add-seo
Author: microsoft

Add essential SEO settings to Power Pages sites for better visibility and sharing.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

The material indicates an open-source, prompt-only SEO helper skill with no required secrets and no declared remote endpoints, so the overall risk is low. The main caveat is that the README includes instructions to run a local Node version-check script and to modify/commit site files, but based on the provided objective checks, there are no clear high-risk red flags.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required. No API tokens, cloud credentials, or third-party account access are indicated, so credential exposure and misuse risk appears low.

Network egressLow risk

No remote endpoints are declared. The skill’s purpose is to add robots.txt, sitemap.xml, and meta tags to a local/existing Power Pages code site. While the documentation mentions collecting the production URL and site routes, the material does not show those data being sent to external services.

Code executionCaution

The README includes an instruction to run a local command, `node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"`, and describes verification and commit steps; this implies ordinary local script execution and possible developer-tool usage. Given the objective check marks it as prompt-only and there are no specific signs of elevated or suspicious execution scope, this is a caution rather than a high-risk issue.

Data accessCaution

The workflow involves locating and reading project files such as `powerpages.config.json` and `package.json`, and generating or modifying site assets like robots.txt, sitemap.xml, and index.html. This is local project file access consistent with the declared SEO purpose. No system-level or unrelated data access beyond that purpose is indicated.

Supply chainLow risk

The source is the open-source GitHub repository `microsoft/power-platform-skills`, which makes the code auditable and materially lowers supply-chain risk. Although the license is unspecified, the repository has 0 stars, and maintenance status is unknown, those uncertainties alone do not constitute a high-risk red flag.

Recommendations

Before use, manually inspect the actual skill prompt and related scripts in the repository to confirm there is no extra command execution or hidden outbound communication.
If you allow it to modify site files, work in version control on a separate branch and review each change to robots.txt, sitemap.xml, and meta tags.
If the local Node check script mentioned in the README is to be used, review the script source and dependency provenance first.
Use it only within a controlled working directory that contains the Power Pages project, and avoid exposing unrelated directories to the skill.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "add-seo" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/add-seo/SKILL.md
2. Save it as ~/.claude/skills/add-seo/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Add SEO basics to a company website

Prompt

Please add essential SEO configuration to my Power Pages code site, including robots.txt, sitemap.xml, meta description, Open Graph tags, and favicon, and explain the purpose of each item.

Expected

Provides SEO-ready site content or code snippets, plus a brief explanation of what each configuration does.

Improve search engine indexing

Prompt

My Power Pages site is hard to find in search results. Help me add the basic SEO files and tag configurations that improve indexing.

Expected

Generates robots.txt, sitemap.xml, and page head tag recommendations or code to improve indexing.

Optimize social sharing previews

Prompt

Please review and add Open Graph tags and favicon configuration for my Power Pages site so shared links look more complete on social platforms.

Expected

Outputs tag configuration for better social link previews along with favicon setup recommendations.

// docs

Plugin check: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Add SEO

Add essential SEO assets to a Power Pages code site: robots.txt, sitemap.xml, and meta tags.

Prerequisite: This skill expects an existing Power Pages code site created via /create-site. Run that skill first if the site does not exist yet.

Core Principles

Crawlability first: Every public page must be discoverable by search engines via a valid robots.txt and sitemap.xml before any other SEO work matters.
Accurate metadata: Meta tags (title, description, Open Graph) must truthfully represent page content — misleading metadata harms rankings.
Framework-aware placement: SEO assets must be placed in the correct location for the detected framework (public directory, layout component, etc.).

Initial request: $ARGUMENTS

Workflow

Phase 1: Verify Site Exists → Locate the Power Pages project
Phase 2: Gather SEO Configuration → Site URL, pages, preferences
Phase 3: Plan & Approve → Present SEO additions inline, get user approval
Phase 4: Add robots.txt → Create robots.txt in public directory
Phase 5: Add sitemap.xml → Generate sitemap.xml from site routes
Phase 6: Add Meta Tags → Add title, description, viewport, Open Graph, and favicon to index.html
Phase 7: Verify & Commit → Verify via Playwright, commit changes

Phase 1: Verify Site Exists

Goal: Confirm a Power Pages code site exists and understand its structure.

Actions

1.1 Locate Project

Look for powerpages.config.json in the current directory or immediate subdirectories to find the project root. Use your file-search tool (e.g., Glob with patterns powerpages.config.json and */powerpages.config.json) rather than a shell-specific command.

If not found: Tell the user to create a site first with /create-site.

1.2 Read Existing Config

Read powerpages.config.json to get the site name and config.

1.3 Detect Framework & Discover Routes

Read package.json to determine the framework and locate key files. See ${CLAUDE_PLUGIN_ROOT}/references/framework-conventions.md for the full framework → public directory → index HTML mapping and route discovery patterns.

Build a list of all routes (e.g., /, /about, /contact, /blog).

Output

Project root path identified
Framework detected (React, Vue, Angular, or Astro)
Full list of discoverable routes

Phase 2: Gather SEO Configuration

Goal: Collect all SEO preferences from the user before making any changes.

Actions

Use AskUserQuestion to collect SEO preferences:

Call 1

Question	Header	Options
What is the production URL for your site? (e.g., https://contoso.powerappsportals.com)	Site URL	(free text — use single generic option so user types via "Other")
Which pages should be excluded from search engine indexing?	Exclusions	None — index all pages (Recommended), Admin/auth pages only, Let me specify

Call 2

Question	Header	Options
What meta description should appear in search results?	Description	(free text — use single generic option so user types via "Other")
Add Open Graph tags for social media sharing?	OG Tags	Yes — add Open Graph and Twitter Card tags (Recommended), No — skip social tags