top of page

SEO for Developers, Not Marketers

  • Contributor
  • Jan 5
  • 4 min read

SEO has a reputation problem among developers. It sounds like marketing — keywords, backlinks, content strategy. And much of the SEO industry is marketing. But the technical foundations of SEO — the parts that determine whether search engines can find, understand, and rank your content — are pure engineering.

If you've built a website or web application, the technical SEO is your domain. You don't need to become a marketer. You need to not actively prevent search engines from doing their job.

What Search Engines Actually Do

Google (and other search engines) do three things:

  1. Crawl: Discover pages by following links. A bot visits your site, reads the HTML, follows links to other pages, and builds a map of your site.

  2. Index: Parse and store the content. The bot extracts text, identifies the topic, notes the structure (headings, lists, links), and stores this in a searchable index.

  3. Rank: For a given search query, decide which indexed pages are most relevant and show them in order.

Your technical SEO job: make crawling easy, indexing accurate, and ranking favorable.

The Technical Fundamentals

Semantic HTML Matters

Search engines read your HTML. The structure of your markup communicates what's important.

<!-- Bad: everything is a div, nothing has semantic meaning -->
<div class="heading">My Blog Post</div>
<div class="content">The post content...</div>

<!-- Good: semantic elements communicate structure -->
<article>
  <h1>My Blog Post</h1>
  <p>The post content...</p>
</article>

<h1> tells the crawler "this is the main topic of the page." <article> says "this is the primary content." <nav> says "this is navigation." Search engines use these signals to understand page structure and content hierarchy.

One <h1> per page. Headings in order (don't skip from <h1> to <h3>). Content in <article> or <main>. Navigation in <nav>. This isn't just accessibility — it's SEO.

Meta Tags

The <title> and <meta description> tags are what appear in search results. They're your first impression.

<head>
  <title>Database Migrations Without the Fear | ShiftQuality</title>
  <meta name="description" content="How to run database schema changes safely — from simple column additions to complex restructuring, without breaking production.">
</head>

Title tag: Under 60 characters. Describes the page content. Unique per page. This is the clickable headline in search results.

Meta description: Under 160 characters. Summarizes what the page offers. Not a direct ranking factor, but it affects click-through rate — a compelling description gets more clicks.

Don't: Stuff keywords. "SEO tips SEO tricks SEO best practices SEO guide SEO help" is spam. Write for humans. Search engines are sophisticated enough to understand natural language.

Page Speed Is a Ranking Factor

Google uses page speed as a ranking signal. Slow pages rank lower. The Core Web Vitals (LCP, INP, CLS) directly affect search rankings for mobile results.

Everything from the web performance posts applies here: compress images, minimize JavaScript, use a CDN, enable caching. Fast pages rank better and convert better. The SEO and user experience incentives are perfectly aligned.

Mobile-First Indexing

Google crawls and indexes the mobile version of your site, not the desktop version. If your mobile experience is broken, missing content, or slow, that's what Google sees — even if the desktop version is perfect.

Responsive design isn't optional for SEO. Your content must be fully accessible on mobile devices.

Crawlability

Search engines need to discover and access your pages.

Internal linking: Every important page should be reachable from other pages through HTML links. A page that's only accessible through JavaScript navigation or a search function may not be discovered by crawlers.

Sitemap: An XML sitemap (/sitemap.xml) lists all pages you want indexed. It's not strictly required, but it helps crawlers discover pages efficiently, especially on large sites.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/blog/database-migrations</loc>
    <lastmod>2026-03-21</lastmod>
  </url>
</urlset>

robots.txt: Tells crawlers which parts of your site to access and which to skip.

User-agent: *
Allow: /
Disallow: /admin/
Sitemap: https://example.com/sitemap.xml

Structured Data

Structured data (Schema.org markup) tells search engines explicitly what type of content you have. This enables rich results — star ratings, recipe cards, FAQ dropdowns, article metadata.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Database Migrations Without the Fear",
  "author": {"@type": "Organization", "name": "ShiftQuality"},
  "datePublished": "2026-03-21",
  "description": "How to run database schema changes safely."
}
</script>

This tells Google: "This page is an article. Here's the title, author, and publish date." Google may display this as a rich result with additional metadata.

URLs Matter

Clean, descriptive URLs rank better than random strings.

Good: /blog/database-migrations-without-fear
Bad:  /blog/post?id=47382&ref=main

Use hyphens, not underscores. Keep URLs short. Include the primary keyword naturally.

HTTPS Is Required

Google has used HTTPS as a ranking signal since 2014. There is no reason to serve any site over HTTP in 2026. Let's Encrypt provides free SSL certificates. Every major hosting platform supports HTTPS by default.

Common Technical SEO Mistakes

Client-side rendering without SSR. A React SPA that renders everything in JavaScript may not be indexed correctly. Google's crawler can execute JavaScript, but it's slower and less reliable than reading server-rendered HTML. Use server-side rendering (Next.js, Nuxt, SvelteKit) for content that needs to be indexed.

Duplicate content. The same content accessible at multiple URLs (/blog/post and /blog/post/) confuses crawlers. Use canonical tags to specify the preferred URL:

<link rel="canonical" href="https://example.com/blog/database-migrations">

Missing alt text on images. Google Image Search is a real traffic source. Images without alt text can't be indexed.

Slow Time to First Byte. If your server takes 3 seconds to respond, the crawler may not wait. And neither will users.

Blocking important resources in robots.txt. Don't block CSS or JavaScript files — Google needs them to render your page correctly.

What NOT to Worry About

Keyword density. There is no optimal percentage. Write naturally. If the page is about database migrations, you'll naturally use relevant terms.

Meta keywords tag. Google has explicitly stated they ignore it. Don't bother.

Submitting to search engines. Google discovers pages through links and sitemaps. You don't need to manually submit URLs (though Google Search Console lets you request indexing for new pages).

SEO plugins that promise rankings. No plugin can guarantee rankings. They can help with meta tags and sitemaps. They can't make mediocre content rank.

Key Takeaway

Technical SEO for developers: use semantic HTML, write descriptive title tags and meta descriptions, optimize page speed, ensure mobile responsiveness, make pages crawlable through internal links and sitemaps, add structured data for rich results, use clean URLs, and serve over HTTPS. Don't stuff keywords, don't rely on client-side rendering for indexable content, and don't obsess over metrics that don't matter. Write useful content with solid technical foundations and search engines will do the rest.

bottom of page