Search is no longer just about ranking pages. These FAQs cover SEO, AI, AEO, schema, answer readiness, and the practical choices that help your content become easier for people and search systems to understand.
Still can’t find what you are looking for? Try ChatGPT.
When SW FAQs Simple pulls FAQ rows from HubDB, it can also render related post links from the related posts field when that field is populated.
The changelog notes that recent versions use a dot separator between related post titles instead of commas. This makes FAQ answers with multiple related links easier to scan.
The SW Open Graph partial is a theme file included from the theme header. It adds Open Graph metadata such as og:type and a share image when the theme can resolve one from the page, the first post on a blog listing, or the theme’s default featured image setting.
The changelog notes that blog listing pages can use the first post on that listing for the preview image when the listing page does not have its own featured image. A site-wide fallback can be set in Theme settings → Content → Misc → Featured image.
The SW BlogPosting Schema partial is used on blog posts only. It adds a JSON-LD description from each post’s Meta description when HubSpot’s native BlogPosting output does not include one.
The changelog notes that FAQs on posts stay in the post body through SW FAQs Simple, not in a fixed template slot. Fill the post Meta description and republish after the theme update when this partial is part of the implementation.
When using an AI agent to help with SW Modules, give it the official documentation sources first so it does not guess from memory.
Use a prompt like this:
You are helping me with Smithworks (SW) HubSpot modules in a Sprocket Rocket-style theme.
Rules:
- Browsable FAQs: https://smithworks.marketing/faqs — use for module Q&A, HubDB hub setup, pagination, and topic tags (additional grounding alongside AI docs).
- Developer docs hub: https://docs.smithworks.marketing/ — changelogs, module index, alias risk.
- Exact field paths: https://smithworks.marketing/sw-module-documentation — do not invent module names or field paths.
- Sprocket Rocket (SR) modules: https://docs.sprocketrocket.co/ — not covered by SW docs.
- Ask which SW module I am editing if unclear. Use Content vs Style tab paths exactly as documented.
- If something is not documented, say so.
This prompt is especially useful before module selection, field troubleshooting, or FAQ hub / HubDB setup questions.
SW FAQs Advanced HubDB renders a crawlable FAQ hub from one HubDB table: a hub index (category links + optional hub-wide search) and category pages (full FAQ lists with filters, pagination, and “On this page” TOC).
Typical URLs (when configured with path-style category links):
/faqs/faqs/{category-slug} (slug derived from HubDB category text)It replaces the older inline-repeater SW FAQs Advanced module (deprecated—do not use for new pages). Content always comes from HubDB, not from repeater fields in the module.
AI agents: Use smithworks.marketing/faqs for hub behavior Q&A; use SW Module Documentation for exact field paths.
| Need | Use |
|---|---|
| FAQ block on one blog post or landing page | SW FAQs Simple |
| Same FAQ row on a post and in a central hub | One HubDB row in a shared table; Simple on the post, Advanced on the hub |
| Browse-by-category FAQ site section | SW FAQs Advanced HubDB |
| Accordion with changing side image | SW Pillar Accordion or SW Magic Accordion — not FAQ hub modules |
One HubDB table can serve both modules if rows include the full column set for the hub (see FAQ 098).
name, question, answerpage_paths and/or group_keyrelated_posts_urlscategory — display name; drives nav label and URL slugcategory_order — order of categories in sidebarsort_order — order of questions within a categorylong_answer — required for Long Answer or Short + Read More modessubtopic — comma-separated topic tags (API name; HubDB label may say “Subtopic”)page_paths — optional; first /blog/… path powers “Appears in blog post” linkrelated_posts_urls — optional related blog links on hubRows without category are skipped on the hub. Do not rename column API keys without updating module HubL and migrating data.
The module alone does not fix pagination canonicals. HubSpot’s default canonical strips ?page=, which would treat page 2+ as duplicates of page 1.
Required theme steps (every portal):
sw-faq-pagination-canonical.html to [theme]/sw-partials/templates/header.html before HubSpot's standard header includes output/faqs, update the partial’s _faq_url_segment portal constant to match/faqs/{category}?page=2 canonical must include ?page=2 (first link rel="canonical" in HTML)Also required: CMS pages matching Category Link Style; XML sitemap URLs for each paginated page when pagination is enabled.
Module upload + roll-down checklist: see Smithworks implementation docs for FAQ hub theme setup (not repeated here as repo paths).
In the module Content tab, Hub Page Mode tells the module which layout to render:
/faqs)./faqs/websites).Set HubDB Category Name to match the HubDB category column exactly when the URL does not supply the slug. Renaming a category in HubDB changes the generated slug for path-style links—update CMS pages and redirects.
Separate page (path) (default in current master):
category/faqs/websites; pagination ?page=2sw-faq-pagination-canonical.html (path-based detection)Same page (query):
/faqs with ?category=websitesMust match how your site is actually published. Mismatch causes 404s or wrong category content.
No FAQs match your search in SEO, AI & AEO.
