Fixing E-E-A-T in Blog Posts, From Byline to Back Catalogue
The blog is usually where a small business site looks least trustworthy. Posts are published under "admin", written to hit a keyword, dated years ago or not at all, and they say what every other post on the topic says.
The E-E-A-T Checker tends to flag the same gaps on every post because they come from one template and one habit. This guide fixes both: a post template that shows who wrote the piece and why they know, a writing pattern that puts your own evidence first, and a way to sort the old posts you already have.
Why blog posts fail E-E-A-T in the same ways
Blog content is written differently from service pages. It is often produced in batches, sometimes by freelancers or with AI help, published through a CMS account shared by the whole team, and rarely revisited. Each of those habits leaves a visible trace that readers, raters and the checker all notice:
- The shared account. WordPress and most other systems show the name of the user who
pressed Publish. If that is
admin,editoror the company name, every post is effectively anonymous. - Keyword-first writing. A post planned around a search phrase tends to open with a definition and a list anyone could write, and never gets to what the business actually knows.
- Borrowed facts. Figures and claims copied from other blogs without a source, often rounded or out of date by the time they are repeated.
- No dates, or misleading ones. Themes that hide the date, or plugins that refresh it on every save.
- A growing archive nobody owns. Hundreds of posts, many overlapping, some wrong, all left to age.
The fix is not a checklist applied post by post. It is a template change that takes care of the structural signals once, plus an editorial habit that makes each new post show real knowledge.
What a trustworthy blog post looks like, top to bottom
| Part of the post | What it should show | Common failure |
|---|---|---|
| Header | Headline, author name linked to their page, role, published date, updated date if different | "Posted by admin", no date |
| First two paragraphs | Who this is for, the direct answer, and why the author is in a position to give it | A dictionary definition and "in this article we will" |
| Body | Specific examples, photos, figures and mistakes from real work, with sources for outside facts | A list that could appear on any competitor's blog |
| Disclosures | Affiliate links, sponsorship, free products, AI assistance where readers would expect to know | Hidden or buried at the foot of the page |
| End of post | A two to four sentence bio and a link to related posts on the same subject | A generic call to action and nothing about the writer |
| Behind the page | Article or BlogPosting markup whose author, headline and dates match the visible post | Author set to the organisation, dates that do not match |
Two of these parts belong to sibling guides. What makes a strong bio page is covered in fixing missing author bios, and how to reference sources well is covered in adding citations and sources. This guide concentrates on how they fit together in a post, and on the parts only a blog has: the opening, the author's own evidence and the archive.
The fix, step by step
Step 1
Give every post a real, named author
Create a separate CMS user for each person who writes, with their real display name, and reassign each post to the person who actually wrote it. In WordPress, set Display name publicly as on each user profile, then use bulk edit on the Posts screen to change the author. Posts that genuinely came from a team can be credited to the person who took responsibility for them. Never invent a persona to fill the byline.
Step 2
Rewrite the opening around what you know first-hand
Replace the generic introduction with two short paragraphs: the direct answer to the question in the title, then one sentence saying how the author knows, such as we have fitted over forty of these in Victorian terraces. Delete any lines announcing what the article will cover. A reader and a rater should know within the first screen who is talking and why they are worth listening to on this particular subject.
Step 3
Replace generic claims with your own evidence
Read the body and mark every sentence that any competitor could have written. For each, ask what your business has seen that proves, contradicts or sharpens it, and add that instead: a real photo from a job, a price range you have actually charged, a mistake a customer made, a result you measured. Keep the generic sentence only if it is needed for context. This is the single change that most separates a useful post from filler.
Step 4
Link the facts you did not produce yourself
Every statistic, legal point, health statement or quoted figure that came from somewhere else needs a link to where it came from, ideally the original publisher rather than a blog that repeated it. Put the link on words that describe the source. If you cannot find the origin of a figure that has been circulating, remove it or say it could not be verified. Check that each linked page still says what you claim.
Step 5
Show the dates honestly in the post header
Show the original published date under the headline, and add an updated date only when the post has been meaningfully revised, labelled clearly as Updated. Check the theme is not hiding dates on single posts, and that no plugin is rewriting the modified date on every save. For posts where timing matters, such as prices, rules or product advice, a short note saying what changed in the update helps readers judge whether it still applies to them.
Step 6
Close with a short bio and matching Article markup
Add a bio box to the post template that pulls from the author profile: name, role,
two or three sentences of relevant experience and a link to the full author page. Then check the structured
data your theme or plugin outputs. The author should be a Person whose name and URL match
the byline, and datePublished and dateModified should match the dates shown.
Test a post in the Rich Results Test to confirm.
Step 7
Sort the back catalogue into keep, improve, merge or remove
Export every post URL with its clicks and impressions for the last twelve months from Search Console, then mark each one. Keep posts that are accurate and useful. Improve posts that get impressions but have weak content. Merge posts that answer the same question, redirecting the weaker one with a 301. Remove or noindex posts that are wrong, out of date and unrecoverable. Record the decision and date for each post.
Article markup that matches the post
Most blog platforms output some structured data already. The usual faults are an author set to the organisation instead of the person, a missing author URL and dates that do not match the page. A corrected block for a fictional bakery's blog post looks like this:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Why our sourdough takes three days, and when a shortcut works",
"image": "https://example.co.uk/blog/images/sourdough-starter.jpg",
"datePublished": "2026-03-04T08:30:00+00:00",
"dateModified": "2026-07-19T10:15:00+01:00",
"author": {
"@type": "Person",
"name": "Morgan Hale",
"jobTitle": "Head baker",
"url": "https://example.co.uk/about/morgan-hale/"
},
"publisher": {
"@type": "Organization",
"name": "Hilltop Loaf Co.",
"url": "https://example.co.uk/",
"logo": "https://example.co.uk/images/logo.png"
},
"mainEntityOfPage": "https://example.co.uk/blog/sourdough-three-days/"
}
</script>Keep one Article-type block per post. If both your theme and an SEO plugin output one, switch one
off. Google accepts Article, BlogPosting or NewsArticle; the choice
matters far less than the author and dates being correct and visible.
Platform notes for blogs
WordPress
Most E-E-A-T gaps on WordPress blogs come from the theme's single post template. Check that it prints the author name and links it to the author archive, prints the dates, and includes a bio from the user's Biographical Info field. Many block themes let you add Post Author, Post Date and Post Author Biography blocks to the single template in the Site Editor without code. Enrich each author archive so it is a real profile page, not just a list of posts.
Shopify
Shopify blog articles take their author from the staff account that created them, and the author name can be edited on the article. There is no author profile page by default, so create a page for each writer and link to it from the article template in your theme's code. Check what your theme outputs as article structured data; some themes set the author to the shop name.
Squarespace, Wix and other hosted builders
Each post has an author field tied to a site contributor. Invite each writer as a contributor with their real name rather than posting everything from the owner's account, and turn on the author and date display in the blog page settings.
Static site generators
Put author, date and updated in each post's front matter, keep
author details in one data file, and generate the byline, bio and markup from the same values so they
cannot drift apart.
Awkward cases on blogs
Posts written with AI help
Google's guidance focuses on whether content is helpful and made for people, not on how it was produced, but it also says using automation mainly to manipulate rankings breaches its spam policies. A post drafted with AI still needs a named human who checked every fact, added the business's own evidence and takes responsibility for it. Where readers would reasonably want to know how the content was made, say so briefly.
Freelance and ghostwritten posts
Credit the person whose knowledge the post represents and who approved it. If a freelancer wrote it from an interview with your engineer, the engineer is the expert; an honest line such as "written with" or "edited by" can credit both.
Guest posts on your blog
Treat guest authors like staff: real name, a bio, a link to their own site and a review by you before publishing. You are responsible for what appears on your domain.
Authors who leave
Keep their name on the posts they wrote and keep their author page, noting that they previously worked with you. When someone else later revises a post substantially, add them as the reviewer or updater rather than silently replacing the original author.
Keeping new posts right
- A pre-publish checklist. Named author, direct answer in the opening, at least one piece of the business's own evidence, sources for outside facts, dates visible, disclosures in place.
- One author per real person. Disable or rename shared publishing accounts so they cannot become the default byline again.
- A yearly archive review. Repeat the keep, improve, merge or remove exercise every year, starting with posts on topics that change fastest.
- Re-run the checker after template changes. Theme updates are the most common reason bylines, bios and dates disappear.
1. Is it bad to publish blog posts under admin or the company name?
It is one of the clearest weak signals a blog can show. A post credited to admin tells the reader nothing about who wrote it or why they know the subject, and the rater guidelines ask raters to find out who is responsible for content. For a company announcement, crediting the business can be fine. For advice, reviews and guides, name the person who wrote or approved it, and link to a page that explains their background.
2. Should I delete old blog posts that get no traffic?
Not automatically. A post with no traffic may still be accurate and useful, or it may be a good candidate to merge into a stronger post on the same subject. Delete or noindex posts that are wrong, out of date and not worth fixing, or that have nothing to offer a reader. Where a removed post has links pointing to it or a closely matching page exists, redirect it with a 301 so visitors and link value are not lost.
3. Can AI-written blog posts meet E-E-A-T standards?
They can if a qualified person does the real work of checking and improving them. AI tools produce fluent text that tends to repeat what is already published and can include confident errors. To meet the standard, a named person with knowledge of the subject needs to verify every fact, add the business's own experience and evidence, remove anything generic and take responsibility for the result. Publishing large numbers of unedited AI posts mainly to attract search traffic risks breaching Google's spam policies.
4. How long should a blog post be for good E-E-A-T?
Length is not the measure. Google says there is no minimum word count, and a long post padded to match competitors often reads worse than a short one that answers the question directly. What matters is whether the post fully answers what the reader came for, shows real knowledge and gives evidence for its claims. Some questions need three hundred words and others need three thousand. Cut sections that restate the obvious and spend the words on specifics.
5. Do I need an author bio at the bottom of every blog post?
A short bio at the end of each post is a good default for advice and review content, because readers who reach the end are often deciding whether to trust you. It should pull from one author profile so it stays consistent everywhere. On a site written entirely by one person, a byline linked to a strong about page can do the same job. What should not happen is a post with no way to find out who wrote it.
6. Should blog posts use Article or BlogPosting markup?
Either works. BlogPosting is a more specific type of Article, and Google's article structured data documentation accepts Article, BlogPosting and NewsArticle. The type you choose matters much less than the content of the block: the author should be a Person with a name and a URL matching the visible byline, and datePublished and dateModified should match the dates shown on the post. Make sure only one Article-type block is output per post.
7. How should I credit a post written by a freelancer from our expert's notes?
Credit the person whose knowledge the post contains and who approved it, usually your in-house expert. If you want to credit the writer as well, use an honest line such as written with, or edited by, alongside the expert's byline. What you should not do is put an expert's name on a post they have never read, or credit a freelancer as an expert in a field they do not work in. The byline should tell the reader whose expertise they are relying on.
The E-E-A-T Checker scans a post for its byline, bio depth, Person markup, citations, update dates, trust pages and reviewer disclosures, and links each gap to the guide that fixes it.
Open E-E-A-T Fixes →