Add SEO Editing Capabilities for Upcoming Website #861
Description
As we prepare the new Status Network website, I need the ability to manage core SEO elements independently, without requiring code deployments for every update. This is essential for ongoing optimisation, campaign work, and adapting content as the ecosystem grows. This same would be needed for status.app
Below is a breakdown of what I would need to be editable on my side, and what can be implemented once by the development team.
SEO Elements That Need to Be Editable (per page):
These require regular updates and should be exposed through a simple config, front-matter, or similar editable mechanism:
• Meta title
• Meta description
• Canonical tag
• Open Graph metadata (title, description, image)
• Twitter card metadata
• JSON-LD schema (preferably injected via a per-page block)
• Image alt text overrides
• H1/H2 structure + page copy
Having direct access to these fields will allow continuous SEO optimisation, content iteration, and campaign-driven updates without developer involvement.
SEO Items Devs Only Need to Implement Once:
These do not require ongoing editing but must be implemented at code level:
• robots.txt setup
• Automatic XML sitemap generation
• Redirect system (301/302)
• Image optimisation (WebP/AVIF support, lazy loading)
• Clean, crawlable URL structure
• SEO-friendly 404 page
• Crawlable navigation
• Proper script loading (async/defer)
To ensure the new website is fully SEO-ready at launch and gives growth/SEO the ability to iterate quickly without blocking developers.
Please advise on the easiest implementation approach based on the current codebase (config files, front-matter, templates, etc.).