A Claude agent moved Junk’s Above, a thrift store site, off GoDaddy hosting onto our own AWS server — clearing the “Not Secure” warning for free and fixing a broken email link across the whole site. It was not quick or clean: the job ran across several separate sessions over more than a day, with real dead ends and heavy human involvement before it worked. The site is live at junksabove.com.
Take the Assignment
The site showed a “Not Secure” warning in the browser, and the public email needed to read the same everywhere. Instead of buying a GoDaddy SSL plan, the job was to move the site onto our own platform where SSL provisions on its own, then fix the email.
Where It Went Sideways
This is the honest part. The first content export was a .wpress file that turned out corrupted at the end, so the built-in import failed with a “corrupted archive” error more than once before we proved the file itself was broken.
The theme editor inside WordPress could not save the email fix either — a broken script on the site silently blocked the write, so the change looked saved but never reached the live page. Each of these was a real stop that cost time, and they happened across different sittings, not in one run.
Honest timing note: This work spanned more than a day across several separate sessions. We did not precisely meter hands-on hours, so this article does not claim a tidy minute count — the point is that it took real, repeated human effort and several failed attempts, not a single fast pass.
Find the Path That Worked
The agent set up the site on our platform and pointed it at the new server, changing only the DNS A-record at GoDaddy and leaving the nameservers and mail records alone so email delivery kept working.
After the corrupted export was abandoned, a clean UpdraftPlus backup was used instead — restoring every page, image, and the theme, then running the database upgrade. The leftover email link (new address as text, old address underneath) was fixed by editing that one line directly on the server through AWS Session Manager, backing up the file first and checking the result on every page.
Make the Hard Calls
The agent dropped the corrupted export instead of re-exporting it endlessly. It changed only the DNS A-record to protect email. It refused to touch the shared database that runs 200+ other client sites, since a raw import there was a needless risk. This is the same kind of infrastructure work as when an agent cleaned a hidden backdoor off blitzmetrics.com and when one imported every client site into Bing.
Know the Limits
The agent handled the migration, the file restore, the server-side email fix, and the checking — but it hit walls it could not get past on its own, and a human carried a real load: every login and 2FA code, uploading the backup files, the manual plugin install, and repeated testing. That honesty is the standard in the meta article process Dennis teaches.
Score the Work
| Guideline | Status | Notes |
|---|---|---|
| Honest about where the agent tripped | PASS | Dead ends documented, not hidden |
| Real timing (no invented minutes) | PARTIAL | Multi-day; exact hands-on hours not metered |
| Short paragraphs / active voice | PASS | |
| No AI fluff phrases | PASS | |
| 2–3 internal links, good anchors | PASS | Backdoor, Bing, meta-article parent |
| Featured image from real photo | NEEDS HUMAN | Agent cannot take photos |
| RankMath SEO configured | NEEDS HUMAN | Agent supplies metadata; human enters it |
| Categories and tags set | PARTIAL | Agent suggests; human applies |
Junk’s Above now loads over https with a valid certificate and no “Not Secure” warning.

