Technical SEO

-

 

Day 4: Technical SEO — Understanding How Search Engines Discover Websites

The first three days of my SEO journey focused on understanding people.

I learned why keyword research matters, how search intent influences content, and how On-Page SEO helps search engines understand a webpage.

Today, I shifted my focus from content to the technical side of SEO.

As a frontend developer, I was especially excited because today's topics felt much closer to the work I do every day.

I wanted to answer one question:

How does Google actually discover and understand a website?

The answer led me into the world of Technical SEO.

What Is Technical SEO?

Technical SEO is the process of optimizing a website so that search engines can efficiently discover, crawl, understand, and index its pages.

Unlike content or backlinks, Technical SEO focuses on the website's infrastructure.

Even if a website has excellent content, poor technical implementation can prevent search engines from finding or ranking it.

That was a surprising realization.

Building a beautiful website isn't enough if search engines can't access it properly.

Crawling: How Search Engines Discover Pages

One of the first concepts I learned today was crawling.

Search engines use automated programs, often called crawlers or bots, to explore websites.

These bots visit a webpage, read its content, follow internal links, and discover new pages.

I like to imagine them as curious visitors walking through every room in a building.

If there are clear pathways between rooms, they can explore everything.

But if doors are locked or pages aren't linked anywhere, they may never find them.

That made me realize how important proper site structure and internal linking really are.

Indexing: When a Page Becomes Searchable

Discovering a page doesn't automatically mean it will appear in search results.

After crawling a page, Google decides whether it should be added to its index.

You can think of Google's index as a massive digital library.

Only indexed pages are eligible to appear in search results.

This explained something I had wondered about before.

Sometimes developers publish new pages and expect them to appear on Google immediately.

In reality, the page must first be crawled, evaluated, and indexed.

That process can take time.

robots.txt: Giving Instructions to Search Engines

Today's learning also introduced me to a small but powerful file called robots.txt.

This file tells search engine crawlers which parts of a website they can or cannot access.

For example, developers may want to prevent search engines from crawling:

  • Admin dashboards

  • Login pages

  • Temporary development folders

  • Duplicate content

However, I also learned an important lesson.

Blocking a page in robots.txt doesn't necessarily remove it from search results.

It simply controls crawling.

Understanding the difference between crawling and indexing helped clear up a common misconception I had.

XML Sitemap: A Roadmap for Search Engines

If robots.txt provides instructions, then an XML Sitemap acts like a roadmap.

A sitemap lists the important pages on a website and helps search engines discover them more efficiently.

This is especially useful for:

  • Large websites

  • Newly launched websites

  • Websites with many pages

  • Pages that don't receive many internal links

As someone who builds websites, I realized that generating and submitting a sitemap should be part of every project launch checklist.

It's a simple step that can make a meaningful difference.

Core Web Vitals: Measuring Real User Experience

One topic I had heard about before—but never fully understood—was Core Web Vitals.

Today, I finally learned what they measure.

Instead of looking only at design, Google also evaluates how users experience a webpage.

Three important metrics are:

Largest Contentful Paint (LCP)

How quickly the main content becomes visible.

A faster loading page creates a better first impression.

Interaction to Next Paint (INP)

How responsive the page feels when users click, tap, or interact with it.

Nobody enjoys clicking a button and waiting for it to respond.

Cumulative Layout Shift (CLS)

Whether elements unexpectedly move while the page is loading.

We've all experienced trying to click a button only for it to shift at the last second.

That's exactly what CLS measures.

These metrics reminded me that performance isn't just about achieving a high Lighthouse score.

It's about delivering a smooth experience for real people.

Technical SEO Is a Shared Responsibility

One of my biggest takeaways today was realizing that SEO isn't only the responsibility of marketers.

Developers play an equally important role.

The decisions we make while building websites directly affect how easily search engines can crawl, understand, and rank them.

Simple things like:

  • Fast loading pages

  • Clean code

  • Proper HTML structure

  • Responsive design

  • Optimized images

  • Well-organized navigation

all contribute to stronger Technical SEO.

It made me appreciate that good development practices often align with good SEO practices.

Looking at My Projects Differently

After today's learning, I started reviewing some of the websites I've worked on.

Instead of focusing only on visual design, I found myself asking new questions.

  • Does the website have an XML sitemap?

  • Is robots.txt configured correctly?

  • Are important pages easy to crawl?

  • How fast does the homepage load?

  • Are there broken links?

  • Is the mobile experience smooth?

These aren't questions I asked a few weeks ago.

Now they feel like an essential part of launching any website.

My Biggest Takeaway From Day 4

Today's lesson changed how I think about websites.

Users see the design.

Developers see the code.

Search engines see the structure.

A website needs to work well for all three.

Technical SEO isn't about tricks or shortcuts.

It's about making websites easier to discover, easier to understand, and faster for everyone to use.

As a developer, that's a mindset I genuinely enjoy.

What's Next?

Tomorrow, I'll start exploring Google Search Console.

I want to learn:

  • How Google reports website performance

  • How to submit XML sitemaps

  • How to identify indexing issues

  • Which keywords are already bringing traffic

  • How developers can monitor SEO health over time

I'm excited because this feels like the point where theory starts turning into practical experience.

Day 4 complete. Learning mode: Still ON. 🚀

The more I learn about SEO, the more I realize it's not a separate skill from web development. Great websites aren't just visually appealing—they're technically sound, easy to discover, and built with both users and search engines in mind. Every small improvement, from optimizing page speed to creating a proper sitemap, helps build a stronger foundation for long-term visibility.

If this Blog helped or motivated you, feel free to visit my profile Linkedin.com and connect.

Comments

Post a Comment

Popular posts from this blog

My First Stipend-Based Internship💻🚀

-
  How I Choose a Different Path as a Fresher🚀 Getting a first internship as a fresher is not easy. Everyone applies on the same job portals, sends hundreds of resumes, and waits for replies that never come.  I was also in the same situation — confused, stressed, and unsure. But instead of giving up, I decided to try a different approach . This blog is about my first stipend-based internship , what I learned, and how choosing my own path helped me move forward in my tech career. 📚  My First Internship Experience  (Sep 2025) In September 2025 , I completed a one-month work-from-home internship . It was my   first  stipend-based internship , and it gave me real confidence as a fresher. Before this, I only knew theory. During this internship, I worked on real-time live projects , which helped me understand how actual development works. 📝What I Learned During This Internship This internship helped me build a strong foundation. 💻 Technical Skills HTML –...
Read more

How I Fixed the Prisma Error

-
How I Fixed the Prisma "The table public.User does not exist" Error It was one of those moments every developer dreads—you've set up your project, written your Prisma schema, and you're ready to seed the database. You run: npm run seed …and immediately get greeted with this error: PrismaClientKnownRequestError: The table `public.User` does not exist in the current database. I stared at it for longer than I'd like to admit. The User model was clearly defined in my schema.prisma file, so why was Prisma saying the table didn't exist? After a bit of digging, I realized the issue wasn't with my code at all—it was with my understanding of how Prisma works. If you're seeing this error too, here's exactly why it happens and how to fix it. Why This Error Happens One of the biggest misconceptions for developers new to Prisma (myself included) is believing that defining a model in schema.prisma automatically creates the corresponding table in the databas...
Read more

Design Web Pages using CSS

-
CSS ( Cascading Style Sheets ) is a styling language used to control the layout and appearance of web pages. It's an essential tool for web developers and designers to create visually appealing and user-friendly websites. In this blog, we will explore the basics of CSS, its types, and some exciting properties that can make your web pages interactive and interesting. Types of CSS There are three types of CSS: 1. Inline CSS: This type of CSS is applied directly to an HTML element using the style attribute. It has the highest priority among all CSS types. 2. Internal CSS: This type of CSS is defined within the <head> section of an HTML document using the <style> tag. 3. External CSS: This type of CSS is stored in an external file with a .css extension and linked to an HTML document using the <link> tag. CSS Syntax The basic syntax of CSS consists of a selector, property, and value: selector {   property: value; } CSS Properties There are many CSS properties t...
Read more