Technical SEO for Developers: What Actually Moves the Needle

SEO often gets treated as a marketing topic, but a big part of it is purely technical, and developers control it. If search engines can't crawl a page, can't render its content, or see five duplicate versions of it, no amount of great writing will help. The good news is that technical SEO is mostly a checklist, and it stays remarkably stable over time.

1. Make pages crawlable and indexable

• Return the right status codes. Real pages return 200, missing ones 404 (not a "not found" page with status 200), moved ones 301. (Status codes explained.)
• Check robots.txt. It controls crawling. A leftover Disallow: / from staging has hidden entire sites from search.
• Use noindex deliberately. A <meta name="robots" content="noindex"> keeps a page out of results. Use it for thank-you pages, internal search results and admin areas, not by accident on real content.
• Link to pages with real <a href> links. Crawlers follow links; they don't click buttons that change routes with JavaScript only.

2. Make content visible in the HTML

Search engines can render JavaScript, but it's slower and less reliable than reading HTML, and many social preview bots don't run JavaScript at all. For public pages, server-render or statically generate the main content. (Rendering strategies.)

Quick test: view the page source (not DevTools' Elements panel). If your main content isn't there, crawlers may not see it either.

3. Unique titles and meta descriptions

Each page needs:

<title>How to Fix CORS Errors: A Clear Guide | YourSite</title>
<meta name="description" content="Why browsers block cross-origin requests, how preflight works, and the right server-side fixes.">

• Titles: unique, descriptive, with the main topic near the start, roughly 50 to 60 characters before they get cut off.
• Descriptions: a compelling summary of about 150 to 160 characters. They don't directly affect ranking, but they affect whether people click.

4. One URL per piece of content

The same content at several URLs splits ranking signals:

• http:// vs https://, www vs non-www: pick one and 301 redirect the rest.
• Trailing slashes, uppercase letters and tracking parameters create duplicates too.
• Add a canonical tag pointing to the preferred URL:

<link rel="canonical" href="https://example.com/blog/fix-cors-errors-guide">

5. Clean, readable URLs

/blog/fix-cors-errors-guide beats /post.php?id=4821. Use lowercase words separated by hyphens, keep them short, and don't change them without a 301 redirect.

6. XML sitemap

List your indexable pages in a sitemap (most frameworks can generate one), reference it in robots.txt, and submit it in Google Search Console. Include only canonical, indexable URLs with accurate last-modified dates.

7. Heading structure

One <h1> describing the page, then <h2> and <h3> in logical order. Headings help both search engines and screen reader users understand the page. (Accessibility overlaps here.)

8. Structured data

JSON-LD structured data describes your content explicitly: an article, a product, a FAQ, breadcrumbs, an organisation. It can make pages eligible for richer search results.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Fix CORS Errors",
  "datePublished": "2026-03-14",
  "author": { "@type": "Person", "name": "Your Name" }
}
</script>

Only mark up content that's actually visible on the page, and validate it with Google's Rich Results Test.

9. Speed and Core Web Vitals

Page experience signals include loading speed (LCP), responsiveness (INP) and visual stability (CLS). They matter most as a tie-breaker between similarly relevant pages, and they strongly affect whether visitors stay. (Fixing a slow site and optimising images.)

10. Internal linking

Link related pages to each other with descriptive anchor text ("our guide to database indexing," not "click here"). Internal links help crawlers discover pages, spread authority across your site and keep readers around longer.

11. Social previews

Open Graph and Twitter card tags control how links look when shared:

<meta property="og:title" content="How to Fix CORS Errors">
<meta property="og:description" content="Why browsers block requests and how to fix it properly.">
<meta property="og:image" content="https://example.com/og/cors.jpg">

A 1200×630 image works well across platforms.

12. Mobile-friendliness

Search engines primarily evaluate the mobile version of your pages. Make sure content, structured data and metadata are the same on mobile as on desktop. (Responsive design.)

Tools you'll actually use

• Google Search Console: indexing status, search queries, crawl errors and Core Web Vitals. Free and essential.
• PageSpeed Insights: performance data for any URL.
• View source and curl: see exactly what crawlers receive.

FAQ

What is technical SEO?

The parts of SEO that make a site crawlable, indexable, fast and understandable to search engines: status codes, rendering, URLs, canonicals, sitemaps, structured data and performance.

Does JavaScript hurt SEO?

Not necessarily, but content rendered only on the client is slower and less reliable for crawlers to process. Server-side rendering or static generation is safer for public pages.

What is a canonical tag?

A tag that tells search engines which URL is the preferred version of a page, consolidating signals when the same content is reachable at several URLs.