completed

HTTP 200

0 redirects

38 checks

Website audit scorecard for datesweep.com

The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.

Submitted

https://datesweep.com

Final URL

https://datesweep.com

Created

Aug 4, 2026, 3:50 PM

Safe fetch

70 ms

Four-score result

Close to ready (Strong): 33 passed, 5 failed, and 0 unknown. Strongest area: Accessibility. Weakest area: Security.

Overall

out of 100

SEO / AEO

out of 100

99/111 rule points

Security

out of 100

60/76 rule points

Accessibility

out of 100

86/94 rule points

Design

out of 100

94/110 rule points

Why this scored this way

Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.

Category point breakdown

SEO / AEO99/111

Security60/76

Accessibility86/94

Design94/110

Biggest score-losing checks

critical

Security

Sensitive file probes

A small allowlist probe returned a public success response.

high

SEO / AEO

sitemap.xml validity

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

medium

Design

Rendered layout ergonomics

Horizontal overflow: 0px. Small tap targets: 17.

medium

Accessibility

Basic contrast

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Recommendations

Score-losing issues ordered by remediation priority, severity, and score impact.

5 fixes

4 opportunities

9 insights

fail

critical

Security

Priority 1

Remove exposed sensitive files

-16 rule pts

What failed

A small public allowlist probe found a sensitive-looking file path.

Evidence

A small allowlist probe returned a public success response.

Priority

Priority 1: fix before sharing the page publicly.

Why it matters

Publicly exposed config or backup files can leak implementation details or secrets.

How to fix it

Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- 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 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.

fail

high

SEO / AEO

Priority 7

Publish a valid sitemap.xml

-12 rule pts

What failed

The sitemap file was not reachable or did not look like valid sitemap XML.

Evidence

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

Priority

Priority 7: fix during launch polish.

Why it matters

A sitemap helps search engines discover the landing page and related public pages sooner.

How to fix it

Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: 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: static sitemap file, dynamic sitemap route, sitemap index, 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 or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it 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 either a static sitemap.xml or dynamic /sitemap.xml route with valid urlset or sitemapindex XML.
- 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:
- /sitemap.xml 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.

fail

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

The browser-rendered page has layout or tap-target issues.

Evidence

Horizontal overflow: 0px. Small tap targets: 17.

Priority

Priority 13: fix during launch polish.

Why it matters

Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

How to fix it

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.

Copyable agent prompt

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

fail

medium

Accessibility

Priority 20

Improve detectable color contrast

-8 rule pts

What failed

The scanner found text/background color pairs that may be hard to read, or could not verify contrast.

Evidence

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Priority

Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters

Low contrast makes a launch page feel less polished and can exclude users with low vision.

How to fix it

Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

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

fail

low

Design

Priority 25

Make spacing more consistent

-7 rule pts

What failed

The page exposes few consistent spacing signals in class or inline styles.

Evidence

Detected 3 spacing class/style signal(s).

Priority

Priority 25: lower-risk cleanup after urgent launch blockers.

Why it matters

Consistent spacing helps the page feel deliberate and easier to scan.

How to fix it

Use consistent section padding, gaps, and margins across repeated content blocks.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 rule points lost.
- Evidence: Detected 3 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- 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: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; 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 consistent section padding, gaps, and margins across repeated content blocks.
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:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- 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:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- 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.

Score aggregation details

Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.

89/100

12 pass, 1 fail, 0 unknown

SEO / AEO

Severity mix: 1 critical, 7 high, 3 medium, 1 low.

high

sitemap.xml validity

-12 rule pts

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

79/100

5 pass, 1 fail, 0 unknown

Security

Severity mix: 2 critical, 3 high, 0 medium, 0 low.

critical

Sensitive file probes

-16 rule pts

A small allowlist probe returned a public success response.

91/100

7 pass, 1 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 3 high, 5 medium, 0 low.

medium

Basic contrast

-8 rule pts

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

85/100

9 pass, 2 fail, 0 unknown

Design

Severity mix: 0 critical, 3 high, 6 medium, 2 low.

medium

Rendered layout ergonomics

-9 rule pts

Horizontal overflow: 0px. Small tap targets: 17.

low

Spacing consistency

-7 rule pts

Detected 3 spacing class/style signal(s).

Full check list

Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.

Showing failed checks.

Failed checks

These checks need attention.

fail

high

SEO / AEO

sitemap.xml validity

0/12

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml 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.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: static sitemap file, dynamic sitemap route, sitemap index, 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 or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it 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 either a static sitemap.xml or dynamic /sitemap.xml route with valid urlset or sitemapindex XML.
- 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:
- /sitemap.xml 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.

fail

critical

Security

Sensitive file probes

0/16

A small allowlist probe returned a public success response.

Failed: earned 0 of 16 points.

Priority: Priority 1: fix before sharing the page publicly.

Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.

Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- 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.

fail

medium

Accessibility

Basic contrast

0/8

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

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

fail

low

Design

Spacing consistency

0/7

Detected 3 spacing class/style signal(s).

Failed: earned 0 of 7 points.

Priority: Priority 25: lower-risk cleanup after urgent launch blockers.

Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.

Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 3 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- 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: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; 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 consistent section padding, gaps, and margins across repeated content blocks.
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:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- 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:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- 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.

fail

medium

Design

Rendered layout ergonomics

0/9

Horizontal overflow: 0px. Small tap targets: 17.

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

Fix: 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.

Copyable agent prompt

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

Page-level AEO readiness

Shared eligibility and content signals that affect every search and answer agent.

90/100 ready

Index and citation eligibility

No general noindex directive was detected.

Snippet and answer controls

No general nosnippet or max-snippet:0 control was detected.

Canonical alignment

The canonical resolves to the scanned public URL.

Sitemap coverage and freshness

The exact scanned URL was not found in the fetched sitemap.xml.

Structured data

Detected 1 JSON-LD block(s), 0 parse error(s), and types Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

Detected 3 of 3 core identity signals across the title, description, and H1.

Answer-ready visible text

Detected 1161 visible words and 17 audience, use-case, pricing, or integration signals.

Authorship and accountability

Detected author or accountable entity: jan.stevens@digtiz.com.

Published or updated date

Structured data reports dateModified 2026-07-21T12:48:45+02:00.

Supporting-source links

Detected 13 external source or reference link(s); link quality still requires editorial review.

Rendered content availability

Rendered audit completed with 253 visible text element(s).

Synthetic search-agent reachability

8 of 8 search/discovery User-Agent probes returned reachable content.

Optional LLM-readable summary

https://datesweep.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

OpenAIChatGPT search

OAI-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

OpenAIChatGPT user fetches

ChatGPT-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity user fetches

Perplexity-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.

Public report link

Markdown export

Share the website audit report

Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.

Share preview

datesweep.com website audit report

Close to ready: 86/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# datesweep.com Website Scan

Scanned URL: [https://datesweep.com](https://datesweep.com)
Report URL: /scan/datesweep-com-86-launch-readiness-report-79d639b5
Created: 2026-08-04T15:50:43.094Z

## Score Summary

- Overall: 86/100
- SEO / AEO: 89/100
- Security: 79/100
- Accessibility: 91/100
- Design: 85/100

## Launch Readiness

Close to ready (Strong).

Passed: 33. Failed: 5. Unknown: 0.
Strongest area: Accessibility. Weakest area: Security.

## AI Crawler Access

These results combine robots.txt policy, page controls, and bounded synthetic User-Agent probes. Synthetic probes do not prove that traffic came from the vendor; training and data-use choices are neutral publisher preferences.

- **OpenAI — ChatGPT search** (OAI-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks GPTBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **OpenAI — ChatGPT user fetches** (ChatGPT-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. ChatGPT-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks ClaudeBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Google-Extended from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Perplexity — Perplexity user fetches** (Perplexity-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. Perplexity-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Applebot-Extended from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks meta-externalagent from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Amazonbot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Amzn-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks CCBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.

## Page-level AEO Readiness

Readiness: 90/100

- **Index and citation eligibility**: PASS — No general noindex directive was detected.
- **Snippet and answer controls**: PASS — No general nosnippet or max-snippet:0 control was detected.
- **Canonical alignment**: PASS — The canonical resolves to the scanned public URL.
- **Sitemap coverage and freshness**: FAIL — The exact scanned URL was not found in the fetched sitemap.xml.
- **Structured data**: PASS — Detected 1 JSON-LD block(s), 0 parse error(s), and types Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: PASS — Detected 3 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: PASS — Detected 1161 visible words and 17 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: PASS — Detected author or accountable entity: jan.stevens@digtiz.com.
- **Published or updated date**: PASS — Structured data reports dateModified 2026-07-21T12:48:45+02:00.
- **Supporting-source links**: PASS — Detected 13 external source or reference link(s); link quality still requires editorial review.
- **Rendered content availability**: PASS — Rendered audit completed with 253 visible text element(s).
- **Synthetic search-agent reachability**: PASS — 8 of 8 search/discovery User-Agent probes returned reachable content.
- **Optional LLM-readable summary**: INFO — https://datesweep.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. Remove exposed sensitive files

- Category: Security
- Status: fail
- Severity: critical
- Rule points lost: 16
- Evidence: A small allowlist probe returned a public success response.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

### 2. Publish a valid sitemap.xml

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

### 3. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 17.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Fix: 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.

### 4. Improve detectable color contrast

- Category: Accessibility
- Status: fail
- Severity: medium
- Rule points lost: 8
- Evidence: 43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

### 5. Make spacing more consistent

- Category: Design
- Status: fail
- Severity: low
- Rule points lost: 7
- Evidence: Detected 3 spacing class/style signal(s).
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

## Opportunities

### Add answer-ready sections for common buyer questions

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 4. Use-case signals: 2. Integration/API signals: 0.
- Why it matters: Answer engines and search visitors need concise textual answers to summarize who the product is for, how it works, what it costs, and what it connects with.
- Next step: Add short, crawlable sections for pricing or plans, ideal users, use cases, integrations, security, and how the product differs from alternatives.

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 43 of 100 rendered contrast sample(s) missed target. Worst ratio: 1.
- Why it matters: Computed contrast catches the actual colors visitors see after CSS, themes, and overlays are applied.
- Next step: Audit foreground/background token pairs for body text, muted text, links, buttons, inputs, and badges, then raise weak pairs to WCAG AA contrast targets.

### Polish rendered responsive ergonomics

- Impact: medium
- Category: Design
- Evidence: Horizontal overflow: 0px. Small tap targets: 17.
- Why it matters: Overflow and tiny controls are easy for static scans to miss but obvious to real users, especially on mobile and tablet layouts.
- Next step: Constrain wide elements, avoid fixed-width content that exceeds the viewport, and increase touch target sizes for interactive controls.

### Measure search performance with first-party data

- Impact: medium
- Category: SEO / AEO
- Evidence: robots.txt and sitemap.xml were reachable, so the site has the basics needed for Search Console verification and monitoring.
- Why it matters: A scan can identify technical readiness, but Search Console and analytics reveal impressions, queries, clicks, pages, and conversions over time.
- Next step: Verify the domain in Search Console, submit the sitemap, and pair query/page data with analytics events for signups, demo requests, and purchases.

## Insights

### The page appears basically crawlable

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: HTTP 200. sitemap.xml: HTTP 301. noindex check: clear.
- Interpretation: The public page satisfies the basic crawl/index path the scan can verify.
- Recommended use: Use this as the first launch gate before deeper content, ranking, or AI visibility work.

### AEO depends on normal SEO plus answerable text

- Category: SEO / AEO
- Evidence: Visible words: 1161. H1 count: 1. Audience signals: 11. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

- Category: SEO / AEO
- Evidence: Title: Bulk-Update WordPress Dates in One Clean Sweep – DateSweep. H1: Give your site a  fresh set of dates  — in one clean sweep.. Schema types: Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### Structured data is present

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 1. Types: Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite. Parse errors: 0.
- Interpretation: The page exposes machine-readable facts, but quality still depends on whether those facts match visible content.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Security
- Evidence: SEO / AEO: 89/100. Security: 79/100. Accessibility: 91/100. Design: 85/100
- Interpretation: The weakest area is Security, so improvements there should have the most visible effect on readiness.
- Recommended use: Use the score mix to choose the next workstream instead of treating every issue as equally urgent.

### LLM-readable file found

- Category: SEO / AEO
- Evidence: https://datesweep.com/llms.txt returned HTTP 200.
- Interpretation: llms.txt can be a useful optional summary for agents, but it should not be treated as a guaranteed AI search ranking factor.
- Recommended use: Invest first in crawlability, helpful visible content, internal links, and accurate schema; add llms.txt as a tidy supplement.

### Rendered page experience snapshot

- Category: Design
- Evidence: Rendered text samples: 100. Contrast failures: 43. Console errors: 0. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 442ms. Load complete: 442ms. First contentful paint: 424ms. Resources: 15. Scripts: 3. Images: 0. Third-party origins: 0. Transfer: not available.
- Interpretation: These are lightweight browser timings from one rendered scan, so they are useful directional signals rather than real-user performance proof.
- Recommended use: Use slow timings, high script counts, heavy transfer size, and many third-party origins to choose focused speed work, then verify important changes with analytics or field data when available.

### Rendered axe accessibility snapshot

- Category: Accessibility
- Evidence: axe violations: 0. Critical: 0. Serious: 0. Top rules: none.
- Interpretation: axe-core catches common accessibility failures in the actual rendered DOM, but it is still automated coverage and not a full manual accessibility audit.
- Recommended use: Treat critical and serious axe failures as high-priority fixes, then manually review keyboard flow, focus states, screen reader meaning, and interaction states.

## Scope

FreeScan.app performs safe public checks only. It is not a penetration test, full SEO engagement, full accessibility audit, WCAG certification, backlink audit, rank tracker, or analytics platform.

Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.

Rescan same URL

Rerun the full deterministic scanner for datesweep.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Start free audit

New scan Visit scanned site

completed

HTTP 200

0 redirects

38 checks

Website audit scorecard for datesweep.com

The scanner fetched the public page, extracted deterministic facts, and stored scored results across SEO / AEO, security, accessibility, and design.

Submitted

https://datesweep.com

Final URL

https://datesweep.com

Created

Aug 4, 2026, 3:50 PM

Safe fetch

70 ms

Four-score result

Close to ready (Strong): 33 passed, 5 failed, and 0 unknown. Strongest area: Accessibility. Weakest area: Security.

Overall

out of 100

SEO / AEO

out of 100

99/111 rule points

Security

out of 100

60/76 rule points

Accessibility

out of 100

86/94 rule points

Design

out of 100

94/110 rule points

Why this scored this way

Scores are deterministic: each category earns rule points for verified public signals and loses points for failed checks. Unknown checks are shown separately instead of guessed.

Category point breakdown

SEO / AEO99/111

Security60/76

Accessibility86/94

Design94/110

Biggest score-losing checks

critical

Security

Sensitive file probes

A small allowlist probe returned a public success response.

high

SEO / AEO

sitemap.xml validity

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

medium

Design

Rendered layout ergonomics

Horizontal overflow: 0px. Small tap targets: 17.

medium

Accessibility

Basic contrast

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Recommendations

Score-losing issues ordered by remediation priority, severity, and score impact.

5 fixes

4 opportunities

9 insights

fail

critical

Security

Priority 1

Remove exposed sensitive files

-16 rule pts

What failed

A small public allowlist probe found a sensitive-looking file path.

Evidence

A small allowlist probe returned a public success response.

Priority

Priority 1: fix before sharing the page publicly.

Why it matters

Publicly exposed config or backup files can leak implementation details or secrets.

How to fix it

Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- 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 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.

fail

high

SEO / AEO

Priority 7

Publish a valid sitemap.xml

-12 rule pts

What failed

The sitemap file was not reachable or did not look like valid sitemap XML.

Evidence

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

Priority

Priority 7: fix during launch polish.

Why it matters

A sitemap helps search engines discover the landing page and related public pages sooner.

How to fix it

Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml validity.
- Category: SEO / AEO.
- Status: fail.
- Severity: high.
- Priority: 7; lower numbers are more urgent.
- Score impact: 12 rule points lost.
- Evidence: 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: static sitemap file, dynamic sitemap route, sitemap index, 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 or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it 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 either a static sitemap.xml or dynamic /sitemap.xml route with valid urlset or sitemapindex XML.
- 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:
- /sitemap.xml 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.

fail

medium

Design

Priority 13

Fix rendered layout ergonomics

-9 rule pts

What failed

The browser-rendered page has layout or tap-target issues.

Evidence

Horizontal overflow: 0px. Small tap targets: 17.

Priority

Priority 13: fix during launch polish.

Why it matters

Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

How to fix it

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.

Copyable agent prompt

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

fail

medium

Accessibility

Priority 20

Improve detectable color contrast

-8 rule pts

What failed

The scanner found text/background color pairs that may be hard to read, or could not verify contrast.

Evidence

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Priority

Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters

Low contrast makes a launch page feel less polished and can exclude users with low vision.

How to fix it

Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

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

fail

low

Design

Priority 25

Make spacing more consistent

-7 rule pts

What failed

The page exposes few consistent spacing signals in class or inline styles.

Evidence

Detected 3 spacing class/style signal(s).

Priority

Priority 25: lower-risk cleanup after urgent launch blockers.

Why it matters

Consistent spacing helps the page feel deliberate and easier to scan.

How to fix it

Use consistent section padding, gaps, and margins across repeated content blocks.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 rule points lost.
- Evidence: Detected 3 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- 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: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; 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 consistent section padding, gaps, and margins across repeated content blocks.
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:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- 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:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- 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.

Score aggregation details

Category scores come from earned rule points divided by available rule points. Failed checks are ordered by severity and score lost.

89/100

12 pass, 1 fail, 0 unknown

SEO / AEO

Severity mix: 1 critical, 7 high, 3 medium, 1 low.

high

sitemap.xml validity

-12 rule pts

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

79/100

5 pass, 1 fail, 0 unknown

Security

Severity mix: 2 critical, 3 high, 0 medium, 0 low.

critical

Sensitive file probes

-16 rule pts

A small allowlist probe returned a public success response.

91/100

7 pass, 1 fail, 0 unknown

Accessibility

Severity mix: 0 critical, 3 high, 5 medium, 0 low.

medium

Basic contrast

-8 rule pts

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

85/100

9 pass, 2 fail, 0 unknown

Design

Severity mix: 0 critical, 3 high, 6 medium, 2 low.

medium

Rendered layout ergonomics

-9 rule pts

Horizontal overflow: 0px. Small tap targets: 17.

low

Spacing consistency

-7 rule pts

Detected 3 spacing class/style signal(s).

Full check list

Failed, unknown, and passed checks are all shown so the report is transparent even when public data is partial.

Showing failed checks.

Failed checks

These checks need attention.

fail

high

SEO / AEO

sitemap.xml validity

0/12

sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.

Failed: earned 0 of 12 points.

Priority: Priority 7: fix during launch polish.

Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.

Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: seo_sitemap_xml.
- Fix title: Publish a valid sitemap.xml.
- Scanner check: sitemap.xml 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.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: static sitemap file, dynamic sitemap route, sitemap index, 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 or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it 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 either a static sitemap.xml or dynamic /sitemap.xml route with valid urlset or sitemapindex XML.
- 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:
- /sitemap.xml 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.

fail

critical

Security

Sensitive file probes

0/16

A small allowlist probe returned a public success response.

Failed: earned 0 of 16 points.

Priority: Priority 1: fix before sharing the page publicly.

Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.

Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- 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.

fail

medium

Accessibility

Basic contrast

0/8

43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.

Failed: earned 0 of 8 points.

Priority: Priority 20: lower-risk cleanup after urgent launch blockers.

Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.

Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

Copyable agent prompt

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

fail

low

Design

Spacing consistency

0/7

Detected 3 spacing class/style signal(s).

Failed: earned 0 of 7 points.

Priority: Priority 25: lower-risk cleanup after urgent launch blockers.

Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.

Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

Copyable agent prompt

## 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 datesweep.com at https://datesweep.com.
- Scanner check ID: design_spacing_consistency.
- Fix title: Make spacing more consistent.
- Scanner check: Spacing consistency.
- Category: Design.
- Status: fail.
- Severity: low.
- Priority: 25; lower numbers are more urgent.
- Score impact: 7 of 7 rule points lost.
- Evidence: Detected 3 spacing class/style signal(s).
- What needs attention: The page exposes few consistent spacing signals in class or inline styles.
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- 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: layout spacing tokens, component padding, section gaps, card grids, mobile breakpoints, and repeated patterns; 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 consistent section padding, gaps, and margins across repeated content blocks.
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:
- Normalize spacing using existing tokens or local conventions.
- Avoid one-off spacing hacks that create new breakpoints or layout shifts.
- 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:
- Spacing feels consistent across related sections and viewport sizes.
- No important UI shifts or overlaps after the change.
- 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.

fail

medium

Design

Rendered layout ergonomics

0/9

Horizontal overflow: 0px. Small tap targets: 17.

Failed: earned 0 of 9 points.

Priority: Priority 13: fix during launch polish.

Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.

Fix: 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.

Copyable agent prompt

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

Page-level AEO readiness

Shared eligibility and content signals that affect every search and answer agent.

90/100 ready

Index and citation eligibility

No general noindex directive was detected.

Snippet and answer controls

No general nosnippet or max-snippet:0 control was detected.

Canonical alignment

The canonical resolves to the scanned public URL.

Sitemap coverage and freshness

The exact scanned URL was not found in the fetched sitemap.xml.

Structured data

Detected 1 JSON-LD block(s), 0 parse error(s), and types Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.

Public or paywalled content

No isAccessibleForFree structured-data value was detected.

Entity clarity

Detected 3 of 3 core identity signals across the title, description, and H1.

Answer-ready visible text

Detected 1161 visible words and 17 audience, use-case, pricing, or integration signals.

Authorship and accountability

Detected author or accountable entity: jan.stevens@digtiz.com.

Published or updated date

Structured data reports dateModified 2026-07-21T12:48:45+02:00.

Supporting-source links

Detected 13 external source or reference link(s); link quality still requires editorial review.

Rendered content availability

Rendered audit completed with 253 visible text element(s).

Synthetic search-agent reachability

8 of 8 search/discovery User-Agent probes returned reachable content.

Optional LLM-readable summary

https://datesweep.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

OpenAIChatGPT search

OAI-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

OpenAIOpenAI model training

GPTBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

OpenAIChatGPT user fetches

ChatGPT-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude model training

ClaudeBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude search

Claude-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AnthropicClaude user fetches

Claude-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

GoogleGoogle Search and AI features

Googlebot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

GoogleGemini data use and grounding

Google-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MicrosoftBing and Copilot

Bingbot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity search

PerplexityBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

PerplexityPerplexity user fetches

Perplexity-User

UNKNOWN

User-requested fetch

Robots: not applicable to user-requested fetches

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AppleSiri, Spotlight, and Safari search

Applebot

PASS · ALLOWED

Search and discovery

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AppleApple foundation-model training

Applebot-Extended

POLICY ALLOWED

Data-use policy control

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral search

MistralAI-Index

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Mistral AIMistral user fetches

MistralAI-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI model and product data

meta-externalagent

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

MetaMeta AI user fetches

meta-externalfetcher

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAmazon model training

Amazonbot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa and Rufus search

Amzn-SearchBot

PASS · ALLOWED

AI search

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

AmazonAlexa user fetches

Amzn-User

PASS · ALLOWED

User-requested fetch

Robots: allowed

Probe: reachable · HTTP 200 · 100% parity

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Common CrawlOpen web datasets

CCBot

POLICY ALLOWED

Model training

Robots: allowed

Probe: not tested for this control

IndexSnippetsSitemapPublic content

Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large

Vendor documentationDefinition checked 2026-07-30

Public report link

Markdown export

Share the website audit report

Copy a public report link or a Markdown version with scores, fixes, opportunities, insights, and a normal link back to the scanned site.

Share preview

datesweep.com website audit report

Close to ready: 86/100 overall, with prioritized fixes for SEO, security, accessibility, and design.

Public report link

Markdown report

# datesweep.com Website Scan

Scanned URL: [https://datesweep.com](https://datesweep.com)
Report URL: /scan/datesweep-com-86-launch-readiness-report-79d639b5
Created: 2026-08-04T15:50:43.094Z

## Score Summary

- Overall: 86/100
- SEO / AEO: 89/100
- Security: 79/100
- Accessibility: 91/100
- Design: 85/100

## Launch Readiness

Close to ready (Strong).

Passed: 33. Failed: 5. Unknown: 0.
Strongest area: Accessibility. Weakest area: Security.

## AI Crawler Access

These results combine robots.txt policy, page controls, and bounded synthetic User-Agent probes. Synthetic probes do not prove that traffic came from the vendor; training and data-use choices are neutral publisher preferences.

- **OpenAI — ChatGPT search** (OAI-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **OpenAI — OpenAI model training** (GPTBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks GPTBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **OpenAI — ChatGPT user fetches** (ChatGPT-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. ChatGPT-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude model training** (ClaudeBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks ClaudeBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude search** (Claude-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Anthropic — Claude user fetches** (Claude-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Google — Google Search and AI features** (Googlebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Googlebot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Google — Gemini data use and grounding** (Google-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Google-Extended from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Microsoft — Bing and Copilot** (Bingbot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Bingbot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Perplexity — Perplexity search** (PerplexityBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Perplexity — Perplexity user fetches** (Perplexity-User): UNKNOWN — robots not_applicable; synthetic probe not_tested. Perplexity-User is used for user-requested retrieval, so robots.txt is not treated as a reliable access control for this row. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Apple — Siri, Spotlight, and Safari search** (Applebot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Apple — Apple foundation-model training** (Applebot-Extended): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Applebot-Extended from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Mistral AI — Mistral search** (MistralAI-Index): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks MistralAI-Index from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Mistral AI — Mistral user fetches** (MistralAI-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Meta — Meta AI model and product data** (meta-externalagent): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks meta-externalagent from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Meta — Meta AI user fetches** (meta-externalfetcher): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Amazon model training** (Amazonbot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks Amazonbot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Alexa and Rufus search** (Amzn-SearchBot): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Amzn-SearchBot from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Amazon — Alexa user fetches** (Amzn-User): PASS — robots allowed; synthetic probe reachable (HTTP 200). No matching robots.txt rule blocks Amzn-User from /. Synthetic User-Agent probe returned HTTP 200 with 100% sampled-content parity. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.
- **Common Crawl — Open web datasets** (CCBot): PREFERENCE — robots allowed; synthetic probe not_tested. No matching robots.txt rule blocks CCBot from /. No synthetic fetch is appropriate for this policy or training control. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large.

## Page-level AEO Readiness

Readiness: 90/100

- **Index and citation eligibility**: PASS — No general noindex directive was detected.
- **Snippet and answer controls**: PASS — No general nosnippet or max-snippet:0 control was detected.
- **Canonical alignment**: PASS — The canonical resolves to the scanned public URL.
- **Sitemap coverage and freshness**: FAIL — The exact scanned URL was not found in the fetched sitemap.xml.
- **Structured data**: PASS — Detected 1 JSON-LD block(s), 0 parse error(s), and types Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.
- **Public or paywalled content**: UNKNOWN — No isAccessibleForFree structured-data value was detected.
- **Entity clarity**: PASS — Detected 3 of 3 core identity signals across the title, description, and H1.
- **Answer-ready visible text**: PASS — Detected 1161 visible words and 17 audience, use-case, pricing, or integration signals.
- **Authorship and accountability**: PASS — Detected author or accountable entity: jan.stevens@digtiz.com.
- **Published or updated date**: PASS — Structured data reports dateModified 2026-07-21T12:48:45+02:00.
- **Supporting-source links**: PASS — Detected 13 external source or reference link(s); link quality still requires editorial review.
- **Rendered content availability**: PASS — Rendered audit completed with 253 visible text element(s).
- **Synthetic search-agent reachability**: PASS — 8 of 8 search/discovery User-Agent probes returned reachable content.
- **Optional LLM-readable summary**: INFO — https://datesweep.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.

## Prioritized Fixes

### 1. Remove exposed sensitive files

- Category: Security
- Status: fail
- Severity: critical
- Rule points lost: 16
- Evidence: A small allowlist probe returned a public success response.
- Why it matters: Publicly exposed config or backup files can leak implementation details or secrets.
- Fix: Remove the exposed file, block public access to that path, and rotate any secrets that may have been exposed.

### 2. Publish a valid sitemap.xml

- Category: SEO / AEO
- Status: fail
- Severity: high
- Rule points lost: 12
- Evidence: sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
- Why it matters: A sitemap helps search engines discover the landing page and related public pages sooner.
- Fix: Add a static sitemap file or dynamic /sitemap.xml route with valid urlset or sitemapindex XML, include your public canonical URLs, and confirm it returns HTTP 200.

### 3. Fix rendered layout ergonomics

- Category: Design
- Status: fail
- Severity: medium
- Rule points lost: 9
- Evidence: Horizontal overflow: 0px. Small tap targets: 17.
- Why it matters: Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
- Fix: 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.

### 4. Improve detectable color contrast

- Category: Accessibility
- Status: fail
- Severity: medium
- Rule points lost: 8
- Evidence: 43 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
- Why it matters: Low contrast makes a launch page feel less polished and can exclude users with low vision.
- Fix: Review key text, buttons, and links against a 4.5:1 contrast target for normal text.

### 5. Make spacing more consistent

- Category: Design
- Status: fail
- Severity: low
- Rule points lost: 7
- Evidence: Detected 3 spacing class/style signal(s).
- Why it matters: Consistent spacing helps the page feel deliberate and easier to scan.
- Fix: Use consistent section padding, gaps, and margins across repeated content blocks.

## Opportunities

### Add answer-ready sections for common buyer questions

- Impact: high
- Category: SEO / AEO
- Evidence: Pricing signals: 4. Use-case signals: 2. Integration/API signals: 0.
- Why it matters: Answer engines and search visitors need concise textual answers to summarize who the product is for, how it works, what it costs, and what it connects with.
- Next step: Add short, crawlable sections for pricing or plans, ideal users, use cases, integrations, security, and how the product differs from alternatives.

### Tighten the live color system

- Impact: high
- Category: Accessibility
- Evidence: 43 of 100 rendered contrast sample(s) missed target. Worst ratio: 1.
- Why it matters: Computed contrast catches the actual colors visitors see after CSS, themes, and overlays are applied.
- Next step: Audit foreground/background token pairs for body text, muted text, links, buttons, inputs, and badges, then raise weak pairs to WCAG AA contrast targets.

### Polish rendered responsive ergonomics

- Impact: medium
- Category: Design
- Evidence: Horizontal overflow: 0px. Small tap targets: 17.
- Why it matters: Overflow and tiny controls are easy for static scans to miss but obvious to real users, especially on mobile and tablet layouts.
- Next step: Constrain wide elements, avoid fixed-width content that exceeds the viewport, and increase touch target sizes for interactive controls.

### Measure search performance with first-party data

- Impact: medium
- Category: SEO / AEO
- Evidence: robots.txt and sitemap.xml were reachable, so the site has the basics needed for Search Console verification and monitoring.
- Why it matters: A scan can identify technical readiness, but Search Console and analytics reveal impressions, queries, clicks, pages, and conversions over time.
- Next step: Verify the domain in Search Console, submit the sitemap, and pair query/page data with analytics events for signups, demo requests, and purchases.

## Insights

### The page appears basically crawlable

- Category: SEO / AEO
- Evidence: HTTP 200. robots.txt: HTTP 200. sitemap.xml: HTTP 301. noindex check: clear.
- Interpretation: The public page satisfies the basic crawl/index path the scan can verify.
- Recommended use: Use this as the first launch gate before deeper content, ranking, or AI visibility work.

### AEO depends on normal SEO plus answerable text

- Category: SEO / AEO
- Evidence: Visible words: 1161. H1 count: 1. Audience signals: 11. CTA labels: none detected.
- Interpretation: Google AI features currently rely on standard Search eligibility; the extra advantage comes from content that is easy to quote, summarize, and verify.
- Recommended use: Prioritize clear text answers, crawlable support pages, accurate schema, and visible proof over speculative AI-only markup.

### Detected entity signals

- Category: SEO / AEO
- Evidence: Title: Bulk-Update WordPress Dates in One Clean Sweep – DateSweep. H1: Give your site a  fresh set of dates  — in one clean sweep.. Schema types: Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite.
- Interpretation: The stronger and more consistent these entity signals are, the easier it is for search and answer systems to identify the brand, product category, and page purpose.
- Recommended use: Keep the title, H1, meta description, Open Graph, schema, footer, and about/pricing/docs pages aligned around the same product facts.

### Structured data is present

- Category: SEO / AEO
- Evidence: JSON-LD blocks: 1. Types: Article, ImageObject, Organization, Person, SearchAction, WebPage, WebSite. Parse errors: 0.
- Interpretation: The page exposes machine-readable facts, but quality still depends on whether those facts match visible content.
- Recommended use: Validate JSON-LD and use only accurate facts that are visible or clearly supported on the public page.

### Weakest score area

- Category: Security
- Evidence: SEO / AEO: 89/100. Security: 79/100. Accessibility: 91/100. Design: 85/100
- Interpretation: The weakest area is Security, so improvements there should have the most visible effect on readiness.
- Recommended use: Use the score mix to choose the next workstream instead of treating every issue as equally urgent.

### LLM-readable file found

- Category: SEO / AEO
- Evidence: https://datesweep.com/llms.txt returned HTTP 200.
- Interpretation: llms.txt can be a useful optional summary for agents, but it should not be treated as a guaranteed AI search ranking factor.
- Recommended use: Invest first in crawlability, helpful visible content, internal links, and accurate schema; add llms.txt as a tidy supplement.

### Rendered page experience snapshot

- Category: Design
- Evidence: Rendered text samples: 100. Contrast failures: 43. Console errors: 0. Horizontal overflow: 0px.
- Interpretation: The scan inspected the browser-rendered page, so contrast, runtime, layout, and timing signals are more representative than static markup alone.
- Recommended use: Use rendered checks to prioritize issues that visitors actually experience after JavaScript and CSS load.

### Rendered speed snapshot

- Category: Design
- Evidence: DOMContentLoaded: 442ms. Load complete: 442ms. First contentful paint: 424ms. Resources: 15. Scripts: 3. Images: 0. Third-party origins: 0. Transfer: not available.
- Interpretation: These are lightweight browser timings from one rendered scan, so they are useful directional signals rather than real-user performance proof.
- Recommended use: Use slow timings, high script counts, heavy transfer size, and many third-party origins to choose focused speed work, then verify important changes with analytics or field data when available.

### Rendered axe accessibility snapshot

- Category: Accessibility
- Evidence: axe violations: 0. Critical: 0. Serious: 0. Top rules: none.
- Interpretation: axe-core catches common accessibility failures in the actual rendered DOM, but it is still automated coverage and not a full manual accessibility audit.
- Recommended use: Treat critical and serious axe failures as high-priority fixes, then manually review keyboard flow, focus states, screen reader meaning, and interaction states.

## Scope

FreeScan.app performs safe public checks only. It is not a penetration test, full SEO engagement, full accessibility audit, WCAG certification, backlink audit, rank tracker, or analytics platform.

Public reports expose the scanned public URL, safe scores, sanitized public evidence, and fix guidance. They do not include credentials, cookies, hidden form values, or sensitive response bodies.

Rescan same URL

Rerun the full deterministic scanner for datesweep.com without re-entering the URL. The previous report stays saved so the next result can be compared against it.

Website audit scorecard for datesweep.com

Remove exposed sensitive files

Copyable agent prompt

Publish a valid sitemap.xml

Copyable agent prompt

Fix rendered layout ergonomics

Copyable agent prompt

Improve detectable color contrast

Copyable agent prompt

Make spacing more consistent

Copyable agent prompt

SEO / AEO

sitemap.xml validity

Security

Sensitive file probes

Accessibility

Basic contrast

Design

Rendered layout ergonomics

Spacing consistency

Failed checks

sitemap.xml validity

Copyable agent prompt

Sensitive file probes

Copyable agent prompt

Basic contrast

Copyable agent prompt

Spacing consistency

Copyable agent prompt

Rendered layout ergonomics

Copyable agent prompt

AI crawler accessMajor AI search, user-fetch, and data-use agents checked for /, with robots evidence, synthetic reachability, and page-level AEO controls.12 pass0 fail2 unknown7 preferences

Unknown and not detected statesFreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.

Safe fetch metadataPublic headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.

Website audit scorecard for datesweep.com

Remove exposed sensitive files

Copyable agent prompt

Publish a valid sitemap.xml

Copyable agent prompt

Fix rendered layout ergonomics

Copyable agent prompt

Improve detectable color contrast

Copyable agent prompt

Make spacing more consistent

Copyable agent prompt

SEO / AEO

sitemap.xml validity

Security

Sensitive file probes

Accessibility

Basic contrast

Design

Rendered layout ergonomics

Spacing consistency

Failed checks

sitemap.xml validity

Copyable agent prompt

Sensitive file probes

Copyable agent prompt

Basic contrast

Copyable agent prompt

Spacing consistency

Copyable agent prompt

Rendered layout ergonomics

Copyable agent prompt

AI crawler accessMajor AI search, user-fetch, and data-use agents checked for /, with robots evidence, synthetic reachability, and page-level AEO controls.12 pass0 fail2 unknown7 preferences

Unknown and not detected statesFreeScan.app keeps partial public data explicit. It marks unverifiable signals as unknown or not detected instead of inventing evidence.

Safe fetch metadataPublic headers and redirects captured during intake. Response bodies, cookies, and credentials are not stored.