AdPages Build Audit for Netlify

Netlify Build Plugin scaffold for lightweight static landing-page QA.

The plugin runs after a Netlify build, walks the generated publish directory, inspects .html files, and prints a local summary for common paid-traffic and local SEO readiness signals:

• <title> quality
• meta description
• H1 presence
• obvious CTA links, buttons, forms, phone, or email links
• common analytics/conversion tracking markers
• JSON-LD or schema.org structured-data markers
• canonical URL
• responsive viewport tag

It does not fetch URLs, call third-party APIs, execute browser JavaScript, inject backlinks, or send page contents anywhere.

Status

This is a distribution-ready scaffold, not a submitted Netlify integration.

Before publishing:

• replace placeholder repository, support, author, and package ownership metadata;
• add a real license file and changelog;
• test in at least one deployed Netlify site using netlify build;
• decide whether the package should remain a Build Plugin or move to a newer Netlify SDK extension surface later.

Local Usage

From a Netlify site repository, add the plugin as a local plugin:

[[plugins]]
package = "./integrations/netlify/adpages-build-plugin"

  [plugins.inputs]
  failOn = "never"
  maxPages = "50"
  reportPath = "adpages-build-audit.json"

For an npm-published version, install the package and use the package name:

[[plugins]]
package = "netlify-plugin-adpages-build-audit"

  [plugins.inputs]
  failOn = "error"

Inputs

| Input | Default | Description | | --- | --- | --- | | publishDir | constants.PUBLISH_DIR | Optional publish directory override. | | maxPages | 50 | Maximum number of HTML files to inspect. | | reportPath | adpages-build-audit.json | JSON report path relative to the site base directory. Use an empty value to skip writing a report. | | failOn | never | Build failure mode: never, error, or warning. | | ignoredDirs | built-in static asset folders | Comma-separated directory names to skip while walking the publish directory. |

Local Smoke Test

npm --prefix integrations/netlify/adpages-build-plugin run check
npm --prefix integrations/netlify/adpages-build-plugin run smoke

The smoke test scans examples/site and writes examples/reports/adpages-build-audit.json.

Output

Build logs include a concise summary:

AdPages Build Audit
Publish directory: /site/dist
HTML files scanned: 4/4
Checks: 25 passed, 5 warnings, 2 errors
Pages needing attention:
- pricing/index.html: cta: No obvious CTA signal found.

The JSON report contains per-page fields, detected signal examples, checks, recommendations, and rollup totals.

Limitations

• Static HTML only. Client-rendered titles, schema, CTAs, and tracking must already exist in generated HTML.
• Tracking detection is marker-based and does not prove analytics delivery or conversion firing.
• Schema detection reports JSON-LD and schema.org markers, but does not validate schema.org compliance.
• The plugin is intentionally local-first and dependency-free; richer browser or URL crawling belongs in a future explicit adapter.