SEO employers want evidence.
They want to know that you haven't just completed keyword research, written recommendations, fixed technical issues, or produced content briefs.
They want to know whether your work actually made a difference.
Did organic traffic grow?
Did rankings improve?
Did conversions increase?
Did technical fixes improve indexation?
Did your strategy generate more qualified leads?
Did organic search contribute more revenue?
That's straightforward when you're allowed to show everything.
But many SEO professionals can't.
You might work for an agency with strict client confidentiality agreements.
You may have signed an NDA.
Your employer may prohibit sharing analytics screenshots.
Revenue figures might be commercially sensitive.
You may not even be allowed to identify the client.
That creates an obvious problem when you're applying for your next SEO role:
How do you prove your impact without revealing information you're not allowed to share?
The answer isn't to avoid discussing results altogether.
It's to learn how to present your SEO wins in a way that demonstrates your skills while respecting confidentiality.
Here's how.
Client Confidentiality Is Normal in SEO
First, don't assume that being unable to name clients puts you at a disadvantage.
Confidentiality is common across:
Agency SEO.
Enterprise SEO.
Ecommerce.
Finance.
Healthcare.
Legal services.
SaaS.
B2B.
Highly competitive industries.
Hiring managers understand that candidates may have restrictions around what they can disclose.
In fact, being careless with confidential client information can create a worse impression than refusing to disclose it.
If you casually show a prospective employer another company's private revenue dashboard, they may reasonably wonder:
Would you do the same with our data one day?
Professional discretion is valuable.
You Don't Need to Name the Client to Tell the Story
Suppose you worked with a well-known financial services company.
You don't necessarily need to say:
"I worked with Company X."
You could say:
"I worked on organic search strategy for a UK financial services business operating in a highly competitive search market."
You've removed the identifying information.
But you've preserved useful context.
Similarly:
Instead of:
"I managed SEO for Brand X, a retailer generating £80 million annually."
You might say:
"I worked on SEO for a large UK ecommerce retailer with thousands of product and category pages."
The employer can still understand the scale and complexity of the project.
Anonymise the Client, Not the Experience
This is one of the most useful principles to remember.
You can remove:
The company name.
The exact website.
Exact revenue.
Confidential product information.
Internal strategy documents.
Customer information.
But still explain:
The industry.
The challenge.
The scale.
Your responsibility.
Your strategy.
The result.
What you learned.
Anonymisation shouldn't turn a strong case study into something meaningless.
Give Enough Context for the Result to Matter
Imagine your CV says:
"Increased organic traffic by 48%."
That's better than:
"Responsible for SEO."
But it's still missing context.
A stronger version might be:
"Increased non-brand organic traffic by 48% over nine months for a UK B2B services client through technical improvements, content consolidation, and commercial landing-page optimisation."
Now the employer understands:
What increased.
By how much.
Over what period.
For what type of business.
And roughly how you achieved it.
You still haven't named the client.
Focus on Percentages Instead of Exact Numbers
One of the easiest ways to protect confidential data is to use percentages.
Instead of:
"Organic revenue increased from £842,000 to £1.14 million."
say:
"Organic revenue increased by 35% year on year."
Instead of:
"Organic sessions increased from 63,481 to 92,117."
say:
"Organic sessions increased by approximately 45%."
Instead of:
"Generated £327,000 in additional organic revenue."
say:
"Generated a significant year-on-year increase in organic revenue."
Percentages often demonstrate impact without revealing commercially sensitive absolute figures.
You Can Use Approximate Figures Too
Sometimes percentages aren't enough.
Scale matters.
Increasing traffic by 100% sounds impressive.
But:
100 visits to 200
is very different from:
100,000 visits to 200,000.
If you're permitted to communicate approximate scale, consider using ranges.
For example:
"Worked on a website receiving more than 500,000 organic visits per month."
or:
"Managed organic strategy across a site containing 50,000+ indexable URLs."
or:
"Contributed to SEO strategy for an ecommerce business generating seven figures in annual organic revenue."
This communicates scale without exposing precise internal figures.
Round Numbers Where Appropriate
You don't always need exact figures.
Instead of:
37.84% increase in organic clicks
you might say:
approximately 38% increase in organic clicks.
Instead of:
12,742 additional monthly visits
you might say:
more than 12,000 additional monthly organic visits.
That can protect precision while keeping the result meaningful.
Be Clear About What the Metric Actually Measures
When presenting anonymised results, clarity becomes especially important.
Don't simply say:
"Traffic increased 50%."
Was that:
Total website traffic?
Organic sessions?
Google Search clicks?
Non-brand organic traffic?
Traffic to one section?
Traffic to newly created pages?
Google's documentation on using Search Console and Google Analytics for SEO explains that the two platforms measure different parts of the user journey: Search Console focuses on performance in Google Search, while Analytics focuses on behaviour after users reach the site.
So specify what you're talking about.
For example:
"Google Search clicks to non-brand commercial landing pages increased 52% year on year."
That's much more credible.
Use Before-and-After Comparisons
You can often demonstrate SEO impact without revealing absolute numbers at all.
For example:
Before
Commercial category pages had limited visibility outside branded searches.
After
Non-brand clicks increased 62% within eight months.
Or:
Before
Hundreds of important product pages weren't being indexed consistently.
After
Technical changes improved indexation across the priority product catalogue.
The contrast makes the impact easy to understand.
Use Indexed Results Rather Than Sensitive Business Metrics
You may not have permission to share:
Revenue.
Customer numbers.
Conversion values.
CRM data.
But perhaps you can discuss:
Organic clicks.
Impressions.
Keyword visibility.
Indexed pages.
CTR.
Technical errors.
Core Web Vitals.
Search Console can be particularly useful here.
Google's Search Console Performance report provides metrics including clicks, impressions, CTR, and average position, with filtering available across queries, pages, countries, devices, and dates.
These metrics can provide evidence of SEO improvement without requiring access to commercially sensitive revenue data.
Search Console Screenshots Can Be Powerful
Visual evidence can make a portfolio much more convincing.
SEO Jobs' guide on what to include in an SEO portfolio to get hired faster recommends using evidence such as Search Console performance graphs, analytics trends, keyword-ranking screenshots, and audit reports where you're permitted to share them.
But don't simply screenshot the entire dashboard.
Remove anything that could identify the client.
That might include:
Domain names.
URLs.
Query data.
Revenue figures.
Account names.
User information.
Internal annotations.
You can crop the screenshot to show only the relevant trend.
Redact Carefully
Redaction can be useful when you have permission to show the underlying work but need to remove identifying information.
For example, you could present:
Organic clicks
██████ → +46%
Organic impressions
██████ → +71%
Average position
Improved across priority commercial terms
The employer doesn't necessarily need every raw figure.
They need enough evidence to understand what changed.
Don't Fake or Alter Performance Data
Anonymising information is different from manipulating it.
Don't change:
Traffic figures.
Percentages.
Dates.
Ranking improvements.
Revenue.
Conversion numbers.
If you can't share something, remove it.
Don't replace it with invented numbers.
Trust matters more than making the case study look perfect.
Explain Why the Data Is Anonymised
You don't need a dramatic disclaimer.
A simple line is enough:
"Client name and commercially sensitive data have been anonymised due to confidentiality agreements."
That immediately explains why information is missing.
It can also make you appear more professional.
You're demonstrating that you take client confidentiality seriously.
Build Case Studies Around Problems, Not Just Numbers
One of the biggest mistakes SEO candidates make is thinking a portfolio needs to be a collection of impressive graphs.
Graphs help.
But employers also want to understand how you think.
A strong case study starts with the problem.
For example:
The Challenge
A large ecommerce website had thousands of category and product pages, but organic visibility for important non-brand commercial terms had stagnated.
That's useful context.
Now explain what you discovered.
Explain Your Diagnosis
Perhaps your analysis found:
Duplicate category pages.
Weak internal linking.
Thin category content.
Poor faceted-navigation controls.
Crawl inefficiencies.
Cannibalisation.
Weak title tags.
Indexation problems.
You can explain all of those issues without naming the client.
For example:
"My audit identified significant keyword cannibalisation across overlapping category pages, alongside weak internal linking to several commercially important sections."
That demonstrates technical and strategic knowledge.
Explain What You Personally Did
This is crucial.
Many case studies use the word:
"We."
That's understandable when you worked within a team.
But the employer needs to know what you contributed.
Explain:
"I conducted the initial technical audit."
"I built the keyword mapping framework."
"I identified the cannibalisation issue."
"I produced the content briefs."
"I worked with developers to prioritise technical fixes."
"I monitored performance after implementation."
You can acknowledge the wider team while still making your contribution clear.
Explain Your Strategy
Don't simply list tasks.
Instead of:
- Keyword research
- Technical audit
- Internal linking
- Content optimisation
explain how they connected.
For example:
"The initial audit showed that several commercial landing pages were competing for overlapping keyword groups. I consolidated the keyword mapping, recommended merging weaker pages, strengthened internal linking towards the primary commercial URLs, and rewrote page targeting around clearer search intent."
Now you're demonstrating strategy.
Show the Outcome
Then explain what happened.
For example:
"Within six months, organic clicks to the affected commercial pages increased approximately 42%, while the number of priority non-brand terms ranking on page one more than doubled."
You don't need the client name.
You don't need exact traffic numbers.
You still have a strong result.
Use a Simple Case Study Structure
A useful format is:
Context
What type of business or website was involved?
Challenge
What problem needed solving?
Diagnosis
What did your analysis uncover?
Action
What did you personally do?
Result
What changed?
Learning
What did the project teach you?
That structure works well in:
Portfolios.
CVs.
Interviews.
LinkedIn profiles.
Presentations.
Show Your Thought Process
Employers aren't only hiring the result.
They're hiring the person who produced it.
Suppose two candidates both say:
"Organic traffic increased 40%."
Candidate A can't explain why.
Candidate B explains:
"The site had strong authority but poor commercial-page targeting. Informational content attracted most organic traffic while key service pages had weak internal links and unclear keyword targeting. I reorganised the internal linking structure and reworked the commercial content around transactional search intent."
Candidate B demonstrates much more SEO understanding.
This is why SEO Jobs' article on how to stand out in a competitive SEO job market emphasises demonstrating results, practical work, and clear strategic thinking rather than simply listing SEO responsibilities.
Show Technical Wins Without Sharing the Website
Technical SEO projects can be particularly easy to anonymise.
You could say:
"Identified a faceted-navigation issue generating more than 80,000 unnecessary crawlable URLs."
or:
"Resolved an internal canonicalisation problem affecting a large ecommerce category structure."
or:
"Worked with developers to improve internal linking to more than 500 orphaned product pages."
or:
"Reduced the number of priority pages excluded from Google's index by approximately 60%."
None of these necessarily requires revealing the domain.
Explain the Business Impact of Technical SEO
Don't stop at:
"Fixed canonical tags."
Explain why it mattered.
For example:
"I identified inconsistent canonical implementation across product variants that was making indexation signals less clear. After working with developers to standardise the implementation, priority product pages became more consistently indexed and organic visibility improved across the affected categories."
That demonstrates much more value.
Show Content Wins Without Sharing Confidential Content
Content SEO can also be anonymised.
Instead of linking directly to an article, you could explain:
"Developed a content cluster around a high-value B2B service category, increasing non-brand organic clicks to the section by 75% over nine months."
Or:
"Reworked 30 underperforming commercial pages based on search intent and cannibalisation analysis, resulting in a 38% increase in organic entrances."
The employer can understand the work without seeing the confidential website.
Show Keyword Wins Carefully
Ranking improvements can be useful.
But avoid presenting:
"Moved keyword from position 12 to position 2."
without context.
A stronger example is:
"Improved visibility across a cluster of commercially important non-brand terms, with 18 priority keywords moving onto page one within six months."
You might also explain:
Search intent.
Search volume.
Commercial relevance.
What you changed.
Why those keywords mattered.
Don't Over-Rely on Rankings
Rankings are useful evidence.
But they shouldn't be the only evidence.
Search results can vary based on factors including:
Location.
Device.
Personalisation.
SERP features.
Time.
Instead, combine ranking improvements with:
Clicks.
Impressions.
Traffic.
Conversions.
Revenue.
Lead quality.
Where available.
Use Search Console Comparisons
Search Console allows you to compare different periods and filter performance by dimensions such as queries, pages, devices, and countries.
Google's guidance on advanced Performance report filtering and comparisons explains how filters can be combined to analyse specific areas of search performance.
That makes it useful for creating anonymised evidence.
For example, you could compare:
Last six months
against:
Previous six months
and crop the graph to show the trend without exposing identifying details.
Remember That Search Console Has Data Limitations
If you're using Search Console evidence in a portfolio, don't overstate what the data proves.
Google notes that some queries are omitted to protect privacy and that the interface may not display every query because of data limitations.
So avoid claiming:
"This screenshot contains every keyword the website ranked for."
It doesn't necessarily.
Use Search Console as evidence of trends, not as an absolute representation of every search interaction.
Demonstrate Commercial Impact Where You Can
Traffic growth is useful.
But employers increasingly want to understand what happened after the traffic arrived.
If you're allowed to discuss it, include:
Leads.
Sales.
Revenue.
Conversion rate.
Qualified enquiries.
Pipeline.
Customer acquisition.
For example:
"Organic traffic increased 28%, but more importantly, qualified organic enquiries increased 41%."
That's much stronger than traffic alone.
Don't Invent Revenue Attribution
Sometimes you won't have access to revenue or CRM data.
That's fine.
Don't guess.
SEO Jobs' guide to proving the commercial value of your SEO work to employers makes an important point: when you don't have access to final sales data, you should explain what you can measure rather than inventing commercial impact.
For example:
"I didn't have access to final customer revenue, so I wouldn't attribute sales directly to the campaign. What I could measure was a 35% increase in qualified organic enquiries."
That's credible.
Separate Correlation from Causation
SEO results rarely happen in a vacuum.
Suppose organic traffic increased 60%.
Was that entirely because of your work?
Maybe.
But perhaps:
The company launched a major PR campaign.
Brand demand increased.
Seasonality helped.
A competitor disappeared.
The website was redesigned.
New products launched.
A Google update affected the sector.
Strong candidates acknowledge relevant context.
You don't weaken your case study by being accurate.
You strengthen your credibility.
Explain Your Contribution Rather Than Claiming Everything
Imagine a major website migration succeeds.
You were responsible for:
Redirect mapping.
Pre-launch crawling.
Technical QA.
Post-launch monitoring.
Don't say:
"I successfully migrated a £50 million website."
unless you genuinely led the entire project.
Say:
"Owned SEO redirect mapping, technical QA, and post-launch monitoring as part of a cross-functional migration team."
That's still strong.
And it's much more believable.
Show Process Improvements Too
Not every SEO win needs to be a traffic graph.
Perhaps you:
Built a new reporting dashboard.
Created an SEO QA process.
Introduced automated crawling.
Developed a keyword-mapping framework.
Improved communication between SEO and developers.
Created technical SEO documentation.
Reduced reporting time.
Built a content briefing system.
These can demonstrate operational impact.
Show How You Prioritised
SEO teams rarely have unlimited resources.
Employers want people who can decide what matters.
For example:
"The audit identified more than 200 potential issues. I prioritised them based on likely organic impact, implementation difficulty, and commercial importance, resulting in a roadmap of 12 high-priority development tasks."
That tells an employer much more than:
"Completed technical SEO audit."
Explain Constraints
Real SEO work involves constraints.
Maybe:
Developers had limited capacity.
The CMS couldn't support your preferred solution.
The client rejected certain recommendations.
Legal approval delayed content.
Budget was limited.
You weren't allowed to change templates.
Discussing constraints can make a case study more convincing.
It demonstrates that you understand real-world SEO rather than textbook SEO.
Show What You Did When Something Didn't Work
Your portfolio doesn't need to pretend every project was perfect.
Imagine you created 20 articles and organic traffic barely moved.
What did you do?
Perhaps you discovered:
The topics had weak commercial relevance.
The domain lacked authority.
The pages weren't internally linked.
Search intent was wrong.
Competitors had much stronger content.
You changed strategy.
That can become an excellent interview example.
A Failed Test Can Still Demonstrate Strong SEO Skills
Suppose you changed page titles expecting CTR to improve.
It didn't.
That's not automatically a failure worth hiding.
Explain:
Hypothesis
We believed clearer commercial messaging would increase CTR.
Action
We tested revised title formats across a defined page group.
Result
CTR remained broadly unchanged.
Learning
The existing titles weren't the main constraint, so we redirected effort towards improving rankings and SERP visibility.
That's evidence of structured experimentation.
Use Public Data When Appropriate
If you can't show private analytics, public SEO tools may help provide additional context.
You might use publicly visible information such as:
Search results.
Indexed pages.
Public website changes.
Third-party visibility estimates.
But be careful.
Third-party SEO tools estimate data.
They aren't substitutes for first-party analytics.
Clearly label estimates as estimates.
Don't Share Someone Else's Tool Login
This should be obvious, but it's worth saying.
Don't give prospective employers access to:
A client's Search Console.
Analytics.
SEMrush.
Ahrefs.
CMS.
Internal dashboards.
CRM.
That isn't a portfolio.
It's a confidentiality breach.
Screenshots, anonymised extracts, and written case studies are safer.
Create a Portfolio Version Specifically for Recruitment
You don't need to use your original client reports.
In fact, you probably shouldn't.
Create a separate recruitment portfolio.
For each project, include:
Project type
Large UK ecommerce website.
Challenge
Organic category visibility had stagnated.
My role
Technical SEO and content strategy.
Actions
Audited category architecture, resolved cannibalisation, improved internal linking, and rewrote commercial-page targeting.
Results
Organic clicks to priority categories increased approximately 45% within eight months.
Tools
Google Search Console, GA4, Screaming Frog, Ahrefs.
Confidentiality note
Client identity and commercially sensitive figures anonymised.
That's enough.
Keep Case Studies Short Enough to Read
You don't need a 30-page case study for every project.
Hiring managers may be reviewing many candidates.
Aim for clarity.
A strong portfolio might contain three to five projects demonstrating different capabilities:
Technical SEO
Content SEO
Ecommerce SEO
SEO strategy
Migration
You can then discuss the projects in more detail during interviews.
Choose Projects That Demonstrate Different Skills
Don't include five nearly identical content examples.
Show range.
For example:
Case Study 1
Technical indexation problem.
Case Study 2
Content strategy and organic growth.
Case Study 3
Website migration.
Case Study 4
Commercial landing-page optimisation.
Case Study 5
International SEO.
This gives employers a clearer picture of your capabilities.
Tailor Your Portfolio to the Role
If you're applying for a Technical SEO role, lead with:
Crawling.
Indexation.
JavaScript.
Site architecture.
Migrations.
Structured data.
If you're applying for an SEO Content role, emphasise:
Search intent.
Keyword research.
Content strategy.
Content briefs.
Internal linking.
Organic growth.
If you're applying for an SEO Manager role, focus more on:
Strategy.
Commercial outcomes.
Prioritisation.
Stakeholder management.
Forecasting.
Team leadership.
Your portfolio doesn't need to be identical for every application.
Your CV Can Use the Same Approach
You don't need to save anonymised wins for your portfolio.
Use them on your CV.
Instead of:
"Responsible for technical SEO."
write:
"Led technical SEO improvements for a large UK ecommerce website, contributing to a 40%+ increase in non-brand organic clicks over 12 months."
Instead of:
"Created SEO content."
write:
"Developed search-led content strategy that increased organic entrances to the client's resource section by more than 60%."
Results make responsibilities more meaningful.
LinkedIn Can Showcase Anonymised Wins Too
You can share lessons from your work without naming the client.
For example:
"Recently worked on an ecommerce site where category cannibalisation was limiting organic visibility. After consolidating overlapping targeting and strengthening internal links, priority category clicks increased substantially over the following months."
Then explain what you learned.
That demonstrates expertise without exposing confidential information.
Be Prepared to Explain Your Evidence in Interviews
If you put:
"Increased organic traffic 80%."
on your CV, expect someone to ask:
How?
You should be able to explain:
The starting problem.
Your analysis.
Your recommendation.
What was implemented.
The timeframe.
How the result was measured.
Any limitations.
If you can't explain the number, it won't help you.
Know Which Tool Produced the Result
If you say:
"Organic clicks increased 40%."
was that from:
Search Console?
GA4?
Adobe Analytics?
Another platform?
Know the answer.
If you say:
"Visibility increased 25%."
which tool measured visibility?
Ahrefs?
Semrush?
Sistrix?
Another platform?
Specificity builds credibility.
Explain Differences Between Tools
Strong candidates also understand that different platforms won't necessarily report identical numbers.
Google explains that Search Console clicks and Google Analytics sessions are calculated differently, so discrepancies between them are normal.
If an interviewer asks why Search Console shows 50,000 clicks while GA4 shows 44,000 organic sessions, don't immediately assume tracking is broken.
Understand what each metric represents.
Don't Reveal Sensitive Search Queries
Search Console query data can sometimes contain information that shouldn't be shared.
Before adding query screenshots to a portfolio, inspect them carefully.
Remove:
Brand-specific confidential terms.
Unreleased product names.
Potentially sensitive searches.
Anything covered by your confidentiality agreement.
Google itself omits some query information from Search Console reporting to protect user privacy.
Your portfolio should apply the same professional mindset.
Be Careful with Competitor Information
You may have worked on detailed competitor analysis.
That doesn't mean every part belongs in your public portfolio.
Instead of sharing an internal document containing:
Competitor weaknesses.
Confidential strategic plans.
Unreleased campaigns.
Budget assumptions.
summarise your approach.
For example:
"Conducted competitor gap analysis across commercial keyword categories to identify areas where competitors had stronger organic coverage."
The skill is what matters.
Ask Permission When You're Unsure
If you aren't sure whether something can be shared, don't assume.
Check:
Your employment agreement.
Your NDA.
Agency policies.
Client agreement.
Internal confidentiality guidance.
Or ask the appropriate person.
A portfolio isn't worth creating a professional or legal problem.
Create Your Own Projects If Restrictions Are Very Tight
Sometimes confidentiality restrictions are so strict that almost nothing can be shown.
You still have options.
Create:
A personal website.
A niche content site.
A local SEO project.
A technical SEO test site.
A small affiliate project.
A volunteer project.
Then document everything.
You can demonstrate:
Keyword research.
Site architecture.
Content strategy.
Technical implementation.
Internal linking.
Search Console growth.
Rankings.
Because you control the project, you control what you can disclose.
Personal Projects Can Be Particularly Useful for Junior SEOs
If you're early in your career, you may not have impressive client case studies yet.
That's fine.
A small website that you've actually grown can be more convincing than a portfolio full of theoretical audits.
Employers want evidence that you can apply what you've learned.
Don't Underestimate Small Wins
Not every case study needs:
+500% organic growth.
Maybe you:
Fixed an indexing problem affecting 200 pages.
Improved CTR by 15%.
Moved an important commercial keyword from page two to page one.
Reduced duplicate pages.
Improved internal linking.
Recovered traffic after a migration.
Small, well-explained improvements can still demonstrate strong SEO skills.
The Story Matters as Much as the Percentage
Consider these two examples.
Candidate A
"Increased organic traffic by 60%."
Candidate B
"Identified that several high-value category pages were receiving little internal link equity despite strong commercial potential. I redesigned the internal linking recommendations around those categories and worked with the content team to improve relevance. Organic clicks to the affected pages increased 38% over the following six months."
Candidate A has the bigger number.
Candidate B tells the stronger story.
Employers need to understand how you think.
Avoid Vanity Metrics
Be careful about presenting numbers simply because they're large.
For example:
"Generated 10 million impressions."
Did those impressions matter?
Did clicks increase?
Did relevant queries improve?
Did conversions grow?
Did revenue change?
A strong case study connects metrics to an objective.
Commercial SEO Wins Are Particularly Powerful
As you become more senior, employers may care less about whether you moved one keyword from position six to position three.
They may care more about:
Qualified leads.
Revenue.
Pipeline.
Customer acquisition.
Visibility across strategically important categories.
Reduced dependence on Paid Search.
Market expansion.
If you have access to these outcomes and permission to discuss them, use them.
Senior Candidates Should Demonstrate Decision-Making
If you're applying for SEO Manager or Head of SEO roles, employers aren't only interested in what you optimised.
They want to know:
How did you prioritise?
How did you allocate resources?
How did you get stakeholder approval?
How did you manage developers?
How did you forecast impact?
How did you decide what not to do?
Your anonymised case studies should reflect that.
Show Collaboration
SEO rarely happens alone.
A strong case study might explain how you worked with:
Developers.
Writers.
Designers.
PR teams.
Product teams.
Paid Media.
Analytics.
Senior leadership.
For example:
"After identifying crawl inefficiencies within the faceted-navigation structure, I worked with developers to agree an implementation that preserved useful category pages while limiting unnecessary URL generation."
That's much more realistic than pretending you fixed everything personally.
Show What You Learned
End each case study with a short lesson.
For example:
"The project reinforced the importance of validating keyword cannibalisation with actual performance data rather than relying only on ranking-tool reports."
or:
"The migration demonstrated why SEO involvement needs to begin during planning rather than immediately before launch."
This shows reflection.
Employers value people who improve from experience.
Confidentiality Can Actually Strengthen Your Interview Story
Handled properly, confidentiality doesn't weaken your application.
It can demonstrate professionalism.
You can say:
"I can't identify the client or share exact revenue figures because of confidentiality restrictions, but I can explain the challenge, my strategy, the percentage improvement, and how we measured the result."
That's completely reasonable.
A good employer should understand.
What If an Interviewer Pushes for Confidential Information?
Maintain the boundary.
You might say:
"I'm happy to explain the project in detail, but I can't share the client's identity or exact commercial figures. I can give you approximate scale and percentage changes instead."
You don't need to break an NDA to prove you're good at SEO.
In fact, refusing to do so demonstrates professional judgement.
What Employers Really Want to Know
When employers ask for case studies, they're usually trying to answer questions such as:
Can this person identify SEO problems?
Can they prioritise?
Do they understand search behaviour?
Can they implement recommendations?
Can they measure impact?
Can they explain why something worked?
Do they understand commercial outcomes?
Can they communicate clearly?
You can answer all of those questions without revealing confidential client information.
Build a Repeatable Portfolio Template
For every project, use the same framework:
Industry
UK ecommerce / B2B SaaS / financial services / recruitment / etc.
Website scale
Small / medium / enterprise / approximate URL count.
Challenge
What needed improvement?
My responsibility
What did you own?
Analysis
What did you discover?
Actions
What did you recommend or implement?
Results
What changed?
Measurement
Which tools did you use?
Learning
What did you take from the project?
Confidentiality
What has been anonymised?
This creates consistency and makes your portfolio easier to scan.
The Bottom Line
You don't need to reveal confidential client information to prove you're good at SEO.
You need to demonstrate impact, reasoning, and ownership.
Anonymise company names.
Use percentages where exact figures are sensitive.
Use ranges where scale matters.
Redact screenshots carefully.
Explain the problem.
Show your diagnosis.
Describe what you personally did.
Measure the result.
Connect SEO metrics to commercial outcomes where possible.
And be transparent about what you can't share.
A strong SEO portfolio isn't valuable because it contains famous client logos or enormous analytics screenshots.
It's valuable because it demonstrates that you can look at a search problem, understand what's happening, develop a sensible strategy, implement it, and measure whether it worked.
That's what employers are trying to identify.
If you can demonstrate those skills while also respecting client confidentiality, you're showing two things at once:
You're capable of producing results.
And:
You're professional enough to be trusted with sensitive information.
Both matter when you're building a long-term career in SEO.
If you're looking for your next opportunity in Technical SEO, Content SEO, Ecommerce SEO, SEO Management, or Organic Search, explore the latest opportunities at SEO Jobs.