E-E-A-T for a SaaS blog: bylines, first-hand experience and sources
E-E-A-T is how Google's raters judge quality, not a score. On a SaaS blog it shows as first-hand evidence, bylines, sources and Article markup.
LLaunchScaler·Published ·8 min read
E-E-A-T stands for Experience, Expertise, Authoritativeness and Trustworthiness, the framework Google's Search Quality Rater Guidelines use to judge whether a page deserves trust. It is not a score and, in Google's words, "isn't a specific ranking factor"; raters "have no control over how pages rank." For a SaaS blog, E-E-A-T shows up as visible things: first-hand screenshots and numbers, a byline that links to a real author page, primary sources, and Article markup naming the author and dates.
Below is what each letter means in Google's own guidelines, how E-E-A-T relates to ranking, and the specific changes that make it visible on a software company's blog.
What does E-E-A-T mean?
Each letter is a question a rater asks about the content creator. The rater guidelines (the version dated September 11, 2025) define them: Experience is "the necessary first-hand or life experience for the topic"; Expertise is "the necessary knowledge or skill"; Authoritativeness is being "known as a go-to source for the topic"; Trust sits above all three.
Letter
The rater guidelines ask
On a SaaS blog, it looks like
Experience
Does the creator have "first-hand or life experience for the topic"?
Screenshots from your own account, numbers from your own usage
Expertise
Does the creator have "the necessary knowledge or skill for the topic"?
An author who does this work, with a bio that says so
Authoritativeness
Is the creator or site "known as a go-to source for the topic"?
Questions, answered
What people ask about this
01
What does E-E-A-T stand for?
Experience, Expertise, Authoritativeness and Trustworthiness. It comes from Google's Search Quality Rater Guidelines, which added the first E, for experience, in December 2022.
Trust carries the most weight. The guidelines call it "the most important member of the E-E-A-T family because untrustworthy pages have low E-E-A-T no matter how Experienced, Expert, or Authoritative they may seem." Google's helpful content page says the same: "Of these aspects, trust is most important."
Experience is the newest letter. Google added it in December 2022, asking whether content was produced "with some degree of experience, such as with actual use of a product, having actually visited a place or communicating what a person experienced." For a software company writing about its own category, that is the letter you are best placed to show.
Is E-E-A-T a ranking factor?
No, not directly. Google's helpful content guidance says "E-E-A-T itself isn't a specific ranking factor," but that its systems use "a mix of factors that can identify content with good E-E-A-T." Raters check whether results seem to show it; their ratings are feedback on Google's systems, not inputs to your page's rank.
Google is explicit about raters: "Search raters have no control over how pages rank. Rater data is not used directly in our ranking algorithms." It compares them to "feedback cards from diners." Its 2022 post announcing the extra E repeats that the guidelines "don't directly influence ranking," and adds that they "can also be useful to creators seeking to understand how to self-assess their own content."
Two practical consequences follow. First, there is no E-E-A-T switch to flip: adding an author box does not raise a score, because there is no score. Second, the visible changes below still matter, because they are the evidence of trust that Google's systems and readers both look for. Google also says its systems give "even more weight" to strong E-E-A-T on "Your Money or Your Life" topics, those that could affect health, finances or safety, so a SaaS blog touching billing, security or compliance has more at stake.
How do you show first-hand experience in a SaaS post?
Show the reader that someone actually did what the post describes. Use screenshots from your own product or account, real numbers from your own usage, the steps you took in order, what failed, and the date you did it. Generic advice any writer could produce without trying anything is the opposite of experience.
Generic version
Version that shows experience
"Setting up SSO can be tricky."
"On our Okta tenant, SSO failed until we changed the NameID format to email; screenshot below."
"Webhooks improve reliability."
"After moving invoice sync to webhooks in March, our failed syncs dropped from 41 a week to 3."
"Choose the right pricing model."
"We tested per-seat and usage pricing on two cohorts for 60 days; here is what each did to churn."
A stock image of a dashboard
A cropped, annotated screenshot of your real settings screen
(The numbers in the table are illustrations of the form. Use your own.)
Google's "How" question points the same way. For reviews, it says it "can build trust with readers when they understand the number of products that were tested, what the test results were, and how the tests were conducted, all accompanied by evidence of the work involved, such as photographs." On a SaaS blog, the equivalent evidence is screenshots, logs, timings and before-and-after numbers.
Keep dates on anything version-specific. "Checked in September 2026" next to a settings path tells the reader how current the steps are, and it tells you when to check them again.
How should bylines and author pages work?
Put a byline on every post, make it link to an author page, and make that page answer who the person is and why they know the subject. Google asks: "Do bylines lead to further information about the author or authors involved, giving background about them and the areas they write about?"
An author page for a SaaS blog should include:
The person's full name and role at the company.
What they work on day to day that relates to what they write.
Relevant background: past roles, projects, talks or open-source work, with links.
A photo, and links to profiles elsewhere (LinkedIn, GitHub) that confirm identity.
A list of their posts.
Google "strongly encourage[s] adding accurate authorship information, such as bylines to content where readers might expect it." Accurate is the key word: an invented persona fails the trust test that sits above everything else. If a post was drafted with AI help and edited by a person, the byline belongs to the person who stands behind it, and Google's "How" questions suggest saying how automation was used where a reader might wonder. The guide to whether Google penalizes AI content covers disclosure in more detail.
How do you cite sources on a SaaS blog?
Link each factual claim to its primary source: the vendor's own documentation for a product behaviour, the standard or RFC for a protocol, the study itself for a statistic. Link in the sentence that makes the claim, with anchor text naming the source, and date anything that changes, such as prices and limits.
Google's expertise questions ask whether content has "clear sourcing" and whether it has "any easily-verified factual errors." A source a reader can click answers the first and makes the second easy to check. Three habits keep sourcing honest:
Prefer the original over a summary. Link the vendor's docs, not a blog about them.
Quote exactly when the wording matters, and say who said it.
Remove a claim you cannot source rather than softening it into a vague one.
Your own data is a source too, and often the strongest. Say where it comes from ("from 1,200 accounts on our platform, June to August 2026") so a reader can judge it.
What Article markup supports E-E-A-T?
Add Article or BlogPosting structured data with the author as a Person whose url points to the author page, plus datePublished and dateModified. Google's Article documentation calls these recommended properties, and its author markup best practices ask for the type and the url so Google can tell who the author is.
Google's author markup rules are specific. Put only the author's name in author.name: no job title, no "posted by", no publisher name. Use jobTitle for the role. List each author in their own object rather than merging names. Use Person for people and Organization for companies. Google adds that sameAs can stand in for url.
The dates must match what the page shows. Google's byline date guidance asks you to "ensure that the date... match[es] between the equivalent user-visible and structured values." The Article schema author markup guide covers the full property list and validation.
What should a SaaS blog change first?
Start with the changes that are visible on every post and cheap to make: bylines linked to real author pages, sources linked in the text, and dated screenshots. Then add Article markup site-wide through your template, and review older posts for claims that are no longer true.
Change
Where
Letter it supports
Byline linked to an author page
Every post template
Expertise, Trust
Author pages with role and background
/authors/<name>
Expertise, Authoritativeness
Screenshots and numbers from your own product
In each post
Experience
Sources linked in the sentence
In each post
Trust
"Checked in" dates next to version-specific steps
In each post
Trust
Article markup with author and dates
Post template
Trust (helps Google identify the author)
About and contact pages linked from every page
Site template
Trust
Once those are in place, run each new draft through the helpful content checklist, which turns Google's expertise and trust questions into yes/no checks.
Get drafts written from your product, ready for your byline
The strongest experience signal a SaaS blog has is its own product, and the content engine starts there. LaunchScaler's content engine writes each article "from your product: what it does, who it is for, how it works," with "no invented facts, no borrowed examples," planned from your own Search Console queries. It writes one article a day, thirty a month, in your voice, and by default every draft waits in your workspace for you to add your screenshots, your numbers and your name before it publishes under your byline.
It costs $99/mo per website, with 3 days free before the first charge. Start the engine and the first draft is ready on day one.
Not directly. Google says E-E-A-T itself isn't a specific ranking factor, and that its search raters have no control over how pages rank. Its systems use a mix of other factors that can identify content with good E-E-A-T.
03
Which part of E-E-A-T matters most?
Trust. Both Google's helpful content guidance and the rater guidelines say trust is the most important member, because an untrustworthy page has low E-E-A-T however experienced or expert its author seems.
04
How do you show experience in a blog post?
Show that you did the thing: screenshots from your own product or account, real numbers from your usage, what you tried, what failed and when. Google describes experience as content produced with actual use of a product.
05
Does author schema help E-E-A-T?
It helps Google identify the author. Google recommends Article markup with author as a Person or Organization, a url to the author's page, and datePublished and dateModified, matching what the page shows.
Create a custom integration for the Admin API key, sign a 5-minute HS256 JWT with audience /admin/, and POST HTML to /ghost/api/admin/posts/?source=html.
