Skip to content

Vertical Landing Pages Redesign

Date: 2026-02-25 Status: Approved

Problem

Current vertical landing pages are inconsistent in quality: - Fintech page (725 lines) is fully built out but doesn't match main site polish - HealthTech (42 lines) and Industrial (47 lines) are bare stubs without header/footer, SEO metadata, or FAQ schema - No consistent template across verticals - Strategic docs call for more verticals than currently exist

Decision

Build 8 vertical landing pages using a single consistent template, covering a wider SEO surface area while being honest about SQUR's capabilities.

Verticals

  1. B2B SaaS (/verticals/saas.html)
  2. Fintech (/verticals/fintech.html) - rebuild from current
  3. HealthTech (/verticals/healthtech.html) - rebuild from stub
  4. E-Commerce (/verticals/ecommerce.html) - new
  5. Industrial / DeepTech (/verticals/industrial.html) - rebuild from stub
  6. Legal Tech (/verticals/legaltech.html) - new
  7. Startups (/verticals/startups.html) - new
  8. Government / Public Sector (/verticals/government.html) - new

Template Structure

Every page follows this identical section structure:

1. Head (SEO)

  • Title: "Autonomous Pentesting for [Vertical] | SQUR"
  • Meta description: industry-specific
  • OG tags, Twitter cards
  • Canonical URL
  • FAQ JSON-LD schema
  • Keywords meta tag

2. Shared Header

  • Via includes/header.html and loadIncludes()

3. Hero Section

  • H1: "Autonomous Pentesting for [Vertical]"
  • Subtitle: 1-2 lines of industry-specific pain point
  • Dual CTA: [Start Pentest] [Book a Demo]
  • Uses main site's hero styling patterns

4. Industry Challenges (3 cards)

  • Heading: "Why [Vertical] Companies Need Autonomous Pentesting"
  • 3 cards, each with icon + title + 2-line description
  • Frames industry-specific security challenges

5. How SQUR Helps (3-4 value props)

  • Reframes SQUR's core capabilities for the vertical:
  • Speed (24h vs weeks)
  • Compliance-supporting reports
  • No security expertise needed
  • Cost-effective continuous testing
  • Each with icon + title + description

6. Compliance Section

  • Heading: "Security Testing for [Industry] Standards"
  • Grid of relevant compliance framework cards
  • CRITICAL: Honest framing only:
  • "Supports the security testing component of [framework]"
  • Cite specific articles/sections where known (e.g., DORA Art. 24)
  • Never claim "achieve compliance with SQUR"
  • SQUR provides pentest evidence, not full compliance

7. Stats Banner

  • Shared across all verticals (same data):
  • 24h Full Pentest
  • 87.5% CTF Benchmark Score
  • AI-Verified Findings
  • Retest Included

8. FAQ Section (5-6 questions)

  • Industry-specific questions
  • JSON-LD FAQ schema for SEO rich snippets
  • Questions address: regulatory fit, speed, expertise requirements, what SQUR tests, report formats

9. CTA Section

  • "Secure Your [Vertical] Platform Today"
  • Dual CTA: [Start Pentest] [Book a Demo]
  • Via includes/footer.html
  • Footer includes "Verticals" column linking all 8 pages

Content Per Vertical

B2B SaaS

  • Subtitle: "Ship faster without security bottlenecks"
  • Pain points: Vendor security questionnaires, customer trust, audit readiness
  • Compliance: SOC 2 / ISO 27001 — pentesting reports customers and auditors ask for
  • Value props: Speed (24h), CI/CD-friendly, developer-friendly reports

Fintech

  • Subtitle: "Security testing that keeps pace with your release cycles"
  • Pain points: Regulatory pressure, fast release cycles, API-heavy architectures
  • Compliance: DORA Article 24 specifically; PCI DSS and BaFin as contexts (not claiming full compliance)
  • Value props: API testing, 24h turnaround, retest after fixes

HealthTech

  • Subtitle: "Protect patient data with continuous security validation"
  • Pain points: Patient data exposure, GDPR pressure, API-first platforms
  • Compliance: GDPR Art. 32 (testing effectiveness of security measures)
  • Value props: PII protection testing, API security, evidence-based reports

E-Commerce

  • Subtitle: "Don't let security slow down your next launch"
  • Pain points: Payment data, customer trust, seasonal peaks
  • Compliance: PCI DSS testing requirements (as context); GDPR for customer data
  • Value props: Payment flow testing, pre-launch validation, 24h results

Industrial / DeepTech

  • Subtitle: "Secure the web interfaces protecting your IP"
  • Pain points: Connected systems exposure, IP theft, supply chain risks
  • Compliance: NIS2 security testing requirements; ISO 27001 Annex A
  • Value props: API security, web portal testing, partner validation
  • Subtitle: "Security your clients expect from their legal partners"
  • Pain points: Client confidentiality, professional obligations, trust
  • Compliance: GDPR (client data); professional due diligence
  • Value props: Confidential data testing, client trust evidence, professional credibility

Startups

  • Subtitle: "Investor-grade security without a security team"
  • Pain points: Due diligence requirements, resource constraints, SOC 2 pressure
  • Compliance: "The pentest report investors and enterprise customers ask for"
  • Value props: No expertise needed, 80% cost reduction, fast turnaround before funding

Government / Public Sector

  • Subtitle: "Meet public sector security standards with autonomous testing"
  • Pain points: BSI requirements, procurement standards, data sovereignty
  • Compliance: BSI IT-Grundschutz, NIS2, EU data residency
  • Value props: EU-hosted, data sovereignty, evidence-based reports, German company

Compliance Honesty Principles

  1. SQUR does autonomous pentesting of web applications and APIs only — not infrastructure, networks, mobile apps, or IoT
  2. Say "supports the security testing component" not "achieves compliance"
  3. Cite specific articles/sections where known; use general language elsewhere
  4. No customer logos per vertical (don't have them yet) — use universal stats
  5. Never imply industry-specific product features that don't exist

Technical Implementation

  • Static HTML pages (consistent with existing architecture)
  • Shared styles-verticals.css for all vertical-specific CSS
  • Shared header/footer via existing loadIncludes() mechanism
  • All pages listed in sitemap-main.xml with priority 0.8
  • Footer updated with "Verticals" column listing all 8 pages

SEO Strategy

  • Visible links in footer (best for internal linking / page authority)
  • Each page targets "[vertical] pentesting" and "[vertical] security testing" keywords
  • FAQ schema for rich snippet eligibility
  • Canonical URLs to prevent duplicate content
  • Industry-specific meta descriptions and keywords

Git Strategy

  • First: merge/rebase to incorporate remote's existing vertical commits
  • Then: implement the redesign on top
? SQUR