Content pages

A store needs more than products: policies Shoppers can trust, answers to common questions, a way to get in touch, and stories worth reading. The storefront gives each of these a designed page, while your team keeps writing in the WordPress editor it already knows.

Where it shows

/returns-refunds, /shipping-policy, /privacy-policy, /terms-and-conditions, /cookies-policy, /faq, /contact-us, /about-us, /find-a-store, /blog

Configure in

StoreFront › Settings › Pages (Contact, FAQ, Static Pages) and Header/Footer Scripts; Posts in WordPress

Requires

WooCommerce mode and the Companion plugin; Contact Form 7 for the contact form

Try it in Demo Mode

Every page renders, with seeded policies and seven Journal posts

What shoppers get

• Policy pages for returns and refunds, shipping, privacy, terms and cookies, styled to match the store.
• An FAQ with questions grouped into sections and answers in accordions.
• A Contact Us page with your address, support email, phone (tap to call or email) and opening hours beside a validated contact form.
• About Us and Find a Store pages that tell your story and show where to find you.
• A Journal: your WordPress blog, redesigned for reading and browsing.

Policy pages

Write each policy as an ordinary WordPress page in the block editor, then pick which page serves which policy. The storefront pulls the page’s content, title, excerpt and SEO through the Port and styles the blocks itself; there is no copy kept on the storefront. A policy with no published page returns a 404, and its links disappear from the header and footer, so Shoppers never hit a dead end.

Privacy and Terms are the same settings as WordPress’s Privacy page and WooCommerce’s Terms page: changing either place updates both.

FAQ and Contact

FAQ. Add sections, each with an optional title, and fill them with questions and short rich-text answers (bold, italic, lists and links). The storefront shows exactly what is saved.

Contact page. Set the headings, intro lines, address, support email, phone and a day-by-day opening schedule. Blank text fields fall back to the storefront’s own wording, so a half-filled tab still gives a complete page. The form delivers each message through a Contact Form 7 form you pick, using that form’s mail settings, and can require Name, Phone and Message (Email is always required). Cloudflare Turnstile can guard the form against spam.

Contact Entries inbox. Every message that passes Contact Form 7’s checks is also saved under StoreFront›Contact Entries, even if the notification email fails. Triage it like an inbox: unread counts on the menu, Unread, Starred and Trash views, search, date and form filters, Reply by email, and Export CSV. Trashed entries are deleted after 30 days.

About Us and Find a Store

These pages are typed configuration in the storefront codebase rather than wp-admin settings. About Us covers a hero, founder story, mission, values, team and a timeline. Find a Store shows store cards with hours, phone and a map link, beside an OpenStreetMap view.

Configured per deployment

Both pages ship with placeholder content, and Find a Store’s locations and map position are sample data. Whoever deploys the storefront replaces them for each store; see Store identity.

Journal

The Journal at /blog turns your WordPress posts into an editorial section. The index leads with a featured post, then cards with a search box, category chips, tag and month filters, sorting (latest or oldest first) and pagination, plus a newsletter block. Each article shows reading time, author and tags, share buttons for Facebook, Pinterest and X, previous and next links, and related posts. Threaded comments sit at the foot of the article; posting a comment requires signing in. Write and publish posts in Posts in wp-admin as usual.

Custom scripts

Paste Google Tag Manager, Meta Pixel, a consent tool, site-verification tags or a chat widget into three boxes: Head, Body start and Footer. The storefront injects them on every page and sends page views to the data layer and Meta Pixel on each client-side navigation, so you don’t need a History Change trigger in Tag Manager. Scripts never load on the checkout or order confirmation pages, which keeps the payment pages under the storefront’s control.

Set it up

• Policy pages, FAQ and Contact: StoreFront›Settings›Pages. See Pages and content.
• Custom scripts: StoreFront›Settings›Header/Footer Scripts. See Scripts and promo popup.
• About and Find a Store: Store identity.

Good to know

• Contact Form 7 is required for the form. Without it, the Contact page shows a notice in place of the form and no entries are recorded.
• Saving scripts needs the unfiltered_html capability, which multisite site admins and sites with DISALLOW_UNFILTERED_HTML don’t have. Scripts are stored exactly as pasted, so only use code from services you trust.
• Turn scripts off away from production. Set STOREFRONT_CUSTOM_SCRIPTS=off on staging, preview and local deployments so they don’t send test traffic to your analytics.
• Languages. Policy pages can differ per language, but adding a language to that list is a developer setting today, not an admin control.
• FAQ limits. Up to 20 sections and 50 questions per section.

Related

Pages and contentSet up policies, FAQ and the contact page.

SEOHow policy pages and articles describe themselves to search engines.

Marketing toolsNewsletter, promo popup and share buttons.

Customers and engagementWork the Contact Entries inbox.