In plain English
This skill helps Lovable follow a safe process for check seo and share previews so non-coders can keep building without guessing the next technical step.
The problem
Review titles, descriptions, Open Graph, canonical URLs, semantic HTML, sitemap, robots.txt, alt text, and structured data.
When to use it
- You publish a marketing site
- You publish articles
- You share links on LinkedIn
- You want AI tools to understand your pages
What this skill checks
- Review metadata and headings
- Check OG and canonical
- Recommend structured data
- Avoid keyword stuffing
What to avoid
- Unrelated redesigns
- Broad rewrites
- Database changes without a reason
- Hidden security risks
- Changing working behaviour without explaining the impact
Skill instructions
Copy this into your Lovable workspace as a saved skill.
SKILL.md
# /seo-launch-review
Use this skill when publishing a website, landing page, article, directory, or public resource in a Lovable project.
Before editing:
1. Explain the current problem in plain English.
2. Identify the affected feature, route, component, table, function, or integration.
3. Review recent changes where relevant.
4. Produce a short fix or implementation plan before making changes.
What to check:
- Review metadata and headings.
- Check OG and canonical.
- Recommend structured data.
- Avoid keyword stuffing.
Rules:
- Do not redesign unrelated parts of the app.
- Do not rewrite unrelated components.
- Do not change database schema unless clearly required.
- Do not expose private data or secrets.
- Prefer the smallest safe change.
Implementation:
1. Apply the smallest safe change first.
2. Keep each change narrow and testable.
3. Preserve existing working behaviour.
4. Add or recommend test scenarios.
Final output:
- Problem summary.
- Root cause or best diagnosis.
- Changes applied or recommended.
- Files, routes, tables, functions, or integrations affected.
- Risk level.
- Test checklist.
- Next recommended step.
Example prompt
Prompt
Use /seo-launch-review to review this issue. Do not make changes yet. First explain the diagnosis, risks, and safest next step.Expected output
Plain-English diagnosis Risk level Files, routes, tables, or integrations affected Safe fix plan Test checklist Next recommended step