Skip to main content

getloot.ca — Website Report

Scored 74/100 · Scanned with Foglift

C
OverallOverall Score — weighted average of all category scores

getloot.ca scored 74. Addressing the 11 listed issues could raise its estimated score to 88.

2 critical5 warnings11 total issues

Quick wins

~90 min total fix time
1Missing Permissions Policy header~2m
2Missing canonical URL~3m
3Missing Content Security Policy header~5m

https://getloot.ca/ · 2026-08-12

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Search Readiness Risk

Your AI Readiness score of 46/100 identifies technical and content barriers that may make this page harder for AI systems to access, understand, or reuse. It does not show whether AI assistants recommend or cite your site. Check answer-level AI visibility →

AI Action Plan

Website Analysis for https://getloot.ca Your site scores 74/100 overall. AI Readiness is 46/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 2 critical issues and 5 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. AI engines can't understand your business — Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.

2. 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 Permissions Policy header — Add a Permissions-Policy header to control browser feature access. 3. Meta

6 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

46F
Technical51
Authority41
Set up all 6 tiers free →
85
Brand Mentions
Found 17+ web mentions of "getloot"
0
Domain Authority
PageRank: 0.0/10, 0+ external references
10
Content Freshness
14 pages in sitemap but none updated recently
51
Technical Readiness
Moderate technical readiness — some improvements possible

Technical Issues

AI engines can't understand your businesscritical~10 min fix

Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://yoursite.com",
  "description": "Brief description of your business",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>
Add JSON-LD structured data so AI models understand your business entity and can cite you accurately.
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.
AI doesn't know who you areinfo~10 min fix

Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany",
    "https://github.com/yourorg"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@yoursite.com",
    "contactType": "customer service"
  }
}
</script>
Entity markup tells AI models who you are, making them more likely to cite your brand accurately.

Pro tip: The biggest drivers of AI visibility are brand mentions and domain authority — not just technical setup. Set up Free monitoring →

How does AI see Getloot?

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

G
C
P
Ge
A

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

SEO & Technical Issues (8)

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 Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }
Permissions-Policy restricts which browser features your site can use, reducing attack surface.
Meta description too longwarningSEO

Your description is 162 characters. Keep it under 160 for best display.

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.
Missing canonical URLwarningSEO~3 min fix

Add a canonical link to prevent duplicate content issues in search engines.

Quick Fix
<link rel="canonical" href="https://yoursite.com/current-page">
Canonical URLs prevent duplicate content issues by telling search engines which version of a page is the original.
No structured data foundinfoSEO

Add JSON-LD structured data (Schema.org) to help search engines understand your content and earn rich snippets in search results.

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.
Heavy inline stylesinfoPerformance

Found 130 elements with large inline styles. Move these to external CSS for better caching and maintainability.

Your Potential Score

74

Now

88

Estimated potential

+14 points estimated improvement from addressing 11 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 Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, 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 Google AI Overview while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+20Ahead
AI Readiness
Avg: 35+11Ahead
Performance
Avg: 55+30Ahead
Security
Avg: 40+20Ahead
Accessibility
Avg: 68+29Ahead

Based on 120+ websites scanned across industries. See full benchmark report →

What This Score Means for You

Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.

Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.

AI visibility preview

See which brands Google AI Overview surfaces for your category.

Recent scans on Foglift

Scan your own site free →