Commercial Landing Variants

PR #37, Add commercial landing page variants, adds a first set of commercial entry pages for Adaptation & Action Explorer. The goal is to make the product easier to discover through intent-led searches such as climate risk data for banks, city climate risk intelligence, infrastructure resilience research, insurance adaptation signals, and adaptation project pipeline discovery.

This is an acquisition and positioning layer on top of the existing public explorer. It does not create a separate product experience or paywall. Each page routes visitors toward the live location explorer while framing the same CDP disclosure data for a specific commercial audience.

Preview Links

Page	Audience	Preview
Climate risk data for banks and lenders	Banks, lenders, credit, and risk teams	Open preview
City climate risk intelligence for partnership teams	City resilience and partnership teams	Open preview
Adaptation project pipeline intelligence	Investors and project origination teams	Open preview
Climate adaptation intelligence for insurance teams	Insurance and reinsurance teams	Open preview
Climate resilience intelligence for infrastructure investors	Infrastructure investors	Open preview
Local climate intelligence for advisors and consultants	Climate advisors and consultants	Open preview

The generated preview sitemap is available at sitemap.xml.

What Changed

The PR adds a shared Angular commercial landing component backed by a JSON page configuration. Routes are explicitly registered for /solutions/... and /industries/..., which keeps the first batch small and intentional while still making it easy to add more commercial variants later.

The build now also runs frontend/scripts/generate-commercial-pages.mjs after the Angular build. That script writes static index.html files for each commercial route, injects page-specific titles, meta descriptions, canonical links, Open Graph/Twitter tags, JSON-LD, and static fallback content, then generates a sitemap. This matters because crawlers get meaningful HTML before Angular hydrates.

The footer now links to the primary “Climate risk data” route, giving the new commercial section at least one internal discovery path from the app shell.

Page Intent

Variant	Why it exists
Banks and lenders	Positions CDP data as a starting point for portfolio screening, market climate exposure review, and financing-signal discovery.
City climate risk intelligence	Frames the explorer for partnership and resilience teams looking for local hazard, action, and peer-learning evidence.
Adaptation project pipeline	Focuses on projects seeking funding and related local hazard context for origination or pipeline research.
Insurance	Makes the value legible for insurance and reinsurance market research, resilience engagement, and local hazard context.
Infrastructure investors	Connects climate hazard, public action, and project signals to infrastructure investment research.
Climate consultants	Helps advisors quickly explain how CDP public disclosure data can support local climate-adaptation research.

Verification

Manual preview checks confirmed all six page URLs and the generated sitemap return 200. Two deployed pages were also spot-checked for page title, meta description, canonical URL, H1, and JSON-LD.

Local verification run before the PR included:

npm run build
npm run commercial:generate
npm run test:ci -- --include='src/app/features/commercial-landing/commercial-landing.spec.ts'
npm run test:ci
npm run check:i18n
git diff --check

Review Notes

Review the live preview pages for whether the commercial framing feels credible and specific enough for each audience. The implementation is intentionally conservative: it reuses existing CDP styling, avoids making unverified data-coverage promises, and sends visitors back to the live explorer or CDP contact page.

Before merging, check the current PR status in GitHub because the preview deployment and CI run independently:

gh pr checks 37

Proposed Commercial Enhancements

1. Add a stronger commercial conversion path, such as a “Request a walkthrough” or “Discuss data access” CTA that can route to CDP partnerships or commercial intake instead of only the generic contact page.
2. Add PostHog tracking for commercial_landing_viewed, CTA clicks, related-page clicks, and explorer handoff clicks, with page_key, audience, route, and UTM properties.
3. Build internal links from high-intent jurisdiction pages into the relevant commercial page, for example projects seeking funding linking toward the adaptation project pipeline page.
4. Add lightweight proof points once approved, such as disclosure coverage counts, example use cases, or short evidence notes tied to the public dataset.
5. Create a small editorial keyword map before adding more routes so future PSEO pages do not become thin duplicates.
6. Add a commercial dashboard that joins page visits, search terms, CTA clicks, explorer handoffs, and high-intent actions inside the product.

Source Files

Key implementation files in PR #37:

• frontend/src/app/features/commercial-landing/commercial-landing-pages.json
• frontend/src/app/features/commercial-landing/commercial-landing.ts
• frontend/src/app/features/commercial-landing/commercial-landing.html
• frontend/scripts/generate-commercial-pages.mjs
• frontend/src/app/app.routes.ts
• frontend/public/robots.txt
• .github/workflows/frontend-preview.yml
• .github/workflows/deploy.yml