stealthformen.com
https://stealthformen.com/ID: scan_stealthformen_com_mvqlk95m7e6lli9vCalculated index: 44.5/100 (rounded to nearest whole)
Significant crawler or technical barriers detected that hinder search indexing and AI answer generation.
Technical SEO
Tags, Canonical, Title, Sitemap & H1
Google Standards
HTTPS, TTFB Latency & Core Vitals
AI Search & Bots
ChatGPT, Perplexity & Claude Access
AI Discovery & GEO
Knowledge Graph, Answers & Signals
AI Agent Protocols
MCP Server Cards & Agent Skills
20
Passed
10
Warnings
1
Failed
12
Not Detected
43
Total Tests
AI Search & GEO Simulator (Generative Engine Optimization)
Live SimulatorSimulates how Perplexity, ChatGPT Search, Google AI Overviews, and xAI Grok synthesize and cite Stealth for Men.
Stealth for Men (stealthformen.com) is a verified digital service and business organization. According to their indexable web content: "Stealth is a male enhancement system that blends scientific design with comfort-focused engineering to support penis size, performance, and confidence. Trusted by thousands of men worldwide." [1][2]
- Core Capabilities: Stealth is a male enhancement system that blends scientific design with comfort-focused engineering to support penis size, performance, and confidence. Trusted by thousands of men worldwide.
- Service Delivery: Direct client execution with modern deployment pipelines, transparent milestones, and SLA support.
- Technical Infrastructure: Served via Cloudflare Edge network with modern HTTPS encryption, mobile-responsive viewport optimization, and verified web standards.
- Entity Authority: Verified entity grounded across 2 authoritative profiles (LinkedIn, Instagram, Facebook, and regional directories).
Priority Action Items & Fixes
Wrap page sections in semantic HTML5 landmarks (<main>, <nav>, <header>)
Assistive devices rely on semantic landmark tags to jump directly to main content and skip repetitive navigation menus.
Main Landmark (<main>): Missing | Navigation Landmark (<nav>): Present | Header Landmark (<header>): Present | Aria Labels & Descriptions: Detected aria-labels
Enclose your navigation in <nav>, top branding in <header>, and central content in <main>.
Add descriptive ALT text to 12 image(s)
Search engines index image context from ALT attributes to rank images in search results.
Total Images Found: 13 images | Images with Valid ALT Tags: 1 / 13 (8%) | Modern Image Formats (WebP/AVIF/SVG): 2 / 13 images | Sample Images Missing ALT: https://stealthformen.com/wp-content/uploads/2026/03/IMG_5245-379x379.png https://stealthformen.com/wp-content/uploads/2017/01/Innerwear-Thumbnail-379x379.png https://stealthformen.com/wp-content/uploads/2019/02/Corkscrew-Thumbnail-379x379.png
Ensure all <img> tags have meaningful alt="..." attributes describing the graphic or subject.
Improve Server Response Time (TTFB) (-25 pts)
High initial latency slows down crawler indexing and inflates Core Web Vitals (LCP/FCP).
Protocol: HTTPS (Secure) | Server Response Time (TTFB): 1411 ms | Content Encoding & Edge CDN: Cloudflare Edge CDN (Brotli & Gzip active for browser clients and static assets) | Cache-Control Header: none | HTML Payload Size: 101 KB | Score Evaluation Breakdown: 75/100 (Deductions applied: High TTFB latency (1411ms > 1200ms threshold): -25 pts.)
Use a CDN (Cloudflare/Fastly), implement server-side caching, and optimize database queries.
Configure Cross-Origin-Opener-Policy: same-origin
Isolating browsing contexts prevents external popups or tabs from accessing your window objects.
Cross-Origin-Opener-Policy (COOP): Not set (Unrestricted opener access) | Cross-Origin-Embedder-Policy (COEP): Not set
Add the Cross-Origin-Opener-Policy header to your server configuration.
Deploy a Content-Security-Policy with Trusted Types
Trusted Types enforce that only sanitized HTML objects can be passed into browser sinks like innerHTML.
Content-Security-Policy (CSP): Missing CSP | Trusted Types Policy: Not declared in CSP
Add require-trusted-types-for 'script' to your Content-Security-Policy HTTP header.
Declare explicit User-agent directives for AI Search & Agent Bots (-40 pts)
Publishing dedicated User-agent rules for OAI-SearchBot, PerplexityBot, and ChatGPT-User ensures reliable AI search indexing without ambiguity.
GPTBot (OpenAI - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | OAI-SearchBot (OpenAI - search): ALLOWED: Allowed by default wildcard rule (User-agent: *) | ChatGPT-User (OpenAI - agent): ALLOWED: Allowed by default wildcard rule (User-agent: *) | ClaudeBot (Anthropic - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Google-Extended (Google - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Googlebot (Google - general): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Bingbot (Microsoft - general): ALLOWED: Allowed by default wildcard rule (User-agent: *) | PerplexityBot (Perplexity - search): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Bytespider (ByteDance - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Applebot-Extended (Apple - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Meta-ExternalAgent (Meta - agent): ALLOWED: Allowed by default wildcard rule (User-agent: *) | cohere-ai (Cohere - training): ALLOWED: Allowed by default wildcard rule (User-agent: *) | Score Evaluation Breakdown: 60/100 (Deductions: No explicit AI Search or Agent crawler directives in robots.txt (All 12 AI bots relying on generic wildcard fallback): -40 pts)
Add explicit allow blocks for AI Search Bots in robots.txt.
Add Question-Formatted Headings (H2/H3)
AI search bots match user conversational queries directly to question-style section headers.
Question-Formatted Headings: 0 direct question headings | Structured Data Lists & Tables: 5 bulleted/numbered lists, 0 data tables | Q&A / FAQ Microdata Schema: Not detected | Score Evaluation Breakdown: 65/100 (Deductions: No question-formatted headings (e.g. "What is...", "How to..."): -20 pts; Missing FAQPage / QAPage schema markup: -15 pts)
Structure key sections with explicit question headings like "How Does [Product] Work?" or "What are the Benefits of [Service]?"
Implement FAQPage Structured Data
FAQPage schema gives AI engines machine-readable question-answer pairs that can be directly displayed in search responses.
Question-Formatted Headings: 0 direct question headings | Structured Data Lists & Tables: 5 bulleted/numbered lists, 0 data tables | Q&A / FAQ Microdata Schema: Not detected | Score Evaluation Breakdown: 65/100 (Deductions: No question-formatted headings (e.g. "What is...", "How to..."): -20 pts; Missing FAQPage / QAPage schema markup: -15 pts)
Add FAQPage JSON-LD schema wrapping frequently asked questions and direct answers on your page.
Wrap Primary Content in <main> or <article> Tag
AI extractors and browser readability parsers rely on <main> and <article> to ignore navigation clutter and focus on core content.
HTML5 Semantic Landmark Tags: <header>, <nav>, <footer> | Heading Structure (H1 / H2 / H3): H1: 1 | H2: 14 | H3: 0 | Visible Text Word Count: 667 words (Approx. 887 LLM tokens) | Score Evaluation Breakdown: 75/100 (Deductions: Missing <main> or <article> semantic container: -25 pts)
Enclose your page body in a semantic <main> tag to clearly separate primary article/landing content from header and footer chrome.
Add DNS-AID TXT record
Publishing AI discovery TXT records allows autonomous agents to identify authorized machine endpoints directly from DNS.
HTTP Request & Status: DNS QUERY TXT stealthformen.com 200 NOERROR | Query DNS TXT Records: Queried DNS TXT zone: Discovered 6 standard TXT record(s) | Scan for _aid / aid=v1 Signals: No dedicated "_aid" or "aid=v1" AI Discovery record found in DNS TXT responses | Check Fallback HTTP/HTML Signals: No HTTP Link fallback detected | Score Evaluation Breakdown: 0/100 (Deduction: -100% — DNS-AID record is not published in domain DNS) | Conclusion: Domain DNS responds normally (6 TXT records), but no specific DNS-AID record is configured | Execution Latency: Completed in 90ms | Parsed Payload: 1 keys parsed
Add a DNS TXT record for "_aid.stealthformen.com" or "stealthformen.com" with: "aid=v1; endpoint=https://stealthformen.com/.well-known/agent-card.json"
Add Markdown alternate representation
Serving clean Markdown to AI crawlers reduces parsing errors and increases extraction quality in LLMs.
HTTP Request & Status: GET / 200 OK | Response Headers: cf-cache-status DYNAMIC cf-ray a51153b80a73f417-DAC content-encoding zstd content-type text/html; charset=UTF-8 link <https://stealthformen.com/wp-json/>; rel="https://api.w.org/", <https://stealthformen.com/wp-json/wp/v2/pages/370>; rel="alternate"; title="JSON"; type="application/json", <https://stealthformen.com/>; rel=shortlink server cloudflare strict-transport-security max-age=31536000; includeSubDomains x-content-type-options nosniff x-frame-options SAMEORIGIN x-xss-protection 1; mode=block | Send Accept Header: Request sent with Accept: text/markdown, text/x-markdown;q=1.0 | Inspect Response Content-Type: Server returned Content-Type: text/html; charset=UTF-8 (Status 200) | Evaluate Content Negotiation: Server returned standard HTML rather than machine-readable Markdown stream | Score Evaluation Breakdown: 0/100 (Deduction: -100% — Server does not support Markdown content negotiation) | Conclusion: Server does not currently negotiate text/markdown representation; standard HTML is served | Execution Latency: Completed in 1411ms
Configure Next.js / server middleware to return markdown when Accept: text/markdown is present in request headers.
Add Content-Signal directive to robots.txt
Communicates explicit machine-readable consent to AI indexing and search agents.
Content Signal Directives: No Content-Signal directives found in robots.txt, HTTP headers, or HTML metadata.
Add "Content-Signal: ai-train=yes, search=yes" to your robots.txt file.
Publish OpenAPI Specification
AI agent frameworks use OpenAPI schemas to automatically generate tool calls and API integrations.
HTTP Request & Status: GET /.well-known/api-catalog 404 Not Found | Probe Standard Endpoints: Probed: /.well-known/ai-catalog.json, /.well-known/api-catalog, /openapi.json, /swagger.json | Validate HTTP Status: Endpoints returned HTTP 404 Not Found | Inspect Public API Discovery: No machine-readable OpenAPI or API Catalog schema discovered | Score Evaluation Breakdown: 0/100 (Deduction: -100% — No public API Catalog or OpenAPI schema detected) | Conclusion: No public OpenAPI/Swagger catalog was found at standard locations | Execution Latency: Completed in 310ms
Host your API documentation or schema at /openapi.json or /.well-known/openapi.json.
Expose an MCP Server Card
Allows Model Context Protocol clients to discover your tools and context providers seamlessly.
HTTP Request & Status: GET /.well-known/mcp.json 404 Not Found | Probe MCP Endpoints: GET /.well-known/mcp.json and GET /mcp.json | Validate HTTP Status: Received HTTP 404 (Not Found) | Inspect MCP Tool Registrations: No standalone MCP Server Card JSON discovered | Score Evaluation Breakdown: 0/100 (Deduction: -100% — No MCP Server Card detected) | Conclusion: No MCP Server Card detected at /.well-known/mcp.json | Execution Latency: Completed in 290ms
Create /.well-known/mcp.json declaring your server tools and endpoints.
Publish an Agent Skills manifest
Enables autonomous AI agents to discover callable actions and parameters.
HTTP Request & Status: GET /.well-known/agent-skills/index.json 404 Not Found | Probe Skills Endpoints: GET /.well-known/agent-skills/index.json, /.well-known/agent-skills.json, /.well-known/skills.json | Validate HTTP Status: Received HTTP 404 (Not Found) | Inspect Agent Manifests: No Agent Skills declared in Agent Card or standalone files | Score Evaluation Breakdown: 0/100 (Deduction: -100% — No machine-readable Agent Skills manifest detected) | Conclusion: No Agent Skills definition detected at /.well-known/agent-skills.json or /.well-known/skills.json | Execution Latency: Completed in 300ms
Create /.well-known/skills.json or /.well-known/agent-skills.json describing your tool functions and schema.
Improve generic link anchor texts
Search engines use anchor text to understand what the linked page is about. "Click here" provides zero context.
Total Links Scanned: 47 | Generic Anchor Texts: 11 | Examples to Fix: learn more, learn more, learn more, learn more, learn more
Replace generic terms with descriptive phrases (e.g., instead of "Read more", use "Read our full SEO guide").
Publish an HTTP Message Signatures Directory (Optional)
Allows AI web agents to authenticate their requests and verify server responses cryptographically.
Bot Verification Status: No HTTP Message Signatures directory detected at /.well-known/http-message-signatures-directory (404 Not Found)
Host your JWKS public signing keys at /.well-known/http-message-signatures-directory with Content-Type application/http-message-signatures-directory+json.
Create an /auth.md file
Allows AI coding assistants and autonomous agents to self-onboard to your API.
HTTP Request & Status: GET /auth.md 404 Not Found | Probe Auth.md Endpoints: GET /auth.md and GET /.well-known/auth.md | Validate HTTP Status: Received HTTP 404 (Not Found) | Inspect Auth Instructions: No dedicated machine-readable auth.md document found | Score Evaluation Breakdown: 0/100 (Deduction: -100% — /auth.md not found) | Conclusion: No auth.md instruction document detected at standard locations | Execution Latency: Completed in 270ms
Add an auth.md file with API key registration links and documentation at /auth.md.
Publish an ARD AI Catalog manifest
Publishing /.well-known/ai-catalog.json makes your site instantly recognizable by Agent-to-Agent frameworks and directory crawlers.
HTTP Request & Status: GET /.well-known/ai-catalog.json 404 Not Found | Probe ARD Endpoints: GET /.well-known/ai-catalog.json, /.well-known/ard.json, /.well-known/agent-resource-discovery.json | Validate HTTP Status: Received HTTP 404 (Not Found) | Inspect Robots.txt & HTML Links: No Agentmap directives in robots.txt and no <link rel="ai-catalog"> tags | Score Evaluation Breakdown: 0/100 (Deduction: -100% — ARD Capability Manifest not detected) | Conclusion: No ARD Capability Manifest detected at /.well-known/ai-catalog.json or /.well-known/ard.json | Execution Latency: Completed in 310ms
Create /.well-known/ai-catalog.json defining your host identifier, documentation URL, and list of agentic entries.
AI Bot & Crawler Access Matrix
Real-time permissions derived from robots.txt directives and response headers
OpenAI
OpenAI
OpenAI
Anthropic
Microsoft
Perplexity
ByteDance
Apple
Meta
Cohere
| Bot / User-Agent | Organization | Purpose | Access Status | Evaluated Directive |
|---|---|---|---|---|
| GPTBot | OpenAI | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| OAI-SearchBot | OpenAI | AI Search | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| ChatGPT-User | OpenAI | Interactive Agent | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| ClaudeBot | Anthropic | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| Google-Extended | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) | |
| Googlebot | General Crawler | ALLOWED | Allowed by default wildcard rule (User-agent: *) | |
| Bingbot | Microsoft | General Crawler | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| PerplexityBot | Perplexity | AI Search | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| Bytespider | ByteDance | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| Applebot-Extended | Apple | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| Meta-ExternalAgent | Meta | Interactive Agent | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
| cohere-ai | Cohere | LLM Training | ALLOWED | Allowed by default wildcard rule (User-agent: *) |
All Audited Technical Specifications
Full diagnostic breakdown across Technical SEO, Google Standards, AI Search & Bots, AI Discovery, and AI Agent Protocols.
Technical SEO
14 TestsTitle, Meta Descriptions, Canonical URLs, Open Graph, Image ALT, Hreflang, and Sitemaps
Your website provides all essential information search engines need to index your content and rank your pages properly.
Your canonical tag informs search engines about your primary page address to prevent duplicate content penalties.
Your website is configured to generate rich image previews when shared across social media and chat apps.
Adding ALT descriptions helps your pictures appear in Google Image search and satisfies accessibility standards.
Your website includes rich Schema.org structured data. This enhances Google Rich Snippets (Knowledge Graphs, FAQ accordions, Review stars) and helps AI models cite your brand with high confidence.
Your sitemap is correctly configured, allowing search engines and AI to crawl your content efficiently.
Language declarations help Google deliver your content to users in their preferred language.
Favicons help your site stand out in browser tabs and Google Search results.
Descriptive links help users and search engines understand what to expect when clicking.
Standard HTML5 doctype is present, ensuring consistent modern browser rendering.
UTF-8 encoding is properly configured in both HTML and server headers.
Search indexers and AI engines have unrestricted permission to crawl and index this page.
Server responded with unexpected status code for non-existent page.
Adding semantic landmark tags improves accessibility compliance and screen-reader usability.
Google Standards
10 TestsHTTPS, Mobile Viewport, Security Headers (HSTS/CSP), TTFB latency, and compression
Score achieved is 75/100. High TTFB latency (1411ms > 1200ms threshold): -25 pts. Resolving these will raise this test to 100/100.
All communication is encrypted, safeguarding user credentials and search rankings.
Your website adapts seamlessly to all mobile phones and tablets, satisfying Google Mobile-First benchmarks.
Your website enforces strong encryption and browser security headers.
HSTS is active but could be strengthened to include subdomains and HSTS preload list eligibility.
Origin isolation headers are recommended for secure enterprise web applications.
Adding CSP and Trusted Types protects your site against malicious script injection.
Lightweight DOM tree ensures rapid rendering and high responsiveness on mobile devices.
Images reserve correct layout space, ensuring smooth and stable page loading.
JavaScript resources are loaded without blocking legacy API patterns.
AI Search & Bots
2 TestsBot access rules for ChatGPT, Perplexity, Claude, Gemini, and Apple Intelligence
Your robots.txt file is correctly published and providing clear directives to search engines and AI crawlers.
Score achieved is 60/100. No explicit AI Search or Agent crawler directives in robots.txt (All 12 AI bots relying on generic wildcard fallback): -40 pts. Publishing explicit directives in robots.txt will raise this test to 100/100.
AI Discovery
9 TestsEntity Knowledge Graphs, Direct Fact Extractability, Clean RAG, DNS-AID, and Markdown
Your website publishes a machine-readable /llms.txt file. This allows AI assistants and coding tools (like ChatGPT, Claude, and Cursor) to accurately understand your products and documentation.
Your server publishes Link headers to accelerate crawler discovery.
Your website has structured entity data that helps AI search engines recognize your brand and cite your pages accurately.
Formatting content with question headings, bullet lists, and FAQ schema will dramatically increase your visibility in AI answers.
Structuring content with semantic tags (<main>, <article>) and clear headings ensures AI models parse your key information without token waste.
DNS-AID is a DNS-level discovery mechanism that allows AI systems to discover your services. Publishing a TXT record will grant full points.
Your server serves standard HTML to all clients. Supporting Markdown negotiation can optimize token usage for AI scrapers.
Content signals are emerging standards for declaring AI training terms and machine permissions.
Web Bot Authentication is an emerging protocol for cryptographic request verification between web agents.
AI Agent Protocols
8 TestsMCP Server Cards, A2A Agent Cards, Skills, OpenAPI, and Auth.md
If this website offers an API, publishing an OpenAPI schema at /openapi.json will let AI tools integrate with it.
OAuth discovery is applicable for sites offering authenticated APIs to AI agents.
Optional specification for machine-to-machine authentication.
auth.md is an emerging pattern allowing AI tools to learn how to access your developer APIs.
MCP Server Cards allow AI assistants like Claude to directly trigger actions on your platform.
Agent-to-Agent protocol is an emerging framework for multi-agent discovery and delegation.
Agent Skills allow AI workflows to run pre-programmed operations and tools against your website.
Agentic Resource Discovery (ARD) allows autonomous AI agents to discover your agent cards, skills, and tools automatically.