> ## Documentation Index
> Fetch the complete documentation index at: https://ownpay.org/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> OwnPay is licensed under AGPL-3.0 and is completely free - no licensing fees.
> Production docs URL: https://ownpay.org/docs - append .md to any page URL for clean markdown.
> OwnPay requires PHP 8.3+, MySQL/MariaDB, and Redis.
> MCP server available at https://ownpay.org/docs/mcp for programmatic documentation queries.
> Use root-relative links (e.g. /quickstart) for internal navigation - do NOT include /docs prefix.
> Plugin development: consult /developer/plugins/ pages for correct interfaces and manifests.
> Canonical locations: API auth = /api/authentication, webhook verification = /api/webhooks, rate limits = /resources/rate-limiting, transaction statuses = /fundamentals/payment-flow.
> The documentation uses the Diataxis framework: Tutorials (learning), How-to (tasks), Reference (lookup), Explanation (understanding).

# Landing page configuration

> How to configure the public landing page including hero section, feature cards, custom HTML, and SEO metadata in OwnPay.

The landing page is the public page visitors see when they go to your OwnPay root URL (for example `https://pay.example.com`). You can use it as a marketing page, a payment portal hub, or disable it entirely.

## Enable or disable the landing page

1. Go to **Appearance** → **Landing Page**.
2. Toggle **Enable Landing Page** on or off.
3. When disabled, visitors who go to the root URL are redirected to the admin login page.

## Set the page title and description

These fields control what appears in the browser tab and in search engine results:

| Field                | Purpose                                           |
| -------------------- | ------------------------------------------------- |
| **Page title**       | Browser tab text and `<title>` tag                |
| **Meta description** | 150–160 character summary shown in search results |
| **Meta keywords**    | Comma-separated keywords for SEO                  |

## Configure the hero section

The hero section is the large banner at the top of the landing page:

| Field               | Description                                         |
| ------------------- | --------------------------------------------------- |
| **Hero title**      | Main headline (for example "Fast, Secure Payments") |
| **Hero subtitle**   | Tagline below the title                             |
| **CTA button text** | Label for the call-to-action button                 |
| **CTA button URL**  | Where the button links to                           |

## Feature cards

You can add feature cards below the hero to highlight capabilities:

1. Click **+ Add Feature Card**.
2. Enter a title, description, and select an icon.
3. Repeat for each feature.
4. Click **Save Settings**.

## Custom HTML

For advanced customization, you can inject custom HTML into the landing page. Use this to add embedded videos, third-party widgets, or custom sections. The HTML is rendered inside the page body, so include your own styling via `<style>` tags if needed.

<Warning>
  Custom HTML runs in the visitor's browser. Do not include tracking scripts from untrusted sources, and avoid inline JavaScript that could conflict with the page's existing scripts.
</Warning>

## Admin login URL

The landing page settings also contain the **Admin Login URL Slug**. By default it is `login`, but you can change it to something unique (for example `my-secure-portal`) to obscure the admin login from automated bots. Only use lowercase letters, numbers, and hyphens.

## Related Pages

* [Branding](/docs/appearance/branding) - logos, colors, and favicons
* [Themes](/docs/appearance/themes) - checkout page themes
* [System settings](/docs/system/settings) - general site configuration
* [Domains](/docs/system/domains) - custom domain setup for landing pages


## Related topics

- [Checkout themes](/docs/appearance/themes.md)
- [Brand identity settings](/docs/appearance/branding.md)
- [Email Notifications](/docs/notifications/email.md)
- [Customer Experience](/docs/checkout/customer-experience.md)
- [Plugins](/docs/system/plugins.md)