seo-page-rules

name	seo-page-rules
description	Code-generation skill. Use only when editing public pages, metadata, canonicals, structured data, sitemaps, robots rules, or other SEO-sensitive repo behavior.
metadata	{"family":"seo","owner":"seo + engineering","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"}

SEO Page Rules

This is a code-generation skill. Use it only for implementation work in the repo.

Use When

• adding or changing page metadata
• adding canonical URLs
• adding JSON-LD
• changing sitemap coverage
• changing robots behavior
• reviewing whether a page is SEO-complete

Source Files

• root metadata: src/lib/site/root-metadata.ts
• metadata helpers: src/lib/seo/metadata.ts
• root layout: src/app/layout.tsx
• global JSON-LD: src/shared/seo/JsonLd.tsx
• feature schemas: src/features/career-hub/shared/seo/EnhancedSchema
• sitemap logic: src/shared/sitemap/*

Required Rules

• Keep metadata server-rendered.
• Keep schema server-rendered.
• Use helper functions from src/lib/seo/metadata.ts.
• Use real production canonicals under https://indeedflex.com.
• Update shared sitemap logic, not ad hoc route-local sitemap code.

Preferred Metadata Helpers

• generateSEOMetadata
• generateGuideMetadata
• generateToolMetadata
• generateRoleMetadata
• generateCityMetadata
• generateLocationMetadata
• generateSalaryMetadata
• generateStateTaxMetadata
• generateNotFoundMetadata

Current Common Schema Components

• FAQSchema
• BreadcrumbSchema
• WebPageSchema
• SoftwareApplicationSchema
• JobPostingSchema
• OccupationSchema

Forbidden Patterns

• duplicating root metadata defaults on every page
• pushing SEO-critical content behind client-only shells
• inventing route-local sitemap logic when shared sitemap code already owns it
• making root layout request-bound without explicit need

Search Rule

Current homepage search behavior:

• homepage quick search calls /api/search
• heavy search index logic is in src/lib/server/search-index.ts

Do not move the heavy search index back into the homepage client bundle.

Minimal Checklist

1. Metadata helper is correct.
2. Canonical is correct.
3. H1 exists.
4. JSON-LD matches page type.
5. Content is crawlable server-rendered HTML.
6. Internal links exist.