How Should a Technical SEO Consultant in Spain Show Audits, Migrations, and Private Client Data?
A technical SEO consultant should show each audit, migration, or implementation as a bounded case, explain the diagnosed constraint and their own action, and disclose only client-approved evidence with clear attribution and time context.
Search Console charts and analytics exports can contain confidential URLs, commercial performance, and user data, while ranking changes rarely have one cause. A trustworthy portfolio makes the work inspectable without turning private dashboards into marketing claims or crediting every outcome to one recommendation.
Which technical SEO engagements belong in a portfolio?
Include engagements with a clear technical problem and attributable scope, such as an indexation audit, platform migration, rendering fix, internal-link redesign, structured-data implementation, or log-analysis project.
Describe site category at the level the client permits, the constraint, your responsibility, the deliverable, and what was actually implemented. Distinguish recommendations from changes you shipped and individual work from agency or client-team delivery.
Group recurring audits for one programme when the methods and outcome are inseparable. Split a migration, tooling product, or reusable crawler when it has an independent artifact and evidence.
- Public site: live implementation or approved case.
- Private audit: anonymised method and deliverable.
- Internal tool: safe demo, docs, or owned repository.
- Old migration: historical case with dates and scope.
What is the fast way to build the SEO proof page with IndieShow?
The fast way is to create one IndieShow card per defensible engagement or tool, label its status, and link to the best approved destination rather than a private reporting dashboard.
Use the description for technical issue, intervention, and contribution, and the tag for migration, crawling, JavaScript SEO, structured data, or another precise area. Leave the metric empty when a number cannot be shared or attributed honestly.
Order cases by the buyer's current problem and preview the page before sending it. A stable personal handle can keep the overview current while client case-study permissions and live implementations change.
Build your IndieShow pageClaim your handle, organise the projects in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.
How can SEO results be described without inventing causation?
Describe the implemented change, measurement window, approved observation, and material confounders, and avoid saying one action caused traffic or revenue unless the evidence supports that conclusion.
Algorithm updates, seasonality, content changes, links, product work, and tracking changes can overlap a technical release. Use careful language such as observed after implementation when causation was not isolated.
Never invent percentages or copy a client dashboard into a public card. A strong no-number case can still show diagnosis quality, implementation depth, verification method, and what the client authorised you to say.
What evidence should an audit or migration link to?
Link to an approved case study, public implementation, talk, technical article, sanitised sample deliverable, or tool you own—whichever directly supports the card's claim.
Test that public URLs still show the relevant implementation and that documents contain no hidden comments, crawl exports, customer queries, staging hosts, credentials, or private issue references.
For migrations, state your phase and responsibility instead of taking credit for the whole programme. Keep recommendations that were not implemented separate from verified production work.
Related IndieShow guides: presenting private audit and remediation work · showing technical deliverables for private clients
How does IndieShow fit a technical SEO consultant portfolio?
IndieShow fits by placing audits, migrations, tooling, active experiments, and historical cases on one maintained page with an explicit status and controlled destination for each.
The project description can carry the bounded claim, the tag can identify the technical speciality, and the optional metric can remain blank unless it is authorised and meaningful. Reordering lets the same truthful evidence serve different prospect needs.
Use IndieShow to close with a precise map of your work; the actual implementation, approved case, article, or sample remains the underlying proof.
Frequently asked questions
Which technical SEO engagements belong in a portfolio?
Include engagements with a clear technical problem and attributable scope, such as an indexation audit, platform migration, rendering fix, internal-link redesign, structured-data implementation, or log-analysis project.
What is the fast way to build the SEO proof page with IndieShow?
The fast way is to create one IndieShow card per defensible engagement or tool, label its status, and link to the best approved destination rather than a private reporting dashboard.
How can SEO results be described without inventing causation?
Describe the implemented change, measurement window, approved observation, and material confounders, and avoid saying one action caused traffic or revenue unless the evidence supports that conclusion.
What evidence should an audit or migration link to?
Link to an approved case study, public implementation, talk, technical article, sanitised sample deliverable, or tool you own—whichever directly supports the card's claim.
How does IndieShow fit a technical SEO consultant portfolio?
IndieShow fits by placing audits, migrations, tooling, active experiments, and historical cases on one maintained page with an explicit status and controlled destination for each.