Documentation

Connect SerionFlow, publish pages, and understand what happens next.

Use this guide when you are setting up programmatic SEO pages through Vercel, Cloudflare, or Custom DNS. WordPress and Shopify integrations are coming soon, and Railway and Netlify flows are planned; send your hosting platform through Contact if you need a route we do not support yet.

Default route

yourdomain.com/explore

Most projects serve SerionFlow pages from a base path like /explore. Your main site stays in place.

The simple flow

SerionFlow does not replace your website. It adds SEO pages under your own domain, usually under /explore, then keeps those pages measurable through a generated sitemap, Google Search Console, and Bing on Pro or Agency.

You control

You create a project, choose Vercel, Cloudflare, or Custom DNS, review generated drafts, publish selected pages, and connect Search Console or Bing when you want real performance data. If you use another host, request that setup from Contact.

SerionFlow handles

SerionFlow prepares routing, generates review drafts, serves live pages through your selected route, maintains the generated sitemap, and recommends weekly improvements.

1Create a project for your website and let SerionFlow scan the site, sitemap, brand context, market opportunities, and SerionFlow-suggested page ideas.
2Choose a routing method: Vercel if the site is hosted on Vercel, Cloudflare if the domain DNS is managed through Cloudflare, or Custom DNS to point a domain or subdomain straight at SerionFlow with one CNAME record.
3For Railway, Netlify, or other manual setup needs, send the host through Contact so we can provide the right route as those flows are added.
4Generate your launch batch or weekly page drafts, preview them in Serion Studio, then publish only the pages you want live.
5Submit the generated SerionFlow sitemap in Google Search Console so Google can discover live generated pages.
6On Pro or Agency, connect Bing to add Bing discovery, IndexNow-supported submission, and AI-related query signals.
7Use the weekly flywheel to review new opportunities and improvement recommendations from real search data.

Cloudflare setup

Use Cloudflare when the domain is active in Cloudflare DNS. SerionFlow uses a scoped API token with both account-level and domain-level permissions to create the Worker and route only your SerionFlow path.

Before you start

The domain must appear as Active in Cloudflare, and the DNS record serving the site must be Proxied (orange cloud), not DNS only. Worker routes do not run on grey-cloud DNS-only records.

What you do not need to create

You do not need to manually create the Worker or Worker routes. After the token is saved, SerionFlow creates or updates them for the project.

Account-level token policy

In Cloudflare's token builder, choose your Cloudflare account as the resource, then add Workers Scripts: Edit. This permission is account-level, so it may not appear while you are scoped to a specific domain or zone.

Domain-level token policy

Add a second policy for the specific zone/domain SerionFlow will manage. Choose the zone, then add Zone: Read, DNS: Read, and Workers Routes: Edit.

1Open Cloudflare and confirm the project domain appears under Domains with an Active status.
2Go to Manage account, then Account API Tokens, then click Create Token.
3Choose Custom token and give it a clear name, such as SerionFlow.
4Create the first permission policy at the account level. Select your Cloudflare account, then add Workers Scripts: Edit.
5Click Add policy and create the second permission policy at the domain or zone level. Select the specific zone SerionFlow should manage, then add Zone: Read, DNS: Read, and Workers Routes: Edit.
6Review the token summary and confirm it includes both policies: one for account-level Workers Scripts access and one for domain-level zone, DNS, and Worker routes access.
7Create the token and copy it immediately. Cloudflare only shows the full token once.
8In Cloudflare DNS, confirm the record for the exact hostname, such as yourdomain.com or www.yourdomain.com, is set to Proxied (orange cloud). Leave MX, TXT, DKIM, SPF, and DMARC records as DNS only.
9In SerionFlow, open the project Integration tab, paste the token into the Cloudflare card, and save it.
10Click Deploy Cloudflare route. SerionFlow finds the zone, uploads or updates the Worker, and creates routes for the base path, usually /explore and /explore/*.
11Click Verify connection after deployment. If Cloudflare is still propagating, wait a moment and verify again.

If you cannot find Workers Scripts

Check the policy resource dropdown. If it is set to a specific domain or zone, Cloudflare will only show zone-level permissions. Switch that policy to the account level, select your Cloudflare account, then search for Workers Scripts again.

Recommended token scope

Keep the token scoped to only the Cloudflare account and the specific zone SerionFlow needs. Avoid using broad all-zone access unless you intentionally want SerionFlow to manage multiple zones.

Expected Cloudflare result

A live visit to https://yourdomain.com/explore should reach SerionFlow content through the Worker route. It should not redirect to Heroku, show a Cloudflare Worker error, or return your main app 404 page.

Custom DNS setup

Use Custom DNS when you do not host on Vercel and do not manage DNS through Cloudflare, or when you simply want the fastest setup. You point a domain or subdomain straight at the SerionFlow edge with one DNS record, and SerionFlow serves your generated pages on that host. No proxy code, no redeploys, and no platform account to connect.

Best for

A dedicated subdomain (for example explore.yourdomain.com) or a domain you want fully served by SerionFlow. The whole host is served by SerionFlow, so it does not change an existing site that lives on the same hostname.

When to use Vercel or Cloudflare instead

If you need SerionFlow pages on a sub-path of your existing main site (for example yourdomain.com/explore) while the rest of that domain keeps serving your current site, use the Vercel or Cloudflare flow instead. DNS routes a whole host, not a single path.

1In SerionFlow, open the project, go to Integration, and in Launch routing choose Use custom DNS. You can also choose your own subdomain label , for example learn, resources, or esports , instead of the default seo.
2SerionFlow shows one DNS record to create: the Type (CNAME for a subdomain), the Name/Host, and the Value pointing at the SerionFlow edge.
3Open your domain registrar or DNS provider and add that exact record. Important: set the Proxy status to DNS only (grey cloud, not orange). A proxied record will prevent verification from passing.
4Save the record. DNS usually propagates within 1-3 minutes but can occasionally take longer depending on your provider and TTL setting. This is normal , just wait a moment before verifying.
5Back in SerionFlow, click Verify DNS. SerionFlow confirms the record resolves to our edge and that the live route responds. If it says DNS is still pending, wait another minute and try again.
6Once verified, publish your pages and submit the generated sitemap in Search Console as usual.

How SerionFlow verifies

SerionFlow resolves your hostname and checks that it points at the SerionFlow edge target shown in the record, then loads the health route on your domain. Because you pointed DNS at SerionFlow, the DNS ownership itself authorizes serving pages for that host , there is no token to paste.

If verification stays pending

The most common reasons are: the record Proxy status was set to Proxied (orange cloud) instead of DNS only, the record has not fully propagated yet (wait 1-3 minutes and try again), or the Name/Value do not match exactly what SerionFlow shows. Fix any of those, then click Verify DNS again.

Expected Custom DNS result

A live visit to your configured host (for example https://explore.yourdomain.com) reaches SerionFlow content directly, along with /robots.txt and /sitemap.xml for that host.

Troubleshooting checklist

Start here when routing is connected but the live URL is not working yet.

Vercel route still pending

Merge the setup PR if one was created, wait for the production deployment to finish, then verify the live route again.

Vercel cannot find the project

Connect the Vercel account or team that owns the production project, and confirm the project domain is added under Vercel Project Settings > Domains.

GitHub setup PR cannot open

Confirm the SerionFlow GitHub App is installed on the exact repository, not just the GitHub account. If repository access is set to selected repos, add this repo and re-approve the installation.

GitHub app can read but cannot create a branch

Grant Contents: Read and write and Pull requests: Read and write, then reinstall or re-approve SerionFlow for the repository. Check repo rulesets if branch creation is still blocked.

GitHub or Vercel popup was blocked

Open GitHub or Vercel directly, finish the install or merge the setup PR from there, wait for Vercel to redeploy production, then return to SerionFlow and verify the route.

Cloudflare token rejected

Create a new scoped token and confirm it has both policies: account-level Workers Scripts: Edit, plus domain-level Zone: Read, DNS: Read, and Workers Routes: Edit.

Cloudflare cannot find the domain

Add the project domain as an active site in the connected Cloudflare account first. If the domain belongs to another Cloudflare account, create and save a token from that account.

Cloudflare deploy returns 422

SerionFlow could not create the Worker route. Check that the domain zone exists in Cloudflare, the token has the required account and zone permissions, and another hosting provider is not already connected for this project.

Site is hosted on Vercel but not using Cloudflare DNS

Use the Vercel setup flow instead of Cloudflare. Cloudflare Worker routing requires the domain to be active in Cloudflare and routed through Cloudflare DNS.

Cannot find Workers Scripts in Cloudflare

Workers Scripts is an account-level permission. Change the token policy resource from the specific domain or zone to your Cloudflare account, then search again.

Cloudflare live URL shows your main app, an empty app shell, or a 404

Confirm the exact hostname record is Proxied (orange cloud), not DNS only. Then confirm SerionFlow deployed routes for both the base path and wildcard path.

Custom DNS verification stays pending

The most common fix: check that the record Proxy status is set to DNS only (grey cloud), not Proxied. A proxied record blocks verification. Also confirm the Type, Name, and Value match exactly, then wait 1-3 minutes for propagation and click Verify DNS again.

Custom DNS apex domain will not accept a CNAME

Many registrars block CNAME at the root domain. Use an ALIAS/ANAME record to the SerionFlow edge target, the provided A record, or point a dedicated subdomain such as explore.yourdomain.com instead.

Sitemap has no URLs

Only live pages appear in the generated sitemap. Publish at least one page, regenerate the sitemap, then check again.

Google account does not show the site

Connect the Google account that owns or has access to the matching Search Console property. If the property is missing, add and verify the domain in Google Search Console first.

Google property does not match the project domain

Choose the Search Console property for the same live domain users visit. A property for another brand, staging site, or old domain cannot submit this project sitemap correctly.

Google has not indexed pages yet

Use URL Inspection for priority URLs and continue monitoring Search Console.

Bing account does not show the site

Connect the Microsoft account that owns the matching Bing Webmaster Tools site. If Bing returns verified sites but none match this project domain, add and verify this site in Bing Webmaster Tools first.

Bing data is empty

Confirm the project is Pro or Agency, Bing is connected, the site URL matches the routed domain, and enough time has passed for Bing Webmaster Tools to return performance data.

Contact support

Connect SerionFlow, publish pages, and understand what happens next.

The simple flow

Vercel setup

Cloudflare setup

Custom DNS setup

Pages, publishing, and sitemap behavior

Google Search Console and Bing

Troubleshooting checklist