Pixie CRMHelp Centre
Sales & Marketing Hub · Feature guide

Publish landing pages, blog posts and knowledge articles with SEO metadata

Build useful public content, set its search title and description, and decide which published pages can appear in the module sitemap.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Hub → Marketing → Landing pages / Blog posts; Service → Knowledge articles

Permission

Manage content or service resources as applicable; independent Approve and Publish

Before you begin

Choose the content type that matches the task. Prepare a descriptive headline, a natural search-focused summary and working links before review.

Follow these steps

  1. Create the appropriate resource. Enter its headline, slug, search title, search description and body.
  2. Add optional call-to-action text and a valid destination. Use Open design studio for structured content when the resource offers it.
  3. Choose whether the page may be indexed. Leave indexing off for material intended only for a shared link.
  4. Preview the content, save it, obtain independent approval and publish. Open the generated public page and check the final address and links.
  5. If indexing is enabled, check the published page’s canonical address and its entry in the module’s public-content sitemap. Pause publication when withdrawing it.

Fields and options

Page identity
Lowercase, hyphen-separated slug up to 100 characters; headline and search title up to 160; search description up to 320.
Body and call to action
Plain body up to 50,000 characters, or supported structured design blocks. Optional call-to-action text is up to 80 characters with a valid URL.
Indexing
Indexing is off by default. Only published, indexable landing pages, blog posts and knowledge articles enter this module’s sitemap.

Rules and limits

  • The public canonical address includes the generated key and the saved slug. A slug alone does not create a standalone root-domain route.
  • Changing content requires pause, edit, independent review and publication again.
  • Indexing permission does not guarantee search-engine discovery, ranking or immediate removal from an external search cache.

Check the result

  • Check the public heading, metadata, mobile preview and call-to-action destination.
  • For an indexable page, verify its canonical URL is in the module sitemap; for a private-link page, verify noindex remains set.

If something does not look right

  • If a page returns unavailable, check its state and current revision rather than publishing an unrelated draft.
  • Replace placeholder or example.invalid links before attempting publication.

Common questions

Does a blog post publish immediately when saved?

No. A saved draft needs independent approval and explicit publication.

Will every form and survey appear in search?

No. Forms and surveys remain noindex/nofollow and are excluded from the indexable-content sitemap.