Build an enterprise website product catalog around categories, product records, detail templates and enquiry routes. As the catalog grows, develop specification filters around the questions customers actually ask. Decide which URLs serve search visitors and which preserve temporary selections, then accept the data, results, language versions and enquiry records together.
This guide serves manufacturers, equipment suppliers and technical service teams building product showcase and enquiry websites. It provides field examples, filter rules, URL policies and repeatable checks. CatchCMS supplies content models, dynamic fields, languages and forms. Public filter controls, parameter queries, combination URLs and their crawl policies require project implementation and acceptance.
1. Map three customer journeys
Ask sales and technical staff for recent selection questions. Organize them into finding documents by model, finding products by application, and narrowing a choice by specifications. For each journey, record the starting point, information customers compare and the next enquiry step before designing navigation.
- Main categories: Use stable product families or equipment types, such as Test Equipment → Pressure Test Equipment. Explain applications and differences alongside the product listing.
- Product details: Give each model a clear primary category, specifications, operating conditions, images, documents and an enquiry route. Application pages can link to the same record from several contexts.
- Selection filters: Start with connections, measurement ranges or installation types that customers ask about. Technical staff confirm options, and result cards display the information needed to judge them.
Separate model pages work when customers look up individual manuals and each model has distinct information. A series page with a comparison table can serve a small set of selectable differences. Each separate page needs meaningful model-specific content. Handle old URLs and internal links when addresses change; use the website redesign and migration checklist.
A showcase site covers presentation, selection and enquiries. Ordering, payments, inventory, orders and subscriptions each involve business processes. Confirm the systems, integrations and development scope for every requested workflow.
2. Design display specifications and filter data together
Use standard fields for names, introductions and covers, and project-specific dynamic fields for model identifiers, connections, ranges and document revisions. CatchCMS supports field types, options and validation rules; see Content Models and Dynamic Fields. Data entry, querying and theme display each need a working connection.
The table is a project design example. Keys, values and validation requirements illustrate a brief. Published specifications require confirmation against the company's approved materials.
| Information and example key | Agreement and acceptance focus |
|---|---|
| Model: model_code | Preserve the manufacturer identifier; agree uniqueness, case handling and model lookup. |
| Connection: connection_code | Store stable option codes, translate display labels and map synonymous input consistently. |
| Upper range: max_pressure_mpa | Agree numeric values, units and gauge or absolute pressure. Implement numeric comparisons in the project query. |
| Range description: range_text | Retain both bounds, units, conditions and limitations for technical and customer review. |
| Applications: applications | Record approved uses and restrictions, then decide whether they participate in filtering. |
| Documents: document_url / document_revision | Match the model, file language and revision, and open the actual download link. |
For example, “0–10 MPa, gauge pressure” includes values, units and conditions. Keep the display description and agree structured fields for numeric comparisons. Define whether a requirement means an upper limit of at least a given value or coverage of an entire interval before implementing it. Give missing values, explicit zero and “awaiting confirmation” separate meanings. Technical staff approve range rules, precision and conversions.
The official site's current content model serves articles and feature information, with fields for items such as price, badges, included features and structured-data type. A customer product model and the business fields above are project configuration. Where PIM or ERP already exists, agree the specification source, update owner and synchronization implementation. The CMS handles public customer-facing content.
3. Turn filter rules into testable requirements
Accept admin queries, public controls and customer-visible results separately. CatchCMS admin queries can filter dynamic fields marked as filterable by value. Current public content lists provide conditions such as category, tag and keyword. Specification ranges, within-group choices and public result pages require query and theme implementation.
- Define combinations: A visitor might choose G1/4 or NPT1/4 and require an upper range of at least 10 MPa. Specify any-match within a group and all-match across groups, then verify known records after implementation.
- Show state: Display active selections, result counts and units. Support removal of one condition and clearing all conditions, with readable labels and keyboard access.
- Define empty results: Retain selections, clearly show zero results and offer clearing or an enquiry about the requirements. Restricted combinations can be disabled with an explanation.
- Handle pagination: Start on page one after conditions change and preserve choices while paging. Check duplicates, missing records, totals and the final page after updates.
- Verify addresses: Agree whether reload, browser history and a copied URL restore selections. Preserve stable option codes when switching languages and handle page position as agreed.
Confirm that queries read only public, published products from the current site. Validate allowed fields, options, numeric bounds and page sizes on the server before querying. Repeat result and cache checks when options or source materials change.
4. Agree separate URL policies for categories and combinations
Assign a purpose, owner and acceptance rule to each URL class, then make theme, query and SEO output follow the same agreement. Options can multiply combinations rapidly. Google's faceted-navigation guidance covers their crawl management.
| URL purpose | Check at delivery |
|---|---|
| Long-term categories and individual models | Complete content, stable links, corresponding language URLs and self-referencing canonicals; sitemap inclusion follows publication rules. |
| Useful selection guides | Plan a small maintained set with a clear customer need, selection scope and useful content, then decide indexing and internal recommendations. |
| Temporary filters, sorting and combinations | Decide crawl and indexing policy for each class and list real parameters and test URLs. Implement precisely matched robots.txt rules for combinations selected for crawl restriction. |
For crawlable combinations, use standard parameter separators and stable ordering. Check duplicate conditions, invalid combinations, empty results and out-of-range pagination; Google recommends HTTP 404 for these invalid URLs. The error response can still display selections, clearing controls and an enquiry route.
A canonical expresses the preferred URL for duplicate or closely similar pages; see Google's canonical guidance. When choosing noindex, allow crawlers to access the page and read that instruction, as explained in Google's noindex guidance. Check status, robots.txt, noindex, canonical and sitemap separately.
CatchCMS provides page SEO and sitemaps; see SEO Features. Canonicals, language links, indexing and crawl rules for custom product filters and pagination require project integration and URL-by-URL acceptance. Record actual crawler and indexing observations using the post-launch search discovery checklist. Search performance and AI citations require measured evidence.
5. Verify results with three fictional products
This is a fully fictional requirements exercise. Assume three pressure-test products: PX-100 has G1/4 and a 6 MPa upper range; PX-200 has G1/4 and 10 MPa; PX-300 has NPT1/4 and 16 MPa. These values test query logic only. Real selection also requires pressure type, medium, temperature and technical confirmation.
- Select G1/4 alone: expect PX-100 and PX-200.
- Select G1/4 or NPT1/4 and an upper range of at least 10 MPa: expect PX-200 and PX-300.
- Select G1/4 and an upper range of at least 16 MPa: expect zero results, preserved choices and a clearing control.
- Remove the upper-range condition: expect the two G1/4 products. Clear all conditions: expect all three samples.
During project testing, temporarily use one result per page. Check preserved conditions on page two, a return to page one after changing conditions and the status beyond the final page. Copy the test URL into a fresh window and compare choices and results. Both languages use the same codes and values with the agreed localized labels. Add a sample with a missing parameter and check its inclusion and presentation against the agreed rules.
6. Maintain specifications, images and documents across languages
Model numbers, values, units, connection codes and document revisions establish product identity. Maintain localized names, descriptions, instructions and page summaries separately. CatchCMS supports site languages, translated bodies and enabled translatable dynamic fields; see the multilingual maintenance checklist. Missing translations follow base-value fallback rules, while explicit empty values follow field rules. Open the English page before release.
For a specification update, list its references in result cards, detail tables, filter options, manuals, translations and caches, then assign checks to owners. Label file links with language and revision using the document center guide. Preserve model detail and mobile loading quality using the product image checklist. Cross-site synchronization, translation approval and document revision workflows require project implementation.
7. Capture the model and requirements in enquiries
Choose fields around sales needs: model, quantity, operating environment, technical requirements, contact name and contact details. Empty results can offer an enquiry so customers can describe conditions for technical evaluation.
CatchCMS Custom Forms supports fields, validation, CAPTCHA, email notifications and submission lookup. Passing models or filter conditions automatically, CRM connections, sales assignment and automatic product selection require project development. Validate incoming models and conditions; handle contact details through the form and agreed privacy process.
Submit a clearly labeled test enquiry in an approved test environment. Check confirmation, the stored record, model and contact details, then the agreed mailbox and notification result. Record who reviews and follows up, and who clears test data. Production testing follows the responsible owner's approved scope.
8. Use a repeatable delivery checklist
- Data and display: Add a dedicated test product, change a specification, and check categories, details, filters and documents. Test empty optional fields and explicit zero.
- Filters and visibility: Use known samples for individual choices, multiple selections, intersections, boundaries, empty results, removal and clearing. Check isolation of drafts and other sites' data.
- URLs and pagination: Test reload, history, copied URLs, language switching, paging and out-of-range access. Compare conditions, totals, sorting and HTTP status.
- Public SEO: Check initial HTML product information, titles, descriptions, one H1, canonicals, language links, applicable structured data, robots and sitemap. Check core pages intended for search with scripts disabled.
- Mobile reading: Operate filters on a phone or narrow viewport. Check readable options, usable clearing controls, fitting tables and images, and reachable enquiry routes.
- Enquiries and maintenance: Verify approved test records and notifications. Use dedicated records to test unpublishing in lists and details. Assign owners for updates, caches, materials and follow-up checks.
Copyable acceptance record: time and tester; environment, language and URL; sample products and document revisions; input conditions, expected and actual models; page number and status; canonical/robots/noindex; reload and sharing results; mobile operation; enquiry record and mailbox evidence; defects, owners and retest date. Reuse the samples after theme or field-rule changes.
Frequently asked questions
Does a small catalog need complex filters immediately?
Start with stable categories, clear listings and details, model lookup and enquiries. Use actual selection questions involving repeated specification comparisons to define subsequent filtering dimensions and scope.
Does enabling admin field filtering enable public filters?
Admin filtering serves content management. Customer controls, public queries, combination rules and result URLs each need integration and acceptance as product-theme deliverables.
Should every filter combination become an SEO page?
Plan long-term categories, individual models and a small set of useful selection guides as acquisition pages. Configure crawl and indexing policies for temporary combinations according to their purpose, then check actual URLs.
How do a website CMS, PIM and ERP divide responsibilities?
The CMS manages public product content, pages and enquiries. PIM governs product information across channels; ERP handles business resources and processes. Agree sources, synchronization frequency and owners, then implement the required interfaces.
Prepare the project brief: Collect one product family, three approved public model records, common customer filtering questions, required languages and enquiry fields. Use CatchCMS project enquiries to confirm models, themes and development scope. Export projects can continue with product showcase and enquiry site selection; review licensing and updates in the source-code plans.