pre-publish-audit

Audits production website builds for SEO, accessibility, and security issues before publishing.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill pre-publish-audit-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-publish-audit
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/pre-publish-audit
Command: npx skills add https://github.com/timikalo7/Execute --skill pre-publish-audit-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Websites often go live with SEO, accessibility, and security mistakes that become expensive to fix after indexing and public exposure. This Skill enforces a mandatory pre-flight audit so nothing ships unaudited. ## Core Features & Use Cases - Gate orchestration: Runs existing quality gates first — visual-qa (WCAG AA accessibility, overflow, console errors), security-gate (secrets, TLS, dependencies), and system-design-gate (lockfile, env example, SQL interpolation) — as ship-blockers. - SEO / GEO audit: Applies the vendored claude-seo methodology covering technical SEO, on-page tags, Schema.org JSON-LD, sitemaps, E-E-A-T content signals, image optimization, and GEO/AEO readiness for AI answer engines. - Prioritized launch checklist: Writes findings into LAUNCH-CHECKLIST.md as blocking / should-fix / nice-to-have items and logs the pass in PROJECT-LOG.md. - Use Case: Before pointing a custom domain at a new marketing site, run this audit to catch a missing sitemap, a stray noindex tag, and absent OG images, fix the blocking items, then publish. ## Quick Start Run the pre-publish audit on my production build and give me the prioritized launch checklist before I deploy.

Frequently Asked Questions about pre-publish-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a website for SEO before publishing?

Build the production artifact first, then run accessibility, security, and system-design gates, followed by an SEO sweep covering crawlability, meta tags, Schema.org JSON-LD, sitemaps, and Core Web Vitals. Record findings as a prioritized blocking / should-fix / nice-to-have checklist and fix blockers before launch.

What should a website launch checklist include?

A launch checklist should cover technical SEO (robots.txt, canonical tags, no accidental noindex), one h1 per page, title and meta descriptions, valid Schema.org markup, sitemap.xml, image alt text, favicon, OG/Twitter cards, a 404 page, HTTPS, analytics, and no leftover placeholder content.

Does this audit run the claude-seo scripts and paid API extensions?

No. Only the markdown methodology and playbooks were vendored; installers, hooks, and Python extensions like DataForSEO and Ahrefs were excluded. Equivalent checks are done with WebFetch, crawl-site, browser-drive, visual-qa, and Lighthouse, and unverifiable items are reported as not-checked.

What is GEO or AEO optimization for AI answer engines?

GEO/AEO prepares a site so AI answer engines like ChatGPT, Perplexity, and AI Overviews can cite it. The audit checks for question-shaped answerable content, citable claims, clean semantic HTML, and an llms.txt file.

Why must the audit run against the production build instead of the dev server?

Dev servers hide issues that only appear in shipped output, such as minification errors, missing environment variables, and incorrect asset paths. Auditing the built artifact ensures the checks reflect exactly what users and crawlers will receive.