tern.so 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 tern.so at https://tern.so.
- Scanner check ID: seo_crawler_access.
- Fix title: Improve AI search and crawler readiness.
- Scanner check: Crawler access.
- Category: SEO / AEO.
- Status: fail.
- Severity: critical.
- Priority: 2; lower numbers are more urgent.
- Score impact: 4 of 14 rule points lost.
- Evidence: FreeScan.app reached the public page with HTTP 200. robots.txt blocks OAI-SearchBot, Claude-SearchBot, Googlebot, and 5 more from AI search or discovery for this page path. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 70%: discovery 45/45, index and snippet eligibility 5/25, synthetic reachability 20/20, sitemap freshness 0/10.
- What needs attention: One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
- Why it matters: AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
- 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: robots.txt rules for the scanned path and common search or AI crawler user agents; CDN, WAF, bot protection, rate-limit, firewall, and security challenge rules that apply to public pages; server responses for unauthenticated HEAD and GET requests to the scanned URL; 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: Use the component scores and exact matched robots rules in the crawler report. Fix blocked search agents, noindex or snippet restrictions, canonical or sitemap gaps, and synthetic WAF/challenge failures. Preserve intentional training opt-outs and keep private, admin, and authenticated paths protected before rescanning.
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:
- Identify exactly which crawler group or HTTP/security layer is blocking access before changing rules.
- Allow legitimate public-page crawling with narrow path, user-agent, or verified-bot rules instead of disabling bot protection globally.
- Keep admin, account, staging, preview, API, and private paths blocked or authenticated.
- 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:
- A fresh unauthenticated request to the scanned public URL no longer returns crawler-blocking HTTP statuses such as 401, 403, 429, or 503.
- robots.txt does not disallow the scanned public path for the intended search and AI crawler user agents.
- Security controls still protect private and authenticated areas.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_title_present.
- Fix title: Write a clear page title.
- Scanner check: Page title.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 8; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Title is 4 characters.
- What needs attention: The browser title is missing, too short, or too long for a reliable search result headline.
- Why it matters: Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
- 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: page title source in metadata config, document head, CMS SEO fields, layout defaults, or server-rendered template; 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: Set one concise title tag, ideally 10 to 70 characters, that includes the product name and the main promise.
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:
- Write one specific title that names the product, page, or offer and its main outcome.
- Avoid duplicated title tags, keyword stuffing, vague words like Home, and titles that depend only on client-side rendering.
- 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 has exactly one useful title between roughly 10 and 70 characters.
- The title matches the visible page promise and brand/product identity.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_meta_description.
- Fix title: Add a useful meta description.
- Scanner check: Meta description.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 3; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: Meta description is 29 characters.
- What needs attention: The page does not expose a strong short summary for search and answer engines.
- Why it matters: A missing description makes previews weaker when early users share or find the page.
- 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: meta description source in metadata config, CMS SEO fields, layout defaults, route config, or template head; 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 a meta description around 50 to 170 characters that says who the product helps and what outcome it creates.
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:
- Write a concise page summary that states who the page helps and what outcome it offers.
- Avoid generic marketing filler, duplicated descriptions across unrelated pages, and facts not visible or supported on the page.
- 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 exposes one accurate meta description around 50 to 170 characters.
- The description aligns with the title, H1, Open Graph description, and visible page content.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_heading_structure.
- Fix title: Use one clear H1 and ordered headings.
- Scanner check: Heading structure.
- Category: SEO / AEO.
- Status: fail.
- Severity: medium.
- Priority: 9; lower numbers are more urgent.
- Score impact: 8 of 8 rule points lost.
- Evidence: Detected 1 H1 heading(s) and 17 total headings.
- What needs attention: The page heading structure is either missing a single main heading or skips heading levels.
- Why it matters: Clear headings help visitors, search engines, and assistive technology understand the page quickly.
- 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: page heading tags in templates, CMS rich text, markdown, MDX, and reusable section components; 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: Keep one H1 for the main promise, then use H2 and H3 headings in order for sections below it.
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:
- Keep one H1 for the page promise or page identity.
- Use H2 for major sections and H3 for subsections without skipping levels for visual styling.
- 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 rendered page has one clear H1 and an ordered heading outline.
- Styling is handled with CSS/classes rather than incorrect heading levels.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_canonical.
- Fix title: Add a canonical URL.
- Scanner check: Canonical tag.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 9; lower numbers are more urgent.
- Score impact: 10 of 10 rule points lost.
- Evidence: No canonical link tag was detected.
- What needs attention: The page does not declare which public URL is the preferred version.
- Why it matters: A canonical tag reduces duplicate URL confusion before marketing links start spreading.
- 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: canonical URL generation, site URL environment variables, routing aliases, trailing slash behavior, and deployment domains; 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 a canonical link tag that points to the final public landing page URL.
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:
- Set the canonical link to the preferred final public URL for this page.
- Keep canonical, og:url, sitemap URLs, and redirects aligned where possible.
- 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 exposes one canonical URL for the scanned page.
- The canonical points to the intended public destination and avoids staging, localhost, tracking parameters, or duplicate variants.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish a valid sitemap.
- Scanner check: Sitemap validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 of 12 rule points lost.
- Evidence: sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
- What needs attention: The sitemap file was not reachable or did not look like valid sitemap XML.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- 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: robots.txt Sitemap directives, static sitemap files, dynamic sitemap routes, sitemap indexes, canonical URL generation, and deployment output; 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 a static sitemap file, dynamic sitemap route, or robots.txt Sitemap directive that returns valid urlset or sitemapindex XML. Include public canonical URLs and confirm the sitemap URL returns HTTP 200.
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:
- Provide a reachable sitemap URL with valid urlset or sitemapindex XML. Preserve an existing robots.txt Sitemap directive such as /sitemap_index.xml when it is intentional and valid.
- Include canonical public URLs and avoid localhost, staging, private, noindex, or duplicate URLs.
- 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 sitemap URL declared in robots.txt, or /sitemap.xml when no directive exists, returns HTTP 200 with a valid urlset or sitemapindex root.
- The sitemap contains at least the scanned public page or its canonical equivalent.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- 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 technical SEO, AEO, and crawlability remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: seo_indexability.
- Fix title: Remove noindex signals.
- Scanner check: Indexability signals.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 2; lower numbers are more urgent.
- Score impact: 9 of 9 rule points lost.
- Evidence: A noindex directive was detected.
- What needs attention: The page appears to tell crawlers not to index it.
- Why it matters: A noindex directive can prevent the launch page from appearing in search results.
- 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: meta robots tags, X-Robots-Tag headers, route metadata, middleware/proxy headers, and deployment protection settings; 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: Remove noindex from meta robots or X-Robots-Tag headers once the page is ready to be public.
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:
- Remove noindex or equivalent blocking directives from the public launch page when it is meant to be discoverable.
- Keep noindex on staging, preview, private, search result, and authenticated pages where appropriate.
- 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 scanned public page no longer sends noindex through HTML or response headers.
- Private and non-public pages remain protected from indexing.
- 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 tern.so at https://tern.so.
- 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: 18 of 18 rule points lost.
- Evidence: Detected 0 of 5 common public security controls. Present: none. Missing: strict-transport-security, 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 public web security remediation expert who can inspect the public page and safely improve the underlying implementation.
## Inputs
- Primary context: Improve tern.so at https://tern.so.
- Scanner check ID: security_sensitive_file_probes.
- Fix title: Remove exposed sensitive files.
- Scanner check: Sensitive file probes.
- Category: Security.
- Status: fail.
- Severity: critical.
- Priority: 1; lower numbers are more urgent.
- Score impact: 16 of 16 rule points lost.
- Evidence: A small allowlist probe returned a public success response.
- What needs attention: A small public allowlist probe found a sensitive-looking file path.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- 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: public/static folders, storage buckets, web server rules, backup artifacts, config files, and deployment output; 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: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.
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:
- Remove exposed sensitive-looking files from public hosting or block public access to those paths.
- If secrets may have been exposed, recommend rotating them and checking access logs.
- 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:
- The probed sensitive path no longer returns a public success response.
- No legitimate public asset or route is removed accidentally.
- 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.
- 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 tern.so at https://tern.so.
- Scanner check ID: accessibility_heading_order.
- Fix title: Fix heading order.
- Scanner check: Heading order.
- Category: Accessibility.
- Status: fail.
- Severity: medium.
- Priority: 13; lower numbers are more urgent.
- Score impact: 11 of 11 rule points lost.
- Evidence: Heading levels found: 1, 3, 3, 3, 2, 3, 3, 3, 2, 2, 2, 2, 2, 2, 3, 3, 2.
- What needs attention: Heading levels appear to jump or start without a clear hierarchy.
- Why it matters: A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
- 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: heading tags in templates, CMS rich text, markdown/MDX, accordions, cards, and reusable sections; 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: Use headings in order: one H1, then H2 for major sections, then H3 for subsections.
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:
- Correct heading levels without changing visual hierarchy unnecessarily.
- Use CSS classes for visual size rather than jumping heading levels.
- 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:
- Heading levels follow a logical order from one H1 through nested section headings.
- The page remains easy to scan visually and semantically.
- 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 tern.so at https://tern.so.
- 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: 19 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.57.
- 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.
## Affected Elements
### Work
- Source: FreeScan rendered contrast check.
- Selector: span.min-w-0.flex-1:nth-of-type(3) > span.flex.items-center:nth-of-type(1) > span.flex.shrink-0:nth-of-type(2) > span.hidden.max-w-16:nth-of-type(1).
- Current colors: foreground rgb(212, 106, 58) on background rgb(235, 216, 203).
- Contrast: 2.57:1 measured; 4.5:1 required.
- Suggested foreground: #974B29, which measures 4.54:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: span.min-w-0.flex-1:nth-of-type(3) > span.flex.items-center:nth-of-type(1) > span.flex.shrink-0:nth-of-type(2) > span.hidden.max-w-16:nth-of-type(1).
- Current colors: foreground rgb(212, 106, 58) on background rgb(236, 218, 205).
- Contrast: 2.61:1 measured; 4.5:1 required.
- Suggested foreground: #994C2A, which measures 4.52:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: span.min-w-0.flex-1:nth-of-type(3) > span.flex.items-center:nth-of-type(1) > span.flex.shrink-0:nth-of-type(2) > span.hidden.max-w-16:nth-of-type(1).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: div.flex.items-center > div.min-w-0.flex-1 > div.flex.items-center > span.rounded-full.px-1\.5:nth-of-type(2).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: div.group.flex:nth-of-type(1) > div.flex.shrink-0:nth-of-type(1) > div.flex.items-center:nth-of-type(1) > span.ml-2.shrink-0:nth-of-type(3).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: div.group.flex:nth-of-type(1) > div.flex.shrink-0:nth-of-type(1) > div.flex.items-center:nth-of-type(3) > span.ml-2.shrink-0:nth-of-type(3).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: div.group.flex:nth-of-type(1) > div.flex.shrink-0:nth-of-type(2) > div.flex.items-center:nth-of-type(1) > span.ml-2.shrink-0:nth-of-type(3).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
### Work
- Source: FreeScan rendered contrast check.
- Selector: div.group.flex:nth-of-type(1) > div.flex.shrink-0:nth-of-type(2) > div.flex.items-center:nth-of-type(3) > span.ml-2.shrink-0:nth-of-type(3).
- Current colors: foreground rgb(212, 106, 58) on background rgb(247, 231, 222).
- Contrast: 2.94:1 measured; 4.5:1 required.
- Suggested foreground: #A5532D, which measures 4.5:1 on the current background.
## 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 tern.so at https://tern.so.
- 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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (6), image-redundant-alt (1).
- 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.
## Affected Elements
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: div:nth-child(2) > .text-white\/35.tracking-\[0\.18em\].uppercase.
- Current colors: foreground #716f6d on background #25221e.
- Contrast: 3.16:1 measured; 4.5:1 required.
- Suggested foreground: #8A8987, which measures 4.53:1 on the current background.
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: div:nth-child(3) > .text-white\/35.tracking-\[0\.18em\].uppercase.
- Current colors: foreground #716f6d on background #25221e.
- Contrast: 3.16:1 measured; 4.5:1 required.
- Suggested foreground: #8A8987, which measures 4.53:1 on the current background.
### Elements must meet minimum color contrast ratio thresholds
- Source: axe rule color-contrast.
- Selector: .border-t > p.
- Current colors: foreground #716f6d on background #25221e.
- Contrast: 3.16:1 measured; 4.5:1 required.
- Suggested foreground: #8A8987, which measures 4.53:1 on the current background.
### Alternative text of images should not be repeated as text
- Rule: image-redundant-alt.
- Selector: .size-6.dark\:brightness-0.dark\:invert.
- Failure: Fix all of the following: Element contains <img> element with alt text that duplicates existing text.
## 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 tern.so at https://tern.so.
- Scanner check ID: design_hero_clarity.
- Fix title: Clarify the hero promise.
- Scanner check: Hero clarity signals.
- Category: Design.
- Status: fail.
- Severity: high.
- Priority: 6; lower numbers are more urgent.
- Score impact: 13 of 13 rule points lost.
- Evidence: Detected 1 H1 heading(s) and 29 meta-description characters.
- What needs attention: The hero area does not provide enough clear product context.
- Why it matters: Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
- 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: hero heading, subcopy, above-the-fold layout, product/offer proof, and first-screen viewport behavior; 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: Use one clear H1 plus supporting copy that names the audience, problem, and outcome.
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:
- Clarify what the product/page is, who it is for, and what outcome it creates.
- Avoid vague slogans that require scrolling to understand the offer.
- 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 first viewport communicates the concrete offer and audience.
- Hero copy aligns with title, meta description, schema, and CTA.
- 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 tern.so at https://tern.so.
- 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 tern.so at https://tern.so.
- 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: 13.
- 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.
## Affected Elements
### Tern
- Selector: div.pointer-events-none.sticky > div.mx-auto.w-full > header.pointer-events-auto.flex > a.inline-flex.shrink-0.
- Tap target size: 64x24px.
### Why Tern
- Selector: div.mx-auto.w-full > header.pointer-events-auto.flex > nav.flex.min-w-0 > a.items-center.justify-center:nth-of-type(1).
- Tap target size: 77x32px.
### Pricing
- Selector: div.mx-auto.w-full > header.pointer-events-auto.flex > nav.flex.min-w-0 > a.inline-flex.items-center:nth-of-type(2).
- Tap target size: 63x32px.
### Notify me
- Selector: div.mx-auto.w-full > header.pointer-events-auto.flex > nav.flex.min-w-0 > a.inline-flex.items-center:nth-of-type(3).
- Tap target size: 78x32px.
### Theme
- Selector: button#radix-_R_14lfdb_.
- Tap target size: 32x32px.
### Why Tern
- Selector: div:nth-of-type(2) > ul.mt-4.space-y-3 > li:nth-of-type(1) > a.text-white\/70.transition-colors.
- Tap target size: 69x22px.
### Accounts
- Selector: div:nth-of-type(2) > ul.mt-4.space-y-3 > li:nth-of-type(2) > a.text-white\/70.transition-colors.
- Tap target size: 71x22px.
### Privacy
- Selector: div:nth-of-type(2) > ul.mt-4.space-y-3 > li:nth-of-type(3) > a.text-white\/70.transition-colors.
- Tap target size: 53x22px.
## 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.