Plugin check: Run

node "${PLUGIN_ROOT}/scripts/check-version.js"

— if it outputs a message, show it to the user before proceeding.

robots.txt

sitemap.xml

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.

• 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.).

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

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

• Production URL confirmed
• Exclusion list finalized
• Meta description text
• Open Graph tag preference (yes/no)

1. robots.txt content — which paths will be allowed/disallowed
2. sitemap.xml content — all discovered routes with the production URL and priority assignments
3. Meta tags to add to index.html — title, description, viewport, charset, Open Graph, Twitter Card
4. Favicon — link tag and placeholder SVG

🚦 Gate (plan · add-seo:3.plan-approval): Final sign-off on the SEO additions before any

robots.txt

/

sitemap.xml

/

index.html

write.

Trigger: Phase 3 has presented the full plan inline (robots.txt, sitemap.xml, meta tags, favicon). Why we ask: SEO assets land on disk with the wrong production URL, wrong exclusions, or unwanted OG tags — fixable but noisy in git history. Cancel leaves: Nothing — no file writes yet.

AskUserQuestion

• User-approved SEO plan ready for implementation

• public/robots.txt

  created with correct directives

sitemap.xml

<PROJECT_ROOT>/public/sitemap.xml

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc><PRODUCTION_URL>/</loc>
    <lastmod><TODAY_DATE></lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc><PRODUCTION_URL>/about</loc>
    <lastmod><TODAY_DATE></lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <!-- Additional routes... -->
</urlset>

• Home page (

  /

  ):

  1.0

• Top-level pages:

  0.8

• Sub-pages:

  0.6

/admin/*

/auth/*

• public/sitemap.xml

  created with all routes, correct URLs, and no placeholders

• Meta tags added to

  index.html

  (or Astro layout equivalent)
• Open Graph and Twitter Card tags added (if opted in)
• Favicon SVG created and linked (if not already present)

• public/robots.txt

• public/sitemap.xml

• public/favicon.svg

  (if created)

• index.html

  or equivalent (meta tags added)

1. Navigate to the site root and use

   browser_snapshot

   to verify meta tags are present in the page source
2. Navigate to

   /robots.txt

   and verify it loads
3. Navigate to

   /sitemap.xml

   and verify it loads

Reference:

${PLUGIN_ROOT}/references/skill-tracking-reference.md

--skillName "AddSeo"

CRITICAL — This step is MANDATORY. You MUST commit the SEO changes before finishing. Do NOT skip this step.

git add public/robots.txt public/sitemap.xml public/favicon.svg index.html
git commit -m "Add SEO: robots.txt, sitemap.xml, meta tags, favicon"

src/layouts/Layout.astro

index.html

favicon.svg

• Deploy the site to make SEO changes live:

  /deploy-site

• If data model is needed:

  /setup-datamodel

• For more advanced SEO: consider structured data (JSON-LD), performance optimization, and accessibility audit

• All files verified on disk
• Playwright verification passed
• Git commit created with all SEO changes

• Phase 1: If

  powerpages.config.json

  is not found, stop and redirect the user to

  /create-site

  .
• Phase 2: If the user specifies custom exclusions, confirm the exact paths before proceeding.
• Phase 3: Do not proceed to implementation until the user explicitly approves the plan.
• Phase 6.4: If the framework is Astro, meta tags go into the layout component, not

  index.html

  .
• Phase 7.2: If Playwright verification fails (e.g., robots.txt does not load), diagnose and fix before committing.