Foglift
solusofttech.com — Website Report
Scored 48/100 · Scanned with Foglift
F
Fixing "Missing HSTS header" would move solusofttech.com from 48 to 68.
5 critical14 warnings26 total issues
Quick wins
~168 min total fix time1Missing viewport meta tag~1m
2Missing language attribute~1m
3Missing HSTS header~2m
https://solusofttech.com/ · 4/23/2026, 11:25:37 AM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://solusofttech.com/ Your site scores 48/100 overall, but AI engines may be missing you. Your AI Visibility is 57/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 5 critical issues and 14 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections.
2. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 3. Missing meta description — No meta description found. Search engines use this as the snippet in results. Add one for better CTR. 4. Missing viewport meta tag — No viewport meta tag found. This is essential for mobile responsiveness. 5. 6 render-blocking scripts — 6 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical script
18 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.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
57D
85
Brand Mentions
Found 17+ web mentions of "solusofttech"
37
Domain Authority
PageRank: 0.9/10, 18+ external references
28
Content Freshness
39 pages in sitemap but none updated recently
63
Technical Readiness
Moderate technical readiness — some improvements possible
Technical Issues
No FAQ section foundwarning~15 min fix
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
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>AI models frequently cite FAQ content. Add FAQPage schema to boost your chances of appearing in AI-generated answers.
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 Solusofttech?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Solusofttech
SEO & Technical Issues (24)
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 meta descriptioncriticalSEO~5 min fix
No meta description found. Search engines use this as the snippet in results. Add one for better CTR.
Quick Fix
<meta name="description" content="Clear, compelling description of your page in 120-160 characters. Include your main keyword naturally.">Meta descriptions appear in search results. A good one improves click-through rate by 5-10%.
Missing viewport meta tagcriticalSEO~1 min fix
No viewport meta tag found. This is essential for mobile responsiveness.
Quick Fix
<meta name="viewport" content="width=device-width, initial-scale=1">Without a viewport meta tag, mobile devices render your page at desktop width. This is critical for mobile SEO.
6 render-blocking scriptscriticalPerformance
6 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
Missing X-Content-Type-Options headerwarningSecurity~2 min fix
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
Quick Fix
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Prevents browsers from MIME-type sniffing, which can lead to security vulnerabilities.
Missing X-Frame-Options headerwarningSecurity~2 min fix
Set X-Frame-Options to prevent clickjacking attacks.
Quick Fix
# Nginx:
add_header X-Frame-Options "SAMEORIGIN" always;
# Next.js (next.config.js headers):
{ key: 'X-Frame-Options', value: 'SAMEORIGIN' }X-Frame-Options prevents clickjacking by controlling who can embed your page in an iframe.
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.
Missing Open Graph tagswarningSEO~10 min fix
Missing og:title, 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.
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.
Missing language attributewarningSEO~1 min fix
Add a lang attribute to your <html> tag (e.g., lang="en"). This helps search engines and screen readers understand your content's language.
Quick Fix
<html lang="en">
<!-- For other languages: lang="es", lang="fr", lang="de", lang="ja", etc. -->The lang attribute helps search engines and screen readers understand your content's language.
Multiple H1 headings foundwarningSEO
Found 13 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.
1 image missing alt textwarningSEO
Found 1 of 198 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
1% of images lack alt textwarningAccessibility
1 of 198 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Skipped heading levelwarningAccessibility
Heading hierarchy jumps from H1 to H3. Don't skip heading levels — this confuses screen readers and assistive technology.
1 link with vague textwarningAccessibility
Links with text like "click here" or "read more" don't make sense out of context. Use descriptive link text that explains the destination.
106 images without lazy loadingwarningPerformance
106 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
Missing Twitter Card tagsinfoSEO~5 min fix
Add twitter:card meta tags for optimized appearance when your pages are shared on Twitter/X.
Quick Fix
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="A compelling description">
<meta name="twitter:image" content="https://yoursite.com/twitter-image.jpg">Twitter Card tags control how your page appears when shared on Twitter/X.
Few internal linksinfoSEO
Add more internal links to help search engines discover and index your other pages. Internal linking also helps distribute page authority.
No main landmarkinfoAccessibility~3 min fix
Add a <main> element to identify the primary content area. Screen reader users use this to skip navigation.
Quick Fix
<!-- Wrap your primary content in a <main> element -->
<main id="main-content">
<h1>Page Title</h1>
<p>Your primary content here...</p>
</main>The <main> element identifies the primary content area, letting screen reader users skip to it directly.
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 18 elements with large inline styles. Move these to external CSS for better caching and maintainability.
No resource hintsinfoPerformance~5 min fix
Add <link rel='preconnect'> for critical third-party domains to reduce connection setup time.
Quick Fix
<!-- Add to <head> for your critical third-party domains -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="dns-prefetch" href="https://cdn.example.com">Preconnect and DNS-prefetch reduce connection time to third-party domains by starting the handshake early.
Your Potential Score
48
Now
73
Potential
+25 points possible by fixing 26 issues
That moves you from F to C — above average
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Start monitoring — from $49/mo
Free tier available · No credit card required
Industry Benchmark
SEO
Avg: 62-15At risk
AI Readiness
Avg: 35+21Ahead
Performance
Avg: 55+7On par
Security
Avg: 40-40At risk
Accessibility
Avg: 68+4On par
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
SEO issues — Your site may be losing 50-70% of potential Google traffic due to missing meta tags, broken structure, or indexing problems.
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: 0/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.
Score of 0 means your site has no security headers at all. Browsers may show security warnings to visitors.