Technical SEO
Canonicals, metadata, robots, sitemaps, structured data, indexing, and common crawl pitfalls.
Olamisan is a personal blog for practical developer notes. Expect short tutorials, checklists, and project write-ups about web performance, technical SEO, Next.js, automation, and developer tools.
What I optimize for: clear structure, measurable outcomes, and content that stays useful. If you’re building a blog, portfolio, or product site, you’ll find patterns you can reuse.
Topic hubs improve internal linking and make it easier to explore related posts.
Canonicals, metadata, robots, sitemaps, structured data, indexing, and common crawl pitfalls.
Core Web Vitals, loading strategy, images & fonts, caching, rendering costs, and performance budgets.
Routing, metadata API, SSR/ISR tradeoffs, SEO-friendly rendering, and common deployment checks.
Small scripts and workflows that remove repetitive work: reports, renames, data checks, and more.
Longer “pillar” guides designed to rank and to be referenced often.
A clean baseline: titles, descriptions, canonicals, internal links, sitemaps, and indexability checks.
Practical actions that improve LCP, CLS, and INP—without overengineering.
Metadata API, Open Graph, canonical URLs, robots rules, structured data, and deployment checklist.
Short posts with focused scope. Great for quick implementation.
A prioritized list: crawlability, canonicals, metadata, internal links, and common mistakes that block indexing.
The fixes that usually work: images, fonts, layout stability, JS cost, hydration, and interaction latency.
How to structure metadata so every page is indexable, shareable, and consistent across routes.
A simple configuration that avoids accidental blocking and helps Google discover pages faster.
Practical defaults for modern image delivery (including lazy loading, responsive sizing, and avoiding CLS).
A practical list: batch renames, report generation, data checks, and quick CLI tooling that saves hours.
Work that turns notes into outcomes. (Add real links/results to increase trust and SEO.)
Templates for auditing Core Web Vitals and turning findings into a prioritized plan.
A minimal baseline for metadata, canonicals, sitemaps, robots, and structured data.
Small scripts to speed up repetitive tasks: asset workflows, reports, and batch operations.
Tools I often reference for performance and SEO work (add/remove as needed).
Measure and debug speed: Lighthouse, WebPageTest, Performance panel, and real-user metrics.
Verify indexing: Google Search Console, URL Inspection, sitemap coverage, and structured data checks.
Lightweight scripts: Node/Python CLI helpers for batch tasks, reports, and content workflows.
Why this blog exists and how the content is written.
Hi, I’m Olamisan. I write to document what works—especially for web performance and technical SEO. Posts are designed to be reusable: clear steps, practical defaults, and checklists you can ship with.
More context for readers and rich results eligibility.
They’re written as reusable documentation: checklists, defaults, and implementation details you can apply quickly.
Both. Posts are step-by-step, and advanced topics include prerequisites plus links to foundational notes.
No—Google decides. But correct structure + helpful content increases eligibility and consistency.
Yes. The goal is to make content that saves time and stays useful across projects.
For questions, feedback, or collaboration.