www.trademo.com — Website Report

Scored 81/100 · Scanned with Foglift

OverallⓘOverall Score — weighted average of all category scores

trademo.com scored 81 — top 15% of sites we've scanned.

Scan another domain Save this scan to your free account

3 critical2 warnings7 total issues

Quick wins

~44 min total fix time

1AI search engines can't read your site~2m

2Missing HSTS header~2m

3Missing Content Security Policy header~5m

https://www.trademo.com/ · 2026-08-19

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://www.trademo.com/ Your site scores 81/100 overall. AI Readiness is 62/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 3 critical issues and 2 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, PerplexityBot...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.

2. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections. 3. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. QUICK WINS (Warnings): 1. No FAQ section found — A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained. 2. Missing Open Graph t

4 more critical fixes + quick wins in your full report

Enter your email and we'll send the complete action plan to your inbox.

No spam. Just your report.

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

62D

Technical57

Authority67

Set up all 6 tiers free →

100

Brand Mentions

Found 20+ web mentions of "trademo"

Domain Authority

PageRank: 2.4/10, 7+ external references

Content Freshness

500 pages in sitemap but none updated recently

Technical Readiness

Moderate technical readiness — some improvements possible

Technical Issues

AI search engines can't read your sitecritical~2 min fix

Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, PerplexityBot...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.

Quick Fix

# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Allow AI crawlers to index your content so you appear in ChatGPT, Perplexity, and Google AI Overviews.

No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

Quick Fix

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>

FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.

How does AI see Trademo?

When users ask AI about your industry, are you recommended?

Start with weekly Perplexity checks for Trademo. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude.

Set up weekly monitoring free

SEO & Technical Issues (5)

Missing HSTS headercriticalSecurity~2 min fix

Enable HTTP Strict Transport Security to force HTTPS connections.

Quick Fix

# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }

HSTS forces browsers to use HTTPS, preventing downgrade attacks and cookie hijacking.

Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix

# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }

Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.

Missing Open Graph tagswarningSEO~10 min fix

Missing og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.

Quick Fix

<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">

Open Graph tags control how your page looks when shared on Facebook, LinkedIn, and other social platforms.

No navigation landmarkinfoAccessibility~5 min fix

Add a <nav> element to help screen reader users quickly find the navigation. This is a WCAG 2.4.1 requirement.

Quick Fix

<!-- Wrap your navigation in a <nav> element -->
<nav aria-label="Main navigation">
  <ul>
    <li><a href="/">Home</a></li>
    <li><a href="/about">About</a></li>
    <li><a href="/contact">Contact</a></li>
  </ul>
</nav>

The <nav> landmark lets screen reader users quickly jump to navigation (WCAG 2.4.1).

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix

<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>

Skip links let keyboard users bypass repetitive navigation and jump straight to content.

Your Potential Score

Now

Estimated potential

+12 points estimated improvement from addressing 7 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Perplexity weekly while you're active. Paid plans add ChatGPT, Google AI Overview, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Perplexity while active · No credit card required

Compare paid plans — from $49/mo