www.gnu.org — 69 needs work
Scanned at 2026-11-14T23:59:07.430Z · Source: LumeLogix live scan
Pillars
- AI readiness: 76
- Technical SEO: 88
- Local SEO: n/a
Top issues
1. AIR-005 — Organization or LocalBusiness entity markup
Applies to the whole site
Found: No Organization or LocalBusiness schema found
Entity markup states who you are, which helps search and AI systems tie mentions to your business.
Fix: Add Organization or LocalBusiness JSON-LD to the homepage with your business name, URL, logo and phone.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Your Business Name", "url": "https://example.com/", "logo": "https://example.com/logo.png", "telephone": "+1-555-555-0100" } </script>2. AIR-110 — Search and answer crawlers are not refused by the server
Applies to the whole site
Found: OAI-SearchBot: HTTP 429 (test request from the LumeLogix scanner); PerplexityBot: HTTP 429 (test request from the LumeLogix scanner); Claude-SearchBot: HTTP 429 (test request from the LumeLogix scanner)
A firewall or bot-protection rule can refuse a crawler even when robots.txt allows it. robots.txt checks alone miss this.
Fix: Stop your firewall, CDN or bot protection from returning 403/429 to search and AI answer crawlers. Allowlist their published user agents and IP ranges.
3. ROB-003 — robots.txt does not block CSS/JS needed for rendering
Applies to the whole site
Found: https://www.gnu.org/server/banners/fundraiser.css
Google renders pages; blocked CSS/JS can hide content and break mobile evaluation.
Fix: Allow crawlers to fetch the CSS and JavaScript files your pages need to render. Remove Disallow rules for theme, plugin and asset folders.
User-agent: * Allow: /wp-content/ Allow: /wp-includes/ Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php
4. SD-001 — Organization or LocalBusiness schema present
Applies to the whole site
Found: No Organization or LocalBusiness schema found
Schema.org entity markup tells search engines who you are, which helps with knowledge panels and AI answers.
Fix: Add Organization or LocalBusiness JSON-LD to the homepage.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Your Business Name", "url": "https://example.com/", "telephone": "+1-555-555-0100", "address": { "@type": "PostalAddress", "streetAddress": "123 Main St", "addressLocality": "Phoenix", "addressRegion": "AZ", "postalCode": "85016", "addressCountry": "US" } } </script>5. CAN-001 — All 4 host/protocol variants resolve to one preferred URL
Page: https://gnu.org/
Found: https://gnu.org/ -> 200 https://www.gnu.org/; https://www.gnu.org/ -> 200 https://www.gnu.org/; http://gnu.org/ -> 200 http://www.gnu.org/
If http/https and www/non-www each serve a page, Google may index duplicates and split signals.
Fix: Redirect all four variants (http, https, www, non-www) with a 301 to your one preferred URL.
# nginx: send every variant to https://example.com server { listen 80; server_name example.com www.example.com; return 301 https://example.com$request_uri; }
11 more findings are available in a full audit.
This free report shows the top 5 findings only.