Audit and Improve SEO

Improve the repository rather than only producing recommendations. Preserve the application's routing, design system, and content model.

Inspect Before Changing

Identify the framework, rendering model, route/page inventory, deployment target, public base URL, locales, CMS/content sources, and existing metadata or image-generation code.
Find indexable page types and their stable identity: marketing pages, articles, docs, products, category/listing pages, and paginated or filtered views. Exclude authenticated, personalized, search-result, duplicate, preview, and utility routes from indexing unless the product deliberately supports them.
Audit the rendered output and source for title/description coverage, canonical URLs, robots directives, sitemap, robots.txt, Open Graph/Twitter metadata, heading structure, semantic landmarks, internal links, image alt text, language declarations, structured data, and avoidable crawl or performance blockers.

Centralize metadata defaults and per-page overrides in the framework's native metadata mechanism. Use accurate, unique titles and descriptions derived from real content; do not invent keywords, duplicate boilerplate, or add irrelevant schema.
Generate absolute canonicals and social-image URLs from the configured production origin. Handle trailing slashes, locales, pagination, and query parameters consistently.
Add or repair robots.txt and a sitemap containing only canonical, indexable URLs. Include meaningful modification dates when the content model provides them.
Add JSON-LD only where it truthfully represents the page (for example Organization, WebSite, Article, BreadcrumbList, Product, or FAQPage). Keep it synchronized with visible content and validate its JSON.
Improve meaningful document structure, headings, link text, alt text, and crawlable navigation without changing product copy or visual behavior gratuitously.