The challenge
My own site needed to explain two connected skills, SEO and web development, without turning into a generic list of services. It also needed to protect useful existing URLs.
What I worked on
I rebuilt the visual system, information architecture, case-study structure, metadata, schema, internal linking and static front end. The site uses HTML, CSS and JavaScript, with no framework required for core rendering.
- Static HTML/CSS/JS
- Structured data
- Clean canonical URLs
- Internal linking
- Performance-minded assets
What changed
The result is a fast, crawlable portfolio with dedicated service pages, case studies, blog content, social identity, and preserved resource routes.
SEO and E-E-A-T choices
I keep project claims tied to work that can be inspected on the website. Instead of inventing traffic or revenue figures, this case study documents the actual architecture, content, navigation, implementation and public features. That makes the portfolio more useful to evaluate and keeps the claims verifiable.
What I would improve next
After launch, the next step is measurement. I would use Search Console, analytics and crawl data to identify search queries, pages with weak click-through rate, internal-link gaps and performance opportunities, then prioritize changes based on evidence.