Key Takeaways
- Expertise is stronger when supported by specific, traceable evidence.
- Valuable content often already exists in project files and employee knowledge.
- SME interviews should connect expert observations to real records.
- Evidence capture works best when built into existing workflows.
- A maintained evidence library strengthens future content over time.
Claiming experience is easy. Proving it takes more. That proof comes from specific observations, project records, photographs, measurements, and the reasoning behind real decisions. Google’s quality rater guidelines put experience first in E-E-A-T for exactly this reason. Raters are asked whether content shows firsthand involvement, not just subject knowledge.
Consider a commercial contractor that promotes decades of experience handling complex projects. Its portfolio may show polished photographs of completed buildings. But what made those projects complex? What challenges arose, and how did the team solve them?
The evidence probably exists. Site photographs document unexpected conditions. Project notes explain why plans changed. Managers can describe the decisions that kept complications from delaying the work.
The company does not lack experience. Its website simply does not show it.
According to Straight North Senior SEO & GEO Strategist Bob Hand, this disconnect is common. Companies often have valuable firsthand knowledge but no reliable way to move it from project files, internal systems, and employees’ memories onto the page.
Closing that gap takes more than asking an expert to write an article or turning every successful project into a case study. Companies need a repeatable process for uncovering what their teams know, connecting those insights to tangible evidence, and using that proof to strengthen the website. Customers get useful information, while search engines get original details that help them evaluate the page.
That process starts with defining what counts as evidence and finding where company knowledge already lives. From there, companies can interview subject-matter experts, capture evidence during the work, turn it into on-page proof, and keep it organized and current.
Evidence vs. Assertion: What Demonstrates Firsthand Experience?
Calling your company experienced is an assertion. Evidence shows what your team observed, how it responded, and what happened next.
Strong evidence must also be traceable and clear about its limits. As Bob explains, companies often overlook both:
I also think that companies tend to skip the limits of the evidence. One project can show that something happened, it can’t prove that that happens everywhere or every time. I think good evidence is tied to specific evidence that’s traceable internally, so you have evidence of that project. You should be able to go back, someone at the company should be able to identify that project, report or source behind that published example, even if those details aren’t public. That makes the content easier to verify, update, and defend later.
“We overcame a difficult installation” is a generic claim. Compare it with: “We found six inches less clearance than the drawings indicated, so we changed how the item was mounted.” The second version names the constraint and shows how it shaped the team’s response.
“The important details are ones that actually affected what the team did — a measurement, a constraint, an unexpected condition, or a failed first approach.”
Senior SEO & GEO Strategist | SEO & GEO Authorship Expert
A few relevant details can demonstrate more expertise than several paragraphs of polished marketing language. Use this test: What information on the page could only have come from this company’s experience?
Find the Knowledge Your Company Already Has
Companies often think they need new research or a large internal study to add firsthand experience to their content. In reality, much of that material already exists. It simply has not been connected to the content process.
Useful knowledge may be sitting in sales calls, support tickets, CRM notes, project closeout files, testing logs, field photographs, training materials, and the memories of employees closest to the work. Start with the teams that hear customers’ questions firsthand.
Start With Sales and Support Conversations
Sales and support teams hear where customers get stuck before and after a purchase. As Bob explains, those conversations can reveal both the questions the website should answer and the language customers use:
They show you where customers repeatedly get stuck. Sales calls reveal objections and questions before someone buys, price, timing, implementation, risk comparisons, with alternatives. I think support tickets show you what becomes confusing once someone actually begins using your product or service. Repetition is especially useful because it indicates that it’s a recurring issue. If a sales team has answered the same question 50 times, there’s a strong argument that the website should be answering it, too. They also capture the customer’s vocabulary, which often differs from how the company talks about itself internally, so that may inspire how you word that question when answered in an FAQ or in content on your website to more closely match what people are actually searching for.
Those insights can shape service-page copy, FAQs, troubleshooting articles, and clearer product instructions. Customer-facing teams are only one source, however.
Look Beyond the Marketing Department
Marketing often sees only the polished result. Operations, engineering, implementation, service, support, and project management retain the records that show how the company reached it.
Those materials reveal what the team tested, what failed, why the plan changed, and which conditions shaped the final decision. Together, they show how the company responds when work does not go as planned.
Those employees do not need to become content writers. They only need to leave a usable trail of observations and records. The content team can verify the material, add context, and translate it for customers.
Begin With the Pages That Matter
Once you know where the evidence lives, focus on the pages where it can make the greatest difference.
Start with pages that already influence the business:
- Service pages that generate leads
- High-traffic pages that shape first impressions
- Commercially important pages that continue to underperform
Competitor pages are worth reviewing, too. They can show where another company is gaining ground by presenting its experience more clearly.
Next, examine the claims each priority page asks readers to believe. If a page says the company solves complex problems, improves efficiency, or reduces risk, what internal evidence supports that claim? A photograph, measurement, report, or expert observation may already make it more specific and credible.
Treat this as a targeted search rather than a companywide knowledge-management exercise. As Bob notes, 10 strong pieces of evidence on high-priority pages can create more value than thousands of internal files no writer knows how to use.
Starting small also makes the process easier to test and refine. The next step is talking with the people who can explain what the evidence means.
Use SME Interviews to Uncover Examples and Evidence
When a subject-matter expert (SME) says, “We see this problem regularly,” the answer may point to valuable firsthand experience. But it needs more detail before it becomes useful content.
Ask follow-up questions that connect the observation to a specific project, customer decision, or result. If the conversation becomes abstract, bring it back to an actual situation and ask what happened.
Ask Questions That Reveal the Observation
Start with what the expert noticed and why it mattered:
- What commonly happens that a general explanation leaves out?
- What do customers usually misunderstand?
- What would you notice that someone less experienced might miss?
- What changed your recommendation?
- When would the standard recommendation not apply?
Questions about exceptions are especially useful. How a team responds when the standard recommendation does not apply can reveal the judgment behind its expertise.
Ask Questions That Lead to Proof
Once the expert identifies a useful observation, ask for the records that support it:
- Where have you seen this happen?
- Can you identify a specific project?
- Do we have a photograph, report, or measurement?
- How did you determine what was happening?
- What did you test?
- What did you try first that did not work?
- What happened afterward, and how was the result measured?
An interview reveals what may be worth saying. The records determine how confidently the company can say it.
Match the Claim to the Available Evidence
Sometimes an interview surfaces a useful claim before anyone has found the supporting records. If those records remain unavailable, the wording should reflect that uncertainty.
As Bob explains, the strength of the claim must match the available evidence:
Match the certainty of your language on your page to the certainty of the evidence. Our service manager commonly sees this is different from, our records show this occurs in 40% of all projects. Look for another source, that’s project records, photos, emails, CRM notes. Any other people that are involved, you can ask them. If you can’t substantiate the specific version of the claim, you can either qualify it or leave that precise claim out. At that point, being more vague is honest. You want to actually say things that you can back up with evidence. The important thing is to not let the writing process turn into a fuzzy recollection of hard statistics. You actually want to be able to leverage those and bring up those specifics in the page.
“Our service manager commonly encounters this issue” is a professional observation. “This occurs in 40% of projects” is a statistic, and statistics need documented data behind them. Without that proof, qualify the claim or drop the number.
Capture Evidence Before Its Context Disappears
Project context fades quickly. Months later, the company may still have a photograph or measurement, but no one remembers what it shows or which conditions shaped the decision. Capturing those details during the work creates a more accurate record of the team’s expertise.
Build Evidence Capture Into Existing Workflows
Evidence collection is more likely to last when it fits into work the team already performs. A separate marketing assignment is easier to delay or forget.
I would make the evidence-capturing part of this equation part of something they’re already doing, rather than a separate marketing assignment. You can maybe add three questions to the project closeout. Specify a few photographs to take at particular milestones, let someone record a one-minute voice memo, just something that captures the specific issues that come up in the project’s course. The person closest to the work should have the smallest possible task. I think if you have somebody else organizing it, adding context, checking permissions, and deciding where it belongs, that can make it a little more implementable, without becoming a burden. If the technician needs to understand your SEO strategy and content calendar before they can contribute, you’re probably already designing the workflow backwards. It’s important that they’re leaving the evidence for you to find, and that it’s organized in a way that you can easily do so. To not overly burden your actual team doing the work. As long as that trail exists and you can go down it, that’s important.
This division of responsibility keeps the process manageable. Operational employees leave a clear evidence trail. Someone else organizes it, adds context, confirms permissions, and makes it accessible to writers.
Preserve the Context That Makes Evidence Useful
Capturing a photograph, statistic, or project note is only the first step. The context around it is what keeps the evidence useful.
Connect each item to its project, collection date, and source. Note the relevant conditions, what the item demonstrates, and whether it is approved for public use.
That context matters when someone who was not involved in the work uses the evidence later. Without testing conditions or a clear explanation, even a precise-looking record can mislead.
Turn Raw Evidence Into Useful On-Page Proof
Once the evidence is captured and organized, the next question is how to use it. Most examples do not need a full case study. A short, specific proof point placed where someone is making a decision may have more impact.
- A service page might use three sentences to explain the problem, the team’s response, and the result.
- An article could add a field observation tied to a recurring condition.
- A photograph becomes stronger when its caption tells readers what to notice.
- Even a brief note can explain how a test was conducted, why an option was rejected, or when the usual recommendation does not apply.
Before-and-after comparisons, decision tables, and lists of common mistakes can also demonstrate experience. Include enough detail to support the point without turning the page into a project report.
Full case studies still have value, but they take time. They may require interviews, customer approval, and a complete narrative. Smaller proof points can be published sooner on service pages, articles, FAQs, and service-area pages.
Match the Evidence to the Reader’s Decision
Choose evidence based on the decision the reader needs to make. A service-page visitor is often evaluating the company: Can this team handle the situation? What complications may arise? How does it respond when work does not go as planned?
An informational reader needs something different. They may want to know how a test was conducted, which variables mattered, or when a recommendation no longer applies. For them, the method and limits may matter more than the outcome.
Matching the evidence to the reader keeps it relevant. It also prevents companies from adding examples simply to appear more authoritative.
“The evidence should help the reader make the particular decision that brought them to that page.”
Senior SEO & GEO Strategist | SEO & GEO Authorship Expert
Before-and-after comparisons deserve special care because they can imply more than the evidence proves.
Make Before-and-After Comparisons Credible
A credible before-and-after example begins with a clear baseline. Readers need to know what was true before the work, what changed, and how the result was measured.
Identify the relevant period and conditions as well. If numbers are involved, measure the same thing the same way before and after. Otherwise, the difference may look meaningful without being a fair comparison.
Causation is harder to establish. If sales rise after a website redesign, the redesign may have contributed. It may not deserve all the credit. Other campaigns, market conditions, seasonal demand, or sales activity could have played a role.
A useful comparison shows the improvement without claiming more than the evidence supports. Once that standard is clear, the company needs a practical way to store and manage the underlying records.
Create a Practical Evidence Library
Evidence loses value when writers cannot find it. Years of photographs, reports, and project notes cannot strengthen content if they remain scattered across phones, inboxes, and department folders.
The system does not need to be sophisticated. A spreadsheet and organized shared folder may be enough. Index each item by topic, storage location, permission status, approved wording, and review date, while preserving its project context.
Use a simple test: Can a writer ask, “Do we have anything real about this?” and find an answer within a few minutes? If not, the system may be too complicated or disconnected from the content team.
Finding the material is only the first step. Before using it, the team needs to decide whether it is ready to publish.
Evaluate Evidence Before Publishing It
Before publishing evidence, confirm that it is relevant, traceable, current, and no stronger than the record supports. Also review customer permissions, personal information, confidential records, trade secrets, and proprietary processes. When needed, anonymize the public example while keeping the original record internally.
Once an example passes those checks, it may support more than one piece of content.
Reuse Evidence Without Repeating Content
One project can support several stories. An implementation page might explain a decision made during installation. A troubleshooting article could use a problem discovered later. An FAQ might answer a customer question that surfaced during the same work.
The source is the same, but each page draws on the detail most relevant to its reader.
Before reusing an example, ask why it belongs on that page. If the connection is clear, reuse adds depth and consistency. If the same anecdote appears on unrelated pages simply because it is available, it stops acting as evidence and starts looking like decoration.
Evidence can also lose value as it ages, which makes ongoing ownership essential.
Assign Owners to Claims That Can Change
Some claims have a natural shelf life. Employee counts, office locations, customers served, completed projects, turnaround times, and pricing can become outdated. Product capabilities, software screenshots, regulations, and industry standards may change even faster.
Bob calls these changing facts “content debt.” Every time-sensitive claim creates something the company will eventually need to review.
Assign an owner and review date when the claim is published. Annual reviews may be enough for stable information, while pricing, software, regulations, and other fast-moving topics may need quarterly checks.
Clear ownership prevents accurate evidence from becoming misleading over time. AI can help with the administrative work, but it cannot take responsibility for the evidence itself.
Use AI to Organize Evidence, Not Create It
AI is most useful when it helps the team process material that already exists. Bob explains where it fits:
AI is very useful for processing material that already exists. So, transcribing interviews, categorizing notes, finding themes across support tickets, organizing examples. It can also help a writer see connections that they might have missed in a large amount of material. That shouldn’t supply the missing fact, or the evidence, because that fact would make the example stronger, and if it’s being surfaced through an AI tool, you’re scraping it from someone else, and it’s less persuasive, it’s more generic content. If nobody documented why a decision was made, AI can’t invent a plausible explanation and call it company experience. That’s fundamentally dishonest and doesn’t really support growth from an organic perspective. My shorthand is, AI can organize the record, it can’t create it.
A person still needs to confirm each claim’s accuracy, relevance, context, permissions, and limits. That human review protects the company’s credibility and preserves what makes the evidence valuable: it came from real work.
Original Evidence Creates a Compounding Advantage
Several companies can explain the same service accurately and still sound nearly identical. Original evidence gives readers and search systems something competitors cannot easily reproduce.
That contribution might be a recurring sales question, an observation from a completed project, or the result of an internal test. It could also be an unexpected constraint, a failed approach, or a condition that changed the usual recommendation.
SEO professionals often call this added value “information gain”: useful material that was not already available in competing content.
This distinction matters more as AI makes generic explanations faster to produce. A familiar summary may be accurate, but it gives readers and search systems little reason to prefer one company over another. Firsthand evidence shows what the company learned through its own work.
The value grows as the company captures that evidence consistently:
I’d say that the advantage starts to compound over time. Every project they complete can generate another photograph, observation, comparison, test result, mistake, or customer question. After several years, they build a bank of real examples and observations that only their company could have collected. And you might have completed just as much work, but if none of it was captured, your content team still starts from scratch every time, possibly pulling generic con tent from Google or AI tools to create content that’s really not going to move the needle. That’s the bigger competitive advantage here, a process where doing more real-world work continuously makes the company’s future content stronger. You can think of it as an authority flywheel. The more you commit to collecting and using evidence, the more you’ll have to use.
That is the authority flywheel. Each project adds examples and observations that can strengthen future content — and that competitors or generic AI-generated content cannot easily reproduce.
Make Your Experience Visible
Before publishing a claim, ask four questions: What did the team observe? What can the company show? How did the team respond? What happened, and what does the example prove?
When companies build those questions into the content process, experience becomes visible. The result is content that gives customers specific, traceable reasons to believe it.
