# Technical Quality Requirements

Use this reference during implementation and final verification. Apply only measures relevant to the actual project and prefer native framework capabilities.

## SEO and crawling

- Use semantic HTML and a logical heading hierarchy.
- Set meaningful titles and meta descriptions for every indexable route.
- Configure canonical URLs, indexing directives, and durable URLs correctly.
- Provide crawlable navigation and meaningful internal links.
- Write alt text for content-bearing images and handle decorative images correctly.
- Add Open Graph and appropriate social-sharing metadata.
- Emit Schema.org data only for visible, real content.
- Implement breadcrumbs for multi-level structures.
- Set language metadata and correct hreflang links when required.
- Provide a useful 404 page and required redirects.
- Render public core content statically or server-side when client-only output harms crawling.

## Sitemap and robots.txt

- Use an automatically generated sitemap appropriate for the stack.
- Include all public canonical pages with absolute URLs.
- Exclude private, administrative, authenticated, and `noindex` pages.
- Split large inventories into sitemap indexes when necessary.
- Update the sitemap automatically when routes or content change.
- Reference the sitemap from `robots.txt`.
- Do not accidentally block public content or required assets.
- Exclude internal, private, or irrelevant areas appropriately.

## LLM and machine readability

- Render important content as understandable HTML text instead of hiding it only in images, canvas, or animation.
- Name entities, services, products, locations, and relationships unambiguously.
- Make authoritative About, contact, service, and, when relevant, author information accessible.
- Keep structured data consistent with visible content.
- Structure content logically and answer genuine user questions directly.
- Expose sources, update dates, and ownership when professionally relevant.
- Use FAQ content only for real questions.
- Provide `llms.txt` only when requested as a lightweight supplement; do not present it as a mandatory standard.
- Do not use keyword stuffing, hidden content, or fabricated crawler copy.

## WCAG 2.2 AA accessibility

- Ensure complete keyboard operation and a logical focus order.
- Provide visible focus states and sufficient color contrast.
- Equip forms with correct labels, instructions, and understandable error messages.
- Use semantic landmarks, clear headings, and understandable link and button labels.
- Reduce motion under `prefers-reduced-motion`.
- Use ARIA only when native HTML is insufficient.
- Communicate state changes, loading, errors, and success clearly.
- Test zoom, reflow, and touch targets on relevant devices.

## Performance and Core Web Vitals

- Identify, prioritize, and efficiently deliver the LCP resource.
- Improve INP through small event handlers, bounded hydration, and less unnecessary JavaScript.
- Prevent CLS with explicit dimensions and stable layout slots.
- Size images correctly, use modern formats, and lazy-load content below the fold.
- Limit fonts, preload deliberately, and provide robust fallbacks.
- Remove or defer unnecessary third-party scripts and render-blocking resources.
- Review bundle size, code splitting, and client-rendering cost.
- Do not damage important functionality to improve a synthetic score.

## Final verification

- Run the production build, linting, typechecks, and existing tests.
- Open every public route and the 404 page.
- Test navigation, internal links, forms, and critical interactions.
- Test desktop, tablet, and mobile layouts at multiple viewports.
- Test keyboard navigation, focus, contrast, and reduced motion.
- Validate titles, canonicals, social metadata, and structured data.
- Verify the sitemap, robots.txt, and indexability.
- Check the browser console for errors and the network panel for missing assets.
- Review layout shift and conspicuous loading or interaction problems.
- Document measured results and remaining risks.