Reading rec
If this channel's your speed, @ScaleEngineSOP runs a sharp feed on programmatic SEO. Different angle, same depth — worth a follow.
If this channel's your speed, @ScaleEngineSOP runs a sharp feed on programmatic SEO. Different angle, same depth — worth a follow.
Author bylines are a weak signal that the industry over-fits
The question: does adding a detailed author bio improve E-E-A-T?
The honest answer is: rarely on its own, and the correlation is widely misread. Google's representatives have stated there is no requirement to use author bylines, and that bylines and bios are for users, not for a ranking bonus. Sites in verticals where authorship is unusual — many e-commerce and tool pages — rank fine without them.
The deeper issue is direction of causation. Credible sites tend to have real, identifiable authors; observers note the bio and conclude the bio caused the credibility. But pasting a fabricated or generic bio onto thin content adds no trust — and per the reputation-research instruction, raters who investigate an invented author and find nothing may register that as a negative trust signal, not a neutral one.
Where authorship does work, it works through what it enables: the named author has a verifiable track record off-site, a consistent entity across the web, real credentials that survive a search. The byline is a pointer to that external evidence. With nothing behind the pointer, the pointer is decorative.
Caveat: for clearly-YMYL content, demonstrable author or organizational credentials carry real weight in the guidelines. The critique is of the empty gesture, not of genuine attribution.
What we still don't know: whether the systems parse author entities directly, or whether the benefit is entirely mediated by off-site reputation signals attached to that person.
The question: does adding a detailed author bio improve E-E-A-T?
The honest answer is: rarely on its own, and the correlation is widely misread. Google's representatives have stated there is no requirement to use author bylines, and that bylines and bios are for users, not for a ranking bonus. Sites in verticals where authorship is unusual — many e-commerce and tool pages — rank fine without them.
The deeper issue is direction of causation. Credible sites tend to have real, identifiable authors; observers note the bio and conclude the bio caused the credibility. But pasting a fabricated or generic bio onto thin content adds no trust — and per the reputation-research instruction, raters who investigate an invented author and find nothing may register that as a negative trust signal, not a neutral one.
Where authorship does work, it works through what it enables: the named author has a verifiable track record off-site, a consistent entity across the web, real credentials that survive a search. The byline is a pointer to that external evidence. With nothing behind the pointer, the pointer is decorative.
Caveat: for clearly-YMYL content, demonstrable author or organizational credentials carry real weight in the guidelines. The critique is of the empty gesture, not of genuine attribution.
What we still don't know: whether the systems parse author entities directly, or whether the benefit is entirely mediated by off-site reputation signals attached to that person.
Page quality is judged on Main Content first, and most audits skip it
The question: when raters score a page's quality, what part of the page are they looking at?
The QRG partitions every page into Main Content, Supplementary Content, and Advertisements, and is explicit that quality is judged primarily on the Main Content — the part that directly satisfies the page's purpose. Supplementary content (navigation, related links) and ads are evaluated for whether they distract from or deceive about the main content.
This ordering is frequently inverted in practice. Audits obsess over schema, internal links, and sidebar widgets — all supplementary — while the main content remains a lightly-reworded competitor summary. Per the guidelines, a beautiful page wrapper around weak main content earns a low rating; the wrapper cannot rescue it.
The guidelines also penalize a specific deceptive pattern: main content that is hard to find because ads or supplementary content are designed to be mistaken for it, or that pushes the real content below a wall of interstitials. For monetized affiliate layouts this is a direct hazard — if a rater cannot quickly distinguish your answer from your ad units, the page reads as deceptive.
Caveat: high-quality supplementary content does count positively, especially for navigation-heavy pages like store category pages. The point is sequence, not dismissal.
What we still don't know: how the systems operationalize the main-versus-supplementary boundary on layouts where the distinction is genuinely blurry, such as comparison tables that are simultaneously content and monetization.
The question: when raters score a page's quality, what part of the page are they looking at?
The QRG partitions every page into Main Content, Supplementary Content, and Advertisements, and is explicit that quality is judged primarily on the Main Content — the part that directly satisfies the page's purpose. Supplementary content (navigation, related links) and ads are evaluated for whether they distract from or deceive about the main content.
This ordering is frequently inverted in practice. Audits obsess over schema, internal links, and sidebar widgets — all supplementary — while the main content remains a lightly-reworded competitor summary. Per the guidelines, a beautiful page wrapper around weak main content earns a low rating; the wrapper cannot rescue it.
The guidelines also penalize a specific deceptive pattern: main content that is hard to find because ads or supplementary content are designed to be mistaken for it, or that pushes the real content below a wall of interstitials. For monetized affiliate layouts this is a direct hazard — if a rater cannot quickly distinguish your answer from your ad units, the page reads as deceptive.
Caveat: high-quality supplementary content does count positively, especially for navigation-heavy pages like store category pages. The point is sequence, not dismissal.
What we still don't know: how the systems operationalize the main-versus-supplementary boundary on layouts where the distinction is genuinely blurry, such as comparison tables that are simultaneously content and monetization.
The fastest E-E-A-T gains come from reading the 'Lowest' rating criteria
The question: where should a struggling site spend the first hour of quality work?
Counterintuitively, not on reaching 'Highest' — on escaping 'Lowest'. The QRG devotes substantial space to what earns the Lowest rating, and those criteria are concrete, binary, and fixable in ways that 'Highest' criteria are not.
The Lowest triggers, per the guidelines, include: a harmful or deceptive purpose; insufficient information about the website or content creator for a YMYL or transactional site; an untrustworthy or malicious reputation found in research; content that is so untrustworthy or low-effort that it harms the user; and the inability to verify who is responsible for a YMYL site. Several of these are presence-checks, not quality gradients — you either have an honest, findable owner and contact, or you do not.
The asymmetry is the point. Moving from 'High' to 'Highest' requires rare expertise and reputation that take years. Moving off 'Lowest' often requires an honest About page, real contact information, removal of deceptive ad patterns, and not publishing demonstrably false claims. The marginal return on the second task is far larger.
Caveat: rating tiers describe rater judgment, not a literal score the systems assign. But the deceptive and trust-deficit patterns the Lowest tier catches map closely to what site-reliability systems are designed to demote.
What we still don't know: how much a single Lowest-tier defect, such as a hidden owner, suppresses an otherwise competent site.
The question: where should a struggling site spend the first hour of quality work?
Counterintuitively, not on reaching 'Highest' — on escaping 'Lowest'. The QRG devotes substantial space to what earns the Lowest rating, and those criteria are concrete, binary, and fixable in ways that 'Highest' criteria are not.
The Lowest triggers, per the guidelines, include: a harmful or deceptive purpose; insufficient information about the website or content creator for a YMYL or transactional site; an untrustworthy or malicious reputation found in research; content that is so untrustworthy or low-effort that it harms the user; and the inability to verify who is responsible for a YMYL site. Several of these are presence-checks, not quality gradients — you either have an honest, findable owner and contact, or you do not.
The asymmetry is the point. Moving from 'High' to 'Highest' requires rare expertise and reputation that take years. Moving off 'Lowest' often requires an honest About page, real contact information, removal of deceptive ad patterns, and not publishing demonstrably false claims. The marginal return on the second task is far larger.
Caveat: rating tiers describe rater judgment, not a literal score the systems assign. But the deceptive and trust-deficit patterns the Lowest tier catches map closely to what site-reliability systems are designed to demote.
What we still don't know: how much a single Lowest-tier defect, such as a hidden owner, suppresses an otherwise competent site.
The 2023 antitrust testimony reframed clicks as a long-running signal
The question: do user clicks influence rankings, and how does that relate to trust?
For years Google publicly minimized click signals. The 2023 U.S. v. Google antitrust trial complicated that. Testimony and exhibits referenced a system, Navboost, that uses aggregated, historical click data — described internally as one of Google's strongest signals — and a long memory of which results users engaged with for a query.
The relevance to E-E-A-T is indirect but real. If aggregated user behavior over time feeds ranking, then a site that earns repeat, satisfied engagement is accumulating something that behaves like trust, expressed through behavior rather than through credentials or links. Conversely, a site whose results are clicked and quickly abandoned is sending the inverse.
This must be stated carefully to avoid the usual overreach. The testimony does not establish a per-page 'click-through-rate dial' that you can game; the systems described use aggregated long-run patterns and are defended against manipulation. Buying clicks or pogo-sticking your own results is not the lesson.
Caveat: trial testimony is adversarial and partial; the exhibits describe systems as they existed at disclosed points in time, not a current, complete architecture. Treat specifics as indicative, not authoritative.
What we still don't know: how click signals interact with the quality and reliability systems — whether they reinforce or can override classifier judgments of low quality.
The question: do user clicks influence rankings, and how does that relate to trust?
For years Google publicly minimized click signals. The 2023 U.S. v. Google antitrust trial complicated that. Testimony and exhibits referenced a system, Navboost, that uses aggregated, historical click data — described internally as one of Google's strongest signals — and a long memory of which results users engaged with for a query.
The relevance to E-E-A-T is indirect but real. If aggregated user behavior over time feeds ranking, then a site that earns repeat, satisfied engagement is accumulating something that behaves like trust, expressed through behavior rather than through credentials or links. Conversely, a site whose results are clicked and quickly abandoned is sending the inverse.
This must be stated carefully to avoid the usual overreach. The testimony does not establish a per-page 'click-through-rate dial' that you can game; the systems described use aggregated long-run patterns and are defended against manipulation. Buying clicks or pogo-sticking your own results is not the lesson.
Caveat: trial testimony is adversarial and partial; the exhibits describe systems as they existed at disclosed points in time, not a current, complete architecture. Treat specifics as indicative, not authoritative.
What we still don't know: how click signals interact with the quality and reliability systems — whether they reinforce or can override classifier judgments of low quality.
The 2024 Content Warehouse leak: read it as vocabulary, not as a manual
The question: what did the May 2024 leak of internal Google API documentation actually tell us about trust signals?
The leaked Content Warehouse documentation exposed thousands of attribute names from an internal data store. Several are suggestive for E-E-A-T discussion: fields referencing site authority concepts, host-level signals, author identification, and a 'siteAuthority' attribute among them. Commentators seized on these as proof of a domain-authority-like metric.
The disciplined reading is narrower. The leak shows that attributes exist in a storage schema. It does not show whether they are used in ranking, how they are weighted, whether they are deprecated, or whether they feed live systems at all. A field name is a label on a box, not evidence of what is in the box or whether the box is opened.
What it does usefully confirm is that Google's internal model of the web includes host-level and author-level concepts — consistent with the idea that some signals operate at site and entity scope, not only per-page. That aligns with the reputation-research framing in the QRG.
Caveat: Google confirmed the documents were genuine but cautioned against drawing conclusions about ranking from a storage schema. That caution is methodologically correct, not merely defensive. Inferring weights from field names is a category error.
What we still don't know: which of the leaked attributes are live, their weights, and whether the trust-relevant fields feed ranking or some unrelated internal process.
The question: what did the May 2024 leak of internal Google API documentation actually tell us about trust signals?
The leaked Content Warehouse documentation exposed thousands of attribute names from an internal data store. Several are suggestive for E-E-A-T discussion: fields referencing site authority concepts, host-level signals, author identification, and a 'siteAuthority' attribute among them. Commentators seized on these as proof of a domain-authority-like metric.
The disciplined reading is narrower. The leak shows that attributes exist in a storage schema. It does not show whether they are used in ranking, how they are weighted, whether they are deprecated, or whether they feed live systems at all. A field name is a label on a box, not evidence of what is in the box or whether the box is opened.
What it does usefully confirm is that Google's internal model of the web includes host-level and author-level concepts — consistent with the idea that some signals operate at site and entity scope, not only per-page. That aligns with the reputation-research framing in the QRG.
Caveat: Google confirmed the documents were genuine but cautioned against drawing conclusions about ranking from a storage schema. That caution is methodologically correct, not merely defensive. Inferring weights from field names is a category error.
What we still don't know: which of the leaked attributes are live, their weights, and whether the trust-relevant fields feed ranking or some unrelated internal process.
Entity consistency is the underrated mechanical layer of authority
The question: how does a search system know that the author on your page is the same person credited elsewhere?
It does not assume it. Establishing that 'Jane Doe' on your byline is the same entity who wrote in a journal, spoke at a named conference, and has a knowledge-graph presence requires consistent, machine-readable identity signals. This is the unglamorous plumbing beneath 'author authority'.
The relevant artifacts are concrete: a consistent name string across properties; a stable author or person page that other pages can point to; sameAs links in structured data connecting that page to authoritative profiles (a professional society, an ORCID, a verified social profile, a Wikidata entry where one legitimately exists); and matching details — affiliation, credentials — across sources. Inconsistency fragments the entity into several weak shadows instead of one resolved identity.
This is where author-authority work pays off, and it is not the bio text. It is reconciliation: making the same person resolvable as one node across the web so that whatever reputation exists attaches to a single identity rather than scattering.
Caveat: structured-data sameAs is a hint, not a guarantee of entity resolution; the systems corroborate it against independent evidence. You cannot assert your way into a knowledge graph by linking to it.
What we still don't know: the corroboration threshold — how much independent, consistent evidence is required before a system treats an author as a recognized entity rather than an unverified claim.
The question: how does a search system know that the author on your page is the same person credited elsewhere?
It does not assume it. Establishing that 'Jane Doe' on your byline is the same entity who wrote in a journal, spoke at a named conference, and has a knowledge-graph presence requires consistent, machine-readable identity signals. This is the unglamorous plumbing beneath 'author authority'.
The relevant artifacts are concrete: a consistent name string across properties; a stable author or person page that other pages can point to; sameAs links in structured data connecting that page to authoritative profiles (a professional society, an ORCID, a verified social profile, a Wikidata entry where one legitimately exists); and matching details — affiliation, credentials — across sources. Inconsistency fragments the entity into several weak shadows instead of one resolved identity.
This is where author-authority work pays off, and it is not the bio text. It is reconciliation: making the same person resolvable as one node across the web so that whatever reputation exists attaches to a single identity rather than scattering.
Caveat: structured-data sameAs is a hint, not a guarantee of entity resolution; the systems corroborate it against independent evidence. You cannot assert your way into a knowledge graph by linking to it.
What we still don't know: the corroboration threshold — how much independent, consistent evidence is required before a system treats an author as a recognized entity rather than an unverified claim.
Freshness and trust pull in opposite directions, and the QRG knows it
The question: should authoritative content be updated frequently to stay fresh?
The two goals conflict more than the 'update your content' advice admits. The QRG treats a long, stable track record as a positive reputation signal — established sites with a history of reliability rate well partly because of that history. Freshness, meanwhile, matters for queries where recency is the user's actual need.
The resolution is query-dependent and is already in the guidelines' logic. For queries deserving freshness — news, prices, evolving situations — currency is part of meeting the need, and stale content fails the user. For evergreen reference content, stability and a long unbroken record of accuracy is itself the value, and churning it for a fresh date stamp can degrade rather than help.
The failure mode to avoid is cosmetic freshness: changing a date, swapping a year in a title, light reshuffling — without new information. This produces the worst of both, sacrificing the trust of a stable record while adding nothing a recency-seeking user needs, and it pattern-matches the 'made for search engines' behaviors Google's guidance names.
Caveat: genuine updates to YMYL content — corrected medical or financial facts — are unambiguously good and expected. The critique targets update-theater, not substantive revision.
What we still don't know: how the systems distinguish substantive updates from cosmetic ones, and whether date metadata is weighted independently of detected content change.
The question: should authoritative content be updated frequently to stay fresh?
The two goals conflict more than the 'update your content' advice admits. The QRG treats a long, stable track record as a positive reputation signal — established sites with a history of reliability rate well partly because of that history. Freshness, meanwhile, matters for queries where recency is the user's actual need.
The resolution is query-dependent and is already in the guidelines' logic. For queries deserving freshness — news, prices, evolving situations — currency is part of meeting the need, and stale content fails the user. For evergreen reference content, stability and a long unbroken record of accuracy is itself the value, and churning it for a fresh date stamp can degrade rather than help.
The failure mode to avoid is cosmetic freshness: changing a date, swapping a year in a title, light reshuffling — without new information. This produces the worst of both, sacrificing the trust of a stable record while adding nothing a recency-seeking user needs, and it pattern-matches the 'made for search engines' behaviors Google's guidance names.
Caveat: genuine updates to YMYL content — corrected medical or financial facts — are unambiguously good and expected. The critique targets update-theater, not substantive revision.
What we still don't know: how the systems distinguish substantive updates from cosmetic ones, and whether date metadata is weighted independently of detected content change.
The QRG explicitly recognizes everyday expertise
The question: can a creator without formal credentials demonstrate expertise that raters accept?
Yes, and the guidelines say so directly. The QRG introduces the concept of everyday expertise: for many topics, people with deep personal experience and self-acquired knowledge can produce high-quality, trustworthy content without formal education or professional credentials. The guidelines give examples — a detailed, experienced product review; advice from people who have lived through a specific illness in a support community.
This is a deliberate counterweight to a credential-only reading of expertise. For non-YMYL and many soft-YMYL topics, demonstrated knowledge can substitute for a diploma. What the rater looks for is evidence in the content itself: depth, specificity, accuracy, and signs the creator genuinely knows the area — not a letterhead.
The boundary is firm, however. The same guidelines hold that for clearly-YMYL topics with serious harm potential — medical, financial, legal advice — formal expertise and appropriate credentials become important, and everyday expertise alone is insufficient. The standard scales with stakes.
For practitioners in hobbyist, product, and lifestyle niches, this is liberating: you do not need a credentialed author to reach high quality, you need genuine demonstrated knowledge. For a health-claims page, you do.
Caveat: 'everyday expertise' is still expertise — it requires real demonstrated depth, not the appearance of it. The bar is evidence, lowered in form but not in substance.
What we still don't know: how the systems detect everyday expertise, which by definition lacks the external credential trail that formal expertise leaves.
The question: can a creator without formal credentials demonstrate expertise that raters accept?
Yes, and the guidelines say so directly. The QRG introduces the concept of everyday expertise: for many topics, people with deep personal experience and self-acquired knowledge can produce high-quality, trustworthy content without formal education or professional credentials. The guidelines give examples — a detailed, experienced product review; advice from people who have lived through a specific illness in a support community.
This is a deliberate counterweight to a credential-only reading of expertise. For non-YMYL and many soft-YMYL topics, demonstrated knowledge can substitute for a diploma. What the rater looks for is evidence in the content itself: depth, specificity, accuracy, and signs the creator genuinely knows the area — not a letterhead.
The boundary is firm, however. The same guidelines hold that for clearly-YMYL topics with serious harm potential — medical, financial, legal advice — formal expertise and appropriate credentials become important, and everyday expertise alone is insufficient. The standard scales with stakes.
For practitioners in hobbyist, product, and lifestyle niches, this is liberating: you do not need a credentialed author to reach high quality, you need genuine demonstrated knowledge. For a health-claims page, you do.
Caveat: 'everyday expertise' is still expertise — it requires real demonstrated depth, not the appearance of it. The bar is evidence, lowered in form but not in substance.
What we still don't know: how the systems detect everyday expertise, which by definition lacks the external credential trail that formal expertise leaves.
On the correlation studies: most measure the wrong thing
The question: what do the published 'E-E-A-T correlation' studies actually establish?
Less than their headlines claim, for a structural reason worth understanding. Studies typically take a set of ranking pages, score some observable feature — author bios present, outbound citations, page length, third-party-tool 'authority' scores — and report a correlation with position. The recurring flaw is confounding.
Sites that rank well tend to have many correlated good properties at once: better content, more links, more mentions, real authors, cleaner technical setup. Any one feature will correlate with ranking, not because it causes the ranking, but because it co-occurs with the bundle of things that do. Isolating the causal contribution of a single E-E-A-T artifact from observational SERP data is, in most published work, not actually attempted.
This is not an argument that the studies are worthless — directional correlation is information. It is an argument against the interpretive leap from 'pages with X rank better' to 'add X to rank better'. The second is a causal claim the data rarely supports, and it is the one practitioners act on.
The more credible evidence is controlled: documented before/after on a single property where one variable changed, ideally with a holdout. Those are rare and small, but they discriminate cause from co-occurrence in a way SERP-wide correlations cannot.
Caveat: even controlled single-site tests generalize poorly across niches and query classes.
What we still don't know: the causal weight of nearly any individual E-E-A-T artifact, because the clean experiments that would isolate it are mostly unrun and unpublishable at scale.
The question: what do the published 'E-E-A-T correlation' studies actually establish?
Less than their headlines claim, for a structural reason worth understanding. Studies typically take a set of ranking pages, score some observable feature — author bios present, outbound citations, page length, third-party-tool 'authority' scores — and report a correlation with position. The recurring flaw is confounding.
Sites that rank well tend to have many correlated good properties at once: better content, more links, more mentions, real authors, cleaner technical setup. Any one feature will correlate with ranking, not because it causes the ranking, but because it co-occurs with the bundle of things that do. Isolating the causal contribution of a single E-E-A-T artifact from observational SERP data is, in most published work, not actually attempted.
This is not an argument that the studies are worthless — directional correlation is information. It is an argument against the interpretive leap from 'pages with X rank better' to 'add X to rank better'. The second is a causal claim the data rarely supports, and it is the one practitioners act on.
The more credible evidence is controlled: documented before/after on a single property where one variable changed, ideally with a holdout. Those are rare and small, but they discriminate cause from co-occurrence in a way SERP-wide correlations cannot.
Caveat: even controlled single-site tests generalize poorly across niches and query classes.
What we still don't know: the causal weight of nearly any individual E-E-A-T artifact, because the clean experiments that would isolate it are mostly unrun and unpublishable at scale.
One to follow
For AI & SGE / AI Overviews done right, @OverviewHotTake is the move. Strong, unfiltered opinions on AI Overviews and generative search — where it's…
For AI & SGE / AI Overviews done right, @OverviewHotTake is the move. Strong, unfiltered opinions on AI Overviews and generative search — where it's…