You can publish Pageflow stories under your own domain. That way permalink URLs of your stories can use your own domain instead of the default *.pageflow.io domain.
In the following steps, we will assume that you are the owner of the domain mydomain.com and wish to publish Pageflow stories under story.mydomain.com. Given there is an entry called my-story in your account named my-account, you want it to be available via
https://story.mydomain.com/my-story
instead of the default permalink:
https://my-account.pageflow.io/my-story
DNS Configuration
You need to make changes to the DNS configuration of your domain. To see the required DNS records, sign in to your Pageflow account, visit the Settings page and enter the desired domain.
Two DNS records need to be created:
- A CNAME record for your domain with the value domains.pageflow.io. This record instructs your DNS server to point browsers visiting story.mydomain.com to the Pageflow server.
- A TXT record with an account specific token. Before associating a domain with an account, Pageflow verifies domain ownership by making sure that the token in the value of the verification record matches the account's verification code.
The DNS configuration itself takes place outside of Pageflow. The exact details of the process depend on the tools you are using to manage your domain. Consult the documentation of your DNS management tool for detailed instructions.
Once the DNS records are in place, click "Save". Your Pageflow stories will now be accessible via your domain. Note that stories must have already been published to be publicly accessible.
Configuring Your Homepage
Now that your stories are available via your domain
https://story.mydomain.com/my-story
you might be wondering what people see when they visit the root path of your domain:
You have two options:
Option 1: Use a story as your homepage – You can select one of your published stories to serve as your homepage. When visitors go to the root path of your domain, they'll see your selected story directly. This is often the best choice if you want to create a dedicated landing page or showcase a specific story.
For detailed instructions, see our guide on how to use a story as your homepage.
Option 2: Set up a Redirect URL – Alternatively, you can configure a redirect URL that sends visitors to an external website when they visit the root path of your domain. By default, this redirects to https://pageflow.io, but you can customize this by entering any URL in the Redirect URL field on the Settings page.
You can redirect to any URL you like, for example:
-
Your main website (e.g., http://mydomain.com) if you want to send visitors to your primary site
-
A custom landing page that lists all your Pageflow stories (note that this content would need to be hosted on a separate server)
-
The permalink of a specific Pageflow story (though using the homepage story option above is generally preferable for this use case)
Using Domains without a Subdomain
If you want to make your Pageflow stories available via URLs of the form:
Pageflow does not directly support apex domains (domains without a subdomain) due to technical DNS limitations. However, you can set up a redirect from your bare domain to a subdomain version that works with Pageflow. The easiest approach is to redirect to a www subdomain and configure Pageflow to use that.
Step 1: Set up Pageflow with your www subdomain (e.g., www.mydomain.com) following the DNS configuration instructions above.
Step 2: Configure a redirect from your bare domain to the www version. You can use specialized redirect services like:
-
https://redirect.pizza - Simple redirect setup for apex domains
-
https://redirection.io - Advanced redirect management service
These services will handle the technical requirements for redirecting your bare domain (mydomain.com) to your www subdomain (www.mydomain.com), where your Pageflow stories will be hosted. This way, your visitors can still start at your root domain, while you maintain a technically supported and reliable setup for serving your Pageflow stories.