Fix a shop file that blocks Google, with a backup
Google can read your shop again the same day, and the old file is kept in case anything needs to go back.
What it replaces: 1 h of FTP and checking
What you write to Claude
„check robots.txt, it probably still has Disallow: / from staging. fix it for production, keep a backup, and check a product page is allowed”
The problem
Since the move from the test server, Google says our product pages are blocked. Someone copied the test site's rules file to the live shop.
What Claude does
- Claude reads the file and finds the rule that blocks Google.
- It shows the corrected file next to the old one.
- After your yes it saves it with a backup.
- It checks that product and category pages are open to Google again.
What you get
The rules file lets Google into the shop again, and the old version is kept as a backup.
You stay in control
You see every change before it is saved and nothing happens without your yes. This deep repair access uses the separate, extra-protected connection, works only for the few hours you switch it on, and keeps a copy of every changed file or record.
Related use cases
- Fix an error page after an update, with a developer's safety net
- Find out why Google stopped showing prices and stars
- Try risky changes on a test copy of the shop first
For developers
- Area
- 5 · Service mode
- Connector
- service connector
- In the free Audit
- no, paid version only
- For
- Developer, Agency / freelancer, Marketer / SEO
- Tools
- ps_server_file, ps_list_file_backups, ps_inspect_page, ps_restore_file_backup
Step by step
- Reads robots.txt with ps_server_file (action read).
- Proposes a production version (no 'Disallow: /', PrestaShop's default disallows and the sitemap line kept) and calls ps_server_file (action edit, search/replace or content); the preview shows the diff and a backup is made.
- After approval saves; restore with ps_list_file_backups and ps_restore_file_backup.
- Checks a product page with ps_inspect_page (status and robots meta).
- Protected files (app/config/parameters.php, .env, the module's own folders) can never be read or written.
Safety
Service mode (block 5) works only through the service connector (separate token, allowlisted IP addresses) and only while its time-limited switch is on (1, 4, 8 or 24 h); then it switches itself off, and the owner gets an e-mail when it is switched on. ps_server_file backs up every file before writing and checks PHP syntax, but cannot run code. Theme and module files are better changed with block 3 and 4 tools, which have extra checks.
Last updated: 2026-10-05