1. Crawl Summary

pass

Fetched 3 of 3 pages successfully

Target: https://arcpay-web-app.vercel.app

Evidence

{
  "pages": [
    {
      "url": "https://arcpay-web-app.vercel.app",
      "bytes": 33136,
      "status": 200,
      "fetchMs": 337
    },
    {
      "url": "https://arcpay-web-app.vercel.app/",
      "bytes": 33136,
      "status": 200,
      "fetchMs": 7
    },
    {
      "url": "https://arcpay-web-app.vercel.app/dashboard",
      "bytes": 9604,
      "status": 200,
      "fetchMs": 215
    }
  ],
  "origin": "https://arcpay-web-app.vercel.app",
  "target": "https://arcpay-web-app.vercel.app"
}

P5

2. Data Found

Data Point	Found?	Source	Notes
Pricing	No	—	—
Customer logos	No	—	—
Social proof	No	—	—
Recent launches	No	—	—
Blog post activity	No	—	—
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Pay anyone easily with stablecoins on ARC
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	No	—	—

3. Homepage Audit

warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
P3

warn

Open Graph: missing image

Evidence

{
  "title": "ArcPay — Easy Stablecoin Payments on ARC",
  "description": "Pay anyone easily with stablecoins on ARC."
}

P3

warn
Twitter Card: missing image
Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
Evidence
```
{
  "card": "summary_large_image",
  "title": "ArcPay — Easy Stablecoin Payments on ARC",
  "description": "Pay anyone easily with stablecoins on ARC."
}
```
P3
warn
Content volume: 218 words
Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
Evidence
```
{
  "wordCount": 218
}
```
P3
warn
Internal links: 2
Few internal links. Add a nav/footer with links to your key pages so AI crawlers can discover them.
Evidence
```
{
  "external": 4,
  "internal": 2
}
```
P3
pass
Homepage fetched successfully
HTTP 200 · 33136 bytes · 337ms
Evidence
```
{
  "bytes": 33136,
  "status": 200,
  "fetchMs": 337
}
```
P5
pass
Page load time: 0.34s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 337
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Single H1
Pay anyone easily with stablecoins on ARC
Evidence
```
{
  "h1": "Pay anyone easily with stablecoins on ARC"
}
```
P5

pass

`<title>` present (40 chars)

Evidence

{
  "title": "ArcPay — Easy Stablecoin Payments on ARC"
}

P5

pass

Meta description present (101 chars)

Evidence

{
  "description": "A minimalist non-custodial payments app for sending USDC and EURC on Arc Testnet with Circle App Kit."
}

P5

pass
Critical content is server-rendered
Raw and rendered text are within 15% of each other.
Evidence
```
{
  "ratio": 0.14623873304692106,
  "rawTextLen": 11871,
  "renderedTextLen": 1736
}
```
P5
pass
Heading structure: 10 (h1:1, h2:2, h3:7)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 2,
  "h3": 7
}
```
P5
pass
Favicon declared
Evidence
```
{
  "href": "/icon.svg"
}
```
P5

4. Content Quality

fail
Snippet-ready blocks: 0 (ul:0, ol:0, table:0)
Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
Evidence
```
{
  "ol": 0,
  "ul": 0,
  "tables": 0
}
```
P2
warn
No question-style headings found
Phrase at least one heading as a user question (e.g. 'How does pricing work?') to match conversational AI queries.
P3
warn
No date signal found
Add <time datetime="…"> or article:published_time meta. AI ranking weights freshness.
P3
warn
Text-to-HTML ratio: 5.1%
Low text density — most of the response is markup/script.
Evidence
```
{
  "ratio": 0.05092536591266481,
  "htmlBytes": 33068,
  "textChars": 1684
}
```
P3

pass

Heading levels are well-ordered

10 headings nested in order.

Evidence

{
  "levels": [
    1,
    2,
    3,
    3,
    3,
    3,
    2,
    3,
    3,
    3
  ]
}

P5

pass
Author byline declared
P5

5. Schema / Structured Data Audit

fail
No JSON-LD structured data found
Add JSON-LD blocks (Organization, SoftwareApplication, FAQPage, BreadcrumbList) so AI answer engines can ingest your data without guessing.
P1

6. Links & Images

pass
External nofollow: 0% (0/4)
Healthy mix of follow and nofollow outbound links.
P5
pass
No broken links in first 6
HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
Evidence
```
{
  "broken": 0,
  "sampled": 6,
  "examples": []
}
```
P5

7. Performance

warn
1 render-blocking script(s) in <head>
Move non-critical scripts to end of <body> or add `defer`/`async`.
P3
pass
Page size: 32 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 33136
}
```
P5

pass

Resource requests: 17 (scripts:16, css:1, img:0)

Reasonable request count.

Evidence

{
  "imgs": 0,
  "styles": 1,
  "scripts": 16,
  "inlineStyles": 0,
  "inlineScripts": 8
}

P5

pass
Inline JS+CSS bulk: 10 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 10146,
  "inlineCssBytes": 0
}
```
P5
pass
Response time: 337ms
Fast first response.
Evidence
```
{
  "bytes": 33136,
  "fetchMs": 337
}
```
P5
pass
Cache-Control set (CDN: Vercel)
Cache-Control: public, max-age=0, must-revalidate CDN detected: Vercel
Evidence
```
{
  "cdn": [
    "Vercel"
  ],
  "cacheControl": "public, max-age=0, must-revalidate"
}
```
P5

8. Security

warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
warn
X-Frame-Options missing
Add `X-Frame-Options: SAMEORIGIN` (or use CSP frame-ancestors) to prevent clickjacking.
P4
warn
X-Content-Type-Options missing
Add `X-Content-Type-Options: nosniff` to block MIME-type sniffing.
P4
warn
Referrer-Policy missing
Add `Referrer-Policy: strict-origin-when-cross-origin` for safer referrers.
P4
warn
Permissions-Policy missing
Restrict browser features (camera, mic, geolocation) you don't use.
P4

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://arcpay-web-app.vercel.app/"
}

P5

pass
No mixed content detected
P5
pass
HSTS set
max-age=63072000; includeSubDomains; preload
Evidence
```
{
  "value": "max-age=63072000; includeSubDomains; preload"
}
```
P5

9. robots.txt and sitemap.xml Audit

fail
sitemap.xml not found
Add /sitemap.xml — required for reliable AI/SERP discovery.
P1
warn
robots.txt not found
No /robots.txt was reachable. Add one explicitly — silence is read differently by different crawlers, and you lose the chance to control AI bots.
P2

10. LLM / AI Crawler Accessibility

warn
llms.txt missing
Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
P2
warn
skill.md missing
Add /skill.md describing what your site lets agents do — speeds up agent task routing.
P3
warn
/.well-known/security.txt missing
Publish a /.well-known/security.txt with at least a Contact: line. Crawlers and security researchers expect it; AI systems use it as a trust signal.
P3

11. Positioning Clarity

fail
No discoverable CTA
Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero.
P1
warn
No clear About/Team link
Add an About or Team link in the nav or footer so LLMs can identify the company.
P2
warn
No pricing/plans link found
AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
P2
warn
Value-prop language not detected
Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
P3
pass
H1 communicates value
Pay anyone easily with stablecoins on ARC
P5

12. Missing or Hard-to-Find Information

fail
10 data point(s) could not be found from public pages
· Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials · Contact/demo/signup paths
Evidence
```
{
  "missing": [
    "Pricing",
    "Customer logos",
    "Social proof",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Positioning",
    "Executive team",
    "Case studies or testimonials",
    "Contact/demo/signup paths"
  ]
}
```
P1

13. Recommended Fixes

warn
Add a discoverable CTA
Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
Evidence
```
{
  "for": "positioning.cta"
}
```
P1
warn
Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "for": "sitemap.exists"
}
```
P1
warn
Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "for": "schema.any"
}
```
P1
warn
Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
Evidence
```
{
  "for": "content.snippet_blocks"
}
```
P2
warn
Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "for": "llms_txt"
}
```
P2
warn
Make your About/Team page reachable
Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site.
Evidence
```
{
  "for": "positioning.who"
}
```
P2
warn
Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "for": "positioning.pricing"
}
```
P2
warn
Create a robots.txt
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
Evidence
```
{
  "for": "robots.exists"
}
```
P2
warn
Phrase a heading as a user question
Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.
Evidence
```
{
  "for": "content.qa_headings"
}
```
P3
warn
Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "for": "content.date_signal"
}
```
P3
warn
Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
Evidence
```
{
  "for": "content.text_ratio"
}
```
P3
warn
Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html <link rel="canonical" href="https://yoursite.com/" /> ```
Evidence
```
{
  "for": "homepage.canonical"
}
```
P3
warn
Complete Open Graph tags
AI bots use OG for fast disambiguation. Add all four: ```html <meta property="og:title" content="Your Page Title" /> <meta property="og:description" content="50–160 char description of this page." /> <meta property="og:image" content="https://yoursite.com/og-image.jpg" /> <meta property="og:url" content="https://yoursite.com/" /> <meta property="og:type" content="website" /> <meta property="og:site_name" content="YourSite" /> ```
Evidence
```
{
  "for": "homepage.og"
}
```
P3
warn
Add Twitter Card meta tags
Used by social platforms and AI agents for richer previews. ```html <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:title" content="Your Page Title" /> <meta name="twitter:description" content="50–160 char description." /> <meta name="twitter:image" content="https://yoursite.com/og-image.jpg" /> ```
Evidence
```
{
  "for": "homepage.twitter"
}
```
P3
warn
Add more substantive homepage content
AI models need 300+ words of visible body text to summarize and recommend a site. Add a value-prop paragraph, a short FAQ, and a 'how it works' section.
Evidence
```
{
  "for": "homepage.word_count"
}
```
P3
warn
Add internal navigation links
Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
Evidence
```
{
  "for": "homepage.internal_links"
}
```
P3
warn
Add /skill.md
Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
Evidence
```
{
  "for": "skill_md"
}
```
P3
warn
Publish /.well-known/security.txt
A security contact builds trust with crawlers and researchers. Minimal example: ``` Contact: mailto:security@yourdomain.com Expires: 2027-01-01T00:00:00.000Z Preferred-Languages: en ```
Evidence
```
{
  "for": "security_txt"
}
```
P3
warn
Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "for": "perf.render_blocking"
}
```
P3
warn
State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "for": "positioning.audience"
}
```
P3
warn
Define a Content-Security-Policy
Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius.
Evidence
```
{
  "for": "security.csp"
}
```
P3
warn
Add X-Frame-Options
`X-Frame-Options: SAMEORIGIN` (or CSP `frame-ancestors`) blocks clickjacking via iframe embeds.
Evidence
```
{
  "for": "security.xfo"
}
```
P4
warn
Add X-Content-Type-Options
`X-Content-Type-Options: nosniff` prevents browsers from MIME-sniffing responses.
Evidence
```
{
  "for": "security.xcto"
}
```
P4
warn
Set a Referrer-Policy
`Referrer-Policy: strict-origin-when-cross-origin` is a safe default.
Evidence
```
{
  "for": "security.referrer"
}
```
P4
warn
Set a Permissions-Policy
Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`.
Evidence
```
{
  "for": "security.permissions"
}
```
P4

14. Priority To-Do List

warn
[ ] Add a discoverable CTA
Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Make your About/Team page reachable
Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Create a robots.txt
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Phrase a heading as a user question
Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html <link rel="canonical" href="https://yoursite.com/" /> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Complete Open Graph tags
AI bots use OG for fast disambiguation. Add all four: ```html <meta property="og:title" content="Your Page Title" /> <meta property="og:description" content="50–160 char description of this page." /> <meta property="og:image" content="https://yoursite.com/og-image.jpg" /> <meta property="og:url" content="https://yoursite.com/" /> <meta property="og:type" content="website" /> <meta property="og:site_name" content="YourSite" /> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add Twitter Card meta tags
Used by social platforms and AI agents for richer previews. ```html <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:title" content="Your Page Title" /> <meta name="twitter:description" content="50–160 char description." /> <meta name="twitter:image" content="https://yoursite.com/og-image.jpg" /> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add more substantive homepage content
AI models need 300+ words of visible body text to summarize and recommend a site. Add a value-prop paragraph, a short FAQ, and a 'how it works' section.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add internal navigation links
Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add /skill.md
Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Publish /.well-known/security.txt
A security contact builds trust with crawlers and researchers. Minimal example: ``` Contact: mailto:security@yourdomain.com Expires: 2027-01-01T00:00:00.000Z Preferred-Languages: en ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for arcpay-web-app.vercel.app

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

https://arcpay-web-app.vercel.app/

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

Track this site week over week

Your charts, not these.