AdPages Deployment Audit for Vercel

Local-first Vercel build-step scaffold for static AdPages and local-service landing pages.

The command scans generated HTML after a build and reports common paid-traffic and local SEO deployment risks before the deployment goes live:

• title, meta description, responsive viewport, H1, and canonical signals;
• CTA, phone, email, form, and service-area signals;
• JSON-LD, schema.org, and LocalBusiness markers;
• common analytics and conversion tracking markers;
• placeholder, localhost, preview-domain, and example.com leaks;
• missing local static asset references.

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

Status

This is a distribution-ready scaffold, not a submitted Vercel Marketplace native product.

Useful near-term publication paths:

• npm package used from a Vercel buildCommand;
• Vercel docs/tutorial snippet for local-service deployment QA;
• GitHub template example for static landing pages;
• future Vercel Marketplace native product if a provider server is intentionally added.

Local Usage

npm --prefix integrations/vercel/adpages-deployment-audit run check
npm --prefix integrations/vercel/adpages-deployment-audit run smoke

Run the CLI against a generated static site:

node integrations/vercel/adpages-deployment-audit/bin/adpages-vercel-audit.mjs \
  --scan-path dist \
  --report-path adpages-vercel-deployment-audit.json \
  --fail-on never

Vercel Build Usage

After publishing the package, install it in a static-site project and add a build audit script:

{
  "scripts": {
    "build": "astro build",
    "adpages:vercel-audit": "adpages-vercel-audit --scan-path dist --report-path adpages-vercel-deployment-audit.json --fail-on error",
    "vercel-build": "npm run build && npm run adpages:vercel-audit"
  },
  "devDependencies": {
    "@adpages/vercel-deployment-audit": "0.1.0"
  }
}

Then configure Vercel to run the combined build step:

{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "buildCommand": "npm run vercel-build",
  "outputDirectory": "dist"
}

The included examples/vercel.json mirrors Vercel's file-based project configuration model, where buildCommand and outputDirectory can be defined in the repository.

CLI Options

| Option | Default | Description | | --- | --- | --- | | --scan-path | dist | Static output directory or one HTML file to inspect. | | --report-path | adpages-vercel-deployment-audit.json | JSON report path. Pass an empty value to skip writing a report. | | --fail-on | never | Build failure mode: never, error, or warning. | | --max-pages | 50 | Maximum number of HTML files to inspect. | | --format | text | Console output format: text or json. |

Marketplace Notes

The marketplace/product-metadata.schema.json file is a draft configuration schema for a future native Vercel Marketplace product.

It is intentionally not enough to publish a native product by itself. Vercel native products currently require an approved provider setup and a provider integration server with a Base URL. That is a deliberate blocker for this scaffold because the current artifact avoids hosted backend assumptions.

Privacy

See PRIVACY.md. In short: this tool reads local build files, reads a small allowlist of public Vercel build metadata environment variables when present, and writes a local report. It does not require secrets.

Publish Blockers

• Choose final package ownership, public repository URL, support URL, and license file.
• Test inside at least one real Vercel project using vercel build.
• Decide whether JSON reports should be persisted as build artifacts, ignored, or copied into deployment output.
• Add screenshots/docs page before template or marketplace promotion.
• For native Vercel Marketplace publication, add and audit a provider integration server, Base URL, terms, privacy URL, billing stance, and review submission path.