You changed the title template in the information block settings, but the product page still shows the old text. There are several possible reasons: the product has its own rule, a previously computed value remains in the database, or the public component is outputting a different source.
Clearing all caches without comparing these layers gives a random result. To make the fix clear and repeatable, first choose one product and trace the path from the SEO settings to the title in its published HTML.
How to choose a test product
Choose a product for which you can write down the expected title after the change in advance. Record the element ID, information block ID, section, and public URL. If it belongs to several sections, include those relationships: the inheritance source may affect how SEO data is computed.
Save the old and new information block templates, as well as the page's actual title. Record the change date and the version of the information blocks module alongside them. “The template isn't updating” is not precise enough: an individual setting may affect one product, while the page template's output may affect another.
Add a second product from the same section and one from a neighboring section. This sample helps distinguish an exception for a specific element from an information block-wide issue. Don't choose three identical product pages with the same manually set rule: they won't show how inheritance works.
A teaching example with a manual exception
Imagine a fan catalog. This is a fictional example. The general template was changed from “Product name — Store” to “Product name: specifications and price.” The model FAN-10 previously had the manually entered title “FAN-10 fan for a small workshop,” while FAN-20 uses the general rule.
After the change, FAN-20 gets the new text, while FAN-10 keeps its own value. This is not necessarily a cache error: a product-specific rule may intentionally differ from the information block template. The owner should decide whether to keep the exception or restore inheritance. The developer should not delete all individual titles just to get a uniform result.
For the third model, FAN-30, the field in the form already matches the new template, but the HTML is still old. This points the investigation to the next areas: computed values, the component, and the page cache. Record the reasons separately in the test table, even if the outward symptom is the same for all of them—the previous title.
Where to check for an individual SEO rule
Open Content → Information Blocks → Information Block Types → the required information block and its SEO tab. Then open the form for the specific section and product. Check whether the general value is being used or whether an override is enabled for that section or element. The official Bitrix course shows SEO templates and individual settings.
Compare the rule text, not just the preview next to the field. The template may contain substitutions for the section name and product properties. If a property used by the template is empty, the expected value will have a blank in its place; that is a different issue from a failure to update.
Before disabling an individual rule, save its contents. Find out why it was set: an important manual formulation, a temporary edit, or an accidental exception. Make the decision for the specific product, rather than applying it automatically to the entire catalog.
What the cache of computed values is
Bitrix stores the results of computing inherited properties. This is a separate data layer, not the finished HTML page in the cache. The API has, for example, the ElementValues. class. The name is useful to a developer, but the owner mainly needs to know at which step the old text remains.
When changing SEO settings, check the available “Clear computed values cache” option and save the form. Then check the result again for the test product. If templates are changed programmatically, the developer should separately check how the code updates data that has already been computed.
The ElementValues::clearValues method clears the entity's computed values from the database cache. It is not a command to delete individual templates, nor does it clear all the site's files. Use it for a verified object after checking the API version, not as an untested bulk operation across all information blocks.
How to distinguish computation from public output
The developer retrieves the actual computed SEO values for the test element and compares them with the expected text. The API provides BaseValues::getValues. for this. If the computed value is already new but the HTML is old, the next question is what outputs the title.
Check the component settings, the page template, and custom handlers. The title in the public document may have been set manually or replaced after the element data was retrieved. A correct API result does not confirm that the page uses it.
If the final title still contains a variable instead of a value, use the SEO template substitution check. To check a stale public document, follow the HTML cache instructions.
If the component uses the new value, compare the response when logged out with the response for an administrator. Then check the applicable component, page, and CDN caches. You don't need to clear the entire site before doing these checks: that can waste time and obscure the source that will return the old text again on the next update.
Make sure there is exactly one title in the HTML. A fix that adds a new title alongside the old one does not resolve the question of which source is being used. Also compare the H1: the visible heading and the title are separate values and should not be assumed to match.
What to check before making a bulk change
Include in the sample a product using the general template, one with an individual rule, one with an empty property, and one from a different section. If the catalog has trade offers, separately check which public URL and which element are used for output. Fixing the main product page does not prove that standalone offer pages are correct.
Write down the expected text for each case in advance. After the change, compare it with the computed value and public HTML. This allows you to keep a manual exception while changing the other products without contradiction: the task does not necessarily require every product page to follow the same pattern.
Repeat the check after the next scheduled import if it updates SEO fields. Otherwise, saving the product manually will fix it only until the next import. In the report, distinguish the confirmed manual result from the unverified outcome of the next data exchange run.
How to assign and accept the work
Give the developer the test IDs, URLs, old and new templates, selected manual exceptions, and expected strings. Ask them to show which layer was fixed: inheritance, computed values, component output, or the public page cache.
Accept the work based on the final HTML values and preserved exceptions, then check neighboring cases. For a large set of published pages, a technical site audit may be suitable; other catalog tasks are covered in the blog. A changed title in the HTML is a verified configuration result. This check cannot predict when a search engine will update its search result title or what text it will choose.