Remove doubled product information that confuses Google

Paid versionAppearance & deployments

Google gets one clear set of product information again, which protects your prices and stars in search results.

What it replaces: 2-3 h of developer debugging

What you write to Claude

„Product pages send Google the product information twice (two Product JSON-LD blocks). Find which one comes from the theme, remove it there, keep the module's, then check again.”

The problem

Google Search Console reports duplicate Product structured data. Our theme and an SEO module both output it.

What Claude does

  1. Claude confirms on a product page that the information is sent twice.
  2. It finds which add-on and which part of the theme send it.
  3. It prepares the theme change and shows exactly what changes.
  4. After your yes it saves with a backup and checks the page again.

What you get

Product pages send one clean set of product information. Confirm the result in Google's own test.

You stay in control

You see every change before it is saved, nothing happens without your yes, and you can undo it later. Changes to the shop's look use a separate, extra-protected connection, usually set up by whoever looks after your shop. Every file is backed up before it changes.

See pricing

Related use cases

For developers
Area
3 · Appearance & deployments
Connector
service connector
In the free Audit
no, paid version only
For
Developer, Agency / freelancer
Tools
ps_inspect_page, ps_list_modules, ps_list_theme_files, ps_read_theme_file, ps_write_theme_file, ps_clear_cache

Step by step

  1. Confirms the duplicate with ps_inspect_page (jsonld section).
  2. Finds the module output with ps_list_modules (hook displayHeader / displayAfterBodyOpeningTag) and the theme partial with ps_list_theme_files and ps_read_theme_file.
  3. Prepares the theme edit and calls ps_write_theme_file (validated, previewed as a diff).
  4. After your approval, saves with a backup and clears the cache.
  5. Re-runs ps_inspect_page to confirm one Product block with the basic fields.

Safety

Block 3 works only through the service connector: a separate token accepted only from allowlisted IP addresses, off after installation. Theme files are backed up automatically before every write and can be restored with ps_restore_file_backup. Limit: 20 theme file writes per hour.

Last updated: 2026-10-05