SEO for Custom-Built Sites

The responsibility shift to developers, avoiding common dev-introduced SEO mistakes, and the SEO handoff.

The Responsibility Shift

With custom builds, there is no platform safety net. WordPress handles meta tags, sitemaps, and schema if you install a plugin. A custom site has no defaults. Every SEO feature must be deliberately implemented.

This is an advantage (complete control) and a liability (complete responsibility). A developer who does not know SEO can build an SEO disaster without realising.

Common Developer-Introduced SEO Mistakes

Soft 404s (200 Status on Missing Pages)

A developer returns HTTP 200 (OK) for pages that do not exist. The user sees an error message, but the server says "success." Googlebot crawls these pages, indexes them as real content, and gets confused. This wastes crawl budget and damages rankings.

Correct approach: return HTTP 404 (Not Found) or 410 (Gone) for missing pages. Googlebot understands immediately that the page should not be indexed.

Missing Canonical Tags

Every page should include a canonical tag pointing to itself (or to the primary version if duplicates exist). A custom site with no canonical tags creates duplicate content issues. The developer must add this deliberately.

No XML Sitemap

Generating an XML sitemap requires deliberate implementation. A custom site might have hundreds of pages with no sitemap. Googlebot must discover everything through crawling, which is slow.

Blocking Googlebot with robots.txt

A developer might create a robots.txt during development (to keep the site out of search while building) and forget to remove the restriction after launch. The site remains blocked from indexation.

Client-Side Rendering Only

If the entire site is rendered with JavaScript in the browser, Googlebot must render JavaScript to see content. This delays indexation and reduces crawl efficiency. The developer must implement server-side rendering (SSR) or use a framework that handles this automatically.

No Meta Tags or Schema

Meta titles, descriptions, and structured data must be generated per page. A developer might hardcode meta tags or skip them entirely. Both are bad. Proper implementation requires templates generating unique meta tags from content.

Broken Internal Links Post-Migration

If the site is migrated to a new domain or URL structure, old URLs must 301 redirect to new ones. If not, links are broken, crawl budget is wasted, and authority is lost.

No Redirect Plan

URLs change over time. When they do, there must be a system for implementing redirects (ideally in a database, not hardcoded). Without this, every URL change breaks links.

SEO Handoff: Before You Build

The best time to address SEO in custom builds is before development starts. An SEO specialist should provide a technical brief addressing:

Required meta tags per page
Canonical tag strategy
XML sitemap structure
robots.txt configuration
Schema markup requirements (product, organization, article, etc.)
URL structure and slugs
Internal linking architecture
Rendering approach (SSR, SSG, or CSR)
Performance targets (Core Web Vitals)

This brief becomes the developer's specification. Including it prevents rework and ensures SEO is built in from the start, not bolted on later.

Essential Minimum Implementation

Every custom site must have:

HTTPS: All pages served over SSL/TLS
Canonical tags: One canonical tag per page (pointing to itself or primary version)
XML sitemap: At /sitemap.xml listing all indexable pages
robots.txt: At /robots.txt allowing indexation of public content
Meta titles and descriptions: Unique, non-empty per page
Proper HTTP status codes: 200 for valid pages, 404 for missing, 301 for redirects
301 redirects: Any changed URLs must redirect to new locations
Structured data: Schema markup for key page types (product, article, organization)
Mobile responsiveness: Site must display properly on mobile
Fast page load: Target Core Web Vitals < 2.5s LCP, < 100ms INP, < 0.1 CLS

This is not optional. These are baseline requirements for any site that expects organic traffic.

Ongoing Monitoring and Maintenance

After launch, monitor: (1) Google Search Console for crawl errors and coverage issues, (2) Page Speed Insights for Core Web Vitals, (3) Your analytics for traffic and behavior, (4) Your log files for crawl patterns.

Address issues immediately. A 404 error affecting 100 pages needs fixing now, not next quarter.

Custom Build Advantage

A well-built custom site can outperform any platform. Complete control over rendering, performance, schema, and architecture allows for optimisation impossible on platforms. But this requires a developer who understands SEO or an SEO specialist collaborating with the developer.

When Custom Builds Are Worth It

You have unique or complex requirements platforms cannot meet
You are scaling to millions of pages (where platform limits apply)
You have a team of experienced developers
Long-term ROI justifies the development cost

For most sites, WordPress or Shopify is simpler and faster to launch. Use custom builds only if the cost/benefit is clear.

How This Connects

Custom builds are powerful but dangerous. Without SEO knowledge during development, you can build a site that never ranks. With proper planning and a developer who understands SEO (or collaboration with an SEO specialist), custom builds offer advantages no platform can match.