Skip to main content

msengineers.co.za — Website Report

Scored 57/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

msengineers.co.za scored 57. Addressing the 21 listed issues could raise its estimated score to 81.

4 critical11 warnings21 total issues

Quick wins

~151 min total fix time
1Missing HSTS header~2m
2Missing X-Content-Type-Options header~2m
3Missing X-Frame-Options header~2m

https://msengineers.co.za/ · 2026-08-16

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Search Readiness Risk

Your AI Readiness score of 45/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 →

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

45F

Some external data sources were unavailable. Score is based on partial data.

Technical48
Authority43
Set up all 6 tiers free →
85
Brand Mentions
Found 19+ web mentions of "msengineers"
0
Domain Authority
PageRank: 0.0/10, 0+ external references
Content Freshness
Unavailable
48
Technical Readiness
Low technical readiness — missing key AI-friendly markup

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

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

G
C
P
Ge
A

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

SEO & Technical Issues (18)

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 page titlecriticalSEO~3 min fix

Your page has no <title> tag. This is critical for SEO — it's what appears in search results.

Quick Fix
<head>
  <title>Your Page Title — Brand Name</title>
</head>
The title tag is the most important on-page SEO element. Keep it under 60 characters and include your primary keyword.
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.
No robots.txt filewarningSEO~5 min fix

Your site is missing a robots.txt file. This file tells search engines which pages to crawl. Create one at your site root.

Quick Fix
User-agent: *
Allow: /

Sitemap: https://yoursite.com/sitemap.xml
robots.txt tells search engines which pages to crawl. Place it at your site root (e.g., yoursite.com/robots.txt).
No sitemap.xml foundwarningSEO~15 min fix

Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.

Quick Fix
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yoursite.com/</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yoursite.com/about</loc>
    <lastmod>2026-03-15</lastmod>
    <priority>0.8</priority>
  </url>
</urlset>
A sitemap.xml helps search engines discover and index all your pages. Place it at your site root.
Skipped heading levelwarningAccessibility

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

Server response could be fasterwarningPerformance

Server responded in 1.5s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.

1 render-blocking scriptwarningPerformance

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

7 images without lazy loadingwarningPerformance

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

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.
HTML contains many commentsinfoPerformance

Found 19 HTML comments. Remove unnecessary comments in production to reduce file size.

Your Potential Score

57

Now

81

Estimated potential

+24 points estimated improvement from addressing 21 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+15Ahead
AI Readiness
Avg: 35+10Ahead
Performance
Avg: 55+22Ahead
Security
Avg: 40-40At risk
Accessibility
Avg: 68+19Ahead

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.

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

AI visibility preview

See which brands Perplexity surfaces for your category.

Recent scans on Foglift

Scan your own site free →