Yoast SEO Premium

Build the following focused alternative to Yoast SEO Premium. Implement the focused workflow below first; the verdict is not evidence of a completed or production-certified build.

WORKING SLICE
Build a focused WordPress plugin that edits per-post titles/descriptions, previews snippets and reports internal-link/redirect issues using native WordPress APIs.

SETUP AND ARCHITECTURE
Use PHP and native WordPress plugin hooks/post metadata, with optional JavaScript editor controls. Prerequisites: A disposable WordPress installation, an editor and subscriber account, and a clear compatibility policy for other SEO plugins. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Store PostMeta, AnalysisRevision and RedirectRule; capability checks and nonces protect mutations, and every frontend meta value is escaped for its output context.

IMPLEMENTATION CONTRACT
Use WordPress capabilities and nonces for mutations, validate redirect destinations and escape output for its HTML context. Plugin activation must not overwrite existing SEO metadata. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.

ACCEPTANCE SCENARIO
Update metadata as an authorized editor, try the same write as a subscriber and add a redirect loop; accept the first, deny the second and reject the loop. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

# AGENTS.md — Build guide for Yoast SEO Premium

## Project scope
Build a focused WordPress plugin that edits per-post titles/descriptions, previews snippets and reports internal-link/redirect issues using native WordPress APIs.

Catalogue verdict: yes. A small WordPress plugin can cover selected metadata and redirect workflows. Yoast SEO Premium combines maintained editor guidance, internal-link suggestions, redirects, structured-data behavior and support; the limited plugin here does not reproduce that whole system.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Runtime and tools: PHP and native WordPress plugin hooks/post metadata, with optional JavaScript editor controls.
- Before starting: A disposable WordPress installation, an editor and subscriber account, and a clear compatibility policy for other SEO plugins.

## Stack and architecture
- PHP and native WordPress plugin hooks/post metadata, with optional JavaScript editor controls
- Data design: Store PostMeta, AnalysisRevision and RedirectRule; capability checks and nonces protect mutations, and every frontend meta value is escaped for its output context.
- Setup: A disposable WordPress installation, an editor and subscriber account, and a clear compatibility policy for other SEO plugins

## Security and data integrity
- Use WordPress capabilities and nonces for mutations, validate redirect destinations and escape output for its HTML context. Plugin activation must not overwrite existing SEO metadata.
- Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.
- Keep secrets outside client bundles and exported projects; document what leaves the device and make retention/deletion controls visible.

## Agent implementation rules
- Project rule — domain: Store PostMeta, AnalysisRevision and RedirectRule; capability checks and nonces protect mutations, and every frontend meta value is escaped for its output context.
- Project rule — scope and recovery: Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.
- Project rule — acceptance: Update metadata as an authorized editor, try the same write as a subscriber and add a redirect loop; accept the first, deny the second and reject the loop.
- Project rule — delivery: document real setup commands and permissions; do not claim a build, accuracy level, performance result or security certification that has not been demonstrated.

## Optional agent skills and references
- Recommended skill: [seo-audit](https://github.com/coreyhaines31/marketingskills/blob/main/skills/seo-audit/SKILL.md) — review crawlability, metadata and evidence-based on-page findings without promising search rankings. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.
- Recommended skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — review configuration and API defaults against the app-specific invariants and recovery boundaries above; this is not a security certification. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this working slice using synthetic or explicitly authorized non-sensitive examples: Build a focused WordPress plugin that edits per-post titles/descriptions, previews snippets and reports internal-link/redirect issues using native WordPress APIs.
- Share a synthetic example export and the acceptance walkthrough; keep real customer, health, financial and source data private: Update metadata as an authorized editor, try the same write as a subscriber and add a redirect loop; accept the first, deny the second and reject the loop.
- State the limits before asking someone to replace their existing tool: Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.

## Engineering roadmap
1. Phase 1 — Pin the working slice and create its example input: Build a focused WordPress plugin that edits per-post titles/descriptions, previews snippets and reports internal-link/redirect issues using native WordPress APIs. Confirm setup: A disposable WordPress installation, an editor and subscriber account, and a clear compatibility policy for other SEO plugins.
2. Phase 2 — Implement persistence and write-time invariants before decorating the UI: Store PostMeta, AnalysisRevision and RedirectRule; capability checks and nonces protect mutations, and every frontend meta value is escaped for its output context.
3. Phase 3 — Connect the working view to real saved state. Use WordPress capabilities and nonces for mutations, validate redirect destinations and escape output for its HTML context. Plugin activation must not overwrite existing SEO metadata.
4. Phase 4 — Expose the app-specific limits and recovery path in context: Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.
5. Phase 5 — Walk through this concrete acceptance case and preserve its exported evidence: Update metadata as an authorized editor, try the same write as a subscriber and add a redirect loop; accept the first, deny the second and reject the loop. Finish the README and backup/restore instructions; report unfinished capabilities explicitly.

## Paid-product capabilities outside this build
- maintained WordPress editor and content-analysis integration
- automated internal-link suggestions and broader redirect tooling
- the full structured-data implementation and compatibility maintenance
- product updates, documentation and support

## Implementation prompt
Build the following focused alternative to Yoast SEO Premium. Implement the focused workflow below first; the verdict is not evidence of a completed or production-certified build.

WORKING SLICE
Build a focused WordPress plugin that edits per-post titles/descriptions, previews snippets and reports internal-link/redirect issues using native WordPress APIs.

SETUP AND ARCHITECTURE
Use PHP and native WordPress plugin hooks/post metadata, with optional JavaScript editor controls. Prerequisites: A disposable WordPress installation, an editor and subscriber account, and a clear compatibility policy for other SEO plugins. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Store PostMeta, AnalysisRevision and RedirectRule; capability checks and nonces protect mutations, and every frontend meta value is escaped for its output context.

IMPLEMENTATION CONTRACT
Use WordPress capabilities and nonces for mutations, validate redirect destinations and escape output for its HTML context. Plugin activation must not overwrite existing SEO metadata. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
Correct the prior Python-crawler-only scope: use PHP and WordPress hooks for the plugin, with optional separate audit scripts. Search previews are approximate; no ranking promises or duplicate/conflicting schema injection.

ACCEPTANCE SCENARIO
Update metadata as an authorized editor, try the same write as a subscriber and add a redirect loop; accept the first, deny the second and reject the loop. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.