Building MySiteSure: what do you need before acting on a website report?
I’m building MySiteSure for people who run their own websites. It’s in private preview, and I’d like feedback on the step between getting a report and actually fixing something.
The website-checking workflow lets you review findings and their evidence, then copy a fix brief for your coding assistant. You still make the change and check whether it worked. There’s also a separate content workflow: choose a topic, edit an outline, and generate an article draft. You don’t have to scan your site before writing.
One lesson from testing on our own Synclip site: a combined performance score could be mistaken for the separate mobile and desktop results. We clarified the label. That was a reporting fix, not evidence that the website itself got faster.
The overview and private-preview sign-in request are at https://mysitesure.com/. Requesting a link doesn’t create an account or guarantee access.
If you’ve put off fixing something in a website report, what was missing? The affected page, an explanation, instructions, or a way to tell whether the fix worked? A specific example would be useful.
Replies
The fix brief you can hand to a coding assistant is exactly how I'd use it. Of your four options, the one I'd want most is the last: a way to tell whether the fix actually worked. My own rule is that a 200 response doesn't count as checked, you look at the real page.