Optimise Seo

Optimise SEO

• IS: crawlability, metadata, structured data, canonicals, redirects, hreflang, Core Web Vitals, programmatic SEO, security/privacy headers, and error-page status behaviour for Next.js App Router apps.
• IS NOT: visual redesigns or layout changes (use ui-design), or page-level UI quality review (use ui-audit). Making a site readable by AI agents (llms.txt, MCP discovery, WebMCP) is out of scope; research current specs rather than relying on static SEO guidance.

Allowed surface: metadata, structured data, semantic HTML, internal links, alt text, app/sitemap.ts, app/robots.ts, next.config.ts redirects and headers, error pages, performance tuning. Never touch component styling or layout.

Workflow

Copy and track this checklist:

SEO progress:
- [ ] Step 1: Inventory routes and decide index intent per route
- [ ] Step 2: Fix crawl/index foundations (sitemap, robots, canonicals, redirects, status codes)
- [ ] Step 3: Implement metadata + structured data
- [ ] Step 4: Improve semantics, internal links, and Core Web Vitals
- [ ] Step 5: Validate with references/seo-checklist.md and report evidence

Before writing code for steps 2-4, read [references/nextjs-implementation.md](references/nextjs-implementation.md): App Router patterns (Metadata API, generateMetadata, sitemap index, JSON-LD component, OG image generation, headers()/redirects() config).

Must-have on every site

• app/sitemap.ts lists all public URLs; app/robots.ts links to it
• Canonical URL set and consistent on every page (one host, one casing, one trailing-slash policy)
• Unique title and description per page via metadata or generateMetadata
• OpenGraph + Twitter Card tags with a 1200x630 image
• JSON-LD: Organization and WebSite on the homepage, BreadcrumbList on inner pages, plus Article/Product/FAQ where the content type matches. Define each entity once in a @graph with a stable @id (/#person, /#website, /#organization); reference by @id, don't duplicate. On articles keep Person as author, use an Organization (with a logo) as publisher
• One h1 per page with logical h2-h6 hierarchy
• Descriptive alt text, internal links between related pages, CWV in target (LCP ` | correct status, redirects, canonical host |

| Served HTML metadata | curl -s \| rg "canonical\|og:\|twitter:\|application/ld\+json" | tags present in source | | Robots | curl -s /robots.txt | expected allow/disallow and sitemap | | Sitemap | curl -s /sitemap.xml | indexed routes, absolute URLs, fresh lastmod when used | | Lighthouse | npx lighthouse --only-categories=seo,performance --output=json --output-path=.lighthouse-seo.json | SEO and Performance >= 90, or blockers listed | | JSON-LD | Google Rich Results Test URL/result | valid or documented unsupported schema | | Search Console after deploy | Pages/Coverage and enhancement reports | no new warnings; indexed/excluded changes explained |

Report remaining blockers with exact URLs and owner/action.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: mblode
• Source: mblode/agent-skills
• License: MIT
• Homepage: https://www.skills.sh/mblode/agent-skills

Install and usage instructions live in the source repository linked above.