Website report

Visit sitehttps://www.trykivo.space/

Hold a key. Say it. Let go. Your words appear at the cursor, in any app on your Mac. On-device, free to use, no account, no credit card.

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

Analysed Nov 8, 2026 · 15 categories · 89 passed · 20 warnings · 2 issues · 39 informational

Partial evidence; some observations were unavailable.

Audit score

D

64/100

Mixed

Agentic
100
SEO
64

What we found

2Needs a fix20Could be better89Looks good39Informational
  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: Your site has no sitemap. see checkA sitemap helps search engines discover your pages.
  3. 3.Could be better: Your page has no preferred URL. see checkA canonical URL tells search engines which version to use.
  4. 4.Could be better: og:url and og:type: needs attention. see checkComplete link previews make your pages easier to recognize and share.
  5. 5.Could be better: JSON-LD present: needs attention. see checkStructured data helps search engines and AI assistants understand your content.

Built with 2 technologies· detected stack

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

How it fits together

  • Next.jsFramework
  • VercelHosting / edge
Hosting and deploymentType
  • VercelHosting / edge
Frameworks and librariesType
  • Next.jsFramework

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

Site checks

89 passed · 20 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: "Kivo. Don’t type, just speak."

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 29 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 "Kivo. Don’t type, just speak." 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: "Hold a key. Say it. Let go. Your words appear at the cursor, in any app on your Mac. On-de…"

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 136 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 2 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://www.trykivo.space/sitemap.xml → 404).

Could be better · Indexing · Review suggested

Observed evidence

No sitemap found (checked https://www.trykivo.space/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 (www.trykivo.space).

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 (1 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 2 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 ≈ 75.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 75.

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 2 sampled page(s). The entered page exposes 588 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 588 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 9.2%.

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: kivo, don, type, just.

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 2 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

6 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 2 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 fix1Could be better3Looks good3Informational

58/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: og:url and og:typeog:url is missing.

Could be better · Social sharing · Review suggested

Observed evidence

og:url is missing.

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 to complete the Open Graph basics.

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: "Kivo. Don’t type, just speak."

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: "Hold a key. Say it. Let go. Your words appear at the cursor, in any app on your Mac. On-de…"

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: Twitter/X card

Looks good · Social sharing · Measured on your page

Observed evidence

twitter:card is "summary".

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 1 crawled inner pages declare BreadcrumbList schema.

Not measured · Structured data · Not established

Observed evidence

None of the 1 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 (1)

  • https://www.trykivo.space/changelog
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

Headings7Looks good

100/100
Looks good: H1 exists

Looks good · Headings · Measured on your page

Observed evidence

H1 found: "Kivo. Don’t type, just speak."

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 11 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 "Kivo. Don’t type, just speak.".

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

11 headings, averaging 5.5 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

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

Images2Looks good2Informational

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

Not applicable: Lazy loadingOnly 1 visible image(s) on the page, too few for lazy loading to change the initial load.

Not applicable · Images · Measured on your page

Observed evidence

Only 1 visible image(s) on the page, too few for lazy loading to change the initial load.

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. Once the page carries several images, add loading="lazy" to the ones below the fold.

Looks good: Alt text coverage

Looks good · Images · Measured on your page

Observed evidence

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

Mobile4Looks good2Informational

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

Not applicable · Mobile · Measured on your page

Observed evidence

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

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

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

Looks good: ARIA references point to source elements

Looks good · Mobile · Measured on your page

Observed evidence

16 ARIA reference(s) resolve within their source documents. Rendered visibility was 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.

Branding2Looks good2Informational

100/100
Not measured: Apple touch iconNo apple-touch-icon link.

Not measured · Branding · Not established

Observed evidence

No apple-touch-icon link.

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 a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

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"> (/icon.svg?icon.3m_intf36yps9.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: Theme color

Looks good · Branding · Measured on your page

Observed evidence

theme-color is "#FFFFFF".

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
Web fonts don't block text—Informational: not applicableNo Google Fonts stylesheet links detected.
Server response time135 msLooks good: goodThe audit received response headers after 135 ms from one test location.
HTML payload size69 KBLooks good: goodThe page's HTML is a lean 69 KB uncompressed.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded0.0 KBLooks good: goodInline styles total 0.0 KB.
Script/stylesheet count—Looks good: good10 total script/style resources — reasonable.
HTML served compressed—Looks good: goodHTML is compressed with br.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight69.4 KBInformational: measured source, not transferred bytes69.4 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

100/100

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: Declared form submission targetsNo HTML forms were found.

Not applicable · Security · Measured on your page

Observed evidence

No HTML forms were found.

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

Check JavaScript-generated form transport separately if present.

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=63072000.

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 no-referrer.

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.

AI answer readiness

100/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: 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 0% of 18 H2/H3 headings are question-shaped.

Could be better · AI answer readiness · Review suggested

Observed evidence

Only 0% of 18 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: "Dictation that stays on your Mac…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "Dictation that stays on your Mac…"

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: Machine-readable provenance signalsOnly 1 of 4 provenance signal types were found: author.

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

Observed evidence

Only 1 of 4 provenance signal types were found: author.

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.trykivo.space/
  • https://www.trykivo.space/changelog
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /changelog.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 /changelog.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://www.trykivo.space/
  • https://www.trykivo.space/changelog
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 density32 concrete figures across 808 words.

Not measured · AI answer readiness · Not established

Observed evidence

32 concrete figures across 808 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: Question headings have concise answersNo question-shaped H2/H3 headings were available to pair with answer paragraphs.

Not measured · AI answer readiness · Not established

Observed evidence

No question-shaped H2/H3 headings were available to pair with answer paragraphs.

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

Write the questions your audience asks as H2/H3 headings, then answer each in a concise paragraph immediately below it.

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: Semantic HTML structure

Looks good · AI answer readiness · Measured on your page

Observed evidence

Semantic structure present: main×1, section×8, nav×1, header×1, footer×1, aside×2.

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 9 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

10 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

32/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 39/100 for publisher readiness. Ignore this section if you do not run ads.

Needs a fix: Privacy policy pageNo privacy policy page is linked or crawlable.

Needs a fix · AdSense policy · Review suggestedCritical

Observed evidence

No privacy policy page is linked or crawlable.

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

Publish an accessible privacy policy that discloses cookies and data use by Google and other third-party ad vendors.

Reference
Could be better: Terms pageNo terms of use page found.

Could be better · AdSense policy · Review suggested

Observed evidence

No terms of use 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

Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.

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: Author or publisher background1/1 attributed editorial pages provide no discoverable author or publisher background.

Could be better · AdSense policy · Review suggested

Observed evidence

1/1 attributed editorial pages provide no discoverable author or publisher background.

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

Link the byline to an author profile or About page, or add truthful structured author details. This is a transparency heuristic, not an AdSense approval rule.

Affected pages (1)

  • https://www.trykivo.space/changelog
Reference
Not measured: Privacy policy advertising disclosuresA privacy page was not present in the crawl sample, so its disclosures could not be verified.

Not measured · AdSense policy · Not established

Observed evidence

A privacy page was not present in the crawl sample, so its disclosures could not be verified.

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

Confirm the policy explains cookies or similar storage, Google or advertising vendors, and third-party data use.

Reference
Not measured: First-party contact emailNo public contact email was found in the sampled home, About, or Contact pages.

Not measured · AdSense policy · Review suggested

Observed evidence

No public contact email was found in the sampled home, About, or Contact pages.

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 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 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: 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: Sampled publisher-content coverage

Looks good · AdSense policy · Review suggested

Observed evidence

All 2 editorial pages expose at least 250 publisher words; those pages hold 1138 publisher words in total.

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

2/2 editorial pages clear the audit's publisher-content triage threshold.

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: Tool pages expose explanatory content

Looks good · AdSense policy · Review suggested

Observed evidence

All 2 sampled tool-style screens include crawlable explanation.

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 1 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 10 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.

Looks good: Article-style content exists

Looks good · AdSense policy · Measured on your page

Observed evidence

Article-style content detected.

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.

Looks good: Author bylines on content

Looks good · AdSense policy · Review suggested

Observed evidence

Author attribution appears on all 1 sampled editorial 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 change.

Reference

Hosting and infrastructure

Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.

Hosting and infrastructure observations
Hostnamewww.trykivo.space
HostingVercel
IP addresses64.29.17.1, 216.198.79.1
DNS A216.198.79.1 · 64.29.17.1
DNS CNAMEae27a865a98848d0.vercel-dns-017.com
DNS CAA{"critical":0,"type":"CAA","issue":"globalsign.com"} · {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}
TLSTLSv1.3TLS_AES_128_GCM_SHA256
Certificate issuerLet's Encrypt / YR1
Certificate valid untilFeb 2 20:36:18 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

588 publisher words

Page structure

html content

Observed discovery

Depth 0 · 1 incoming links

HTTP 200 · 69.4 KB source

Source interactions

32 controls · 0 unnamed

8 script / 2 stylesheet references

Canonical declaration
Not declared
Schema types
None observed
Outgoing links in sampled graph
/changelog · /download/Kivo.dmg

Routes: / · /changelog

Resource origins 2

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

  • https://www.trykivo.space/stylesheet, script, image · 24 references · same origin
  • https://api.producthunt.com/image · 1 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/changelogallowedDeclared policy for this page.
bingbotsearch/allowedDeclared policy for this page.
bingbotsearch/changelogallowedDeclared policy for this page.
OAI-SearchBotsearch/allowedDeclared policy for this page.
OAI-SearchBotsearch/changelogallowedDeclared policy for this page.
PerplexityBotsearch/allowedDeclared policy for this page.
PerplexityBotsearch/changelogallowedDeclared policy for this page.
Claude-SearchBotsearch/allowedDeclared policy for this page.
Claude-SearchBotsearch/changelogallowedDeclared policy for this page.
GPTBottraining/allowedDeclared policy for this page.
GPTBottraining/changelogallowedDeclared policy for this page.
ClaudeBottraining/allowedDeclared policy for this page.
ClaudeBottraining/changelogallowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/changelogallowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/changelogallowedDeclared 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

www.trykivo.space · observed · 64.29.17.1, 216.198.79.1

A
216.198.79.1 · 64.29.17.1
AAAA
Unavailable for this exact hostname
CNAME
ae27a865a98848d0.vercel-dns-017.com
NS
Unavailable for this exact hostname
MX
Unavailable for this exact hostname
CAA
{"critical":0,"type":"CAA","issue":"globalsign.com"} · {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"pki.goog"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Let's Encrypt / YR1

Certificate valid until: Feb 2 20:36:18 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://www.trykivo.space/
  • https://www.trykivo.space/changelog