AEO Audit for biztechra.site
Target: https://www.biztechra.site/
Score: 61 / 100
Generated: 2026-08-23T02:37:09.159Z
Pages crawled: 9
Findings: 69 pass · 75 warn · 0 fail · 0 unknown
1. Crawl Summary
- ✅ Fetched 9 of 9 pages successfully Target: https://www.biztechra.site
2. Data Found
| Data Point | Found? | Source | Notes |
|---|---|---|---|
| Pricing | Yes | Pricing page | https://www.biztechra.site/pricing |
| Customer logos | No | — | — |
| Social proof | No | — | — |
| Recent launches | No | Navigation links | — |
| Blog post activity | No | Navigation links | — |
| New hires | No | — | Often only on a /blog/team or LinkedIn page |
| Headline copy | Yes | Homepage | You built the foundation. Now scale with a proven digital growth agency |
| Positioning | Yes | Homepage | we help |
| Executive team | Yes | About/team page | https://www.biztechra.site/about |
| Product/service descriptions | Yes | Homepage | From meta description |
| Case studies or testimonials | Yes | Homepage | testimonial |
| Contact/demo/signup paths | Yes | Navigation links | — |
3. Homepage Audit
- ✅ Homepage fetched successfully HTTP 200 · 135994 bytes · 642ms
- ✅ Page load time: 0.64s Fast — well within AI crawler budgets.
- ✅ declared
- ✅ Single H1 You built the foundation. Now scale with a proven digital growth agency
- ✅
<title>present (51 chars) - ✅ Meta description present (122 chars)
- ✅ Canonical present https://www.biztechra.site
- ✅ Open Graph tags complete
- ✅ Twitter Card tags complete
- ✅ Critical content is server-rendered Raw and rendered text are within 15% of each other.
- ✅ Content volume: 1248 words Substantive content — AI models have enough to summarize and recommend.
- ✅ Heading structure: 27 (h1:1, h2:7, h3:19) Multiple headings help AI chunk and outline your page.
- ✅ Internal links: 110 110 internal + 3 external links help crawlers navigate.
- ✅ Robots meta: "index, follow"
- ✅ Favicon declared
4. Content Quality
- ⚠️ No date signal found Add or article:published_time meta. AI ranking weights freshness.
- ⚠️ Text-to-HTML ratio: 7.1% Low text density — most of the response is markup/script.
- ✅ Heading levels are well-ordered 27 headings nested in order.
- ✅ Snippet-ready blocks: 3 (ul:2, ol:1, table:0) Lists and tables are extracted verbatim by AI answer engines.
- ✅ 1 definition list(s) present Definition lists give AI answer engines explicit term→meaning pairs.
- ✅ 1 question-style heading(s) Questions in headings map cleanly to user queries. Pair with FAQPage JSON-LD for max lift.
- ✅ Author byline declared
5. Schema / Structured Data Audit
- ⚠️ Organization missing Adding Organization JSON-LD helps LLMs identify your entity.
- ⚠️ WebSite missing Adding WebSite JSON-LD helps LLMs identify your entity.
- ⚠️ SoftwareApplication missing Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
- ⚠️ 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.
- ⚠️ Product / Offer JSON-LD not found Add Product / Offer 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.
- ✅ 3 JSON-LD block(s) found Types: WebPage, ProfessionalService+LocalBusiness, FAQPage
- ✅ FAQPage JSON-LD present
- ✅ LocalBusiness JSON-LD present
6. Links & Images
- ✅ External nofollow: 0% (0/3) Healthy mix of follow and nofollow outbound links.
- ✅ No broken links in first 20 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
7. Performance
- ⚠️ 1 render-blocking script(s) in Move non-critical scripts to end of or add
defer/async. - ⚠️ Response time: 642ms Slow response. Check CDN/cache headers and origin latency.
- ✅ Page size: 133 KB Compact HTML payload — well within AI crawler limits.
- ✅ Resource requests: 16 (scripts:14, css:2, img:0) Reasonable request count.
- ✅ Inline JS+CSS bulk: 42 KB Inline payload is modest.
- ✅ Cache-Control set (CDN: Vercel) Cache-Control: public, max-age=3600, stale-while-revalidate=59 CDN detected: Vercel
- ✅ Compression enabled (Brotli) Content-Encoding: br
8. Security
- ✅ Served over HTTPS
- ✅ No mixed content detected
- ✅ HSTS set max-age=63072000; includeSubDomains; preload
- ✅ Content-Security-Policy set default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-…
- ✅ X-Frame-Options set SAMEORIGIN
- ✅ X-Content-Type-Options set nosniff
- ✅ Referrer-Policy set strict-origin-when-cross-origin
- ✅ Permissions-Policy set camera=(), microphone=(self), geolocation=()
9. robots.txt and sitemap.xml Audit
- ✅ robots.txt present 530 chars
- ✅ robots.txt references sitemap(s)
- ✅ sitemap.xml present (143 URLs)
10. LLM / AI Crawler Accessibility
- ⚠️ 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.
- ✅ GPTBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
- ✅ ClaudeBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
- ✅ PerplexityBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
- ✅ Google-Extended has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
- ✅ llms.txt present 1688 chars
- ✅ /llms-full.txt present 5688 chars — full site content for LLM ingest.
11. Positioning Clarity
- ✅ About/Team path discoverable
- ✅ H1 communicates value You built the foundation. Now scale with a proven digital growth agency
- ✅ Value-prop language detected
- ✅ Pricing path discoverable
- ✅ Contact / signup path discoverable
12. Missing or Hard-to-Find Information
- ⚠️ 5 data point(s) could not be found from public pages · Customer logos · Social proof · Recent launches · Blog post activity · New hires
13. Recommended Fixes
⚠️ Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include
sameAspointing 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 IDAlso consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
⚠️ Add Organization JSON-LD Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
⚠️ 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.
⚠️ 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.
⚠️ 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⚠️ Eliminate render-blocking head scripts Add
deferorasyncto any<script src="…">in<head>, or move it to the end of<body>.⚠️ Reduce response time Push static HTML to a CDN edge cache. If you must server-render per-request, profile DB/template work and add
Cache-Control: s-maxage=….⚠️ Add WebSite JSON-LD Helps engines understand the root site and enables sitelinks-search-box features.
⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
⚠️ 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 Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
⚠️ 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
P2 — Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include
sameAspointing 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 Organization JSON-LD Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
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 — 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 — Allow OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
P3 — Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
P3 — Allow CCBot in robots.txt Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
P3 — Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
P3 — 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 ```P3 — Eliminate render-blocking head scripts Add
deferorasyncto any<script src="…">in<head>, or move it to the end of<body>.P3 — Reduce response time Push static HTML to a CDN edge cache. If you must server-render per-request, profile DB/template work and add
Cache-Control: s-maxage=….P3 — Add WebSite JSON-LD Helps engines understand the root site and enables sitelinks-search-box features.
P3 — Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
P3 — 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.
P3 — Add BreadcrumbList JSON-LD Helps AI engines understand site hierarchy and improves citation context.
P3 — Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
P4 — 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.
P4 — 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.
Report by CrawlProof. Reusable after every major website change.