Google Labs scores B (89/100) for traditional SEO and A (96/100) for AI and answer-engine visibility, so the site is in strong shape overall. The lower SEO score is almost entirely driven by a weak Search Visibility category (62/100), pulled down by three foundational technical issues: a soft-404 misconfiguration, duplicate-host indexing, and a missing HTTP-to-HTTPS redirect. These gaps don't affect how AI tools read the site today, but they create crawling and duplicate-content risks that hold the SEO grade back.
Fix soft 404s so error pages return HTTP 404 status
SEO + AIOTo do
When we requested a deliberately non-existent URL, the server returned HTTP 200 instead of a proper 404 — meaning search engines may treat error pages as real, indexable content. This wastes crawl budget and can dilute the site's authority by surfacing meaningless pages in search indexes. Audit your server or CMS routing rules to ensure any URL that doesn't match a real page returns a true HTTP 404 (or 410 for permanently removed content); this typically helps search engines focus crawling on pages that matter.
I need help fixing an issue on my website labs.google.com.
My site is built with: [YOUR PLATFORM].
Issue found by an automated review: Fix soft 404s so error pages return HTTP 404 status
Details and evidence from the crawl: When we requested a deliberately non-existent URL, the server returned HTTP 200 instead of a proper 404 — meaning search engines may treat error pages as real, indexable content. This wastes crawl budget and can dilute the site's authority by surfacing meaningless pages in search indexes. Audit your server or CMS routing rules to ensure any URL that doesn't match a real page returns a true HTTP 404 (or 410 for permanently removed content); this typically helps search engines focus crawling on pages that matter.
Area: Search visibility — improves my SEO + AIO score.
Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
Add a discoverable Contact page linked from the homepage
SEO + AIOTo do
We found links to an About page and a Privacy page from the homepage, but no Contact page was detected. Search engines and AI answer engines use trust signals like About, Contact, and Privacy pages to assess site credibility, and a missing Contact link is a common reason authority scores plateau. Adding a Contact page and linking to it clearly from the main navigation or footer typically helps both user trust and quality assessments.
I need help fixing an issue on my website labs.google.com.
My site is built with: [YOUR PLATFORM].
Issue found by an automated review: Add a discoverable Contact page linked from the homepage
Details and evidence from the crawl: We found links to an About page and a Privacy page from the homepage, but no Contact page was detected. Search engines and AI answer engines use trust signals like About, Contact, and Privacy pages to assess site credibility, and a missing Contact link is a common reason authority scores plateau. Adding a Contact page and linking to it clearly from the main navigation or footer typically helps both user trust and quality assessments.
Area: Authority & trust — improves my SEO + AIO score.
Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
Redirect www or apex to one canonical host consistently
SEO + AIOTo do
Both the www (www.labs.google) and non-www (labs.google) versions of the site currently return HTTP 200 without redirecting to a single preferred host, which means search engines may index the same content under two different addresses. This creates a duplicate-content risk that can split ranking signals and confuse crawlers about which version to treat as authoritative. Choose one canonical host and configure a permanent 301 redirect from the other; this typically helps consolidate any link equity and prevents duplicate indexing.
I need help fixing an issue on my website labs.google.com.
My site is built with: [YOUR PLATFORM].
Issue found by an automated review: Redirect www or apex to one canonical host consistently
Details and evidence from the crawl: Both the www (www.labs.google) and non-www (labs.google) versions of the site currently return HTTP 200 without redirecting to a single preferred host, which means search engines may index the same content under two different addresses. This creates a duplicate-content risk that can split ranking signals and confuse crawlers about which version to treat as authoritative. Choose one canonical host and configure a permanent 301 redirect from the other; this typically helps consolidate any link equity and prevents duplicate indexing.
Area: Search visibility — improves my SEO + AIO score.
Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
Our test found that the http:// version of the site did not redirect to https://, leaving open the possibility that both the secure and insecure versions are crawled and indexed separately. Beyond the duplicate-content risk this shares with the canonical-host issue, serving any traffic over plain HTTP is a security concern that browsers and search engines flag negatively. Adding a server-level 301 redirect from http:// to https:// for all URLs typically helps unify signals and ensures visitors always land on the secure version.
I need help fixing an issue on my website labs.google.com.
My site is built with: [YOUR PLATFORM].
Issue found by an automated review: Redirect all HTTP traffic to HTTPS automatically
Details and evidence from the crawl: Our test found that the http:// version of the site did not redirect to https://, leaving open the possibility that both the secure and insecure versions are crawled and indexed separately. Beyond the duplicate-content risk this shares with the canonical-host issue, serving any traffic over plain HTTP is a security concern that browsers and search engines flag negatively. Adding a server-level 301 redirect from http:// to https:// for all URLs typically helps unify signals and ensures visitors always land on the secure version.
Area: Search visibility — improves my SEO + AIO score.
Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
Reduce homepage HTML size below 100 KB where possible
SEO + AIOTo do
The homepage HTML document weighs 285 KB before any images or scripts are loaded, which is well above the commonly recommended threshold of around 100 KB for a lean HTML payload. Large HTML documents slow initial parsing, can delay time-to-first-byte on slower connections, and may cause crawlers to truncate content before reaching important elements lower in the page. Review the markup for inline scripts, large inline SVGs, or redundant whitespace that could be moved to external files or minified to bring the document size down.
I need help fixing an issue on my website labs.google.com.
My site is built with: [YOUR PLATFORM].
Issue found by an automated review: Reduce homepage HTML size below 100 KB where possible
Details and evidence from the crawl: The homepage HTML document weighs 285 KB before any images or scripts are loaded, which is well above the commonly recommended threshold of around 100 KB for a lean HTML payload. Large HTML documents slow initial parsing, can delay time-to-first-byte on slower connections, and may cause crawlers to truncate content before reaching important elements lower in the page. Review the markup for inline scripts, large inline SVGs, or redundant whitespace that could be moved to external files or minified to bring the document size down.
Area: Speed & performance — improves my SEO + AIO score.
Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
An SEO consultant can act on crawl/indexing issues beyond a homepage review, including log-file analysis and index coverage in Google Search Console (free).
I need help fixing 5 issues on my website labs.google.com, found by an automated review. My site is built with: [YOUR PLATFORM].
1. Fix soft 404s so error pages return HTTP 404 status
Evidence: When we requested a deliberately non-existent URL, the server returned HTTP 200 instead of a proper 404 — meaning search engines may treat error pages as real, indexable content. This wastes crawl budget and can dilute the site's authority by surfacing meaningless pages in search indexes. Audit your server or CMS routing rules to ensure any URL that doesn't match a real page returns a true HTTP 404 (or 410 for permanently removed content); this typically helps search engines focus crawling on pages that matter.
Area: Search visibility — improves SEO + AIO.
2. Add a discoverable Contact page linked from the homepage
Evidence: We found links to an About page and a Privacy page from the homepage, but no Contact page was detected. Search engines and AI answer engines use trust signals like About, Contact, and Privacy pages to assess site credibility, and a missing Contact link is a common reason authority scores plateau. Adding a Contact page and linking to it clearly from the main navigation or footer typically helps both user trust and quality assessments.
Area: Authority & trust — improves SEO + AIO.
3. Redirect www or apex to one canonical host consistently
Evidence: Both the www (www.labs.google) and non-www (labs.google) versions of the site currently return HTTP 200 without redirecting to a single preferred host, which means search engines may index the same content under two different addresses. This creates a duplicate-content risk that can split ranking signals and confuse crawlers about which version to treat as authoritative. Choose one canonical host and configure a permanent 301 redirect from the other; this typically helps consolidate any link equity and prevents duplicate indexing.
Area: Search visibility — improves SEO + AIO.
4. Redirect all HTTP traffic to HTTPS automatically
Evidence: Our test found that the http:// version of the site did not redirect to https://, leaving open the possibility that both the secure and insecure versions are crawled and indexed separately. Beyond the duplicate-content risk this shares with the canonical-host issue, serving any traffic over plain HTTP is a security concern that browsers and search engines flag negatively. Adding a server-level 301 redirect from http:// to https:// for all URLs typically helps unify signals and ensures visitors always land on the secure version.
Area: Search visibility — improves SEO + AIO.
5. Reduce homepage HTML size below 100 KB where possible
Evidence: The homepage HTML document weighs 285 KB before any images or scripts are loaded, which is well above the commonly recommended threshold of around 100 KB for a lean HTML payload. Large HTML documents slow initial parsing, can delay time-to-first-byte on slower connections, and may cause crawlers to truncate content before reaching important elements lower in the page. Review the markup for inline scripts, large inline SVGs, or redundant whitespace that could be moved to external files or minified to bring the document size down.
Area: Speed & performance — improves SEO + AIO.
Work through them one at a time, in order. For each: Please: 1) briefly explain what needs to change for my specific platform, 2) give me the exact code or settings changes to make, 3) tell me exactly where to put them, and 4) list what I should double-check after publishing. Keep the changes minimal and safe, and don't touch unrelated code.
Media queries detected in the delivered HTML/linked styles.
構造化データとソーシャル に加算されます SEO + AIO
i
Structured data (JSON-LD)
Not scored: this domain ranks #1 globally (Tranco). At this prominence, discovery aids do not limit visibility, and top platforms are JavaScript applications whose no-JS fallback shell is what a static crawl sees. Measured on that shell anyway: No valid JSON-LD structured data on the homepage.
i
Identity schema (Organization/WebSite)
Not scored: this domain ranks #1 globally (Tranco). At this prominence, discovery aids do not limit visibility, and top platforms are JavaScript applications whose no-JS fallback shell is what a static crawl sees. Measured on that shell anyway: No Organization/WebSite-type schema found.
No AI/answer-engine crawlers are blocked in robots.txt (checked: GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, CCBot).
✓
llms.txt
/llms.txt present.
i
Q&A / HowTo schema
Not scored: this domain ranks #1 globally (Tranco). At this prominence, discovery aids do not limit visibility, and top platforms are JavaScript applications whose no-JS fallback shell is what a static crawl sees. Measured on that shell anyway: No FAQPage/QAPage/HowTo schema — answer engines favor explicitly structured questions and answers.
✓
Clear content sections (H2s)
22 H2 section heading(s) on the homepage.
✓
Direct opening summary
First paragraph is 30 words. “Discover our latest experiments and help shape the future of AI technology. Get early access, share …”
i
RSS/Atom feed
Not scored: this domain ranks #1 globally (Tranco). At this prominence, discovery aids do not limit visibility, and top platforms are JavaScript applications whose no-JS fallback shell is what a static crawl sees. Measured on that shell anyway: No RSS/Atom feed link.
i
Freshness signals
Not scored: this domain ranks #1 globally (Tranco). At this prominence, discovery aids do not limit visibility, and top platforms are JavaScript applications whose no-JS fallback shell is what a static crawl sees. Measured on that shell anyway: No Last-Modified header, dated <time> elements, or recent year visible — assistants prefer content they can date.
ローカル検索 に加算されます SEO
–
Local-business signals
No phone number, street address or map found — this category is excluded from the grade. If you serve a local area, adding these matters a lot; if you're not a local business, it doesn't apply.
権威性・信頼性 に加算されます SEO + AIO
✓
Global popularity rank
Ranked #1 of the ~1M most-visited domains worldwide (Tranco research list — aggregated from major traffic datasets). Prominence like this is the strongest visibility signal there is.
✓
Domain age
Registered 2023-04-11 (3.4 years ago) per the public RDAP registry record.
!
About / Contact / Privacy discoverable
Linked from homepage: about, privacy.
✓
Social profiles linked
Profiles linked: x.com
–
Backlink profile
Not measured: external backlink counts and domain-authority scores require commercial link-index data this tool does not query. Treat any tool that shows them 'free' with care — ask where the numbers come from.
アクセシビリティ に加算されます SEO + AIO
✓
Page language declared
<html lang="en">
✓
Image alt text
20 of 24 images have alt text (83%).
–
Form fields labelled
No visible form fields on the homepage.
✓
Links have accessible names
All links have text or accessible names.
クロール情報: TTFB 28 ms · 285 KB HTML · HTTP/2 · 1 redirect(s) · 弊社サーバーより計測（基準日時： 2026-09-02T13:39:10+00:00.