Skip to main content

www.puc.edu — Website Report

Scored 45/100 · Scanned with Foglift

Site Technical HealthMean of SEO, Performance, Security, and Accessibility. AI Readiness is reported separately.
F
Site Technical Health

Mean of SEO, Performance, Security, and Accessibility.

puc.edu: start with "No structured data for AI engines". Addressing the 11 listed issues could raise its estimated score from 45 to 64.

SEOSearch Engine Optimization — how well your site ranks in traditional search engines like Google
AI ReadinessAI Readiness: this saved audit's weighted combination of Technical (T1) and Authority (T2) signals.Unavailable
PerformancePerformance — how fast your site loads (Core Web Vitals, page weight, render speed)
SecuritySecurity — how well your site protects against threats (HTTPS, headers, CSP, HSTS)
AccessibilityAccessibility — how usable your site is for people with disabilities, including screen readers and keyboard navigation
3 critical6 warnings11 total issues

Quick wins

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

https://www.puc.edu/home · 2026-03-15

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://www.puc.edu/home Your website needs significant improvements — Site Technical Health is 45/100. We found 3 critical issues and 6 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. No structured data for AI engines — Add JSON-LD structured data (Schema.org) so AI models can understand your business type, services, and key information. This is critical for appearing in AI-generated answers.

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. IMPROVE NEXT (Warnings): 1. No FAQ section detected — Add an FAQ section with common questions about your business. AI models frequently extract Q&A content for generated answers. Use FAQPage schema markup for best results. 2. Missing Referrer Policy header — Add a Referrer-Policy header

8 more critical fixes + quick wins in your full report

Create a free account to save this audit and unlock the complete action plan.

Save and unlock my full report

Free account. No credit card required.

Share This Technical Audit

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

Email to Contact

AI Search Readiness

Technical and content signals that affect whether AI systems can access, understand, and reuse your page

No structured data for AI enginescritical

Add JSON-LD structured data (Schema.org) so AI models can understand your business type, services, and key information. This is critical for appearing in AI-generated answers.

No FAQ section detectedwarning

Add an FAQ section with common questions about your business. AI models frequently extract Q&A content for generated answers. Use FAQPage schema markup for best results.

No entity identity markupinfo

Add Organization, LocalBusiness, or Person schema to define your entity. AI models use this to understand who you are and recommend you as an authority in your domain.

How does AI see Puc?

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

G
C
P
Ge
A

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

SEO & Technical Issues (8)

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 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 113 characters. Keep it under 60 for best display in search results.

Missing Open Graph tagswarningSEO~10 min fix

Missing og:description, 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.
Multiple H1 headings foundwarningSEO

Found 2 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.

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.

Your Potential Score

45

Now

64

Estimated potential

+19 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 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-12At risk
AI Readiness
Avg: 35Unavailable
Performance
Avg: 55-5Behind
Security
Avg: 40-10Behind
Accessibility
Avg: 68-18At risk

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

What This Score Means for You

SEO issues — Your site may be losing 20-40% of potential Google traffic due to missing meta tags, broken structure, or indexing problems.

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.

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

Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).

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.

Recent scans on Foglift

Scan your own site free →