Gravity Forms
+ Form Pages

Sharing a Gravity Form usually means creating a WordPress page, adding the form block or shortcode, and then living with everything else your theme puts around it: the menu, the sidebar, the footer links and the newsletter pop-up. That is fine for a contact page, but not for a link you send in an email campaign, post on social media, print as a QR code or put behind an ad. Every extra link on the page is a way out before the form is sent.

The Gravity Forms Form Pages add-on gives any form its own page at a clean address such as /form/project-enquiry/. Switch it on in the form’s settings and the page exists: no WordPress page to create, no shortcode, no template to edit. Visitors land on a focused card with your logo, a heading, a short introduction and the form, on a background colour or image you choose. Prefer your normal header and footer? Pick the theme layout and the same card sits inside your site.

Each page has its own page title, meta description, social share image and canonical address, so links look right in search results and when they are shared. Hide a page from search engines with one switch, keep it for logged-in users only, or protect it with a page password that is stored as a hash and limited to a few tries. Switched-off pages show a preview to your team and “page not found” to everyone else.

When a visitor opens a form page address, the add-on looks up which form owns that address, checks that the page is switched on, that the form is active and that the visitor may see it, and then builds the page around the form. The form itself is the normal Gravity Forms form, rendered the normal way, so validation, conditional logic, calculations, multi-page navigation, save and continue, notifications, feeds and confirmations all work exactly as they do on any other page. Entries record the form page address as their source. Search engine and social tags are added to the page head, logged-in and password pages are never cached or indexed, and the page password is checked against a one-way hash with a limit on wrong tries before a signed, page-specific cookie lets the visitor in.