www.waikatoregion.govt.nz — Website Report

Scored 48/100 · Scanned with Foglift

OverallⓘOverall Score — weighted average of all category scores

Fixing "AI engines can't understand your business" would move waikatoregion.govt.nz from 48 to 68.

7 critical11 warnings27 total issues

Quick wins

~173 min total fix time

1Missing language attribute~1m

2Missing HSTS header~2m

3Missing X-Content-Type-Options header~2m

https://www.waikatoregion.govt.nz/council/ · 4/28/2026, 3:54:41 AM

Scanned with Foglift · SEO + AI Visibility analysis

AI Action Plan

Website Analysis for https://www.waikatoregion.govt.nz/council/ Your site scores 48/100 overall, but AI engines may be missing you. Your AI Visibility is 65/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 7 critical issues and 11 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. Missing page title — Your page has no <title> tag. This is critical for SEO — it's what appears in search results. 5. Missing meta description — No meta description found. Search engines use this as the snippet in results. Add one for better CTR. 6. Missing H1 heading — Every page shoul

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

How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand

65D

Technical30

Authority78

Unlock full 6-tier AI Visibility Ladder →

Brand Mentions

Found 11+ web mentions of "waikatoregion"

Domain Authority

PageRank: 4.0/10, 20+ external references

Content Freshness

22 of 22 pages updated in the last 30 days

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

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.

Page content is too thin for AIwarning

Your page has very few headings and paragraphs. AI assistants need well-organized, text-rich content to understand and recommend your site. Add clear headings, descriptive paragraphs, and detailed information about your offerings.

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.

Content is hard for AI to scaninfo

Your page relies on plain text without lists, tables, or comparison charts. AI assistants extract and cite structured content (bullet points, comparison tables, step-by-step lists) far more accurately than long paragraphs.

How does AI see Waikatoregion?

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

See how ChatGPT, Claude, Perplexity, and Gemini talk about Waikatoregion

Monitor AI Visibility — 7 Days Free

SEO & Technical Issues (22)

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 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 H1 headingcriticalSEO~3 min fix

Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility.

Quick Fix

<h1>Your Main Page Heading</h1>
<!-- Only use one H1 per page. Make it descriptive and include your target keyword. -->

Every page needs exactly one H1 that describes the main topic. It's a key SEO signal.

Page is set to noindexcriticalSEO

This page has a noindex robots meta tag. Search engines will not index this page. Remove it if you want this page to appear in search results.

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.

No H2 subheadingswarningSEO

Add H2 subheadings to organize your content. Good heading hierarchy helps search engines understand your page structure.

Server response could be fasterwarningPerformance

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

No favicon detectedinfoSEO~10 min fix

Add a favicon so your site has an icon in browser tabs, bookmarks, and search results.

Quick Fix

<!-- Add to <head> — SVG favicon (modern browsers) + PNG fallback -->
<link rel="icon" type="image/svg+xml" href="/favicon.svg">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">

Favicons appear in browser tabs, bookmarks, and search results. They build brand recognition.

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.

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

Your Potential Score

Now

Potential

+8 points possible by fixing 27 issues

That moves you from F to D — 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-56At risk

AI Readiness

Avg: 35+21Ahead

Performance

Avg: 55+35Ahead

Security

Avg: 40-40At risk

Accessibility

Avg: 68+9On 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.

Not AI-ready — ChatGPT, Perplexity, and Google AI Overviews likely cannot cite your site. You're invisible to the fastest-growing search channel.

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.

Compare with a Competitor Rescan After Fixing

Recent scans on Foglift

59makeonlinecourse.com 59jhonrtmls.github.io 59jhonrtmls.github.io 82mangools.com 59jhonrtmls.github.io

Scan your own site free →