Technical SEO foundations
Canonical URLs, redirects, robots controls, XML sitemaps, crawl paths, and indexation safeguards.
- Crawlability audits
- Duplicate-path control
- Internal link validation
I improve crawlability, metadata, structured data, internal discovery, and performance, then validate the work with repeatable checks and source-backed reporting.
Independent portfolio · owned-site case study · no inflated traffic claims
The evidence below comes directly from the reports generated for PuteraGani.com on June 12, 2026. Each card links to the full owned-site case study.
Strong fundamentals across headings, metadata, canonicalization, schema, and crawl controls.
A useful independent check that also keeps unresolved priorities visible.
The same report flags link authority as weak, an important limitation rather than a hidden detail.
Practical technical work for websites that need clearer discovery, cleaner signals, and an implementation trail stakeholders can verify.
Canonical URLs, redirects, robots controls, XML sitemaps, crawl paths, and indexation safeguards.
Repeatable metadata, heading hierarchy, social previews, image signals, and content discoverability.
Schema designed around the page purpose, entity relationships, and content type instead of generic markup.
Lean assets, stable layouts, production checks, and reports that separate completed work from next priorities.
Owned editorial website · Technical SEO
PuteraGani.com is a static editorial site with JavaScript-driven discovery and more than one hundred production pages. The work focused on consistent technical signals, initial-HTML discoverability, production CSS, and repeatable validation.
A technical recommendation only matters when it becomes a production change and the result can be checked again.
Inspect templates, routes, rendering behavior, metadata, crawl controls, and current evidence.
Separate indexation and discovery risks from cosmetic checker recommendations.
Use shared templates and maintenance scripts so fixes remain consistent as the site grows.
Run local checks, inspect the rendered site, and report both wins and unresolved limitations.
I am building a portfolio around transparent implementation work: what changed, why it mattered, how it was verified, and what still needs attention.