The import updated inventory levels, but also replaced manually written titles—the titles shown in browser tabs—and meta descriptions—the brief descriptions of pages—with generic text. Fixing one product will not restore the other fields. First, find the column mapping rule and save a list of affected records, then verify the restoration in groups.
Which fields the import updates
Google may use the meta description to describe a search result, but it may also select page text based on the query. Official documentation.
An inventory import should not change the description if that field is not managed by the import source. But some templates automatically update every product column. Before restoring anything, record who updates each field: price and availability come from the inventory system, the editor sets the title, and an SEO plugin generates the fallback template. For each field, clarify what an empty cell means. It may mean “clear the field” or “do not update.” Without that agreement, running the import again could erase the restored text, even if the current manual edit looks correct.
Manual, template-generated, and empty meta tags
| Field after import | What changed | Where to fix it | What to compare with the product |
|---|---|---|---|
| Manual title | Editorial setting | Save or restore it | Not overwritten by the import |
| Template-generated title | Controlled by a generator | Check the input fields | Correct substitution |
| Empty description | It is unclear whether empty means “clear the field” | Agree on how to handle clearing | Predictable behavior |
| Inventory import | SEO is not its responsibility | Limit column mapping to the relevant fields | Only inventory levels change |
Check the column-to-field mapping
Compare the previous and current import settings with the file itself. For each column, check which content management system (CMS) field it updates. Check the change log for specific records if available. An SEO field may have been confused with the product name or a system column. In another case, the import cleared an optional brand field, and the general template changed the title based on it. These causes produce similar symptoms but require different fixes. Check database values through the designated interface and inspect the public HTML. Do not automatically treat an old cache as proof that the data was not restored.
Open the published product page and run this in the browser console to get the current meta tags:
({ title: document.title, description: document.querySelector('meta[name="description"]')?.content });Save the values before and after a safe test import. Prices and inventory levels change according to the input file; manual SEO fields excluded from the update remain unchanged.
Repeat the import on three test products
On a test group, repeat the same import that caused the change. Before running it, save the values of four fields and the product IDs. Afterward, compare the exact differences. Then fix the column-to-field mapping and repeat the test with the same input data. Inventory levels should update according to the file, while titles and descriptions excluded from the import should remain unchanged. Do not use the entire catalog for the first experiment. It is easier to check IDs and restore previous values for three products. After a successful test, process only the confirmed list of affected products.
Restore the necessary fields from a backup
If a backup exists, restore the specific affected fields for the specific products while keeping the new, correct inventory levels and prices. Restoring the entire database could undo other current changes. Match records by a stable identifier, not just by name. Keep a list of restored values and unresolved cases. Create a separate editorial task for any missing old text. If a title was always generated from a template for some products, restore its source and rule rather than turning the calculated value into a permanent manual field without agreement.
Protect them from the next run
Exclude protected SEO fields from the import, or configure them to update only when the incoming value is valid. Check how empty cells are handled and verify the identifier mapping. If the import runs on a schedule, apply changes to its actual configuration, not just to the tester’s manual screen. When adding a new product type, check again which fields the import is allowed to update. It is useful to keep a minimal test file with a manual, a template-generated, and an empty case. It tests the import boundary itself and avoids having to change the entire catalog again every time the CMS is updated.
Repeat the same file after the fix
The three test products retain their manual title/description, the template-generated one gets the correct data, and the empty cell is handled as configured. The restoration did not undo the new prices and inventory levels. The old text that could not be verified is marked as needing new editorial copy.
Also read: How to monitor changes to Title, meta robots, and canonical and Meta tags for SEO: a complete guide to optimizing titles and descriptions. Website checks are available on the reChecker technical audit page.