Website report
Visit sitehttps://www.flywingmen.com/
Finds the signals, starts the conversation, books the meeting. $69 per seat, Concierge from $999.
Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Cloudflare
Analysed Nov 7, 2026 · 15 categories · 112 passed · 15 warnings · 2 issues · 21 informational
Audit score
C78/100
Mixed
- Agentic
- 74
- SEO
- 85
What we found
2Needs a fix15Could be better112Looks good21Informational- 1.Needs a fix: llms.txt follows the spec: needs fixing. see checkClear, accessible information helps AI assistants understand and cite your website.
- 2.Could be better: Semantic HTML structure: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
- 3.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
- 4.Could be better: Your images use older file formats. see checkEfficient image formats reduce download size.
- 5.Could be better: ARIA references point to source elements: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
Built with 1 technology· detected stack
Read from the public source and response headers of the sampled pages.
CloudflareCDN / edge
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata11Looks good
100/100Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Wingmen: know who's buying this week"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 36 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "Wingmen: know who's buying this week" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Finds the signals, starts the conversation, books the meeting. $69 per seat, Concierge fro…"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 97 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 9 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 10 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. Most specific matching path; allow wins equal-length conflicts.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://www.flywingmen.com/sitemap.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 32 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://www.flywingmen.com/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (www.flywingmen.com).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (22 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content10Looks good1Informational
100/100Not measured: ReadabilityFlesch reading ease ≈ 61.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 61.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 1731 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 1731 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Text-to-HTML ratio
Looks good · Content · Measured on your page
Observed evidence
Text-to-HTML ratio is 11.1%.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Title and H1 agree
Looks good · Content · Measured on your page
Observed evidence
Title and H1 share topic words: know, who, buying, thi.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 8 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
11 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 9 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured data5Looks good
100/100Looks good: JSON-LD present
Looks good · Structured data · Measured on your page
Observed evidence
2 JSON-LD block(s) found on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: JSON-LD parses
Looks good · Structured data · Measured on your page
Observed evidence
All 17 JSON-LD block(s) parse cleanly.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Organization or WebSite schema
Looks good · Structured data · Measured on your page
Observed evidence
Identity schema present: ProfessionalService, WebSite, Organization.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content-specific schema
Looks good · Structured data · Measured on your page
Observed evidence
Content schema found: Offer, FAQPage, ItemList, CollectionPage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Headings7Looks good
100/100Looks good: H1 exists
Looks good · Headings · Measured on your page
Observed evidence
H1 found: "Know who's buying this week. Be the first to reach them."
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Single H1
Looks good · Headings · Measured on your page
Observed evidence
Exactly one H1 on the homepage.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 17 headings.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: H1 has real text
Looks good · Headings · Measured on your page
Observed evidence
H1 reads "Know who's buying this week. Be the first to reach them.".
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
17 headings, averaging 6.3 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
10 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Element IDs are unique per document
Looks good · Headings · Measured on your page
Observed evidence
All inspected element IDs are unique within their documents.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images1Could be better3Looks good
84/100Could be better: Modern image formats14 of 15 raster images are served only as PNG or JPEG: DR.jpg, ML.jpg, PS.jpg, ….
Could be better · Images · Review suggested
Observed evidence
14 of 15 raster images are served only as PNG or JPEG: DR.jpg, ML.jpg, PS.jpg, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 15 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Width/height attributes
Looks good · Images · Measured on your page
Observed evidence
All 15 visible images declare dimensions or are sized by their container.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Lazy loading
Looks good · Images · Measured on your page
Observed evidence
15/15 images are lazy-loaded.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links6Looks good
100/100Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Anchor text is meaningful
Looks good · Links · Measured on your page
Observed evidence
42 of 42 links have descriptive text or labels.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: External links use rel=noopener
Looks good · Links · Measured on your page
Observed evidence
All target="_blank" links carry rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 24 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
4 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile2Could be better2Looks good2Informational
69/100Could be better: Interactive controls have source labels5 of 422 source controls lack a detectable name.
Could be better · Mobile · Measured on your page
Observed evidence
5 of 422 source controls lack a detectable name.
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.
Affected pages (2)
- https://www.flywingmen.com/pricing
- https://www.flywingmen.com/playbook
Could be better: ARIA references point to source elementsARIA references point at IDs that do not exist on 1 sampled page(s), e.g.
Could be better · Mobile · Measured on your page
Observed evidence
ARIA references point at IDs that do not exist on 1 sampled page(s), e.g. aria-controls="radix-:R9p:-content-all", aria-controls="radix-:R9p:-content-guide", aria-controls="radix-:R9p:-content-case-study".
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Connect ARIA references to unique existing IDs. If JavaScript adds the targets, verify the rendered accessibility tree.
Affected pages (1)
- https://www.flywingmen.com/resources
Not applicable: Responsive image markupNone of the 20 images use srcset.
Not applicable · Mobile · Measured on your page
Observed evidence
None of the 20 images use srcset.
Why this matters
Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.
Recommended fix
Serve smaller variants to phones with srcset/sizes (next/image handles this) — mobile users shouldn't download desktop-sized images.
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1.0".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (/favicon.svg).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 243 ms | Looks good: goodThe audit received response headers after 243 ms from one test location. |
| HTML payload size | 108 KB | Looks good: goodThe page's HTML is 108 KB uncompressed: acceptable, though under 100 KB is a good target for content pages. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 0.0 KB | Looks good: goodInline styles total 0.0 KB. |
| Script/stylesheet count | — | Looks good: good4 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Iframe usage | — | Looks good: goodNo iframes. |
| Source HTML weight | 108.2 KB | Informational: measured source, not transferred bytes108.2 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: Content Security PolicyA CSP is present but its script or object restrictions need review.
Could be better · Security · Review suggested
Observed evidence
A CSP is present but its script or object restrictions need review.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.
Recommended fix
Restrict script origins, use nonces or hashes for inline scripts, avoid unsafe evaluation, and set object-src 'none'.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=31536000; includeSubDomains.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Frame embedding protection
Looks good · Security · Measured on your page
Observed evidence
Response headers restrict cross-origin framing (frame-ancestors 'none').
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
Referrer-Policy is strict-origin-when-cross-origin.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Browser feature permissions
Looks good · Security · Measured on your page
Observed evidence
A Permissions-Policy disables at least one sensitive browser feature.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Review remaining features and allow only origins the application needs.
Looks good: X-Content-Type-Options
Looks good · Security · Measured on your page
Observed evidence
nosniff is set.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Server technology disclosure
Looks good · Security · Measured on your page
Observed evidence
No X-Powered-By disclosure.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
3 declared form(s) submit over HTTPS to this site. Runtime submission behavior is untested.
Why this matters
HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Needs a fix: llms.txt follows the specllms.txt is missing markdown links in the form [name](url).
Needs a fix · AI answer readiness · Published platform rule
Observed evidence
llms.txt is missing markdown links in the form [name](url).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. Right now the sampled pages don't provide it.
Recommended fix
Follow the published structure: a single H1, a blockquote summary, then H2 sections whose lists use [name](url): short note. Parsers read the H1 and the link lists.
Could be better: Semantic HTML structureSemantic landmarks exist (16) but there's no <main> or role="main".
Could be better · AI answer readiness · Review suggested
Observed evidence
Semantic landmarks exist (16) but there's no <main> or role="main".
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Wrap the primary content in one <main>. Readers, screen readers and content extractors use it to find the substance and skip the navigation and footer.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "// for B2B sellers running the whole show.…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "// for B2B sellers running the whole show.…"
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.
Could be better: llms.txt links resolve to this sitellms.txt contains no Markdown links to discoverable pages.
Could be better · AI answer readiness · Measured on your page
Observed evidence
llms.txt contains no Markdown links to discoverable pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add Markdown links such as [Pricing](/pricing) for the pages an answer engine should retrieve first.
Affected pages (1)
- https://www.flywingmen.com/
Could be better: Question headings have concise answers29/61 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
29/61 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (8)
- https://www.flywingmen.com/
- https://www.flywingmen.com/privacy
- https://www.flywingmen.com/signals
- https://www.flywingmen.com/docs/mcp
- https://www.flywingmen.com/performance
- https://www.flywingmen.com/for/saas
- https://www.flywingmen.com/features/ai-conversations
- https://www.flywingmen.com/pricing
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: author, date, breadcrumb.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 3 of 4 provenance signal types were found: author, date, breadcrumb.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (2)
- https://www.flywingmen.com/privacy
- https://www.flywingmen.com/signals
Could be better: Markdown copies of pages3 of 3 markdown URLs answered 200 but returned HTML, not markdown.
Could be better · AI answer readiness · Measured on your page
Observed evidence
3 of 3 markdown URLs answered 200 but returned HTML, not markdown.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.
Recommended fix
Either serve real markdown at those URLs or return 404. A 200 that hands back the HTML page wastes a retrieval and can be cached as the markdown copy.
Affected pages (3)
- https://www.flywingmen.com/index.md
- https://www.flywingmen.com/privacy.md
- https://www.flywingmen.com/index.html.md
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density84 concrete figures across 1951 words.
Not measured · AI answer readiness · Not established
Observed evidence
84 concrete figures across 1951 words.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=utf-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=utf-8.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: llms.txt
Looks good · AI answer readiness · Measured on your page
Observed evidence
llms.txt exists (10751 chars of markdown).
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: FAQ/QA schema
Looks good · AI answer readiness · Measured on your page
Observed evidence
FAQ/QA schema found.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Question-style headings
Looks good · AI answer readiness · Measured on your page
Observed evidence
39% of 155 subheadings are question-shaped.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 19 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Freshness signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
dateModified present in schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
51 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "Wingmen" + identity schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "Wingmen" and 6 identity URL(s) stay on flywingmen.com.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 35/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: No "coming soon" or placeholder pages2 sampled page(s) still read as unfinished — found "coming soon".
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
2 sampled page(s) still read as unfinished — found "coming soon".
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Finish those pages, or redirect, noindex or remove them. Google policy prohibits ads on screens under construction.
Affected pages (2)
- https://www.flywingmen.com/signals
- https://www.flywingmen.com/pricing
Could be better: Sampled publisher-content coverage1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 8501 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
1/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 8501 publisher words in total. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (1)
- https://www.flywingmen.com/resources
Could be better: About pageNo about page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No about page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.
Could be better: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Could be better: Tool pages expose explanatory content1/10 tool-style screen(s) expose fewer than 80 publisher words.
Could be better · AdSense policy · Review suggested
Observed evidence
1/10 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.
Affected pages (1)
- https://www.flywingmen.com/resources
Could be better: ads.txtads.txt exists but contains no google.com pub- line.
Could be better · AdSense policy · Review suggested
Observed evidence
ads.txt exists but contains no google.com pub- line.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add your AdSense publisher line exactly as shown in your AdSense account.
Not measured: First-party contact emailA contact page or form exists, but no public email address was found.
Not measured · AdSense policy · Review suggested
Observed evidence
A contact page or form exists, but no public email address was found.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.
Not applicable: Article-style content existsNo article/blog-style pages detected among crawled pages.
Not applicable · AdSense policy · Measured on your page
Observed evidence
No article/blog-style pages detected among crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. This check does not apply to the features observed in this sample.
Recommended fix
No action is required solely because articles are absent. For tool or directory sites, make the unique publisher value and explanation crawlable on each relevant screen.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: Privacy policy page
Looks good · AdSense policy · Measured on your page
Observed evidence
Privacy policy found: https://www.flywingmen.com/privacy
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Privacy policy advertising disclosures
Looks good · AdSense policy · Published platform rule
Observed evidence
Fetched privacy policy contains cookie/storage, advertising, and third-party/vendor disclosure signals.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Terms page
Looks good · AdSense policy · Measured on your page
Observed evidence
Terms page found: /terms
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
7/8 editorial pages clear the audit's publisher-content triage threshold. 2 of the 10 sampled pages are support or tool pages and were excluded from this check.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 8 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Policy pages linked site-wide
Looks good · AdSense policy · Measured on your page
Observed evidence
All 10 crawled pages link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | www.flywingmen.com |
|---|---|
| CDN / edge | Cloudflare |
| IP addresses | 172.67.137.101, 104.21.26.169, 2606:4700:3035::ac43:8965, 2606:4700:3034::6815:1aa9 |
| DNS A | 104.21.26.169 · 172.67.137.101 |
| DNS AAAA | 2606:4700:3035::ac43:8965 · 2606:4700:3034::6815:1aa9 |
| TLS | TLSv1.3TLS_AES_256_GCM_SHA384 |
| Certificate issuer | Google Trust Services / WE1 |
| Certificate valid until | Dec 17 13:17:12 2026 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
1731 publisher words
Page structure
html content
Observed discovery
Depth 0 · 9 incoming links
HTTP 200 · 108.2 KB source
Source interactions
61 controls · 0 unnamed
2 script / 2 stylesheet references
- Canonical declaration
- https://www.flywingmen.com/
- Schema types
- FAQPage, Question, Answer, Organization, ImageObject, WebSite, ProfessionalService, Offer
- Outgoing links in sampled graph
- /signals · /docs/mcp · /performance · /for/saas · /for/agencies · /for/consulting · /for/startups · /for/b2b-services · /for/recruitment · /for/dev-shops · /features/ai-conversations · /features/lead-sources · /features/dashboard · /features/multi-channel · /features/ai-wingman · /features/automation · /features/integrations · /features/personalization · /features/reporting · /pricing · /resources · /playbook · /privacy · /terms
Routes: / · /privacy · /signals · /docs · /performance · /for · /features · /pricing · /resources · /playbook
Resource origins 2
Resources associated with your website. External resources may belong to the same organization.
- https://www.flywingmen.com/stylesheet, script, image, media · 56 references · same origin
- https://static.cloudflareinsights.com/script · 10 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | allow: / |
| Googlebotsearch | /privacy | allowed | allow: / |
| Googlebotsearch | /signals | allowed | allow: / |
| Googlebotsearch | /docs/mcp | allowed | allow: / |
| Googlebotsearch | /performance | allowed | allow: / |
| Googlebotsearch | /for/saas | allowed | allow: / |
| Googlebotsearch | /features/ai-conversations | allowed | allow: / |
| Googlebotsearch | /pricing | allowed | allow: / |
| Googlebotsearch | /resources | allowed | allow: / |
| Googlebotsearch | /playbook | allowed | allow: / |
| bingbotsearch | / | allowed | allow: / |
| bingbotsearch | /privacy | allowed | allow: / |
| bingbotsearch | /signals | allowed | allow: / |
| bingbotsearch | /docs/mcp | allowed | allow: / |
| bingbotsearch | /performance | allowed | allow: / |
| bingbotsearch | /for/saas | allowed | allow: / |
| bingbotsearch | /features/ai-conversations | allowed | allow: / |
| bingbotsearch | /pricing | allowed | allow: / |
| bingbotsearch | /resources | allowed | allow: / |
| bingbotsearch | /playbook | allowed | allow: / |
| OAI-SearchBotsearch | / | allowed | allow: / |
| OAI-SearchBotsearch | /privacy | allowed | allow: / |
| OAI-SearchBotsearch | /signals | allowed | allow: / |
| OAI-SearchBotsearch | /docs/mcp | allowed | allow: / |
| OAI-SearchBotsearch | /performance | allowed | allow: / |
| OAI-SearchBotsearch | /for/saas | allowed | allow: / |
| OAI-SearchBotsearch | /features/ai-conversations | allowed | allow: / |
| OAI-SearchBotsearch | /pricing | allowed | allow: / |
| OAI-SearchBotsearch | /resources | allowed | allow: / |
| OAI-SearchBotsearch | /playbook | allowed | allow: / |
| PerplexityBotsearch | / | allowed | allow: / |
| PerplexityBotsearch | /privacy | allowed | allow: / |
| PerplexityBotsearch | /signals | allowed | allow: / |
| PerplexityBotsearch | /docs/mcp | allowed | allow: / |
| PerplexityBotsearch | /performance | allowed | allow: / |
| PerplexityBotsearch | /for/saas | allowed | allow: / |
| PerplexityBotsearch | /features/ai-conversations | allowed | allow: / |
| PerplexityBotsearch | /pricing | allowed | allow: / |
| PerplexityBotsearch | /resources | allowed | allow: / |
| PerplexityBotsearch | /playbook | allowed | allow: / |
| Claude-SearchBotsearch | / | allowed | allow: / |
| Claude-SearchBotsearch | /privacy | allowed | allow: / |
| Claude-SearchBotsearch | /signals | allowed | allow: / |
| Claude-SearchBotsearch | /docs/mcp | allowed | allow: / |
| Claude-SearchBotsearch | /performance | allowed | allow: / |
| Claude-SearchBotsearch | /for/saas | allowed | allow: / |
| Claude-SearchBotsearch | /features/ai-conversations | allowed | allow: / |
| Claude-SearchBotsearch | /pricing | allowed | allow: / |
| Claude-SearchBotsearch | /resources | allowed | allow: / |
| Claude-SearchBotsearch | /playbook | allowed | allow: / |
| GPTBottraining | / | allowed | allow: / |
| GPTBottraining | /privacy | allowed | allow: / |
| GPTBottraining | /signals | allowed | allow: / |
| GPTBottraining | /docs/mcp | allowed | allow: / |
| GPTBottraining | /performance | allowed | allow: / |
| GPTBottraining | /for/saas | allowed | allow: / |
| GPTBottraining | /features/ai-conversations | allowed | allow: / |
| GPTBottraining | /pricing | allowed | allow: / |
| GPTBottraining | /resources | allowed | allow: / |
| GPTBottraining | /playbook | allowed | allow: / |
| ClaudeBottraining | / | allowed | allow: / |
| ClaudeBottraining | /privacy | allowed | allow: / |
| ClaudeBottraining | /signals | allowed | allow: / |
| ClaudeBottraining | /docs/mcp | allowed | allow: / |
| ClaudeBottraining | /performance | allowed | allow: / |
| ClaudeBottraining | /for/saas | allowed | allow: / |
| ClaudeBottraining | /features/ai-conversations | allowed | allow: / |
| ClaudeBottraining | /pricing | allowed | allow: / |
| ClaudeBottraining | /resources | allowed | allow: / |
| ClaudeBottraining | /playbook | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | / | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /privacy | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /signals | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /docs/mcp | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /performance | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /for/saas | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /features/ai-conversations | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /pricing | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /resources | allowed | allow: / |
| Google-Extendedtraining and other Google AI uses | /playbook | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /privacy | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /signals | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /docs/mcp | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /performance | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /for/saas | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /features/ai-conversations | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /pricing | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /resources | allowed | allow: / |
| ChatGPT-Useruser-initiated; robots may not apply | /playbook | allowed | allow: / |
Advertised APIs and machine interfaces
documentation · declared
https://www.flywingmen.com/docs/mcp
This interface was advertised; its runtime behavior remains unverified.
Public DNS and TLS endpoint
www.flywingmen.com · observed · 172.67.137.101, 104.21.26.169, 2606:4700:3035::ac43:8965, 2606:4700:3034::6815:1aa9
- A
- 104.21.26.169 · 172.67.137.101
- AAAA
- 2606:4700:3035::ac43:8965 · 2606:4700:3034::6815:1aa9
- CNAME
- Unavailable for this exact hostname
- NS
- Unavailable for this exact hostname
- MX
- Unavailable for this exact hostname
- CAA
- Unavailable for this exact hostname
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Google Trust Services / WE1
Certificate valid until: Dec 17 13:17:12 2026 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Build content depth around real keywords
Technical basics are in place — use pages that answer actual searches as the next content focus. This audit does not measure rankings.
- 02
Steal from our keyword datasets
Curated keyword collections by niche give you a content calendar without paid tools.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://www.flywingmen.com/
- https://www.flywingmen.com/privacy
- https://www.flywingmen.com/signals
- https://www.flywingmen.com/docs/mcp
- https://www.flywingmen.com/performance
- https://www.flywingmen.com/for/saas
- https://www.flywingmen.com/features/ai-conversations
- https://www.flywingmen.com/pricing
- https://www.flywingmen.com/resources
- https://www.flywingmen.com/playbook