SEO Knowledge Base

SEO for Nitrogen Projects

This knowledge base is the canonical reference for delivering enterprise-grade SEO on Nitrogen-based web projects. It documents both the frontend (what crawlers see in the HTML output) and the backend (how the server delivers content, manages URLs, handles redirects, and integrates with search engines).

Why two layers?

SEO is a cross-stack discipline. The frontend determines what crawlers parse; the backend determines whether crawlers can find content, whether duplicates exist, whether old URLs redirect correctly, and how content lifecycle interacts with the search index.

A typical case: a perfectly meta-tagged SvelteKit page that returns 200 status on the wrong URL parameter combination, generating thousands of duplicate-content entries in the index. The frontend is correct. The backend is wrong. Both must work together.

This is also why this knowledge base is part of the Nitrogen Frontend Ecosystem documentation rather than a separate backend project — SEO architecture decisions made on the frontend (URL structure, canonical strategy, hreflang) constrain the backend, and vice versa.

How to use this knowledge base

For a new Nitrogen-based project SEO setup, follow this sequence:

Architecture decisions first: read Server-Side Rendering, URL Structure, and Multilingual Routing to make the architectural choices that will constrain everything else.
Frontend implementation: Meta Tags, OpenGraph, Canonical URLs, Structured Data.
Backend infrastructure: Sitemap, Redirects, Caching, Security Headers.
Search engine integration: Google Search Console, IndexNow.
Quarterly audit: SEO Audit Checklist.

Frontend SEO scope

Topics covered in Frontend SEO:

Meta tags (title, description, robots, viewport)
OpenGraph and Twitter Card protocols
Canonical URLs
Hreflang for multilingual sites
Structured data (JSON-LD with Schema.org)
Build-time sitemap generation
robots.txt patterns
Core Web Vitals and performance
Accessibility as an SEO factor
Internal linking strategies
URL structure rules

Related package: @nitrogen/frontend-seo.

Backend SEO scope

Topics covered in Backend SEO:

Server-side rendering strategies (SSR, SSG, ISR, CSR)
HTTP status codes and their SEO implications
Redirect management (301, 302, 307, 308)
Server-side sitemap generation
CMS content workflow and SEO interaction
Slug history and automated redirects
Image optimization pipeline
Caching strategies across layers
Multilingual routing and translation management
Search engine integration (Google Search Console, Bing Webmaster Tools)
IndexNow protocol for instant indexing
Crawl budget management
HTTP security headers

The backend stack assumes Laravel 12 + Filament 4 as the Nitrogen platform default.

Cross-references

This knowledge base interconnects with other parts of the documentation:

@nitrogen/frontend-seo package docs — code reference for the SEO components
@nitrogen/frontend-tracking package docs — analytics integration
Skill: Consent Mode v2 Debug — debugging tracking which affects analytics-driven SEO insights
Skill: CSP allow-list — Content Security Policy without breaking SEO-relevant tracking
Skill: GTM Consent-aware Tags — search-relevant analytics setup

What’s NOT covered

E-commerce-specific SEO: product schema, review aggregation, shopping feeds. Add when the first e-commerce Nitrogen project arrives.
Local SEO: Google Business Profile, LocalBusiness schema in depth. Covered briefly in Structured Data, expanded later if needed.
News SEO: Google News inclusion. Niche topic; not in MVP.
AI search optimization: ChatGPT search, Perplexity, etc. Field is evolving too fast for stable guidance.
Voice search: another evolving area; covered when patterns stabilize.
AMP: deprecated by Google; not relevant.
Magyar nyelvű fordítás: en-only in MVP. Translation plan is a separate ADR.