SEO audit dashboard
Translate site checks into a prioritized queue with supporting evidence.
Customize the recipe
Prompt preview
# SEO audit dashboard Translate site checks into a prioritized queue with supporting evidence. ## Deliverable A dashboard with inspectable findings, evidence links and a report export. ## Stack and visual direction - Recommended starting stack: Next.js and TypeScript with a small data model. Build the core workflow with fixtures before connecting external services. - Swiss grid: Use a visible modular grid, aligned baselines, asymmetric composition and tight typographic hierarchy. Reflow the grid without shrinking essential text. Apply this direction to the interface while keeping data and controls easy to read. - Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [OpenSEO](https://openseo.so/docs/skills) (Skill) — Run an appropriate site audit, keyword or local visibility workflow when data access is available. Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges. [Official setup](https://openseo.so/docs/agent-setup). Fallback: Inspect local page metadata, internal links and available first-party exports. Label unavailable competitive or search-volume data as unknown. - [Lighthouse](https://github.com/GoogleChrome/lighthouse) (Repository) — Capture comparable page performance, SEO and accessibility diagnostics. - [Lychee](https://github.com/lycheeverse/lychee) (Repository) — Check internal and external links and make transient failures distinguishable. - [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance. Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually. ## Workflow 1. Use a permitted site or a representative fixture. Normalize crawl findings, group duplicates, and prioritize issues by page scope and severity. Use local crawl checks when live data is unavailable. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] A known broken link and duplicate title reach the correct issue groups. - [ ] Data gaps and crawl errors appear as explicit states with a retry or manual path. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path. - [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.
Recipe resources
Source, setup, and compatibility details.
OpenSEO
Run an appropriate site audit, keyword or local visibility workflow when data access is available.
Live data may require OpenSEO access or a configured MCP connection. Some lookups can incur charges.
Upstream documents Codex, Claude Code.
Setup guide for OpenSEOLighthouse
Capture comparable page performance, SEO and accessibility diagnostics.
License · Apache-2.0
Lychee
Check internal and external links and make transient failures distinguishable.
License · Apache-2.0 or MIT
Web Design Guidelines
Review frontend UI against usability and accessibility guidance.
Access to the current upstream guidelines for the skill's full review.
License · MIT
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI