Skip to content

Page

Puts a single WordPress page into your navigation — an about page, community rules, a contact page.

PluginNone. WordPress core
Endpoint groupContent
PlanEvery plan
  1. Drag Page onto a navigation bar, usually the side drawer.
  2. Choose the page.
  3. Set a Title.
SettingWhat it doesDefault
PageWhich WordPress page to renderNone — you must choose one
Page titleWhether to show the page’s own titleOn
Title, DescriptionThe tab label and screen headingEmpty
RestrictionsWhich roles see the tabEveryone

The page’s content, rendered natively rather than in a webview. Links inside it route to the app’s own screens where they can: a link to a post opens Single Post, a link to a member opens their profile.

A WordPress page opened inside the app shell

Three features can show a page. They are not the same thing.

PageWebview PageCustom Link
Drawn byThe appYour siteYour site
Page-builder layoutLostKeptKept
Site header and footerNot applicableHiddenShown
Matches your app’s designYesNo, it matches your websiteNo
SpeedFasterA web page loadA web page load
Best forText your app should own the look ofPages where the design is the pointAnything not on your own site

Use Page for plain content — rules, a contact page, an about page — where matching your app matters more than matching your website.

Use Webview Page when the page was designed: an Elementor landing page, a layout with columns, anything that needs the scripts and styles your site registered for it.

Use Custom Link for a page that is not on your own site.

SymptomCauseFix
The screen is emptyThe Content group is offEnable it
The page picker is emptyThe Content group is off, or there are no published pagesEnable it, and publish a page
Content looks unstyledNative rendering ignores your theme’s CSSUse Webview Page if the styling matters
A shortcode shows as raw textNative rendering does not run every plugin shortcodeUse Webview Page for that page
A form on the page does not workIt needs your site’s scriptsUse Webview Page