Do not make a quotation-only page look like an immediate offer

Product markup can describe information to search engines, but it should not turn a quotation-only catalog into a fictional immediate purchase offer. The visible page and the data need to agree.

Identify the actual route

A Czech business may publish product information while reviewing each request before providing commercial terms. That page should clearly explain its inquiry process. Adding a made-up price, availability claim or review rating to fill structured-data fields would misrepresent the offer.

Use confirmed facts

The product owner approves identifiers, descriptions, imagery and any current commercial information. A developer can implement appropriate markup only after those facts and the supported page type are understood.

Check syntax and eligibility separately

Valid JSON does not establish that a page qualifies for a particular search feature. A testing tool can identify technical issues while the underlying content and provider rules still require review. Appearance in search is not guaranteed.

Review a representative page

Compare the displayed product, inquiry action and parsed structured data. Remove unsupported claims rather than treating them as harmless hidden fields.

Google's product structured-data documentation is the primary reference for its own requirements. We can include the visible-content and markup review in search work and catalog development.