SEO for Developers: A Practical Checklist That Actually Helps Pages Rank

Most SEO advice aimed at developers is either too vague or weirdly obsessed with tiny details that barely matter. This tutorial is the checklist I wish more developers used before launching a website. It is not about gaming Google. It is about making sure search engines can: Find your pages Understand what each page is about Trust the content enough to show it Send users to a page that actually works well If you build websites for clients, SaaS products, local businesses, or your own projects, this will keep you from shipping a technically nice site that search engines quietly ignore. 1. Make sure Google can crawl the site Before worrying about keywords, schema, or blog posts, check the boring foundation. If Google cannot crawl the site, nothing else matters. Check robots.txt Your robots.txt file should not block important pages. A basic version looks like this: User-agent: * Allow: / Sitemap: https://example.com/sitemap.xml Do not ship something like this to production: User-agent: * Disallow: / That blocks the entire site. It happens more often than people admit. Make sure the sitemap exists Your sitemap should be available at: https://example.com/sitemap.xml A good sitemap includes your important indexable pages: <urlset xmlns= "http://www.sitemaps.org/schemas/sitemap/0.9" > <url> <loc> https://example.com/ </loc> <lastmod> 2026-01-15 </lastmod> </url> <url> <loc> https://example.com/services/ </loc> <lastmod> 2026-01-15 </lastmod> </url> </urlset> Do not include: Redirected URLs 404 pages Duplicate pages Internal search results Staging URLs Noindex pages A sitemap is not a magic ranking button. It is a clean list of pages you actually want search engines to consider. 2. Use one clear URL for each page Duplicate versions of the same page can split signals and confuse crawlers. Pick one canonical version of the site: https://example.com Then make sure these redirect properly: http://example.com http://www.example.com https://www.example.com They should all point to the preferred version. For each page, add a canonical tag: <link rel= "canonical" href= "https://example.com/services/" /> Canonical tags are especially important when pages can be reached through multiple URLs. Examples: /services /services/ /services?ref=nav The canonical tells search engines which version should count. 3. Write title tags like a human, not a keyword robot Your title tag is one of the most important on-page SEO elements. It should explain the page clearly and give people a reason to click. Bad: <title> Home </title> Also bad: <title> SEO SEO Company Best SEO Services SEO Agency Near Me </title> Better: <title> SEO Services for Local Businesses | Example Agency </title> For local service pages, this structure usually works well: Primary Service in City, State | Brand Name Example: <title> Plumbing Repair in Ogden, UT | Example Plumbing </title> Keep it specific. Keep it readable. 4. Give every important page one clear H1 The H1 should describe the main topic of the page. Bad: <h1> Welcome </h1> Better: <h1> Website Design and SEO for Local Businesses </h1> For most pages, use one H1. Then use H2s and H3s to structure the rest of the content: <h1> Website Design and SEO for Local Businesses </h1> <h2> What We Help With </h2> <h3> Website Design </h3> <h3> Local SEO </h3> <h3> Google Ads </h3> <h2> Who We Work With </h2> <h2> Frequently Asked Questions </h2> Headings are not just visual styling. They help users and crawlers understand the page. 5. Make the page match search intent This is where a lot of technically solid sites fail. A page can load fast, have schema, pass Lighthouse, and still not rank because it does not answer the searcher’s actual question. Before building a page, ask: What would someone