Adding First-Hand Experience Signals
Plenty of pages are accurate and still unconvincing, because they read like a summary of other pages: correct in general, vague in every detail, with no sign that the writer has ever done the thing. Experience is the first E in E-E-A-T, and it is shown through specifics that only come from doing the work.
This guide explains what those specifics look like on how-to guides, service pages, case studies and advice, how to get them out of the people in your business who actually do the job, and how to add them without turning a useful page into a diary.
What experience looks like on a page
Google added Experience to its quality rater guidelines in December 2022. The idea is simple: someone who has used a product, visited a place, run a process or lived through a situation can offer something that research alone cannot. Raters are asked whether content shows that kind of first-hand knowledge, and a page can be valuable because of it even when the writer has no formal qualifications.
Experience is not a claim like "we have years of experience". It is evidence woven into the content. Compare two versions of the same advice from a fictional plumbing firm, Kestrel Heating:
Generic:
Low boiler pressure is a common problem. Check the pressure
gauge and top up using the filling loop if needed. If the
problem continues, contact a professional.
Experienced:
On most combi boilers we service, the gauge should sit between
1 and 1.5 bar when the heating is cold. If yours keeps dropping
back below 1 within a week of topping up, the filling loop is
rarely the answer: in our jobs last winter the usual culprits
were a weeping radiator valve or a failed pressure relief
valve dripping outside. Check the copper pipe that exits the
wall near the boiler for a drip or a green stain first.Both are correct. Only the second shows that someone has stood in front of these boilers. The signs are specific ranges, a pattern noticed over many jobs, a named cause, and a practical check a reader can do. That is what the checker and, more importantly, readers look for.
| Signal | What it shows | Example |
|---|---|---|
| Precise detail | The writer knows the exact setting, size, time or step | "Use a 10 mm spanner; the 11 mm slips" |
| Patterns across cases | They have seen it many times | "Nine times out of ten it is the valve, not the pump" (only if true in your records) |
| Mistakes and surprises | They have hit the problems | "The first time, we forgot to bleed the top floor" |
| Original visuals | They were there | A photo of the actual valve with the stain |
| Own numbers | They measured or counted | "Our last 40 installs took 1.5 to 2 days" |
| Real outcomes | The advice worked for someone | A short case with the result and the customer's permission |
Why businesses end up with generic pages
The usual cause is not a lack of experience; it is that the person who writes the website is not the person who does the work. A marketing assistant, an agency or an AI tool drafts a page from what is already online, and the owner or technician who could add the telling details never sees it. The result reads like every competitor's page because it was built from them.
The fix is therefore mostly about process. The knowledge exists in your engineers, advisers, chefs or consultants; it simply needs a route onto the page. A fifteen-minute conversation with the right person usually yields more useful detail than a day of research.
Questions that draw out experience
When you sit down with the person who does the work, avoid asking them to "tell you about" the topic; you will get the textbook version. Ask about specific jobs instead:
- What was the last time you dealt with this? What happened?
- What do customers usually get wrong before they call you?
- What is the first thing you check, and why that first?
- What is the most common cause in practice, as opposed to the one in manuals?
- What tools or settings do you actually use, and which do you avoid?
- When have you seen this go badly wrong? What did you learn?
- How long does it really take, and what makes it take longer?
- What would you tell a friend in this situation that you would not put in a brochure?
Write down numbers, names of parts or tools, and any story with a clear outcome. These become the specific sentences, photos and examples that replace generic text.
The fix, step by step
Step 1
Find the pages that could have been written by anyone
Go through your guides, service pages and advice articles and ask of each one: could a competitor publish this page unchanged? If swapping your business name for theirs would leave it just as true, it lacks experience. Start with the pages that matter most to customers and those the E-E-A-T Checker flags. Note for each page who in your business actually does the work it describes, because that person is your source for the rewrite.
Step 2
Interview the person who does the work
Book fifteen to thirty minutes with the technician, adviser or owner who handles this job, and ask about real recent cases rather than the topic in general. Ask what customers get wrong, what they check first, the most common cause in practice, how long it takes and what went badly once. Record and transcribe the conversation with their permission. Pull out every number, tool, place and outcome they mention, since these become the specifics that replace generic sentences.
Step 3
Swap general statements for specific ones
Go through the page line by line and replace vague phrases with the details from your interview. Turn "it may take some time" into the real range you see, "use the right tools" into the tools you actually use, and "common causes include" into the order you check things and why. Keep only numbers you can back with records. Credit the person where it helps, for example our engineer checks, so readers know the knowledge comes from practice.
Step 4
Add your own photos, screenshots and figures
Replace stock images with pictures taken on real jobs, in your own premises or of your own screens, showing the thing the text is describing. Ask staff to photograph interesting jobs as a habit and keep a shared folder. For software or online processes, use screenshots of your own account with personal data removed. Add figures from your own records, such as times, costs or counts, and say where they come from and what period they cover.
Step 5
Include what went wrong and what you learned
Add at least one honest note about a mistake, a surprise or a situation where the usual advice did not work, and what you do differently because of it. This could be a short paragraph, a tip box or a line in a step. Readers trust a guide more when it shows the writer has hit the problems they are worried about, and it often answers the exact question that sent them searching. Keep it relevant and brief, not a confession.
Step 6
Show a real outcome with permission
Where a page describes a service or method, add a short example of it working: the situation, what you did, and the result, ideally with a before and after photo or a number. Get written permission from the customer before naming them or showing identifiable details, and anonymise otherwise. Never compose composite or invented cases and present them as real. A single genuine, specific outcome is more convincing than a paragraph of promises about what you can do.
Step 7
Build experience capture into how you work
Make gathering experience routine so pages do not drift back to generic. Add a photo and a one-line note to your job sheet or project template, keep a running list of questions customers ask, and schedule a short review of key pages with the relevant expert every six or twelve months. When you publish new content, require at least one detail from real work, whether a photo, a figure or a lesson learned, before it goes live.
Experience on different kinds of page
How-to guides
Show the steps as you actually do them, with your own photos of each stage, the real time each part takes, the mistakes to watch for and what the finished result looks like. Mention the tools and materials by type and size, and why you prefer them.
Service pages
Describe what happens on a real visit or project from the customer's side: who turns up, what they check, how long it takes, what the customer needs to do, and what can change the price. Photos of your team at work beat any stock image of a smiling person in a hard hat.
Case studies
A case study is experience in its purest form, but many are thin: a logo, a quote and a vague "great results". Include the starting situation in numbers where possible, the constraints, what you tried, what did not work, the outcome and how it was measured. Get the client's sign-off on anything identifiable.
Advice and opinion
Ground each recommendation in something you have seen: "we have moved three clients off this setup, and each time the reason was..." Say clearly where you are giving a view rather than a fact.
Local and travel content
Say when you were there, what it was actually like, and details a visitor needs that listings leave out, such as where to park, which entrance to use or when it gets busy. Your own photos with the season visible help readers judge how current the information is.
What not to do
- Adding "In my experience" to generic text. The phrase is not the signal; the detail that follows it is. If nothing specific follows, delete the phrase.
- Inventing anecdotes. Made-up stories, composite customers presented as real, or experiences that belong to someone else are deceptive, and they tend to fall apart on detail.
- Stock photos with a caption claiming they are yours. Readers increasingly recognise stock images, and a reverse image search takes seconds.
- Burying the answer in a story. Experience should make the useful content better, not push it further down. Lead with the answer and use experience to support it.
- Sharing customer details without consent. Names, addresses, photos of homes or anything identifying need permission, and some sectors have extra confidentiality duties.
Experience and AI-assisted writing
AI writing tools are good at producing the generic version of a page, because they are trained on what is already published. That is exactly the part that lacks experience. If you use them, use them for structure and first drafts, then add the details from your interview, your photos and your records, and check every claim. Google's guidance focuses on whether content is helpful and original, not on how it was produced, but a page that only restates what is already out there offers readers little reason to choose it.
After rewriting, run the E-E-A-T Checker again. It cannot confirm that a story happened, but it can show whether the page now carries the visible signals that go with first-hand work, such as a named author with relevant background and specific, sourced detail.
1. What counts as first-hand experience for E-E-A-T?
Having actually done, used, visited or lived through what the content describes, and showing it through detail. That might be a technician describing the faults they see most often, a reviewer who used a product for weeks, a traveller who visited a place last month, or a business owner explaining how a process works in their shop. The evidence is in specifics: precise figures, original photos, patterns noticed over many cases, mistakes made and real outcomes, rather than a statement that you are experienced.
2. Can I show experience if I am not the person who does the work?
Yes, by getting it from the person who does. Interview the engineer, adviser or owner about real recent cases, record the conversation, and use their details, figures and stories in the page. Credit them in the text or as a contributor, and ideally ask them to check the finished page. Writers who are not practitioners can produce excellent experienced content this way, as long as they report what the practitioner said accurately and do not add invented detail.
3. Is it enough to write in the first person?
No. Writing I or we does not show experience on its own; plenty of generic content is written in the first person. What matters is what follows: a detail that only someone who did the work would know, a number from your records, a photo from the job, or a lesson from something that went wrong. If a first-person sentence could be pasted onto a competitor's site unchanged, it is not adding experience, however personal it sounds.
4. Do I need original photos on every page?
Not on every page, but on pages that describe physical work, products, places or processes, your own photos are one of the clearest signs of experience. A single real photo of the job, the product or the screen is worth more than several polished stock images. For topics where photos do not make sense, such as tax advice, specific examples, worked figures and anonymised cases do the same job. Label any images that are not yours.
5. How can I use customer stories without breaching privacy?
Ask the customer first and get their agreement in writing, ideally by email, stating exactly what you will publish: their name or not, photos, location and results. Where they would rather not be named, remove identifying details such as street names, company names and faces, and say the example is anonymised. Never publish health, financial or other sensitive details without explicit consent. Some professions, such as healthcare and law, have additional confidentiality rules that apply on top of data protection law.
6. Will adding experience improve my rankings?
It can help, but there is no guarantee and no single signal that switches it on. Google's systems aim to reward helpful, original content, and first-hand detail is one of the things that makes content original and more useful than pages that restate what is already published. The more reliable benefit is with readers: specific, experienced pages answer their real questions, which tends to improve how long they stay, whether they trust you and whether they get in touch.
The E-E-A-T Checker scans your page for bylines, bio depth, Person markup, citations, update dates, trust pages, reviewer disclosures and signals for sensitive topics, and links each finding to the guide that fixes it.
Open E-E-A-T Fixes →