build-source-grounded-landing-pages

name

build-source-grounded-landing-pages

description

Build or refactor one focused, source-grounded landing page from interviews, chats, documents, posts, images, videos, and verified links. Use when a person or small business needs one conversion page with honest copy, one primary CTA, basic SEO and AEO, RTL support when relevant, media consent controls, policy utility pages, and end-to-end verification. Do not use for a multi-page authority website, content hub, blog, or separate service architecture.

Build Source-Grounded Landing Pages

Build one persuasive page from evidence. Keep one business goal, one primary audience, and one primary CTA. Treat the supplied sources as the factual boundary.

Required workflow

1. Read the project instructions, objective, existing files, and supplied source material.
2. Copy the templates in assets/ into the project workspace. Do not edit the skill originals.
3. Read references/workflow.md and follow its gates in order.
4. Create the facts ledger before drafting. Record facts, unknowns, contradictions, media permissions, source locations, and publication authority.
5. Ask only when a missing answer would materially change the public page. Omit unsupported claims instead of guessing.
6. Define one conversion goal and one primary CTA. Keep secondary actions subordinate.
7. Build one main index.html page with anchored sections. Policy and accessibility pages are utility pages, not additional marketing pages.
8. Write in the owner's voice. Avoid detached third-person wording and repetitive paragraphs beginning with I or אני.
9. Use media only according to recorded permission. A CSS crop never protects a sensitive original.
10. Apply the SEO and AEO checks in references/aeo-and-authority.md.
11. Run scripts/audit-static-site.mjs and complete the browser checks in references/verification.md.
12. Publish only with explicit authority. After publication, verify the live URL, metadata, links, assets, policy pages, and contact action.

Landing-page contract

The deliverable contains one marketing page. Use sections such as:

• hero with a specific promise and primary CTA;
• audience or problem;
• approach, offer, or solution;
• verified owner or business context;
• process or next steps;
• proof only when a real source supports it;
• useful FAQ with direct answers;
• contact or conversion section;
• footer with appropriate policy links.

Allow separate utility routes for privacy, accessibility, and terms when the page is intended for public business use. Do not add an about route, service routes, a knowledge hub, article routes, or category pages.

If the user needs those elements, state that the request has become a full website project and stop expanding the landing page into a disguised site.

Non-negotiable rules

• Publish only claims traceable to a source or explicit approval.
• Preserve contradictions until an authorized source resolves them.
• Do not invent testimonials, credentials, results, client counts, experience, pricing, availability, locations, or endorsements.
• Do not import claims from an external profile without confirming identity and resolving conflicts.
• Do not publish exact private addresses or sensitive details without explicit consent.
• Do not ship sensitive originals when only a crop is allowed. Create a real derivative and keep the original out of the publish folder.
• Do not claim that a crop guarantees ad-platform approval.
• Do not inflate SEO or AEO scores. Cite visible or machine-readable evidence for every awarded point.
• Do not promise rankings, indexing, answer-engine mentions, leads, or sales.
• Do not deploy, send, submit forms, or contact third parties without the required authority.

Scope boundary

This free workflow is intentionally narrow. It does not build:

• a multi-page corporate or authority website;
• separate pages for services, categories, audiences, or locations;
• a blog, knowledge center, guide library, or media library;
• advanced editorial workflows or content migration;
• a full legal-compliance program;
• custom backend systems, accounts, payments, or dashboards.

Recommend a full authority-website engagement when the business needs multiple independent discovery paths, substantial content, stronger topical authority, or separate legal and operational architecture.

Static audit

Run:

node scripts/audit-static-site.mjs <landing-page-directory-or-index-file> --hebrew

For a public build:

node scripts/audit-static-site.mjs <landing-page-directory-or-index-file> --hebrew --public-url https://example.com

Use --max-first-person-rate 15 to set the maximum percentage of visible content fragments that may begin with אני. Treat the number as a signal, then read the page aloud.

The audit cannot verify factual truth, visual quality, identity, consent, legal adequacy, or live conversions. Complete the manual checks.

Resource routing

• Read references/workflow.md before discovery or drafting.
• Read references/aeo-and-authority.md before scoring or adding structured data.
• Read references/verification.md before browser testing or publication.
• Copy and complete the templates in assets/ for each project.

Completion standard

Finish only when:

• every public claim maps to evidence or explicit approval;
• the page serves one audience and one conversion goal;
• every navigation anchor opens an existing section;
• the primary CTA works and remains visually dominant;
• media follows recorded permission;
• policy links required by the project's context exist and work;
• automated checks pass;
• desktop and mobile browser checks pass;
• live HTTP and conversion-path checks pass after publication;
• the final report names remaining uncertainty and limits.