How these pages are written and checked
Everything on this site is published by me, Christopher Abraham, and I'm responsible for every word of it. Here's how the guides, case studies, and service pages are made, so you can decide how much to trust them.
Written from the work
The case studies describe engagements I worked on myself: the problem, my role, what I found, what was done and by whom, and where it stands. The guides come from the same work. When I explain how to read the Page indexing report or how to lock down a domain that sends no email, it's because I've done it for clients or for my own sites, often in the same week.
Primary sources for every factual claim
Where a guide states how Google, Bing, a standard, or a protocol behaves, it links to the primary documentation: Google Search Central, Bing Webmaster Guidelines, the W3C's accessibility standards, the RFCs that define email records, and the specifications for files like llms.txt. Those links are listed under "Sources" at the end of each guide, and in the page's structured data as citations. When the official documentation and common practice disagree, I say so.
How I use AI tools
I use AI assistants the way I'd use a capable junior colleague: to draft outlines and first passes, to check code and markup, and to build and test this site's generator. I don't publish anything they produce until I've read it, corrected it, and checked its claims. Two rules are absolute:
- Personal and biographical details come only from my own records and verifiable published sources, never from an AI summary. AI search tools have confidently told the world things about me that aren't true, and none of those get a second life here.
- Technical claims are checked against primary documentation, not against what an assistant remembers.
Clients and confidentiality
Case studies describe clients by industry and problem, never by name, and leave out anything that could identify them: addresses, revenue, account details, and screenshots of private dashboards. Where a client's engagement is ongoing or paused, the case study says so. I don't claim results I can't show, and I don't round up.
Quotes and testimonials
Quotes from clients and colleagues are reproduced as written, with attribution. Where I've shortened a quote, an ellipsis marks the cut. Upwork figures, such as my Job Success Score and job counts, are copied from my profile with the date they were taken, and the profile itself is linked so anyone can check the current numbers.
Independence
- No affiliate links, sponsored posts, or paid placements, anywhere on the site.
- Tools and platforms are named because I use them or because clients run on them, not because anyone pays me to mention them.
- The firms I'm affiliated with are named on the About page, so you can weigh any recommendation with that in mind.
Dates and updates
Every guide shows when it was published and when it was last updated. Search changes quickly, so I revise guides when Google, Bing, or a standard changes, and the updated date moves with the revision. Pages describing my own memberships and activities use past and present tense carefully, and I correct them when something changes.
Corrections
If you find an error, email cja@well.com with the page and what's wrong. I'll check it against the source, fix it if you're right, and update the page's date. Significant corrections to a guide are noted on the guide itself.
Who's behind the site
This is a one-person practice. My background, credentials, and the third-party sources that confirm them are on the About page, and the life behind the work is off the clock. You can also find me on Upwork and LinkedIn, or get in touch directly.
Updated October 6, 2026