FlourivateHelp Center

Page settings: search title, private pages, code and cookie banner

Last reviewed October 21, 2026

Set how a page appears in Google, keep private pages out of search, add tracking code, and turn on a cookie banner.

Each page has its own settings for search, style and tracking. Your website also has a Code tab for scripts that run on every page.

Before you start

  • Time: 5 minutes per page.
  • Where: open the page in the builder, then click ⋯ (top right) > All Page Settings. The panel has three tabs: SEO & AI, Style and Tracking. It shows Autosave Ready, so changes save as you make them.

Set the search title and description

  1. On SEO & AI, under Content, write the Title. This is the blue link people see in Google. Keep it under 60 characters; the counter helps. Put what you do first, then your name, like "Leadership Coaching for New Managers | Jane Rivera".
  2. Scroll down and write the description: one or two sentences, about 150 characters, saying who the page is for and what they'll get.
  3. Check URL path. Keep it short and readable, like /coaching.
  4. The Preview Snippet at the top shows roughly how the page may look in search.

For more on search, see Help your website get found in search.

Use this for pages only clients should find: a paid booking page, a client resources page, a thank-you page.

  1. Open Tracking.
  2. Under Search Engine Indexing, tick Hide from search engines. This adds "noindex, nofollow" to the published page.
  3. Also keep the page out of your site menu, and don't link to it from public pages.

Hidden isn't locked

Hiding a page from search doesn't password-protect it. Anyone with the link can open it. Don't put anything on it you'd mind being shared.

Preview links are always hidden from search engines, whatever this setting says.

Set the page background and fonts

Style has Background Color, Page Background Image, and a Typography section with Body Font, Heading Font and Base Font Size. These apply to this page only. See Set your page fonts, colors and animations.

If you use tracking (like a Meta pixel or Google Analytics), privacy rules in many places expect a cookie notice. For most practices, the easiest route is the workspace-wide banner in Settings: see Set up your cookie banner and handle data requests. Each page also has its own banner setting, useful when one page needs different wording:

  1. Open Tracking and switch Cookie Consent on.
  2. On General, choose a Compliance type:
    • Ask to opt in: visitors choose whether to allow cookies. Expected in the UK and EU.
    • Don't ask: visitors are only told you use cookies.
  3. Edit the button text (Accept essential, Accept all, Customize) and the Message description so it sounds like you.
  4. Add Link to your own policy so the banner links to your privacy policy page.
  5. Use Layout and Cookie List to adjust the look and list your cookies.

Add tracking code or a script

Where you paste code decides where it runs.

Paste it in It runs on
Website Code tab: Head Tracking Code, Body Tracking Code, Footer Code, Analytics Tracking Code Every page of that website
Builder ⋯ > Tracking Code This page only
Builder ⋯ > Custom CSS Style tweaks for this page only
Funnel Settings (head and body tracking code) and Events (tracking pixels) That funnel

To reach the website Code tab: Sites > the website's ⋯ > Settings > Code.

Only paste code from a source you trust, such as Google or Meta. Blog post pages don't run your website's custom code.

Check it worked

  • Open the live page in a private window. The cookie banner appears if you turned it on.
  • The Preview Snippet shows your new title and description.

If something's off

  • A page vanished from Google: check that Hide from search engines isn't ticked by mistake. Untick it and keep the page published.
  • A script only belongs on one page but runs everywhere: move it from the website Code tab to that page's Tracking Code.
  • Typography in the ⋯ menu won't load: use All Page Settings > Style instead.
  • Your changes aren't on the live page: see My live page doesn't match the editor.