ohayo.
← All skills

OHAYO / SKILL 002

Check the build.
Then release.

Catch conflicting SEO signals before they reach your website. A small, offline release check with file evidence and a clear fix list.

Claude Code & CodexPython 3.10+v1.0.0
REAL EXAMPLE OUTPUT↗

Hold: 3 conflicting release signals.

Canonical: index.html:3 points to the staging origin.

Indexing: private/index.html:3 contains noindex, yet appears in sitemap.xml.

Missing route: sitemap.xml lists /missing/, with no matching HTML file.

Read the worked example →

A CHECK YOU CAN REPEAT

From build files
to a fix list.

  1. Point at your static build

    Supply the HTML output directory and intended HTTPS origin. Your files stay on your computer; the checker makes no network requests.

  2. Find conflicting signals

    Review sitemap targets, canonical URLs, noindex directives, missing metadata and duplicate titles. Findings include file evidence.

  3. Fix, rebuild, verify

    Use the skill and report template to propose source changes, rerun the check and record the live checks still needed.

Know what it checks.

Who is this for?

Developers and small-site owners shipping static HTML builds who want a repeatable SEO check before publishing. The CLI runs independently; an AI assistant is optional.

What build layouts are supported?

Root and directory index.html routes, .html/.htm file routes, UTF-8 files and one sitemap.xml URL set. Maximum 1,000 HTML files, 2 MiB each and 64 MiB total. Sitemap indexes, HTML base elements, symlinks and custom router rewrites are unsupported.

Does a pass guarantee indexing or ranking?

No. It checks local markup. Live HTTP status, redirects, response headers, robots.txt, JavaScript rendering and Search Console inspection remain separate checks. A passing report does not predict traffic.

How is this different from Landing Page Audit?

This package checks SEO release consistency across a build and its sitemap. Landing Page Audit reviews a single page’s messaging, conversion friction and basic HTML signals.

Can I use it for client work?

One purchaser may use and modify it across personal and client projects and share generated reports. Reselling or publicly redistributing the package is not included. Future major versions and consulting are separate.

What happens after payment?

Once the verified payment notification arrives, the correct versioned ZIP appears in My library. Sign in with the same Google account to download it again.

START WITH ONE PAGE

Try the free Meta Tag Checker.

Paste HTML for a quick local metadata review. The paid package adds checks across your build and sitemap.

Open the free checker →