Skip to app details
Back to app library
APPNEURAL APP FAMILYMarketing & Branding

Landing Pages

Turn campaign ideas into landing pages

Build branded landing pages with lead forms, versions, and A/B tests.

01 / OVERVIEW

See where it fits in your day.

Pages are built from 17 block types: hero, features, benefits, testimonials, pricing, FAQ, call to action, lead form, countdown, logo strip, image, video and rich text, plus blocks that embed a Forms form, a Meetings booking page, a Payments button or a Coupons offer. Blocks are reordered, duplicated and hidden with a live desktop and phone preview, undo and autosave. 24 templates (lead magnet, webinar, product launch, coming soon, offer, ebook, event, app download, service, thank-you and more) start in the domain's brand. Pages publish at page.<domain>/p/<slug> as server-rendered HTML with title, description, Open Graph tags and a noindex option; every publish is a version that can be restored. Lead forms store leads with UTM tags and referrer, email the team, fire a lead.created webhook, push to Contacts when connected, export as CSV and redirect to a thank-you page. Up to four A/B variants split the traffic, with views, visitors and conversion rate per variant and bots filtered out. Claude writes a page from a brief, rewrites a block and suggests headlines. pages.appneural.com holds every domain; page.<domain> holds one domain's pages and leads.

A LOOK INSIDEExample layout · sample content
A landing page with clear purpose
T
ContentWorkshop registration
Product introduction
Service enquiry
02 / CAPABILITIES

Built around the work you do.

What Landing Pages does for you.

01

Page building

Create landing pages from blocks and templates.

02

Brand and forms

Style pages for the domain and include lead forms.

03

Versions and tests

Work with page versions and A/B tests.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Landing Pages. What you can do depends on your access in the app.

01

Choose a starting point

Select blocks or a template for the campaign.

02

Shape the page

Review brand styling, content, and the lead form.

03

Review versions

Compare the page versions or A/B choices.

YOUR NEXT MOVE

Make Landing Pages part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE80 items
P2PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Pages are built from 17 block types: hero, features, benefits, testimonials, pricing, FAQ, call to action, lead form, countdown, logo strip, image, video and rich text, plus blocks that embed a Forms form, a Meetings booking page, a Payments button or a Coupons offer. Blocks are reordered, duplicated and hidden with a live desktop and phone preview, undo and autosave. 24 templates (lead magnet, webinar, product launch, coming soon, offer, ebook, event, app download, service, thank-you and more) start in the domain's brand. Pages publish at page.<domain>/p/<slug> as server-rendered HTML with title, description, Open Graph tags and a noindex option; every publish is a version that can be restored. Lead forms store leads with UTM tags and referrer, email the team, fire a lead.created webhook, push to Contacts when connected, export as CSV and redirect to a thank-you page. Up to four A/B variants split the traffic, with views, visitors and conversion rate per variant and bots filtered out. Claude writes a page from a brief, rewrites a block and suggests headlines. pages.appneural.com holds every domain; page.<domain> holds one domain's pages and leads.

Landing pages for a connected domain built from blocks and templates in its brand, published at page.<domain>/p/<slug> with versions, lead forms and A/B variants.

Forms, booking, pay links and offers are embedded from Forms, Meetings, Payments and Coupons; leads become people in Contacts; site traffic belongs to Analytics.

Priority
P2
Portfolio
Marketing & Branding
Capability
Marketing & Branding
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T05:19:09.962Z
Semantic inventory

Every number says what it counts

80Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

landing schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

pages.appneural.com DEPLOYED

pages.appneural.com

Worker
landing-catalog
Health
HEALTHY
Last deployment
2026-11-08 10:24:36
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

Repository provider is not connected. Existing references remain unverified.

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is partially verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app