tinybundle.app Website Audit

## Role
Act as a focused technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: seo_schema_presence.
- Fix title: Add basic structured data.
- Scanner check: Schema presence.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 12; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Detected 0 JSON-LD schema block(s).
- What needs attention: No JSON-LD schema was detected on the page.
- Why it matters: Structured data gives search and answer engines explicit facts about your product.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: JSON-LD generation in document head, route metadata, CMS SEO/schema fields, or server-rendered templates; metadata/head configuration, canonical URL logic, robots and sitemap routes, structured data blocks, page copy, headings, and internal navigation; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add JSON-LD for SoftwareApplication, Product, Organization, or WebSite using only accurate public facts.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add JSON-LD types that fit the visible page, such as Organization, WebSite, SoftwareApplication/Product, FAQPage, or BreadcrumbList.
- Use only accurate public facts and avoid unsupported ratings, prices, reviews, authors, or claims.
- Keep all metadata, headings, schema, canonical URLs, and visible copy consistent with the same public facts.
- Use accurate, crawlable, human-visible content as the source for search and answer-engine improvements.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The public HTML includes at least one application/ld+json block.
- The schema parses as valid JSON and matches facts visible or clearly supported on the public page.
- The public URL exposes the corrected crawl/search/answer signal in rendered HTML or reachable public files.
- The change should be visible to a fresh unauthenticated request and likely improve the related FreeScan SEO / AEO check on rescan.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused public web security remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: security_common_headers.
- Fix title: Add common public security headers.
- Scanner check: Common security headers.
- Category: Security.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 14 of 18 rule points lost.
- Evidence: Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
- What needs attention: Several basic browser protection headers were not visible.
- Why it matters: These headers reduce avoidable browser-side risk and show a baseline of care before launch.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: hosting headers, server middleware, edge/proxy config, CDN rules, and framework security header configuration; server, edge, CDN, hosting, proxy, form action, asset URL, cookie, and public file access configuration; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add only the missing protections among Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, frame protection, and Referrer-Policy. An existing CSP frame-ancestors directive already provides frame protection and must remain unchanged.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add missing common browser protection headers with values appropriate for the site.
- Treat an existing CSP frame-ancestors directive as valid frame protection; preserve the directive and its allowed origins exactly instead of adding or substituting X-Frame-Options.
- Test CSP or frame policies carefully so they do not break scripts, images, analytics, payments, embeds, or auth.
- Prefer narrow, production-safe security configuration changes over blanket disables or permissive rules.
- Preserve authentication, authorization, private paths, and sensitive file protections while fixing the public launch page.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Important security headers are visible on the public response.
- Any existing CSP frame-ancestors directive and its allowed origins remain unchanged.
- The page still renders and key flows still work after header changes.
- The public URL keeps legitimate visitors and assets working while removing the reported browser-side or public exposure risk.
- The change does not weaken security headers, authentication, authorization, or private route protections.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- If an existing Content-Security-Policy contains a frame-ancestors directive, preserve that directive exactly, including its allowed origins, unless the site owner explicitly asks to change it. Do not replace it with X-Frame-Options merely to satisfy this scan.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: accessibility_contrast.
- Fix title: Improve detectable color contrast.
- Scanner check: Basic contrast.
- Category: Accessibility.
- Status: fail.
- Severity: medium.
- Priority: 20; lower numbers are more urgent.
- Score impact: 8 of 8 rule points lost.
- Evidence: 5 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.02.
- What needs attention: The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: CSS variables, design tokens, theme config, text/background combinations, buttons, links, badges, and disabled states; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Adjust foreground/background colors or font treatment where contrast is too low.
- Preserve brand feel while making text readable in real viewport states.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Important text and controls meet reasonable contrast targets in rendered states.
- No new low-contrast states are introduced.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused web accessibility remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: accessibility_axe_violations.
- Fix title: Fix rendered axe accessibility violations.
- Scanner check: Rendered axe accessibility violations.
- Category: Accessibility.
- Status: fail.
- Severity: high.
- Priority: 5; lower numbers are more urgent.
- Score impact: 18 of 18 rule points lost.
- Evidence: axe found 1 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (6).
- What needs attention: The rendered page has accessibility rule violations detected by axe-core.
- Why it matters: axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: axe violation details, affected selectors, rendered DOM, component source, and interaction state that triggered the issue; semantic markup, labels, landmarks, headings, focus states, image rendering, form controls, and browser-rendered accessibility output; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Fix the top axe rule IDs first, especially critical and serious violations around names, roles, labels, headings, contrast, landmarks, and keyboard-accessible controls.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Fix each reported accessibility violation at the semantic source.
- Avoid suppressing automated checks unless there is a documented false positive.
- Fix the semantic or interaction source of the issue rather than hiding warnings with ARIA or visual-only workarounds.
- Keep keyboard, screen reader, and touch users in the verification path.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- Critical and serious axe issues tied to this page are resolved or clearly documented as non-reproducible.
- Fixes do not introduce new keyboard, label, contrast, or landmark regressions.
- The affected UI remains usable by keyboard and assistive technology and does not introduce heading, label, focus, or contrast regressions.
- The change can be checked in the browser or with an accessibility audit tool when available.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: design_trust_signals.
- Fix title: Add trust signals.
- Scanner check: Trust signals.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 16; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Detected 0 trust-signal keyword occurrence(s).
- What needs attention: The page does not expose detectable proof, customer, review, security, or credibility signals.
- Why it matters: Trust signals reduce hesitation when strangers see the product for the first time.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: testimonials, logos, security notes, proof points, customer examples, reviews, guarantees, and contact/legal links; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Add honest proof such as customer quotes, usage stats, founder credibility, security notes, or relevant logos.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Add accurate trust signals that are true and supportable.
- Do not invent customers, ratings, awards, claims, or testimonials.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The public page includes credible support for why visitors should trust the offer.
- All trust claims are accurate and safe to publish.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.

## Role
Act as a focused conversion-focused frontend quality remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tinybundle.app at https://www.tinybundle.app.
- Scanner check ID: design_rendered_layout.
- Fix title: Fix rendered layout ergonomics.
- Scanner check: Rendered layout ergonomics.
- Category: Design.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: Horizontal overflow: 0px. Small tap targets: 21.
- What needs attention: The browser-rendered page has layout or tap-target issues.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Status-specific guidance: A public check reported a failure. Reproduce or inspect the issue first, then make the smallest safe fix.
- Audience or recipient: The site owner, builder, or marketing team responsible for improving this public page.
- Constraints, examples, or source material: Treat the live URL as the public target to inspect, not as the only source of truth. When repository, CMS, or hosting access is available, use that implementation context before changing anything.
- Target outcome: After the fix is deployed and the public page is rescanned, this specific check should improve or pass without lowering other SEO / AEO, security, accessibility, or design signals.
- Likely places to inspect: mobile viewport, horizontal overflow sources, tap target sizes, fixed-position elements, menus, forms, and embeds; page layout, responsive CSS, component states, copy hierarchy, CTA placement, spacing tokens, rendered console output, and performance-sensitive assets; the route, template, component, CMS entry, theme file, or static page that renders the scanned URL; shared layout, metadata, routing, middleware, server, CDN, or hosting configuration if the issue is not in page content; existing tests, build scripts, preview commands, and deployment notes before choosing verification steps.
## Task
Use the provided context to safely complete this workflow: Remove elements wider than the viewport, add responsive constraints, and make important links, buttons, inputs, and controls at least 40px tall and wide where possible.
First reproduce or verify the issue from the public page and available implementation source. Then make the smallest stack-appropriate change that fixes the scanner signal and improves the real user experience.
Use this check-specific implementation guide:
- Constrain overflowing elements and increase small important tap targets where possible.
- Preserve layout intent while making the rendered page usable on real devices.
- Improve the actual rendered page at mobile and desktop sizes, not only the source code shape.
- Preserve core conversion flows while making layout, hierarchy, readability, or runtime health better.
- Keep the implementation stack-appropriate: use the existing framework, CMS, hosting provider, design system, and deployment workflow already in the project.
Acceptance criteria for this fix:
- The rendered page has no meaningful horizontal overflow.
- Important links, buttons, inputs, and controls are comfortably tappable.
- The rendered page is visually stable and usable on mobile and desktop viewports.
- The fix does not hide content, break CTAs, introduce console errors, or reduce clarity for visitors.
- A fresh FreeScan rescan should show this check improved or passing after deployment.
## Output
Return a structured response with these headings: Findings, Changes Made, Verification Results, Rescan Expectation, Rollback Notes, Assumptions.
## Rules
- Ask a clarifying question when required context is missing.
- Preserve the user's intent and avoid inventing facts.
- Verify the issue exists before changing code or content. If the issue is not reproducible, explain what you checked and recommend no code change.
- If the live URL and implementation source disagree, trust the implementation source for edits and use the live URL only to understand current public behavior.
- Keep the change narrowly scoped to this fix unless another change is required to avoid a regression.
- Match the existing framework, style, design system, routing patterns, and content conventions.
- Preserve existing URLs, forms, analytics, SEO metadata, accessibility semantics, and conversion flows unless the fix explicitly requires changing them.
- Do not perform broad refactors, dependency upgrades, redesigns, rewrites, migrations, file deletions, route changes, or destructive commands unless they are explicitly required and approved.
- Make changes that are easy to review and roll back.
- Prefer editing the canonical source of the page over patching built output, generated files, CDN-cached HTML, or minified assets.
- Do not make a cosmetic or placeholder change just to satisfy the scanner; the public page should be materially better for visitors, crawlers, or assistive technology.
- Verify the result with the smallest reliable test, build, browser check, or manual inspection available.
## Safety
- Do not request, expose, or reproduce sensitive data.
- Redact private details from examples unless the user explicitly says they are safe to include.
- Do not use credentials, cookies, authenticated data, hidden form values, or private response bodies.
- Do not weaken security headers, authentication, authorization, privacy controls, accessibility, or error handling to make the scan pass.