Where I work best
I work best with websites with technical, content and reporting needs that have engineering support, GSC/GA4 access and a need to turn SEO decisions into cross-team execution.
My SEO journey started in İzmir in 2008 and evolved into a consulting practice focused on solving organic growth problems for websites with technical, content and reporting needs.
During the iProspect period, I worked across multiple brands and sectors. Later, I worked on e-commerce SEO and migration processes at Hepsiburada and Markafoni, and marketplace growth at Zingat.
Since 2018, I have been consulting under my own name. My current focus is technical SEO, publisher growth, e-commerce SEO, finance/YMYL visibility, AI Search and reporting systems.
This is not a score claim; it is a visual summary of where the most repeated project experience sits.
I work best with websites with technical, content and reporting needs that have engineering support, GSC/GA4 access and a need to turn SEO decisions into cross-team execution.
Projects expecting short-term ranking guarantees, diagnosis without data or SEO impact without implementation support are not a good fit.
Strong work narratives can be built without exposing private URL lists, contracts or raw performance metrics.
Recommendations are not enough. Each action needs ownership, implementation context, acceptance criteria and measurable follow-up.
A responsible diagnosis needs GSC, GA4, crawl, indexability and page-type data.
Strong work narratives can be built without exposing raw metrics, private URLs or commercial data.
Content, product, engineering, data and leadership need to operate in the same system.
Technical SEO, publisher SEO, e-commerce SEO, finance websites, AI Search readiness and SEO reporting.
Yes. The focus is on building a workflow that the team can execute and track.
Websites with technical, content and reporting needs with engineering support, many URLs and a need for structured organic visibility tracking are a better fit.
Google Search Console, GA4, crawl data, key page types, technical workflow context and current goals are usually needed.
No. Crawlability, content quality, entity clarity and trust signals still form the foundation.