DEV Community

pickuma
pickuma

Posted on • Originally published at pickuma.com

The E-E-A-T Signals We Actually Invest In (and the Ones We Skip)

E-E-A-T — Experience, Expertise, Authoritativeness, Trustworthiness — is not a ranking factor you can wire into a meta tag. Google's Search Quality Rater Guidelines describe it as a lens human raters use to judge whether a page deserves to be trusted. That makes it slippery. You cannot measure it directly, and most advice online flattens it into a checklist: add an author bio, link out to a study, paste in some schema markup, done.

We run an AI-assisted publication, which drops us into the exact spot where trust signals matter most and where shortcuts get punished hardest. If a reader or a rater suspects a page was generated and shipped without a human checking it, every other signal on the page gets discounted. So we have had to be deliberate about where the effort goes. Here is where we actually spend it, and where we have decided it is wasted motion.

Disclosure is the first signal, not a footnote

The single highest-leverage thing we do is tell you when a language model helped write something. Every article carries an aiAssisted flag in its frontmatter, and when that flag is set, a visible note renders near the top of the page. We do not bury it in a privacy policy or a 9-point gray footer. The reasoning is partly legal — the FTC's endorsement guides treat undisclosed material connections and misleading provenance as deceptive — and partly practical: a reader who knows the production method up front reads the rest of the page more charitably than one who figures it out and feels tricked.

The same logic governs affiliate links. Every monetized link routes through a /go/<slug> redirect rather than a raw partner URL, and a standing disclosure page spells out that we earn a commission when you buy through those links. The redirect is not a trust gimmick; it exists so we can swap a dead partner link in one place and so click tracking stays honest. But the side effect is that what we earn from is auditable. You can hover any link and see it points at our own domain, not a tracking parameter smuggled into a vendor URL.

The failure mode here is treating disclosure as a compliance tax — the smallest, least visible label that a lawyer signs off on. That inverts the value. A disclosure a reader has to hunt for reads as concealment the moment they find it. If you are going to disclose at all, make it the kind of thing a skeptical reader notices before they go looking.

Provenance you can audit beats credentials you have to trust

Most E-E-A-T advice fixates on author identity: a headshot, a job title, a LinkedIn link. Those help, but they are claims. A claim that the author is a senior engineer is only as good as your willingness to believe it. We lean harder on provenance you can verify without trusting us.

Two frontmatter fields do most of the work. updatedAt records when an article was last meaningfully touched, separate from when it was first published — so a 2024 review that we revised this month does not masquerade as forever-fresh, and a piece we have not revisited does not pretend it was. An optional changelog array records what changed and why, in plain language, when an update is substantive enough to matter. A reader who wants to know whether the pricing figures are current can read the changelog instead of taking "updated" on faith.

Underneath that, the git history is the real audit trail. We do not force-push the main branch, by policy, because the commit log is the provenance record for every piece of content on the site. Every article's full edit history — who changed what, when — survives. That is a costlier discipline than it sounds; it means living with a messy history rather than rewriting it clean. We keep it because a tamper-evident record of how a page evolved is worth more than a tidy one.

Experience is the expensive one, and the one that pays

The first E — Experience — is the hardest to fake and the most valuable when it is real. It is the difference between a page that paraphrases a vendor's landing page and one written by someone who actually opened the tool. Raters are explicitly told to look for it, and it is the signal generated content most often lacks.

So this is where we refuse to cut. When we review a tool, we install it and use it, and the article reports specifics that only come from doing so: the actual onboarding steps, a real pricing tier as of a stated date, the thing that broke, the limit we hit. We do not write "intuitive interface" or "powerful features." We write what happened. Numbers come with units and a date attached, because a price or a benchmark without a timestamp is a liability the moment the vendor changes it.

This is slower than summarizing marketing copy, and that is the point. The cost is the signal. A page that demonstrably required someone to do the work is one an AI shortcut cannot cheaply imitate, which is exactly why it carries weight.

What we deliberately skip

A fair amount of received E-E-A-T wisdom is cargo cult, and chasing it dilutes the signals that work. We skip inventing author personas — no "Jane, 10-year industry veteran" stock-photo bylines, because a fabricated authority is worse than an honest "AI-assisted, human-reviewed" note. We skip schema-markup stuffing as a trust play; structured data helps search engines parse a page, but it does not make an untrustworthy page trustworthy, and raters look at the content, not the JSON-LD. We skip word-count padding, since length is not depth and a 3,000-word article that says what a 1,200-word one would have just wastes your time. And we skip reciprocal link schemes, which signal a link economy rather than a citation.

The through-line is that real E-E-A-T comes from things that are costly to fake — disclosed methods, auditable history, demonstrated firsthand use — and the cheap proxies for it are noise at best and tells at worst.


Originally published at pickuma.com. Subscribe to the RSS or follow @pickuma.bsky.social for new reviews.

Top comments (0)