Public share link

AEO Audit for tapersuite.com

Target: https://tapersuite.com/
Score: 45 / 100
Generated: 2026-07-25T08:45:20.869Z
Pages crawled: 9
Findings: 51 pass · 102 warn · 6 fail · 0 unknown

1. Crawl Summary

✅ Fetched 9 of 9 pages successfully Target: https://tapersuite.com

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	TaperSuite
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

⚠️ Multiple H1s found 3 <h1> tags. Prefer one focused H1 per page.
❌ Alt text coverage: 0% 0/2 images have alt text.
⚠️ Content volume: 251 words Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
✅ Homepage fetched successfully HTTP 200 · 29666 bytes · 522ms
✅ Page load time: 0.52s Fast — well within AI crawler budgets.
✅ declared
✅ <title> present (55 chars)
✅ Meta description present (131 chars)
✅ Canonical present https://tapersuite.com/
✅ Open Graph tags complete
✅ Twitter Card tags complete
✅ Critical content is server-rendered Raw and rendered text are within 15% of each other.
✅ Heading structure: 13 (h1:3, h2:8, h3:2) Multiple headings help AI chunk and outline your page.
✅ Internal links: 8 8 internal + 0 external links help crawlers navigate.
✅ Robots meta: "index, follow, max-image-preview:large"
✅ hreflang: 2 alternate(s) Locales: pt-PT, x-default
✅ Favicon declared

4. Content Quality

❌ 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.
⚠️ 1 heading-level skip(s) Heading levels jump (e.g. h2 → h4). AI outline parsers expect monotonic nesting.
⚠️ 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.
⚠️ No date signal found Add or article:published_time meta. AI ranking weights freshness.
⚠️ Text-to-HTML ratio: 6.5% Low text density — most of the response is markup/script.
✅ Author byline declared

5. Schema / Structured Data Audit

⚠️ Article / BlogPosting JSON-LD not found Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
⚠️ BreadcrumbList JSON-LD not found Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
⚠️ LocalBusiness JSON-LD not found Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
⚠️ Person (author / founder) JSON-LD not found Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
⚠️ HowTo JSON-LD not found Add HowTo where applicable so AI answer engines can resolve the entity precisely.
⚠️ VideoObject JSON-LD not found Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
✅ 4 JSON-LD block(s) found Types: Organization, WebSite, SoftwareApplication, FAQPage
✅ Organization present
✅ WebSite present
✅ SoftwareApplication present
✅ FAQPage JSON-LD present

6. Links & Images

❌ Explicit dimensions: 0% (0/2) Add width and height attributes on tags to prevent CLS.
✅ Modern image formats: 100% (2/2 webp/avif) All raster images use modern formats.
✅ No broken links in first 8 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.

7. Performance

⚠️ No images use loading=lazy Add loading="lazy" to off-screen images to defer their fetch until needed.
✅ Page size: 29 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 5 (scripts:2, css:1, img:2) Reasonable request count.
✅ No render-blocking head scripts All head scripts use async or defer.
✅ Inline JS+CSS bulk: 19 KB Inline payload is modest.
✅ Response time: 522ms Fast first response.
✅ Cache-Control set Cache-Control: no-cache, must-revalidate
✅ Compression enabled (gzip) Content-Encoding: gzip

8. Security

✅ Served over HTTPS
✅ No mixed content detected
✅ HSTS set max-age=31536000; includeSubDomains
✅ Content-Security-Policy set default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; script-src 'self' https://js.stripe.com;…
✅ X-Frame-Options set SAMEORIGIN
✅ X-Content-Type-Options set nosniff
✅ Referrer-Policy set strict-origin-when-cross-origin
✅ Permissions-Policy set camera=(), microphone=(), geolocation=()

9. robots.txt and sitemap.xml Audit

✅ robots.txt present 463 chars
✅ robots.txt references sitemap(s)
✅ sitemap.xml present (16 URLs)

10. LLM / AI Crawler Accessibility

⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
⚠️ GPTBot not explicitly addressed No User-agent: GPTBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ ClaudeBot not explicitly addressed No User-agent: ClaudeBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ PerplexityBot not explicitly addressed No User-agent: PerplexityBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ Google-Extended not explicitly addressed No User-agent: Google-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ OAI-SearchBot not explicitly addressed No User-agent: OAI-SearchBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ Applebot-Extended not explicitly addressed No User-agent: Applebot-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ CCBot not explicitly addressed No User-agent: CCBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ skill.md missing Add /skill.md describing what your site lets agents do — speeds up agent task routing.
⚠️ /.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.
⚠️ /llms-full.txt missing Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.

11. Positioning Clarity

❌ No discoverable CTA Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero.
⚠️ No clear About/Team link Add an About or Team link in the nav or footer so LLMs can identify the company.
⚠️ No pricing/plans link found AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
⚠️ Value-prop language not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
✅ H1 communicates value TaperSuite

12. Missing or Hard-to-Find Information

❌ 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

13. Recommended Fixes

⚠️ Create or enrich /llms.txt Follow the llmstxt.org spec:

# Your Brand

> One-line description of your site.

## Docs

- [Getting Started](https://yoursite.com/docs/start): How to get up and running.
- [API Reference](https://yoursite.com/docs/api): Full API details.

## About

- [About us](https://yoursite.com/about): Mission and team.

Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.

⚠️ Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
⚠️ 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.

⚠️ Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

⚠️ Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:
```
# Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID
```
Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
⚠️ Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
⚠️ 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.
⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
⚠️ Fix heading-level skips Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
⚠️ 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.
⚠️ Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.
⚠️ 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.
⚠️ Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:
```
# Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>
```
Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
⚠️ Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.
Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
⚠️ Add a single, focused H1 to the homepage One <h1> per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim.
⚠️ Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
⚠️ 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.
⚠️ Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
⚠️ Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
⚠️ Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
⚠️ Allow PerplexityBot in robots.txt Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
⚠️ Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
⚠️ Allow OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
⚠️ Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
⚠️ Allow CCBot in robots.txt Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
⚠️ Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
⚠️ 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
```
⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
⚠️ Add Article / BlogPosting JSON-LD On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
⚠️ Add BreadcrumbList JSON-LD Helps AI engines understand site hierarchy and improves citation context.
⚠️ Add LocalBusiness JSON-LD (if you have a physical location) Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
⚠️ Add Person JSON-LD for authors / founders Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
⚠️ Add HowTo JSON-LD for step-by-step content For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.
⚠️ Add VideoObject JSON-LD For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.

14. Priority To-Do List

P1 — Create or enrich /llms.txt Follow the llmstxt.org spec:

```
# Your Brand

> One-line description of your site.

## Docs

- [Getting Started](https://yoursite.com/docs/start): How to get up and running.
- [API Reference](https://yoursite.com/docs/api): Full API details.

## About

- [About us](https://yoursite.com/about): Mission and team.
```

Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.

P1 — Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
P2 — 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.

P2 — Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}
```

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

P2 — Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:

```markdown
# Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID
```

Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.

P2 — Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
P2 — 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.
P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
P3 — Fix heading-level skips Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
P3 — 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.
P3 — Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.
P3 — 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.

P3 — Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:

```
# Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>
```

Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.

P3 — Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.
```
Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
```
P3 — Add a single, focused H1 to the homepage One <h1> per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim.
P3 — Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
P3 — 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.
P3 — Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
P3 — Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
P3 — Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://tapersuite.com/

Completed 7/25/2026, 8:45:21 AM

/100

1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://tapersuite.com

Evidence

{
  "pages": [
    {
      "url": "https://tapersuite.com",
      "bytes": 29666,
      "status": 200,
      "fetchMs": 522
    },
    {
      "url": "https://tapersuite.com/",
      "bytes": 29666,
      "status": 200,
      "fetchMs": 155
    },
    {
      "url": "https://tapersuite.com/register",
      "bytes": 29666,
      "status": 200,
      "fetchMs": 153
    },
    {
      "url": "https://tapersuite.com/precos/",
      "bytes": 9980,
      "status": 200,
      "fetchMs": 153
    },
    {
      "url": "https://tapersuite.com/como-funciona/",
      "bytes": 8667,
      "status": 200,
      "fetchMs": 153
    },
    {
      "url": "https://tapersuite.com/software-marcacoes-saloes/",
      "bytes": 9430,
      "status": 200,
      "fetchMs": 153
    },
    {
      "url": "https://tapersuite.com/sistema-marcacoes-online/",
      "bytes": 7336,
      "status": 200,
      "fetchMs": 152
    },
    {
      "url": "https://tapersuite.com/pagina-marcacoes-online/",
      "bytes": 7474,
      "status": 200,
      "fetchMs": 152
    },
    {
      "url": "https://tapersuite.com/recursos/",
      "bytes": 6907,
      "status": 200,
      "fetchMs": 152
    }
  ],
  "origin": "https://tapersuite.com",
  "target": "https://tapersuite.com"
}

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	TaperSuite
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
Content volume: 251 words
Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
Evidence
```
{
  "wordCount": 251
}
```
P3

warn

Multiple H1s found

3 `<h1>` tags. Prefer one focused H1 per page.

Evidence

{
  "h1s": [
    "TaperSuite",
    "Uma formamais calma de marcar.",
    "Software de marcações online para negócios por agenda."
  ]
}

fail
Alt text coverage: 0%
0/2 images have alt text.
P3
pass
Homepage fetched successfully
HTTP 200 · 29666 bytes · 522ms
Evidence
```
{
  "bytes": 29666,
  "status": 200,
  "fetchMs": 522
}
```
P5
pass
Page load time: 0.52s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 522
}
```
P5
pass
<html lang="pt-PT"> declared
Evidence
```
{
  "lang": "pt-PT"
}
```
P5

pass

`<title>` present (55 chars)

Evidence

{
  "title": "Software de marcações online para negócios | TaperSuite"
}

pass

Meta description present (131 chars)

Evidence

{
  "description": "Crie uma página de marcações online para o seu negócio. Configure serviços, horários e equipa, partilhe o link e organize a agenda."
}

pass
Canonical present
https://tapersuite.com/
Evidence
```
{
  "canonical": "https://tapersuite.com/"
}
```
P5

pass

Open Graph tags complete

Evidence

{
  "image": "https://tapersuite.com/shareable.png",
  "title": "Software de marcações online para negócios | TaperSuite",
  "description": "Página de marcações, agenda online, clientes, equipa e serviços no mesmo painel. Feito para negócios que trabalham por marcação."
}

pass

Twitter Card tags complete

Evidence

{
  "card": "summary_large_image",
  "image": "https://tapersuite.com/shareable.png",
  "title": "Software de marcações online para negócios | TaperSuite",
  "description": "Crie a página de marcações da loja, partilhe o link e organize a agenda no TaperSuite."
}

pass
Critical content is server-rendered
Raw and rendered text are within 15% of each other.
Evidence
```
{
  "ratio": 0.14833645967025372,
  "rawTextLen": 20258,
  "renderedTextLen": 3005
}
```
P5
pass
Heading structure: 13 (h1:3, h2:8, h3:2)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 3,
  "h2": 8,
  "h3": 2
}
```
P5
pass
Internal links: 8
8 internal + 0 external links help crawlers navigate.
Evidence
```
{
  "external": 0,
  "internal": 8
}
```
P5
pass
Robots meta: "index, follow, max-image-preview:large"
Evidence
```
{
  "content": "index, follow, max-image-preview:large"
}
```
P5
pass
hreflang: 2 alternate(s)
Locales: pt-PT, x-default
Evidence
```
{
  "hreflangs": [
    "pt-PT",
    "x-default"
  ]
}
```
P5
pass
Favicon declared
Evidence
```
{
  "href": "/favicon.ico"
}
```
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
Text-to-HTML ratio: 6.5%
Low text density — most of the response is markup/script.
Evidence
```
{
  "ratio": 0.06502630239266927,
  "htmlBytes": 29465,
  "textChars": 1916
}
```
P3
warn
1 heading-level skip(s)
Heading levels jump (e.g. h2 → h4). AI outline parsers expect monotonic nesting.
Evidence
```
{
  "levels": [
    1,
    2,
    3,
    1,
    3,
    1,
    2,
    2,
    2,
    2,
    2,
    2,
    2
  ]
}
```
P3
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
pass
Author byline declared
P5

5. Schema / Structured Data Audit

warn
Article / BlogPosting JSON-LD not found
Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
P3
warn
BreadcrumbList JSON-LD not found
Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
P3
warn
LocalBusiness JSON-LD not found
Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
P4
warn
Person (author / founder) JSON-LD not found
Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
P4
warn
HowTo JSON-LD not found
Add HowTo where applicable so AI answer engines can resolve the entity precisely.
P4
warn
VideoObject JSON-LD not found
Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
P4

pass

4 JSON-LD block(s) found

Types: Organization, WebSite, SoftwareApplication, FAQPage

Evidence

{
  "types": [
    "Organization",
    "WebSite",
    "SoftwareApplication",
    "FAQPage"
  ],
  "blocks": 4
}

pass
Organization present
P5
pass
WebSite present
P5
pass
SoftwareApplication present
P5
pass
FAQPage JSON-LD present
P5

6. Links & Images

fail
Explicit dimensions: 0% (0/2)
Add width and height attributes on <img> tags to prevent CLS.
Evidence
```
{
  "total": 2,
  "withDims": 0
}
```
P3
pass
Modern image formats: 100% (2/2 webp/avif)
All raster images use modern formats.
Evidence
```
{
  "total": 2,
  "legacy": 0,
  "modern": 2
}
```
P5
pass
No broken links in first 8
HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
Evidence
```
{
  "broken": 0,
  "sampled": 8,
  "examples": []
}
```
P5

7. Performance

warn
No images use loading=lazy
Add loading="lazy" to off-screen images to defer their fetch until needed.
P3
pass
Page size: 29 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 29666
}
```
P5

pass

Resource requests: 5 (scripts:2, css:1, img:2)

Reasonable request count.

Evidence

{
  "imgs": 2,
  "styles": 1,
  "scripts": 2,
  "inlineStyles": 1,
  "inlineScripts": 3
}

pass
No render-blocking head scripts
All head scripts use async or defer.
P5
pass
Inline JS+CSS bulk: 19 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 5262,
  "inlineCssBytes": 13771
}
```
P5
pass
Response time: 522ms
Fast first response.
Evidence
```
{
  "bytes": 29666,
  "fetchMs": 522
}
```
P5
pass
Cache-Control set
Cache-Control: no-cache, must-revalidate
Evidence
```
{
  "cdn": [],
  "cacheControl": "no-cache, must-revalidate"
}
```
P5
pass
Compression enabled (gzip)
Content-Encoding: gzip
Evidence
```
{
  "encoding": "gzip"
}
```
P5

8. Security

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://tapersuite.com/"
}

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

pass

Content-Security-Policy set

default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; script-src 'self' https://js.stripe.com;…

Evidence

{
  "value": "default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; script-src 'self' https://js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https://api.tapersuite.com wss://api.tapersuite.com https://*.sentry.io; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://checkout.stripe.com; form-action 'self' https://checkout.stripe.com"
}

pass
X-Frame-Options set
SAMEORIGIN
Evidence
```
{
  "value": "SAMEORIGIN"
}
```
P5
pass
X-Content-Type-Options set
nosniff
Evidence
```
{
  "value": "nosniff"
}
```
P5
pass
Referrer-Policy set
strict-origin-when-cross-origin
Evidence
```
{
  "value": "strict-origin-when-cross-origin"
}
```
P5
pass
Permissions-Policy set
camera=(), microphone=(), geolocation=()
Evidence
```
{
  "value": "camera=(), microphone=(), geolocation=()"
}
```
P5

9. robots.txt and sitemap.xml Audit

pass

robots.txt present

463 chars

Evidence

{
  "snippet": "User-agent: *\nAllow: /\nDisallow: /dashboard\nDisallow: /owner\nDisallow: /admin\nDisallow: /worker-dashboard\nDisallow: /subscription\nDisallow: /booking/manage\nDisallow: /onboarding\nDisallow: /forgot-password\nDisallow: /reset-password\nDisallow: /login\nDisallow: /register\nDisallow: /mock-checkout\nDisallow: /mock-customer-portal\nDisallow: /graphql\nDisallow: /auth\nDisallow: /general\nDisallow: /upload\nDisallow: /socket.io\n\nSitemap: https://tapersuite.com/sitemap.xml\n"
}

pass

robots.txt references sitemap(s)

Evidence

{
  "sitemaps": [
    "https://tapersuite.com/sitemap.xml"
  ]
}

pass

sitemap.xml present (16 URLs)

Evidence

{
  "snippet": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://tapersuite.com/</loc>\n    <lastmod>2026-07-10</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/como-funciona/</loc>\n    <lastmod>2026-07-10</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/precos/</loc>\n    <lastmod>2026-07-10</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/sistema-marcacoes-online/</loc>\n    <lastmod>2026-07-23</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/software-marcacoes-barbearias/</loc>\n    <lastmod>2026-07-23</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/agenda-online-barbearias/</loc>\n    <lastmod>2026-07-23</lastmod>\n  </url>\n  <url>\n    <loc>https://tapersuite.com/software-gestao-sal",
  "urlCount": 16
}

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
GPTBot not explicitly addressed
No User-agent: GPTBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
ClaudeBot not explicitly addressed
No User-agent: ClaudeBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
PerplexityBot not explicitly addressed
No User-agent: PerplexityBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
Google-Extended not explicitly addressed
No User-agent: Google-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
OAI-SearchBot not explicitly addressed
No User-agent: OAI-SearchBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
Applebot-Extended not explicitly addressed
No User-agent: Applebot-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
CCBot not explicitly addressed
No User-agent: CCBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
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
warn
/llms-full.txt missing
Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
P3

11. Generative Engine Optimization (GEO)

fail
No llms.txt found
llms.txt tells generative AI systems what to read, index, and cite. Create /llms.txt following the llmstxt.org spec — include headings, page descriptions, and links to key resources.
P1
warn
Organization schema has no knowledge graph sameAs links
Add `sameAs` pointing to Wikipedia, Wikidata, LinkedIn, or Crunchbase. AI systems use these links to resolve your brand name as a known entity rather than an ambiguous string.
Evidence
```
{
  "existingSameAs": []
}
```
P2
warn
No AI agent integration files found
Add at least one: /.well-known/ai-plugin.json (ChatGPT plugin discovery), /.well-known/agent-card.json (A2A protocol), or /skill.md (Claude tool integration). These let AI agents interact with your site programmatically and signal that your site is AI-native.
P2
warn
No llms-full.txt found
llms-full.txt is an extended version of llms.txt that embeds the full text of every listed resource. Large-context models and RAG pipelines can ingest your entire site in one request — greatly improving citation coverage.
P3
warn
No outbound links to authoritative sources on the homepage
Generative AI systems cite pages that themselves cite credible sources. Link to Wikipedia, .gov, .edu, peer-reviewed research, or major news outlets to signal epistemic trustworthiness.
P3
pass
Brand entity declared: "TaperSuite"
AI systems can resolve "TaperSuite" as a distinct entity. Ensure this name is used consistently in titles, H1s, and social profiles.
Evidence
```
{
  "schemaName": "TaperSuite"
}
```
P5

12. 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
TaperSuite
P5

13. Foundations

pass
<!doctype html> declared
P5
pass
Meta viewport present
content="width=device-width,initial-scale=1"
Evidence
```
{
  "content": "width=device-width,initial-scale=1"
}
```
P5
pass
Theme color set (#2f6f73)
Evidence
```
{
  "color": "#2f6f73"
}
```
P5

pass

1 feed(s) discovered

application/rss+xml: https://tapersuite.com/feed.xml

Evidence

{
  "feeds": [
    {
      "href": "https://tapersuite.com/feed.xml",
      "type": "application/rss+xml"
    }
  ]
}

14. Accessibility

warn
No skip navigation link found
Add a visible-on-focus skip link as the first focusable element: <a href="#main">Skip to main content</a>.
P3
warn
Missing landmark(s): <nav>, <footer>
Semantic landmarks help screen readers and AI agents navigate page structure.
Evidence
```
{
  "nav": 0,
  "main": 1,
  "footer": 0,
  "header": 2
}
```
P3

15. Well-Known URIs

warn
/.well-known/agent-card.json missing
Publish an agent card at /.well-known/agent-card.json to enable agent-to-agent (A2A) discovery.
P4
warn
No HTTP Link header
Add a Link response header to advertise sitemap, llms.txt, and api-catalog to crawlers without requiring HTML parsing.
P4
warn
/.well-known/api-catalog missing
Publish a /.well-known/api-catalog (RFC 9727 Linkset) so agents can discover your API endpoints automatically.
P4
warn
/.well-known/change-password missing
Redirect /.well-known/change-password to your password-change page so password managers can deep-link directly.
P4

16. Privacy

warn
No privacy policy link found
Add a visible link to your privacy policy. Required by GDPR, CCPA, and expected by AI agents assessing trustworthiness.
P2
pass
No third-party scripts detected
P5

17. Resilience

pass
Web App Manifest declared
/manifest.json
Evidence
```
{
  "href": "/manifest.json"
}
```
P5

18. Website Specification

No findings.

19. 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

20. Recommended Fixes

warn
Create or enrich /llms.txt
Follow the llmstxt.org spec: ``` # Your Brand > One-line description of your site. ## Docs - [Getting Started](https://yoursite.com/docs/start): How to get up and running. - [API Reference](https://yoursite.com/docs/api): Full API details. ## About - [About us](https://yoursite.com/about): Mission and team. ``` Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.
Evidence
```
{
  "for": "geo.llms_txt"
}
```
P1
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
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
Add sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "for": "geo.knowledge_graph"
}
```
P2
warn
Add an AI agent integration file
At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API: ```markdown # Your Brand Skill API endpoint: https://yoursite.com/api Auth: Bearer token ## Tools - search: Search the knowledge base - get_article: Retrieve a full article by ID ``` Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
Evidence
```
{
  "for": "geo.agent_integration"
}
```
P2
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 Article / BlogPosting JSON-LD
On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
Evidence
```
{
  "for": "schema.article"
}
```
P3
warn
Fix heading-level skips
Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
Evidence
```
{
  "for": "content.heading_order"
}
```
P3
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
Generate /llms-full.txt for RAG pipelines
llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root: ``` # Your Brand — Full Content ## Getting Started <full markdown content of /docs/start> ## API Reference <full markdown content of /docs/api> ``` Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
Evidence
```
{
  "for": "geo.llms_full_txt"
}
```
P3
warn
Add outbound links to authoritative sources
Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood. Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
Evidence
```
{
  "for": "geo.citation_signals"
}
```
P3
warn
Add a single, focused H1 to the homepage
One `<h1>` per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim.
Evidence
```
{
  "for": "homepage.h1"
}
```
P3
warn
Add alt text to all meaningful images
Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
Evidence
```
{
  "for": "homepage.alt_text"
}
```
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
Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "for": "images.dimensions"
}
```
P3
warn
Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.GPTBot"
}
```
P3
warn
Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.ClaudeBot"
}
```
P3
warn
Allow PerplexityBot in robots.txt
Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.PerplexityBot"
}
```
P3
warn
Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Google-Extended"
}
```
P3
warn
Allow OAI-SearchBot in robots.txt
Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.OAI-SearchBot"
}
```
P3
warn
Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Applebot-Extended"
}
```
P3
warn
Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.CCBot"
}
```
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
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
Add BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "for": "schema.breadcrumb"
}
```
P3
warn
Add HowTo JSON-LD for step-by-step content
For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.
Evidence
```
{
  "for": "schema.howto"
}
```
P4
warn
Add Person JSON-LD for authors / founders
Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
Evidence
```
{
  "for": "schema.person"
}
```
P4
warn
Add LocalBusiness JSON-LD (if you have a physical location)
Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
Evidence
```
{
  "for": "schema.local_business"
}
```
P4
warn
Add VideoObject JSON-LD
For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.
Evidence
```
{
  "for": "schema.video"
}
```
P4

21. Priority To-Do List

warn
[ ] Create or enrich /llms.txt
Follow the llmstxt.org spec: ``` # Your Brand > One-line description of your site. ## Docs - [Getting Started](https://yoursite.com/docs/start): How to get up and running. - [API Reference](https://yoursite.com/docs/api): Full API details. ## About - [About us](https://yoursite.com/about): Mission and team. ``` Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.
Evidence
```
{
  "priority": 1
}
```
P1
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
[ ] Add an AI agent integration file
At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API: ```markdown # Your Brand Skill API endpoint: https://yoursite.com/api Auth: Bearer token ## Tools - search: Search the knowledge base - get_article: Retrieve a full article by ID ``` Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
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
[ ] 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 sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "priority": 2
}
```
P2
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
[ ] Generate /llms-full.txt for RAG pipelines
llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root: ``` # Your Brand — Full Content ## Getting Started <full markdown content of /docs/start> ## API Reference <full markdown content of /docs/api> ``` Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add outbound links to authoritative sources
Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood. Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add a single, focused H1 to the homepage
One `<h1>` per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add alt text to all meaningful images
Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
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
[ ] Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Fix heading-level skips
Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
Evidence
```
{
  "priority": 3
}
```
P3
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

AEO Audit for tapersuite.com

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://tapersuite.com/

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. Generative Engine Optimization (GEO)

12. Positioning Clarity

13. Foundations

14. Accessibility

15. Well-Known URIs

16. Privacy

17. Resilience

18. Website Specification

19. Missing or Hard-to-Find Information

20. Recommended Fixes

21. Priority To-Do List

Track this site week over week

Your charts, not these.

Email yourself this report