Landing Pages

Landing pages are identified by a unique path: if a landing page and a redirect are both defined for the same path, the redirect will take priority.

While most other entities use UUIDs as the primary key, landing pages are uniquely identified by their path. Because these paths can contain slashes, we append the path as a URL query parameter when making API calls (instead of the typical REST convention used elsewhere wherein the identifier is embedded in the URL structure itself).

All landing pages are defined as an Experiment. The conversion event for all landing page experiments is when an individual signs up and a new account is created.

HTML Header

The HTML Header attributes will appear in the section of all versions of the landing page.

Attributes:

Name	Type	Description
title	string	The value of the `title` tag -- will also be replicated in `og:title`.
canonical_url	uri	Will be used to supply `<link rel="canonical">` tag. If not set, it will default to the full URL given the path of the landing page. This can be useful when you have public landing pages that are widely the same and you want to consolidate link equity for SEO purposes. `og:url` will always be the full URL of the landing page (given its path). The canonical URL is only used in the link tag defined above to give you more control over SEO.
description	string	The value of the `<meta name="description">` tag -- will also be replicated in `og:description`.
keywords	string	The value of the `<meta name="keywords">` tag.
social_image	uri	The URL to the image that will be used in `og:image:url`.
prevent_indexing	boolean	If this page should be suppressed from search indexes. If set to `true`, the `X-Robots-Tag` header will be set with a value of `noindex` and the `<meta name="robots" content="noindex">` tag will also be added to the `<head>` section of all landing page versions. Furthermore, if `true`, this page will be excluded in the auto-generated Sitemap. By default, landing pages are indexable (meaning `prevent_indexing` is set to false). The reasoning for this is outlined in our commitment to backwards compatibility