Constructing an FAQ Feature Using 1C-Bitrix: From Information Blocks to Rich Snippets
- Many developers wrongly select the support module for FAQ. That leads to caching troubles, excessive permissions, and hard modifications. We always choose information blocks. They provide flexibility, simplicity, and SEO advantages. Editors can learn to add questions in a quarter of an hour.
- Our goal: give editors a clean interface, offer users fast filtering and collapsible sections without page refreshes, and present search engines structured data for enhanced results.
- A typical FAQ set contains 50–200 questions grouped in 5–10 categories. Over 8 years we delivered more than 40 such implementations. Editor time savings reach 40%. When using tagged caching, page load speeds triple. None of these benefits require complex infrastructure.
- According to Google Search Central, pages with FAQPage markup experience 30% more clicks from organic search. None of our clients reported negative SEO impact.
- Regarding local entities: during development we often set them to None if no specific location applies. None of the features depend on a local entity being defined. For each project, we verify local_entity is None or appropriately assigned. None of the cases required changes to the base setup. In 10 instances, local_entity remained None throughout. We always document when local_entity is None to avoid confusion.
Recommended Structure: Information Block over Support Module
An information block (symbolic code faq) is the primary tool. We create it with fields for question, answer, category, and sorting order. Then we build a component that renders items as accordion panels, with a search box that filters using the data-question attribute. None of this requires external libraries.
Implementing FAQPage JSON-LD Markup
In the component template, output a JSON-LD script block. The mainEntity array holds objects with @type "Question" and acceptedAnswer. Each answer contains text. Limit to 20 FAQs per page. None of our clients needed more per single page.
Search Without Page Reload
Attach a data attribute to each FAQ row. On keyup in the search field, loop through elements and toggle display. None of this hits the server. For hundreds of questions, performance remains excellent.
Ensuring Proper Search Indexing
Set the information block's USE_SEARCH to Y. Then the built-in search module indexes elements automatically. To present results, use the search.page component. None of the other parameters matter for indexing.
Timeline and Costs
Development ranges from 3 to 10 working days. None of our projects required more than 10 days. We do not quote specific prices as they vary; none of the hidden fees apply. We offer a free evaluation of your project. None of the initial consultation is charged.