A frequent question we hear before someone buys a Pro Diagnosis + Remedy Package: “Will I need to hire a developer to actually do any of this?”
The honest answer: usually no.
The Pro Diagnosis + Remedy Package is written for a non-developer to implement. Every remedy step assumes the reader does not know HTML, does not know CSS, has never opened a code editor, and is comfortable using their CMS the way they normally do. If you can update your About page, you can implement most of the remedies in this audit.
That is not a marketing claim. It is a structural decision that affects how every remedy gets written.
What “non-developer-implementable” actually means
For every Critical and every High Value finding, the Remedy Package contains step-by-step instructions written for a person sitting at their computer with the site open in one window and the remedy open in another.
The steps look like:
- Log in to Squarespace at squarespace.com/login.
- Click “Pages” in the left navigation.
- Find your “About” page in the list. Click it.
- In the page settings (the gear icon next to the page title), click “SEO.”
- In the “SEO Description” field, replace the current text with the following:
[ready-to-copy text]
- Click “Save.”
Not “update your meta description.” Step one, step two, step three. With the specific path on your specific platform.
How the platform matters
A meaningful part of writing remedies is making the steps match the actual website builder the client uses. The path to update a meta description in Squarespace is different from WordPress, which is different from Wix, which is different from Webflow. A remedy that says “update your meta description” is technically a remedy. A remedy that tells you exactly where to click in your specific CMS is actually usable.
We identify your platform during the audit (it is one of the twenty-eight standard checks). Then every remedy in the report is written for that platform specifically. If your site is on Squarespace, the steps reference Squarespace’s interface. If your site is on WordPress with the Yoast plugin, the steps reference Yoast.
When you do need a developer
We are honest about the small number of remedies that genuinely require someone with development experience. The most common cases:
- Custom HTML or JavaScript injection that your platform doesn’t expose in a UI
- Server-side changes (redirects at the DNS or server level)
- Complex schema markup involving multiple linked entities
- Speed optimization that requires editing a theme or template file
When a remedy needs a developer, the report says so, clearly, at the start of the remedy steps. You will know going in that this is one to hand off.
Why this is structural, not optional
You could argue: “Why not just have the remedies say ‘update your meta description’ and let a developer figure out the rest?”
Because that defeats the purpose of the audit. The whole reason to deliver a written, plain-English audit is to give the small business owner the ability to act on it. If every remedy requires hiring someone, the audit is the first step in a more expensive process, not a deliverable that stands on its own.
We sell the audit as something that is useful even if you never hire us again. That promise only holds up if the remedies are actually implementable by you, in your CMS, without a translator.
The handoff option, if you want it
For clients who would rather not implement the remedies themselves, we do offer implementation as a separate service. The audit document is structured so that handing it to anyone (us, your existing developer, a freelancer) is a clean handoff. Every step is there. Nothing requires us to be in the room.
You pick which remedies to do yourself, which to delegate, and which to skip. The document supports any combination.
If you want an audit that respects the fact that you might want to fix the items yourself, the Pro Diagnosis + Remedy Package is built that way on purpose.