Skip to main content

marijuanadoctor.com — Website Report

Scored 67/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

marijuanadoctor.com scored 67. Addressing the 16 listed issues could raise its estimated score to 93.

4 critical8 warnings16 total issues

Quick wins

~121 min total fix time
1Missing HSTS header~2m
2Missing Referrer Policy header~2m
3Missing Permissions Policy header~2m

https://marijuanadoctor.com/ · 2026-08-22

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://marijuanadoctor.com Your site scores 67/100 overall. AI Readiness is 65/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 4 critical issues and 8 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 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. 4. 4 render-blocking scripts — 4 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. Missing Referrer Policy header — Add a Referrer-Policy header to control information leakage. 2. Missing Permission

11 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

65D
Technical59
Authority70
Set up all 6 tiers free →
100
Brand Mentions
Found 20+ web mentions of "marijuanadoctor"
43
Domain Authority
PageRank: 3.0/10, 9+ external references
41
Content Freshness
500 pages in sitemap but none updated recently
59
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.
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.

How does AI see Marijuanadoctor?

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

G
C
P
Ge
A

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

SEO & Technical Issues (14)

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.
4 render-blocking scriptscriticalPerformance

4 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Referrer Policy headerwarningSecurity~2 min fix

Add a Referrer-Policy header to control information leakage.

Quick Fix
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }
Controls how much referrer information is sent with requests, protecting user privacy.
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.
Title tag too longwarningSEO

Your title is 77 characters. Keep it under 60 for best display in search results.

Meta description too longwarningSEO

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

1 image missing alt textwarningSEO

Found 1 of 52 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).

2% of images lack alt textwarningAccessibility

1 of 52 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H2 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.

52 images without lazy loadingwarningPerformance

52 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.

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

67

Now

93

Estimated potential

+26 points estimated improvement from addressing 16 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

Industry Benchmark

SEO
Avg: 62+23Ahead
AI Readiness
Avg: 35+30Ahead
Performance
Avg: 55+18Ahead
Security
Avg: 40-10Behind
Accessibility
Avg: 68+16Ahead

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

What This Score Means for You

Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.

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

Security score: 30/100

Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.

AI visibility preview

See which brands Perplexity surfaces for your category.

Recent scans on Foglift

Scan your own site free →