Website report

Visit sitehttps://heywisp.ai/

Wisp is a little AI fairy who lives on your desktop and can do anything for you. Just ask out loud. Available for Windows and macOS.

Audit Full discovery audit·Language English (en)·Response HTTP 200·Served by Netlify

Analysed Nov 8, 2026 · 15 categories · 84 passed · 28 warnings · 2 issues · 36 informational

Partial evidence; some observations were unavailable.

Audit score

F

49/100

Needs work

Agentic
87
SEO
52

What we found

2Needs a fix28Could be better84Looks good36Informational
  1. 1.Needs a fix: Your link preview image needs attention. see checkA preview image makes your links easier to notice and recognize.
  2. 2.Could be better: Twitter/X card: needs attention. see checkComplete link previews make your pages easier to recognize and share.
  3. 3.Could be better: Your site has no sitemap. see checkA sitemap helps search engines discover your pages.
  4. 4.Could be better: Your page has no preferred URL. see checkA canonical URL tells search engines which version to use.
  5. 5.Could be better: Semantic HTML structure: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.

Built with 2 technologies· detected stack

Read from the public source and response headers of the sampled pages.

Hosting and deploymentType
  • NetlifyHosting / edge
Payments and servicesType
  • Google FontsFont integration

A framework or CDN signal describes the public response, not the origin host or private backend.

Site checks

84 passed · 28 warnings · 2 issues

Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.

Metadata11Looks good

100/100
Looks good: Page title exists

Looks good · Metadata · Measured on your page

Observed evidence

Title found: "Wisp, your guiding light on the desktop"

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 39 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 "Wisp, your guiding light on the desktop" 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: "Wisp is a little AI fairy who lives on your desktop and can do anything for you. Just ask …"

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

Indexing2Could be better9Looks good5Informational

69/100
Could be better: Sitemap existsNo sitemap found (checked https://heywisp.ai/sitemap.xml → 404).

Could be better · Indexing · Review suggested

Observed evidence

No sitemap found (checked https://heywisp.ai/sitemap.xml → 404).

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Recommended fix

Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.

Reference
Could be better: Canonical URL setThe homepage has no canonical link.

Could be better · Indexing · Review suggested

Observed evidence

The homepage has no canonical link.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Recommended fix

Add <link rel="canonical"> (Next.js: metadata.alternates.canonical). It consolidates ranking signals when the page is reachable under several URLs (with/without query params, trailing slash…).

Reference
Not applicable: Sampled URLs have aligned indexability signalsNo sitemap was found, so there are no submitted URLs to compare against.

Not applicable · Indexing · Measured on your page

Observed evidence

No sitemap was found, so there are no submitted URLs to compare against.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Recommended fix

The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.

Not applicable: robots.txt existsrobots.txt is absent.

Not applicable · Indexing · Measured on your page

Observed evidence

robots.txt is absent. A missing policy permits crawling by default.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Recommended fix

Optional: publish a robots policy to advertise a sitemap or restrict selected paths.

Not measured: Sitemap parses and lists URLsNo sitemap was reachable, so its contents cannot be validated.

Not measured · Indexing · Not established

Observed evidence

No sitemap was reachable, so its contents cannot be validated.

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 /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.

Not applicable: Sitemap declared in robots.txtNo sitemap was reachable, so robots.txt has nothing to point at.

Not applicable · Indexing · Measured on your page

Observed evidence

No sitemap was reachable, so robots.txt has nothing to point at.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Recommended fix

Publish the sitemap first, then add a Sitemap: line to robots.txt naming its absolute URL.

Show 10 more checks
Not applicable: Canonical is absolute and self-referencingThe page declares no canonical URL, so there is nothing to validate.

Not applicable · Indexing · Measured on your page

Observed evidence

The page declares no canonical URL, so there is nothing to validate.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Recommended fix

Add <link rel="canonical" href="…"> pointing at the absolute, preferred URL of the page.

Looks good: Single canonical declaration

Looks good · Indexing · Measured on your page

Observed evidence

No canonical declaration to conflict.

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

No canonical target to validate in this 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: robots.txt doesn't block everything

Looks good · Indexing · Measured on your page

Observed evidence

The audited URL is allowed for Googlebot. HTTP 404: no available robots policy.

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 (heywisp.ai).

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 (4 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 7 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/100
Not measured: ReadabilityFlesch reading ease ≈ 72.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 72.

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 7 sampled page(s). The entered page exposes 1046 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 1046 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 13.9%.

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

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 4 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: No deprecated HTML tags

Looks good · Content · Measured on your page

Observed evidence

No deprecated HTML tags.

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

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

Social sharing1Needs a fix2Could be better2Looks good3Informational

40/100
Needs a fix: Open Graph imageNo og:image tag.

Needs a fix · Social sharing · Review suggestedCritical

Observed evidence

No og:image tag.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. Right now the sampled pages don't provide it.

Recommended fix

Add a 1200×630 og:image. Without one, a shared link renders as plain text in most apps. Next.js generates one from opengraph-image.tsx.

Reference
Could be better: Twitter/X cardNo twitter:card tag.

Could be better · Social sharing · Review suggested

Observed evidence

No twitter:card tag.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Recommended fix

Add <meta name="twitter:card" content="summary_large_image">. X falls back to Open Graph for the rest, but the card type itself must be declared.

Reference
Could be better: og:url and og:typeNeither og:url nor og:type is set.

Could be better · Social sharing · Review suggested

Observed evidence

Neither og:url nor og:type is set.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Recommended fix

Add og:url (canonical URL) and og:type ("website" for the homepage).

Reference
Not applicable: Share image loadsNo og:image tag was found, so there is no image URL to fetch and verify.

Not applicable · Social sharing · Measured on your page

Observed evidence

No og:image tag was found, so there is no image URL to fetch and verify.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Recommended fix

Add <meta property="og:image" content="…"> with an absolute URL. This check then confirms the file actually loads.

Not applicable: Share image dimensions declaredNo og:image tag was found, so its declared dimensions cannot be reviewed.

Not applicable · Social sharing · Measured on your page

Observed evidence

No og:image tag was found, so its declared dimensions cannot be reviewed.

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Recommended fix

Add the og:image tag first, then declare og:image:width and og:image:height alongside it.

Not measured: og:site_nameNo og:site_name tag.

Not measured · Social sharing · Not established

Observed evidence

No og:site_name 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 it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

Reference
Looks good: Open Graph title

Looks good · Social sharing · Measured on your page

Observed evidence

og:title: "Wisp"

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Open Graph description

Looks good · Social sharing · Measured on your page

Observed evidence

og:description: "Meet Wisp, your guiding light. A little fairy who lives on your desktop and does the rest."

Why this matters

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Structured dataNot measured

Not measured
Could be better: JSON-LD presentNo JSON-LD structured data on the homepage.

Could be better · Structured data · Review suggested

Observed evidence

No JSON-LD structured data on the homepage.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Recommended fix

Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.

Reference
Could be better: Organization or WebSite schemaNo Organization, WebSite or Person schema found.

Could be better · Structured data · Review suggested

Observed evidence

No Organization, WebSite or Person schema found.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Recommended fix

Add an identity node so search engines and AI assistants can attribute your content to a real entity.

Reference
Not applicable: JSON-LD parsesNo JSON-LD blocks were found, so there is no syntax to validate.

Not applicable · Structured data · Measured on your page

Observed evidence

No JSON-LD blocks were found, so there is no syntax to validate.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

Recommended fix

Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.

Not measured: Breadcrumb schema on inner pagesNone of the 6 crawled inner pages declare BreadcrumbList schema.

Not measured · Structured data · Not established

Observed evidence

None of the 6 crawled inner pages declare BreadcrumbList schema.

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 BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

Affected pages (6)

  • https://heywisp.ai/privacy
  • https://heywisp.ai/help
  • https://heywisp.ai/account/
  • https://heywisp.ai/terms
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
Reference
Not applicable: Content-specific schemaNo content-specific schema (Article, Product, FAQPage…) detected.

Not applicable · Structured data · Measured on your page

Observed evidence

No content-specific schema (Article, Product, FAQPage…) detected.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

Recommended fix

If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.

Reference

Headings1Could be better6Looks good

91/100
Could be better: Heading levels don't skip1 heading level skip: H2 → H4 "Your morning brief Tuesday".

Could be better · Headings · Review suggested

Observed evidence

1 heading level skip: H2 → H4 "Your morning brief Tuesday".

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.

Recommended fix

Use the next level down for each subsection (H2 under H1, H3 under H2). If a heading level was chosen for its font size, keep the level and change the styling instead.

Looks good: H1 exists

Looks good · Headings · Measured on your page

Observed evidence

H1 found: "Meet Wisp."

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: H1 has real text

Looks good · Headings · Measured on your page

Observed evidence

H1 reads "Meet Wisp.".

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

24 headings, averaging 4.2 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

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

Images2Could be better1Looks good1Informational

64/100
Could be better: Width/height attributes2 of 4 visible images lack width and height attributes: logo.svg, logo.svg.

Could be better · Images · Review suggested

Observed evidence

2 of 4 visible images lack width and height attributes: logo.svg, logo.svg.

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

Set explicit width and height so the browser reserves the space before the image loads. Without them the page shifts as images arrive, which is what Cumulative Layout Shift measures. next/image sets them for you.

Reference
Could be better: Lazy loadingNone of the 4 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).

Could be better · Images · Review suggested

Observed evidence

None of the 4 visible images are lazy-loaded (no loading="lazy" and no lazy-loading library markers).

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

Add loading="lazy" to below-the-fold images so the initial render doesn't wait on them. Keep the hero image eager.

Reference
Not applicable: Modern image formatsNo raster images with a recognizable file extension were found.

Not applicable · Images · Measured on your page

Observed evidence

No raster images with a recognizable file extension were found.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Recommended fix

Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.

Looks good: Alt text coverage

Looks good · Images · Measured on your page

Observed evidence

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

Mobile3Looks good3Informational

100/100
Not applicable: Responsive image markupNone of the 4 images use srcset.

Not applicable · Mobile · Measured on your page

Observed evidence

None of the 4 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.

Not applicable: ARIA references point to source elementsNo ARIA ID references found in the sampled HTML.

Not applicable · Mobile · Measured on your page

Observed evidence

No ARIA ID references found in the sampled HTML.

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

Verify rendered accessibility separately.

Looks good: Viewport meta tag

Looks good · Mobile · Measured on your page

Observed evidence

Viewport configured: "width=device-width, initial-scale=1".

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.

Looks good: Interactive controls have source labels

Looks good · Mobile · Measured on your page

Observed evidence

136 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

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/100
Not 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.

Branding3Looks good1Informational

100/100
Not 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.

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.

Looks good: Theme color

Looks good · Branding · Measured on your page

Observed evidence

theme-color is "#0A0C12".

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

100/100

Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.

Performance measurements observed during the audit
MeasureThis siteReading
Server response time377 msLooks good: goodThe audit received response headers after 377 ms from one test location.
HTML payload size46 KBLooks good: goodThe page's HTML is a lean 46 KB uncompressed.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded3.2 KBLooks good: goodInline styles total 3.2 KB.
Script/stylesheet count—Looks good: good7 total script/style resources — reasonable.
Web fonts don't block text—Looks good: goodGoogle Fonts links set a non-blocking font-display value.
HTML served compressed—Looks good: goodHTML is compressed with br.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight46.3 KBInformational: measured source, not transferred bytes46.3 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

89/100

HTTPS, transport security and the response headers the audited pages send.

Could be better: Frame embedding protectionNo frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).

Could be better · Security · Review suggested

Observed evidence

No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).

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

Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).

Reference
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.

Could be better · Security · Review suggested

Observed evidence

X-Content-Type-Options: nosniff is not set.

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

Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).

Could be better: Content Security PolicyNo Content-Security-Policy detected.

Could be better · Security · Review suggested

Observed evidence

No Content-Security-Policy detected.

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

Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.

Reference
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.

Could be better · Security · Review suggested

Observed evidence

No explicit restriction on sensitive browser features was observed.

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

Disable unused camera, microphone, or geolocation access using Permissions-Policy.

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.

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

No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.

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

7 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

55/100

Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.

Could be better: Semantic HTML structureSemantic landmarks exist (17) but there's no <main> or role="main".

Could be better · AI answer readiness · Review suggested

Observed evidence

Semantic landmarks exist (17) 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: llms.txtNo /llms.txt file.

Could be better · AI answer readiness · Review suggested

Observed evidence

No /llms.txt file.

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

Optional: publish an llms.txt index of useful pages. This proposal is not a requirement for Google AI features, and its absence does not reduce the core score.

Reference
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.

Could be better · AI answer readiness · Review suggested

Observed evidence

No FAQPage or QAPage schema on any crawled page.

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

If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.

Reference
Could be better: Question-style headingsOnly 8% of 124 H2/H3 headings are question-shaped.

Could be better · AI answer readiness · Review suggested

Observed evidence

Only 8% of 124 H2/H3 headings are question-shaped.

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

Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.

Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "// Your guiding light on the desktop…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "// Your guiding light on the desktop…"

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: Freshness signalsNo dateModified schema or visible 'updated' dates found.

Could be better · AI answer readiness · Review suggested

Observed evidence

No dateModified schema or visible 'updated' dates found.

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

For content where dates matter, show the actual update date and mirror it in dateModified. Do not invent dates or change them without a substantive update. Missing dates alone do not prove stale content.

Could be better: Consistent brand entityThe site does not declare its name: no og:site_name and no Organization or WebSite schema.

Could be better · AI answer readiness · Review suggested

Observed evidence

The site does not declare its name: no og:site_name and no Organization or WebSite schema.

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

Declare the site's name once in Organization or WebSite schema and in og:site_name, using the same name as the title. Readers, search engines and AI assistants then attribute the pages to one named publisher.

Could be better: Question headings have concise answers5/10 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

5/10 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 (5)

  • https://heywisp.ai/privacy
  • https://heywisp.ai/help
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: author, contact, date.

Could be better · AI answer readiness · Measured on your page

Observed evidence

Only 3 of 4 provenance signal types were found: author, contact, date.

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 (7)

  • https://heywisp.ai/
  • https://heywisp.ai/privacy
  • https://heywisp.ai/help
  • https://heywisp.ai/account/
  • https://heywisp.ai/terms
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /privacy.md or /index.html.md.

Could be better · AI answer readiness · Measured on your page

Observed evidence

No markdown copy answered at /index.md or /privacy.md or /index.html.md.

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

Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.

Affected pages (2)

  • https://heywisp.ai/
  • https://heywisp.ai/privacy
Reference
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.

Reference
Not measured: Authored, dated articlesNo Article/BlogPosting schema found.

Not measured · AI answer readiness · Not established

Observed evidence

No Article/BlogPosting schema 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

Add Article schema with author and datePublished so the page exposes clear provenance for retrieval. This audit does not measure or guarantee citations or rankings.

Not measured: Citable facts density41 concrete figures across 1080 words.

Not measured · AI answer readiness · Not established

Observed evidence

41 concrete figures across 1080 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: Entity identity agrees across signalsThe page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.

Not applicable · AI answer readiness · Measured on your page

Observed evidence

The page declares no site or organization name (no og:site_name and no Organization or WebSite schema name), so there is nothing to compare.

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

Declare the site's name once in Organization or WebSite schema and in og:site_name, and use the same name in the title.

Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.

Not measured · AI answer readiness · Not established

Observed evidence

No readable /llms.txt, so its structure cannot be checked.

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 llms.txt first — the llms.txt check covers that — then this one verifies the structure.

Reference
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: 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: 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 24 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: Cites external sources

Looks good · AI answer readiness · Measured on your page

Observed evidence

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

AdSense readinessOptional

28/100

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: Sampled publisher-content coverage3/5 editorial pages expose fewer than 80 publisher words in source HTML.

Needs a fix · AdSense policy · Review suggestedCritical

Observed evidence

3/5 editorial pages expose fewer than 80 publisher words in source HTML. 2 of the 7 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. Right now the sampled pages don't provide it.

Recommended fix

Add crawlable explanation or original publisher material to those pages. Most of the sample currently reads as chrome rather than content.

Affected pages (3)

  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
Reference
Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks cookie/storage, third-party/vendor disclosure signals.

Could be better · AdSense policy · Published platform ruleCritical

Observed evidence

Fetched privacy policy lacks cookie/storage, third-party/vendor disclosure signals.

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

Describe data collection, sharing, and cookie use by Google and other third-party ad vendors.

Affected pages (1)

  • https://heywisp.ai/privacy
Reference
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: Thin page share3/5 editorial pages expose fewer than 80 publisher words.

Could be better · AdSense policy · Review suggested

Observed evidence

3/5 editorial pages expose fewer than 80 publisher words. 2 of the 7 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 these pages for a clear purpose and useful publisher material. This cutoff is a triage heuristic, not an AdSense minimum.

Affected pages (3)

  • https://heywisp.ai/account/ (24 publisher words)
  • https://heywisp.ai/account/ (24 publisher words)
  • https://heywisp.ai/account/ (24 publisher words)
Could be better: Tool pages expose explanatory content3/4 tool-style screen(s) expose fewer than 80 publisher words.

Could be better · AdSense policy · Review suggested

Observed evidence

3/4 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 (3)

  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/
Reference
Could be better: First-party contact emailOnly consumer-provider contact email found: wispaisupport@gmail.com.

Could be better · AdSense policy · Review suggested

Observed evidence

Only consumer-provider contact email found: wispaisupport@gmail.com.

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

Use an address on the publisher's domain when practical so readers can verify the publisher identity. This is a practitioner trust heuristic, not an AdSense requirement.

Not measured: ads.txtNo ads.txt yet.

Not measured · AdSense policy · Not established

Observed evidence

No ads.txt yet.

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

When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.

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

Reference
Not measured: Author bylines on contentNo editorial pages were identified in the crawl sample.

Not measured · AdSense policy · Review suggested

Observed evidence

No editorial pages were identified in the crawl sample.

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

Tool and application pages do not need article bylines. Identify the publisher through the site and About page instead.

Not measured: Author or publisher backgroundNo editorial pages were identified, so author-background links were not expected.

Not measured · AdSense policy · Review suggested

Observed evidence

No editorial pages were identified, so author-background links were not expected.

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

For non-editorial sites, use the About page and publisher identity signals instead.

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.

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

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

Reference
Looks good: Privacy policy page

Looks good · AdSense policy · Measured on your page

Observed evidence

Privacy policy found: https://heywisp.ai/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: Terms page

Looks good · AdSense policy · Measured on your page

Observed evidence

Terms page found: https://heywisp.ai/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: Contact method

Looks good · AdSense policy · Measured on your page

Observed evidence

Contact email found: mailto:wispaisupport@gmail.com

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.

Reference
Looks good: Publisher content differs across URLs

Looks good · AdSense policy · Review suggested

Observed evidence

No high publisher-content repetition among 3 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.

Looks good: Clear navigation

Looks good · AdSense policy · Measured on your page

Observed evidence

Navigation present with 9 links.

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: No "coming soon" or placeholder pages

Looks good · AdSense policy · Measured on your page

Observed evidence

No "coming soon", "under construction" or lorem-ipsum text on crawled pages.

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

Hosting and infrastructure observations
Hostnameheywisp.ai
HostingNetlify
IP addresses18.208.88.157, 98.84.224.111
DNS A18.208.88.157 · 98.84.224.111
DNS NSdns1.p05.nsone.net · dns2.p05.nsone.net · dns3.p05.nsone.net · dns4.p05.nsone.net
TLSTLSv1.3TLS_AES_128_GCM_SHA256
Certificate issuerLet's Encrypt / YE1
Certificate valid untilJan 28 21:30:14 2027 GMT
Certificate validationPassed

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

1046 publisher words

Page structure

html content

Observed discovery

Depth 0 · 6 incoming links

HTTP 200 · 46.3 KB source

Source interactions

36 controls · 0 unnamed

5 script / 2 stylesheet references

Canonical declaration
Not declared
Schema types
None observed
Outgoing links in sampled graph
/help · /account/ · /account/ · /account/ · /privacy · /terms

Routes: / · /privacy · /help · /account · /terms

Repeated metadata in the sample

Same title: your wisp account

/account/ · /account/ · /account/

Same description: sign in to see your wisp plan, upgrade or change it, and manage billing.

/account/ · /account/ · /account/

Resource origins 2

Resources associated with your website. External resources may belong to the same organization.

  • https://heywisp.ai/stylesheet, image, media, script · 39 references · same origin
  • https://fonts.googleapis.com/stylesheet · 7 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.

Robots policy for every evaluated crawler and sampled page
Crawler / purposePagePolicyMatched directive
Googlebotsearch/allowedDeclared policy for this page.
Googlebotsearch/privacyallowedDeclared policy for this page.
Googlebotsearch/helpallowedDeclared policy for this page.
Googlebotsearch/account/allowedDeclared policy for this page.
Googlebotsearch/termsallowedDeclared policy for this page.
Googlebotsearch/account/allowedDeclared policy for this page.
Googlebotsearch/account/allowedDeclared policy for this page.
bingbotsearch/allowedDeclared policy for this page.
bingbotsearch/privacyallowedDeclared policy for this page.
bingbotsearch/helpallowedDeclared policy for this page.
bingbotsearch/account/allowedDeclared policy for this page.
bingbotsearch/termsallowedDeclared policy for this page.
bingbotsearch/account/allowedDeclared policy for this page.
bingbotsearch/account/allowedDeclared policy for this page.
OAI-SearchBotsearch/allowedDeclared policy for this page.
OAI-SearchBotsearch/privacyallowedDeclared policy for this page.
OAI-SearchBotsearch/helpallowedDeclared policy for this page.
OAI-SearchBotsearch/account/allowedDeclared policy for this page.
OAI-SearchBotsearch/termsallowedDeclared policy for this page.
OAI-SearchBotsearch/account/allowedDeclared policy for this page.
OAI-SearchBotsearch/account/allowedDeclared policy for this page.
PerplexityBotsearch/allowedDeclared policy for this page.
PerplexityBotsearch/privacyallowedDeclared policy for this page.
PerplexityBotsearch/helpallowedDeclared policy for this page.
PerplexityBotsearch/account/allowedDeclared policy for this page.
PerplexityBotsearch/termsallowedDeclared policy for this page.
PerplexityBotsearch/account/allowedDeclared policy for this page.
PerplexityBotsearch/account/allowedDeclared policy for this page.
Claude-SearchBotsearch/allowedDeclared policy for this page.
Claude-SearchBotsearch/privacyallowedDeclared policy for this page.
Claude-SearchBotsearch/helpallowedDeclared policy for this page.
Claude-SearchBotsearch/account/allowedDeclared policy for this page.
Claude-SearchBotsearch/termsallowedDeclared policy for this page.
Claude-SearchBotsearch/account/allowedDeclared policy for this page.
Claude-SearchBotsearch/account/allowedDeclared policy for this page.
GPTBottraining/allowedDeclared policy for this page.
GPTBottraining/privacyallowedDeclared policy for this page.
GPTBottraining/helpallowedDeclared policy for this page.
GPTBottraining/account/allowedDeclared policy for this page.
GPTBottraining/termsallowedDeclared policy for this page.
GPTBottraining/account/allowedDeclared policy for this page.
GPTBottraining/account/allowedDeclared policy for this page.
ClaudeBottraining/allowedDeclared policy for this page.
ClaudeBottraining/privacyallowedDeclared policy for this page.
ClaudeBottraining/helpallowedDeclared policy for this page.
ClaudeBottraining/account/allowedDeclared policy for this page.
ClaudeBottraining/termsallowedDeclared policy for this page.
ClaudeBottraining/account/allowedDeclared policy for this page.
ClaudeBottraining/account/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/privacyallowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/helpallowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/account/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/termsallowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/account/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/account/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/privacyallowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/helpallowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/account/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/termsallowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/account/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/account/allowedDeclared policy for this page.
Advertised APIs and machine interfaces

No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.

Public DNS and TLS endpoint

heywisp.ai · observed · 18.208.88.157, 98.84.224.111

A
18.208.88.157 · 98.84.224.111
AAAA
Unavailable for this exact hostname
CNAME
Unavailable for this exact hostname
NS
dns1.p05.nsone.net · dns2.p05.nsone.net · dns3.p05.nsone.net · dns4.p05.nsone.net
MX
Unavailable for this exact hostname
CAA
Unavailable for this exact hostname

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Let's Encrypt / YE1

Certificate valid until: Jan 28 21:30:14 2027 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.

  1. 01

    Fix the fundamentals first

    Your top fixes list is the priority order — clear the red items before creating more content.

  2. 02

    Re-run the combined audit after each batch of fixes

    Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.

  3. 03

    Fix AdSense policy signals

    Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.

  4. 04

    Fix social previews next

    Broken previews make shared links harder to interpret. Add stable Open Graph metadata and an image URL; this audit does not measure resulting clicks or traffic.

Apply the recommended fixes

Hand the complete evidence to a coding agent, or take the report with you.

Open in ChatGPT Open in Grok Open in Perplexity

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://heywisp.ai/
  • https://heywisp.ai/privacy
  • https://heywisp.ai/help
  • https://heywisp.ai/account/
  • https://heywisp.ai/terms
  • https://heywisp.ai/account/
  • https://heywisp.ai/account/