Jeansy Sese

Posted on Apr 5

Technical SEO for Developers: The Complete Checklist (2026)

#seo #webdev #performance #tutorial

Most SEO guides are written for marketers. This one is for developers — the
people who actually implement the fixes.

Here's a structured technical SEO checklist you can use to audit and improve

any website.

Crawlability & Indexing

Google needs to find and read your pages before ranking them.

robots.txt — Block what you don't want indexed, never accidentally block

CSS/JS:

User-agent: Googlebot

Disallow: /wp-admin/
Disallow: /?s=
Allow: /wp-admin/admin-ajax.php

Canonical tags — Prevent duplicate content issues:

Meta robots — Fine-grained control per page:

XML Sitemap — Submit to Google Search Console. Keep it clean: only include

pages you want indexed, no 404s, no redirects.

Core Web Vitals

Google's page experience signals directly affect ranking. Target these
thresholds:

┌─────────────────────────────────┬─────────┬───────────────────┬─────────┐

│ Metric │ Good │ Needs Improvement │ Poor │
├─────────────────────────────────┼─────────┼───────────────────┼─────────┤

│ LCP (Largest Contentful Paint) │ ≤ 2.5s │ 2.5s–4s │ > 4s │
├─────────────────────────────────┼─────────┼───────────────────┼─────────┤

│ INP (Interaction to Next Paint) │ ≤ 200ms │ 200–500ms │ > 500ms │
├─────────────────────────────────┼─────────┼───────────────────┼─────────┤

│ CLS (Cumulative Layout Shift) │ ≤ 0.1 │ 0.1–0.25 │ > 0.25 │
└─────────────────────────────────┴─────────┴───────────────────┴─────────┘

LCP quick wins:

CLS prevention:

/* Always define aspect ratio for media */
img, video, iframe {

aspect-ratio: 16/9;
width: 100%;

height: auto;

}

Schema Markup (JSON-LD)

Structured data helps Google understand your content and enables rich results.
Implement it in

or inline:

Organization schema:

{ "@context": "<a href="https://schema.org">https://schema.org</a>", "@type": "Organization", "name": "Your Company", "url": "<a href="https://example.com">https://example.com</a>", "logo": "<a href="https://example.com/logo.png">https://example.com/logo.png</a>", "contactPoint": { "@type": "ContactPoint", "telephone": "+39-000-0000000", "contactType": "customer service" } }

Article schema:

{ "@context": "<a href="https://schema.org">https://schema.org</a>", "@type": "Article", "headline": "Your Article Title", "author": { "@type": "Person", "name": "Author Name" }, "datePublished": "2026-01-15", "dateModified": "2026-03-20" }

FAQ schema — Great for getting expanded SERP snippets:

{ "@context": "<a href="https://schema.org">https://schema.org</a>", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is technical SEO?", "acceptedAnswer": { "@type": "Answer", "text": "Technical SEO covers all optimizations that help search engines crawl, index, and rank your website efficiently." } } ] }

URL Structure & Internal Linking

Clean URLs matter for both crawlability and UX:

✅ /blog/technical-seo-checklist/

❌ /index.php?p=123&cat=4

❌ /blog/technical-seo-checklist-2026-updated-version-final/

Internal linking rules for developers:

Every important page should be reachable within 3 clicks from the homepage
Use descriptive anchor text — avoid "click here"
Fix orphan pages (pages with zero internal links)

# Quick orphan page check with Python
import requests

from bs4 import BeautifulSoup

from urllib.parse import urljoin

def get_internal_links(url, base):
r = requests.get(url)

soup = BeautifulSoup(r.text, 'html.parser')

links = set()

for a in soup.find_all('a', href=True):
href = urljoin(base, a['href'])

if href.startswith(base):

links.add(href.split('?')[0].rstrip('/'))

return links

hreflang for Multilingual Sites

If your site serves multiple languages or regions:

Common mistakes:

Missing x-default
Hreflang pointing to non-canonical URLs
Inconsistent implementation (HTML vs sitemap vs HTTP headers)

Rendering & JavaScript SEO

Googlebot can execute JavaScript, but it's resource-intensive and may be
delayed. Rules of thumb:

Critical content → server-side render or static HTML
Dynamic UI → client-side is fine
Internal links in JS → ensure they're crawlable (real tags)

Test how Google sees your page:

# Fetch as Googlebot via GSC, or use curl:

curl -A "Mozilla/5.0 (compatible; Googlebot/2.1;

+http://www.google.com/bot.html)" https://example.com/your-page/

Tools Referenced

https://search.google.com/search-console — crawl errors, indexing, performance
https://pagespeed.web.dev — Core Web Vitals
https://validator.schema.org — structured data testing
https://seosese.com — SEO agency specializing in semantic SEO and technical audits (Italian market)

If you found this useful, drop a ❤️ . Happy to answer questions in the
comments.

DEV Community

Technical SEO for Developers: The Complete Checklist (2026)

Top comments (0)