Aither Watch Action Plan: What I’m Fixing on JackRighteous.com After the Test
Gary Whittaker
Aither Watch · Action plan · Updated September 8, 2026
FROM FINDINGS TO ACTION
The first Aither Watch test gave JackRighteous.com a clean technical baseline, then pointed to a smaller set of things worth reviewing. This page now records what happened when I actually tested those recommendations against the live site.
Rule for this page: do not fix what already passed. Verify the findings that require human testing, make only the changes that improve the real visitor journey, and document the result.
Aither reported 0 failures, 0 warnings, 8 passed checks and 4 informational items in its limited sample. I preserved that baseline while testing the recommendations that required human review.
Homepage returned HTTP 200.
Page title and search description were present.
One main heading was detected.
Mobile viewport was present.
HTTPS passed.
A contact route was visible.
Organization structured data was detected.
The seven sampled same-site links did not return missing-page or server-error failures.
What changed in practice: the audit became a review trigger, not an instruction to rewrite the site.
Priority 1 · Completed
Service, audience and delivery clarity
Validated
Finding
Aither recommended stating the service, intended customer and delivery model more plainly.
Validation
The homepage already explains the creator audience, the current starting points, the four operating roads and the access model clearly. ASK JACK and Work With Jack were then reviewed separately to test delivery mechanics.
Action
No homepage rewrite. One narrow clarification was added to ASK JACK so the page explicitly identifies it as an email-based written review and directs live-conversation needs to Work With Jack.
Result
PASS WITH MINOR CLARIFICATION
Priority 2 · Completed
Contact journey and inbox delivery
Live test
Finding
Aither detected contact routes and forms but did not submit them or verify delivery.
Validation
The primary ASK JACK route was tested through the intended inbox path. The test message reached the correct inbox successfully.
Result
PASS
Caveat
The internal delivery test confirms the route is receiving correctly, but an outside visitor's own mail client can still behave differently. No site defect was found.
Priority 3 · Completed
Public profile references
Identity check
Finding
Aither found public-profile references but correctly did not treat a link as proof of ownership or current use.
Validation
The current YouTube, Instagram, Facebook group, Spotify, Facebook, TikTok and X destinations were checked against the identities used across the site.
Result
PASS
Maintenance note
The Contact page still uses the older twitter.com form for the X profile. It routes to the same account, so it is maintenance rather than a broken identity path.
Priority 4 · Completed
Structured identity versus visible identity
Consistency check
Finding
Organization structured data identified Jack Righteous, so the machine-readable identity needed to be checked against the public business identity.
Validation
The core relationship is consistent: Gary Whittaker is the person behind the business, Jack Righteous is the creative identity, and JackRighteous.com is the operating creator ecosystem.
Action
A duplicate-role problem between the current About page and the older Jack Righteous story page was reviewed. The About page was preserved as the current identity/business authority. The story page was repositioned as the origin and evolution page, existing useful routes were restored, and its presentation was upgraded without removing current information.
Testing win: this was the clearest example of the audit leading to a useful improvement without manufacturing a problem. The review exposed role duplication, preserved the stronger current About page, and gave the story page a distinct purpose.
Priority 5 · Completed
Shopify authentication 400
Edge case resolved
Finding
One sampled Shopify customer-authentication redirect returned HTTP 400 during Aither's limited link check.
Validation
Shopify confirms New Customer Accounts are active, login links are visible on the storefront and checkout, login is optional at checkout, and the canonical account destination is account.jackrighteous.com. The normal customer-account link was then tested manually in a real browser and passed.
Decision
The 400 is treated as a context/crawler edge case, not evidence of a broken customer journey.
Result
PASS — NO REPAIR REQUIRED
Additional finding · Completed
The machine-facing store description was stale—and this one was worth changing.
The review surfaced a machine-facing issue that survived validation. Shopify's previous store-level meta description said:
“Turn AI ideas into books, songs, products, guides, courses, and brands. Start free, choose your creator road, and build with the JR Creator System.”
That wording reflected an older version of the site's architecture. After confirming the issue, I did not simply copy the first recommendation into Shopify. I researched the current SEO constraints, tightened the language, added stronger action language and aligned it to what JackRighteous.com actually offers now.
Live replacement:
“Build AI-assisted music, writing, products and brands with free creator training, practical guides and tools designed to turn ideas into real projects.”
COMPLETED / PASS
This became another useful contrast in the test cycle: unlike the sampled authentication 400, the metadata issue held up under review and deserved a real change.
Working record
Recommendation → validation → result
Finding
Final state
Result / evidence
Service + audience + delivery clarity
Completed
Homepage already healthy; ASK JACK received one narrow delivery clarification.
Contact journey
Completed
Primary inbox route received the test successfully.
Public profiles
Completed
Current identities aligned; only minor X URL maintenance noted.
Structured identity
Completed
Core identity consistent; About/story duplication resolved and story page upgraded.
Shopify authentication 400
Completed
New Customer Accounts configuration verified and normal account journey passed manually.
Store-level meta description
Completed
Stale description confirmed, researched, rewritten within SEO constraints and updated live in Shopify.
Main lesson: the useful outcome was not a pile of fixes. Some recommendations were already healthy, one needed a tiny clarification, one led to a worthwhile structural/presentation improvement, one apparent technical error was disproven by real-world testing, and one machine-facing metadata issue was confirmed and fixed.
