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.
Filtered URLs (?q=, ?tags=) canonicalize to the clean category URL without filter params
While visitors search or filter tags, pagination and TOC hide; results search the whole category (lazy-loaded index from the hub page).
HubSpot may output two canonical tags on page 2+; treat the first (from the theme partial) as authoritative.
How do topic tags (HubDB subtopic) work on the FAQ hub?
Each FAQ row can list tags in subtopic:
Comma separates tags: HubSpot, Websites = two tags
HubSpot Websites without a comma = one tag
On category pages (not the index):
Sidebar Topic tag filter with OR/AND
Clickable tags on each FAQ (above related posts)
When any tag filter is active, FAQs with no tags are hidden
Pagination and “On this page” TOC hide during filter/search
Many tags (>8 default): panel can start collapsed with “Find a topic…”
How does FAQ search work on the hub?
Hub index: empty search shows category browse; with ?q= shows cross-category results (can respect ?category= on the index URL).
Category page: search runs across all FAQs in the category, not only the current paginated page. The module fetches the hub index JSON from the hub base path (e.g. /faqs) on first search or tag filter—preload on search focus.
Search all FAQs links to /faqs?q=… (and can pass category context). Combining ?q=, ?tags=, and ?page=: active search/tags reset pagination in the UI.
What does “Appears in blog post” use in HubDB?
When Show Appears In Blog Post Link is on, the module scans page_paths for a blog URL. That path should be where the FAQ is embedded with SW FAQs Simple.
Turn the toggle off for hub-only sites with no blog embedding. If no blog path exists, no link shows—expected behavior.
Do not confuse with Related Posts, which uses related_posts_urls for “other posts that address this question.”
What are Answer Display Mode options on the FAQ hub?
Choose under Content → Answer Display Mode:
Short Answer — hub shows HubDB answer only
Long Answer — hub shows long_answer (populate column in HubDB)
Short Answer + Read More — visible short text plus expandable long body; customize button labels in module fields
FAQPage schema on each paginated page reflects visible Q&A on that page only.
Should I enable Output FAQPage Schema on the hub?
Keep Output FAQPage Schema on for most hub implementations. Schema must match visible content—do not enable for hidden or filtered-away rows on that URL.
With pagination, each URL’s schema includes only the FAQs shown on that page (e.g. 10 per page), which aligns with Google’s expectation for paginated FAQ content.
This is FAQPage schema, not QAPage or other types.
How do I set up CMS pages for the FAQ hub?
Typical path-style setup:
Create hub index page at /faqs (or your base path). Module: FAQ Hub Index.
For each HubDB category value, create a CMS page whose URL slug matches the auto-generated slug (from category text).
On each category page: module FAQ Category Page; set HubDB Category Name if the URL cannot supply the slug.
HubDB table ID in module → HubDB Settings.
Complete theme partial + header merge and canonical verification.
Add paginated URLs to sitemap when pagination is on.
Dedicated “FAQ Hub Index/Category” templates are optional; general page + module mode is the supported pattern.
