Turn 'page not found' errors into a plan for old addresses
Works in the free TellMyShop AuditContent & SEOReady job: Fix broken links
Visitors and Google stop landing on dead pages, and you keep the traffic those old addresses still get.
What it replaces: 2-4 h of spreadsheet work
What you write to Claude
„show me the most visited 404s from the last 30 days and suggest where each one should redirect”
The problem
After we renamed a few categories, Google shows a pile of 'not found' pages. I don't know which old address should go where.
What Claude does
- Claude reads which missing pages people tried to open, and how often.
- For each one, it looks for the product or category that should be there now.
- It checks that the suggested new page really works.
- It gives you a table: old address, visits, where it should lead.
What you get
A plan ordered by traffic. Items that match a renamed product or category can be fixed in the next step, with visitors forwarded automatically from the old address.
You stay in control
Claude only reads. Nothing in your shop changes.
Related use cases
- Change a product's page address without losing Google traffic
- Rename a category's page address after a reorganisation
- Monthly audit report for an agency client
- Retire a product without losing its Google traffic
- Send visitors from any old address to the right new page
For developers
- Area
- 1 · Content & SEO
- Connector
- daily connector
- In the free Audit
- yes
- For
- Marketer / SEO, Agency / freelancer, Store owner
- Tools
- ps_get_404_report, ps_search_products, ps_get_category_tree, ps_inspect_page, ps_list_redirects, ps_get_ready_job, ps_manage_redirects
Step by step
- Calls ps_get_404_report for the period (needs the PrestaShop 'Pages not found' stats module to be collecting data).
- For each top address, looks for the matching product or category with ps_search_products and ps_get_category_tree.
- Checks candidate targets with ps_inspect_page to confirm they return 200.
- Builds a table: old URL, visits, referring page, suggested target, and whether it can be fixed with a URL change in PrestaShop or needs a redirect; existing redirects are checked with ps_list_redirects so nothing is set twice. Setting the redirects is the next step with ps_manage_redirects (preview, approval, undo).
Safety
Read-only: nothing in the shop changes, so there is no preview or undo step. Works in the free Audit edition and in whole-shop read-only mode. The 404 data comes from PrestaShop's own stats module; if it isn't installed, the report is empty.
Last updated: 2026-10-05