- Home
- Skills
- Marketing & SEO
- Website Launch Audit
Works with the AI Agents you already use
Website Launch Audit
Find and fix 57 kinds of launch blockers (SEO, broken links, social previews, accessibility, speed, security, GDPR, leftover placeholders), with a 0-100 score and a client-ready report.
$9.90
Website Launch Audit
Example session with this skill installed
I'm ready to deploy this Astro site to https://example.com. Can you audit the build output in the dist folder and fix any high priority issues?
- Read your context and instructions
- Compiled the website launch audit
I have completed the launch audit for the Astro site in the dist folder. The site initially scored a
68 (Grade C) due to missing meta tags, placeholder content, and a robots.txt that was still blocking search engines. I have applied fixes to the source components and the configuration.
Launch Audit Results
| Category | Initial Issues | Fixed | Remaining | Impact |
|---|---|---|---|---|
| SEO | 8 | 6 | 2 | Missing canonicals and robots.txt fixed. |
| Performance | 4 | 2 | 2 | Fixed 2MB hero image; 2 render-blocking scripts remain. |
| Content | 3 | 3 | 0 | Removed "Lorem Ipsum" from the About page. |
| Social | 2 | 2 | 0 | Added Open Graph image and Twitter card tags. |
| Accessibility | 5 | 3 | 2 | Added form labels; manual alt-text check needed. |
Final Score: 92 (Grade A)
Verdict: READY FOR LAUNCH (All critical and high-priority issues resolved).
Key Fixes Applied
- astro.config.mjs: Defined
site: 'https://example.com'to fix canonical URLs. - public/robots.txt: Updated from
Disallow: /toAllow: /and added sitemap link. - src/layouts/Layout.astro: Added missing
og:imageandviewportmeta tags. - src/pages/index.astro: Optimized the hero image using
astro:assets.
Next steps
- Check
src/pages/contact.astroto add your real office phone number where I left an HTML comment. - Verify the generated
launch-report.mdbefore sending it to the client. - Run the audit one final time against the live URL after deployment to verify security headers.
Connects securely to your tools. The creator never sees your data.
About this skill
Websites built quickly or with AI tools often ship with invisible blockers: staging robots.txt files, broken links, missing SEO tags, or leftover placeholder content. This skill scans built sites or live URLs for 57 specific launch issues, scores the site from 0-100, and provides a path to fix them at the source.
What it does
- Multi-point scanning identifies 57 failure points across SEO, performance, accessibility, and security.
- Source-level remediation applies fixes directly to your framework components rather than just the build output.
- Automated scoring generates a 0-100 readiness grade based on issue severity and frequency.
- Client-ready reporting translates technical findings into plain-language Markdown reports suitable for stakeholders.
- CI/CD integration provides a launch gate using exit codes to block deployments with critical issues.
How it works
- Target selection involves identifying the production URL and the build output folder or local preview server.
- Scan execution triggers a Python-based audit of rendered HTML to catch issues that static analysis misses.
- Issue triage categorizes findings by severity (Critical, High, Medium, Low) and filters intentional choices.
- Source fixing updates layout files, config objects, or public assets based on the framework detected.
Frameworks & tools
This skill supports Astro, Next.js, Vite/React, Nuxt, SvelteKit, Hugo, Jekyll, 11ty, and plain HTML. It also audits live production sites on WordPress, Webflow, and Shopify via URL.
Why this beats prompting it yourself
Writing a prompt to find SEO issues is easy, but verifying 57 specific technical rules across hundreds of files is impossible for a standard chat window. This tool uses a deterministic Python engine to ensure every single link, meta tag, and file reference is checked without the hallucinations or omissions common in manual reviews.
Use cases
- Auditing a site before a client handover to ensure professional standards.
- Fixing SEO and social preview tags across a large multi-page project.
- Catching staging environment settings that accidentally leaked into production.
- Implementing a final QA gate in a GitHub Actions deployment pipeline.
Known limitations
Folder scans are static and cannot verify server-side headers or HTTPS status. URL scans are required for security header validation. Alt text for images must be verified by the user.
Requires Python 3.8+. Folder scans miss security headers and HTTPS checks. Does not invent business facts (phone numbers, addresses) or legal content. 500 page limit by default.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 16 days ago
Requires
Permissions
Allowed Hosts