How to Fix E-E-A-T: Show First-Hand Experience in Content
This check flags content that gives readers no evidence its author has actually used, tested, visited or done the thing being described. By the end of this guide, your key pages will carry verifiable proof of experience: original photos, documented test methods, real results, named authors and first-person insights that a copycat page could not reproduce.

Why it matters
Google's Search Quality Rater Guidelines list Experience as the first E in E-E-A-T, and its helpful-content guidance asks whether content shows first-hand expertise, such as having used a product or visited a place. Reviews, tutorials and comparison pages that only summarize other sources tend to lose ground to pages with original evidence. AI answer engines also prefer citing sources that add unique facts like measurements, prices paid and failure cases, because those details can't be found elsewhere.
Readers notice too: stock photos and vague claims raise bounce rates and lower conversions.
What you need
Step-by-step fix
Audit priority pages for missing experience signals
Open each priority page and score it against five questions:
- Is there at least one photo, video or screenshot we created ourselves?
- Does it say how we know this (tested, used, visited, built)?
- Are there specific numbers from our own work (time, cost, measurements, results)?
- Is a real, named person accountable for it?
- Is there at least one insight a competitor couldn't copy, such as a drawback, surprise or lesson learned?
Pages that miss three or more go to the top of your list.
URL | Original media | Method stated | Own data | Named author | Unique insight | Score /best-standing-desks | no | no | no | no | no | 0/5 /guides/migrate-to-ga4 | screenshots | yes | no | yes | no | 3/5
Collect proof from the people who did the work
Interview the tester, technician or consultant for 20 minutes per page. Ask for photos, raw notes, spreadsheets, before/after screenshots and the one thing that surprised them. Record exact figures, for example 'assembly took 47 minutes' rather than 'quick to assemble'.
Get written permission before using client names or data, or anonymize it as 'a 40-person SaaS client'.
Replace stock images with original, captioned photos
Swap stock and manufacturer images for photos or screenshots you took. Use captions that state who, where and when, because captions carry context that alt text alone doesn't. Keep alt text descriptive for accessibility.
Show real-use details such as wear, scale next to a familiar object, or the actual settings screen.
<figure> <img src="/images/desk-flexi-wobble-test.jpg" alt="Flexi Pro desk at 120 cm height with a phone accelerometer app on the desktop" width="1200" height="800" loading="lazy"> <figcaption>Wobble test at full height, Example Co office, March 2026. Photo: Jane Doe.</figcaption> </figure>
Add a 'How we tested' or 'Our experience' section
Place a short method box near the top of the page. State what was tested, for how long, by whom, under what conditions, and what you measured. For service pages, use a mini case study instead: the starting situation, what you did, the measured result and the timeframe.
Include at least one honest limitation or downside.
<aside class="how-we-tested" id="how-we-tested">
<h2>How we tested</h2>
<ul>
<li>8 desks bought at retail price (not supplied by brands)</li>
<li>Used daily by 3 staff for 90 days, Jan–Mar 2026</li>
<li>Measured wobble at 120 cm with a phone accelerometer, noise with a dB meter at 1 m</li>
<li>Lead tester: <a href="/team/jane-doe">Jane Doe</a>, workplace ergonomics consultant</li>
</ul>
<p>Limitation: we did not test weight capacity above 80 kg.</p>
</aside>Rewrite generic passages with first-person specifics
Find sentences any competitor could have written, such as 'easy to install' or 'great customer service', and replace them with what happened to you. Use first person where it's natural ('we', 'I'). Add a short 'What we'd do differently' or 'Who should skip this' paragraph.
Remove specs and claims you can't personally verify, or attribute them to their source.
Before: "The Flexi Pro is sturdy and easy to assemble." After: "Our Flexi Pro took 47 minutes to assemble with two people. At 120 cm it wobbled 40% less than the cheapest desk we tested, but the motor hit 52 dB, loud enough that Jane stopped adjusting it during calls."
Attach a named author with a bio and markup
Add a visible byline linking to an author page. The author page should list the person's relevant hands-on background, years in the role, and links such as LinkedIn. Then add Article JSON-LD that connects the author and the original images.
Keep dateModified honest, and only change it when the content materially changes.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Best Standing Desks 2026: 8 Desks Tested for 90 Days",
"datePublished": "2026-03-20",
"dateModified": "2026-03-20",
"author": {
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/team/jane-doe",
"jobTitle": "Workplace Ergonomics Consultant",
"sameAs": ["https://www.linkedin.com/in/janedoe-example"]
},
"publisher": {"@type": "Organization", "name": "Example Co", "url": "https://example.com"},
"image": [{
"@type": "ImageObject",
"contentUrl": "https://example.com/images/desk-flexi-wobble-test.jpg",
"creator": {"@type": "Person", "name": "Jane Doe"},
"creditText": "Example Co",
"copyrightNotice": "© 2026 Example Co"
}]
}
</script>Check the page as a skeptical reader would
Run the five-question audit from step 1 again and aim for 5/5. Run your main images through Google Lens. If identical copies show up on other sites, they aren't seen as original.
Validate the markup, then track the page in Search Console for 4-8 weeks, comparing clicks and average position to the period before.
Platform-specific notes
WordPress
WordPress resizes uploads and can strip metadata from the generated sizes. Write IPTC and XMP metadata before upload, and check the served file. Yoast SEO and Rank Math already output Article/Person schema from the post author, so complete the user profile (Users > Profile: biographical info, website, social profiles) instead of adding a duplicate Person block. Build the 'How we tested' box as a reusable block pattern (Appearance > Editor > Patterns).
Shopify
Product pages rarely have bylines. Show experience through original product photos and video under Products > [product] > Media, plus a metafield-driven 'Tested by our team' section added via Online Store > Themes > Customize. Blog posts use the staff account name as the author, so create a real staff account per writer. Shopify's CDN may re-encode images, so confirm credits survive by checking the served file.
Webflow
Create an Authors CMS Collection (name, bio, photo, LinkedIn) and reference it from your Blog Posts collection. Bind the byline to it, and add the JSON-LD in Page Settings > Custom Code > Before </body> using CMS field embeds for name and URL.
Wix
In the Wix Blog, set each writer up under Blog > Writers with a profile and bio. Add the 'How we tested' box with a text or HTML embed element. Custom JSON-LD goes in the page's SEO settings under Advanced SEO > Structured data markup. Avoid adding images from the Wix or Unsplash media libraries to review content.
Next.js
Render the JSON-LD server-side in the page component (a <script type="application/ld+json"> with JSON.stringify of your data) so it appears in the initial HTML. If you serve images through next/image, the optimized output usually drops metadata. Keep the original file reachable and use it as the contentUrl in ImageObject.
Check that it worked
✅ How to verify
- Re-score each fixed page with the five-question checklist: original media, stated method, own data, named author and unique insight should all be present above or near the fold.
- Upload your main images to Google Lens (lens.google.com). No identical matches on unrelated sites confirms they read as original.
- Paste the URL into Google's Rich Results Test (search.google.com/test/rich-results) or validator.schema.org and confirm the Article, author Person and ImageObject creator fields parse without errors.
- In Search Console, open Performance > Pages, filter to the updated URL, and compare 28 days after the change with the 28 days before for clicks, impressions and average position.
⚠️ Common mistakes
- Adding a 'we tested' claim with no visible evidence. A method box without photos, numbers or a named tester reads as fabricated and can hurt trust more than saying nothing.
- Using AI-generated or lightly edited stock images as 'original' photos. They are easy to spot and often appear elsewhere on the web.
- Inventing author personas or credentials. Raters and readers check LinkedIn, and a fake expert damages trust for the whole site.
- Bumping dateModified or the '2026' title year without new testing or content. That signals freshness you can't back up.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What is the difference between experience and expertise in E-E-A-T?
Experience means the creator has personally done the thing: used the product, visited the place or run the campaign. Expertise is knowledge or skill in the subject, often shown by credentials. A product review needs experience most. A tax or medical page needs expertise most, and the strongest pages show both.
Does Google read photo EXIF data to judge first-hand experience?
Google has not said EXIF is a ranking signal for experience. It does read IPTC metadata (Creator, Credit Line, Copyright Notice) to show image credits in Google Images. The main value of original photos is that readers and quality raters can see real use, and that the images aren't duplicates of content found elsewhere.
Can AI-written content show first-hand experience?
Only if a real person supplies the experience. AI can help structure and edit, but the photos, measurements, results and opinions must come from someone who did the work, and that person should be named and accountable for the page.
How do I show experience on a service business site with confidential clients?
Publish anonymized case studies, for example 'a 40-person B2B SaaS company'. Include the starting metrics, what you did, the timeframe and the measured outcome. Add screenshots with sensitive data blurred, and name the consultant who led the work. With client permission, a named testimonial linked to the case study adds further proof.
How to Add Author Bios and Expert Profile Pages to Your Site
How to Fix Search Intent Mismatch on Your Pages
How to Fix Missing Cited Sources and Statistics in Articles
How to Fix Topical Coverage Gaps Against Your Competitors
How to Fix Thin Service and Product Pages (Under 500 Words)
How to Fix Spelling and Grammar Errors on Your Website