DEV Community

Cover image for What I Learned from Studying SEO: Notes, Checklist, and Developer Takeaways
홍다은
홍다은

Posted on

What I Learned from Studying SEO: Notes, Checklist, and Developer Takeaways

#seo #study #devjournal #portfolio

What I Learned from Studying SEO: Notes, Checklist, and Developer Takeaways

I recently spent time studying Search Engine Optimization (SEO) — not because I wanted to be a marketer, but because I wanted to understand how information should be structured, presented, and optimized.

For me, SEO is not just about “ranking higher.” It’s about clarity, trust, and structure — skills that are directly relevant to being a developer. This post is a record of what I learned, the checklist I built, and how I believe this experience connects to my growth as a developer.

Why I Studied SEO

When I build projects or write technical blogs, I don’t just want them to exist — I want them to be accessible and professional.

  • Without clear metadata or a sitemap, even a great project can feel incomplete.
  • Without optimized performance, users lose trust quickly.
  • Without structured data, search engines (and people) miss important context.

That’s why I decided to research SEO and turn my notes into something reusable for both personal and professional projects.

Core Concepts I Learned

Here are the foundational ideas that stood out to me:

  1. Metadata (Title & Description)

    • Each page needs a unique title and meta description.
    • These act like an “elevator pitch” for both users and search engines.

  2. Open Graph & Twitter Cards

    • Rich link previews are not just cosmetic — they build credibility when sharing projects.

  3. robots.txt & sitemap.xml

    • These files are the “map and rules” for crawlers.
    • A well-maintained sitemap makes indexing predictable.

  4. Structured Data (JSON-LD)

    • By using schemas like BlogPosting or CreativeWork, content can appear with rich results in SERPs.
    • For portfolios, this means projects can be represented with more detail.

  5. Core Web Vitals

    • Metrics like LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), and FID (First Input Delay) measure real user experience.
    • They connect performance optimization directly with SEO.

  6. Internal Linking

    • Consistent linking between related posts and projects builds a logical site structure.

  7. hreflang for Multilingual Sites

    • Essential if content targets multiple languages or countries.

  8. 404 Handling & Redirects

    • Broken links hurt authority.
    • Proper 301 redirects preserve reputation and user flow.

  9. RSS Feeds (Optional)

    • While less common today, they provide syndication and accessibility.

  10. Analytics & Monitoring

    • Google Search Console and GA4 aren’t just tools — they’re the feedback loop for improvement.

My 22-Point SEO Checklist

To make my learning actionable, I created a checklist that I can apply to any future project.

Metadata & Previews

  • Unique title and description per page
  • Consistent Open Graph and Twitter Card metadata
  • Standard preview images (1200×630 px)

Search Engine Indexing

  • Valid robots.txt file
  • Dynamic sitemap.xml with lastModified dates
  • Canonical URLs defined

Structured Data

  • Blog posts use BlogPosting schema
  • Projects use CreativeWork or Project schema
  • Author and date metadata included

Performance & Core Web Vitals

  • Optimized and lazy-loaded images
  • Fonts with display=swap or subsets
  • Largest Contentful Paint under 2.5s

Navigation & Linking

  • Internal links between posts/projects
  • Consistent use of categories and tags
  • Custom 404 page in place
  • 301 redirects for old URLs

Advanced Considerations

  • hreflang for multilingual targeting
  • Breadcrumb structured data
  • RSS feed for subscribers
  • Integrated analytics and monitoring

What Surprised Me

The biggest insight I had was that SEO is not just about “visibility.” It’s about thinking structurally:

  • How should information be organized?
  • How do we make it accessible for both humans and machines?
  • How do we align technical performance with user trust?

As a developer, this way of thinking directly overlaps with API design, data modeling, and performance optimization.

How This Helps Me as a Developer

This SEO study wasn’t just a side hobby — it was professional development.

  • Communication & Documentation: Writing meta descriptions is like writing concise commit messages or technical summaries.
  • Performance Awareness: Core Web Vitals trained me to think about real-world speed and UX, not just code correctness.
  • Structured Thinking: Learning structured data reinforced my ability to design clear data schemas.
  • Professional Presentation: A well-optimized project reflects attention to detail, which is exactly what hiring managers look for.

In short: I don’t just build features. I care about how projects are experienced, discovered, and understood.

Conclusion

Studying SEO gave me practical knowledge and a mindset shift. For me, SEO means:

  • Clearer communication of project goals
  • Stronger technical foundation for professional blogs and apps
  • A more holistic view of what “quality” means in software

This post is both a study log and part of my portfolio.

Top comments (0)