Website report

Visit sitehttps://mizzi.com/

Kalvin Mizzi — founder of SKU.io. Builds companies with fleets of AI agents.

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

Analysed Nov 7, 2026 · 15 categories · 90 passed · 28 warnings · 32 informational

Partial evidence; some observations were unavailable.

Audit score

D

62/100

Mixed

Agentic
88
SEO
62

What we found

28Could be better90Looks good32Informational
  1. 1.Could be better: Your site has no sitemap. see checkA sitemap helps search engines discover your pages.
  2. 2.Could be better: Your page has no preferred URL. see checkA canonical URL tells search engines which version to use.
  3. 3.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
  4. 4.Could be better: Share image dimensions declared: needs attention. see checkComplete link previews make your pages easier to recognize and share.
  5. 5.Could be better: og:url and og:type: needs attention. see checkComplete link previews make your pages easier to recognize and share.

Built with 3 technologies· detected stack

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

How it fits together

  • AstroSite generator
  • CloudflareCDN / edge
InfrastructureType
  • CloudflareCDN / edge
Frameworks and librariesType
  • AstroSite generator
Payments and servicesType
  • Google FontsFont integration

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

Site checks

90 passed · 28 warnings · 0 issues

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

Metadata1Could be better10Looks good

100/100
Could be better: Title lengthTitle "Kalvin Mizzi" is 12 characters, under this audit's 15-character review point (a heuristic, not a Google minimum).

Could be better · Metadata · Review suggested

Observed evidence

Title "Kalvin Mizzi" is 12 characters, under this audit's 15-character review point (a heuristic, not a Google minimum).

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Recommended fix

Make the title descriptive enough to identify the page topic and purpose without padding it to a target count.

Looks good: Page title exists

Looks good · Metadata · Measured on your page

Observed evidence

Title found: "Kalvin Mizzi"

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 "Kalvin Mizzi" 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: "Kalvin Mizzi — founder of SKU.io. Builds companies with fleets of AI agents."

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 76 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 5 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 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 better10Looks good4Informational

70/100
Could be better: Sitemap existsNo sitemap found (checked https://mizzi.com/sitemap.xml → 404).

Could be better · Indexing · Review suggested

Observed evidence

No sitemap found (checked https://mizzi.com/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 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.

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.

Show 10 more checks
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 exists

Looks good · Indexing · Measured on your page

Observed evidence

robots.txt responds with 200.

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: robots.txt doesn't block everything

Looks good · Indexing · Measured on your page

Observed evidence

The audited URL is allowed for Googlebot. No matching group; crawling is permitted by default.

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 (mizzi.com).

Why this matters

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: URLs are readable slugs

Looks good · Indexing · Measured on your page

Observed evidence

URL slugs are readable (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 5 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.

Content1Could be better9Looks good1Informational

100/100
Could be better: Title and H1 agreeTitle ("Kalvin Mizzi") and H1 ("KalvinMizzi") share no significant words.

Could be better · Content · Review suggested

Observed evidence

Title ("Kalvin Mizzi") and H1 ("KalvinMizzi") share no significant words.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Recommended fix

Align them around the same core topic — mixed signals confuse both rankers and readers.

Not measured: ReadabilityFlesch reading ease ≈ 48.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 48.

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 5 sampled page(s). The entered page exposes 1432 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 1432 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 22.3%.

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.

Show 5 more checks
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.

Looks good: Crawled pages aren't near-duplicates

Looks good · Content · Measured on your page

Observed evidence

No near-duplicate main content among 5 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

28 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 5 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 sharing2Could be better5Looks good1Informational

85/100
Could be better: Share image dimensions declaredog:image:width / og:image:height are missing.

Could be better · Social sharing · Review suggested

Observed evidence

og:image:width / og:image:height are 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

Declare them (1200×630 recommended) so platforms render the preview immediately on first share instead of after re-scraping.

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 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: "Kalvin Mizzi"

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: "Kalvin Mizzi — founder of SKU.io. Builds companies with fleets of AI agents."

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 image

Looks good · Social sharing · Measured on your page

Observed evidence

og:image is set: "https://mizzi.com/og-portrait.jpg"

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: Share image loads

Looks good · Social sharing · Measured on your page

Observed evidence

og:image returns 200 (image/jpeg).

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

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

Not measured · Structured data · Not established

Observed evidence

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

  • https://mizzi.com/privacy/
  • https://mizzi.com/how-i-build/
  • https://mizzi.com/snaptiles/
  • https://mizzi.com/2003/
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: "KalvinMizzi"

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 39 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 "KalvinMizzi".

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

39 headings, averaging 2.6 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.

Images4Looks good

100/100
Looks good: Alt text coverage

Looks good · Images · Measured on your page

Observed evidence

All 55 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 55 visible images declare dimensions or are sized by their container.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Modern image formats

Looks good · Images · Measured on your page

Observed evidence

50 of 55 raster images have a WebP/AVIF source or come from a format-negotiating image service.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Lazy loading

Looks good · Images · Measured on your page

Observed evidence

55/55 images are lazy-loaded.

Why this matters

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Mobile1Could be better3Looks good2Informational

76/100
Could be better: Interactive controls have source labels6 of 347 source controls lack a detectable name.

Could be better · Mobile · Measured on your page

Observed evidence

6 of 347 source controls lack a detectable name.

Why this matters

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Recommended fix

Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.

Affected pages (1)

  • https://mizzi.com/2003/
Reference
Not applicable: Responsive image markupNone of the 55 images use srcset.

Not applicable · Mobile · Measured on your page

Observed evidence

None of the 55 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: ARIA references point to source elements

Looks good · Mobile · Measured on your page

Observed evidence

1 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"> (/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: Theme color

Looks good · Branding · Measured on your page

Observed evidence

theme-color is "#050608".

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 time154 msLooks good: goodThe audit received response headers after 154 ms from one test location.
HTML payload size45 KBLooks good: goodThe page's HTML is a lean 45 KB uncompressed.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded1.6 KBLooks good: goodInline styles total 1.6 KB.
Script/stylesheet count—Looks good: good5 total script/style resources — reasonable.
HTML served compressed—Looks good: goodHTML is compressed with br.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight45.5 KBInformational: measured source, not transferred bytes45.5 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

83/100

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

Could be better: HSTS headerNo active Strict-Transport-Security max-age was observed.

Could be better · Security · Review suggested

Observed evidence

No active Strict-Transport-Security max-age 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

Add HSTS (e.g. max-age=63072000; includeSubDomains) so browsers never even try HTTP after the first visit.

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

2 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

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 98 H2/H3 headings are question-shaped.

Could be better · AI answer readiness · Review suggested

Observed evidence

Only 0% of 98 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: "I build companies with fleets of AI agents.…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "I build companies with fleets of AI agents.…"

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 2 of 4 provenance signal types were found: author, date.

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

Observed evidence

Only 2 of 4 provenance signal types were found: author, 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 (3)

  • https://mizzi.com/
  • https://mizzi.com/privacy/
  • https://mizzi.com/how-i-build/
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /privacy/index.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/index.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://mizzi.com/
  • https://mizzi.com/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 density94 concrete figures across 1497 words.

Not measured · AI answer readiness · Not established

Observed evidence

94 concrete figures across 1497 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.

Not applicable · AI answer readiness · Measured on your page

Observed evidence

The homepage answered Accept: text/markdown with text/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

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×10, nav×1, header×1, footer×1.

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 28 words — 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

47 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

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

Could be better: Privacy policy advertising disclosuresFetched privacy policy lacks third-party/vendor disclosure signals.

Could be better · AdSense policy · Published platform ruleCritical

Observed evidence

Fetched privacy policy lacks 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://mizzi.com/privacy/
Reference
Could be better: Sampled publisher-content coverage2/4 editorial pages expose fewer than 250 publisher words; those 4 pages hold 11971 publisher words in total.

Could be better · AdSense policy · Review suggestedCritical

Observed evidence

2/4 editorial pages expose fewer than 250 publisher words; those 4 pages hold 11971 publisher words in total. 1 of the 5 sampled pages is a support or tool page and was excluded from this check.

Why this matters

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Recommended fix

Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.

Affected pages (2)

  • https://mizzi.com/snaptiles/
  • https://mizzi.com/2003/
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: 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://mizzi.com/how-i-build/
Reference
Not measured: First-party contact emailA contact page or form exists, but no public email address was found.

Not measured · AdSense policy · Review suggested

Observed evidence

A contact page or form exists, but no public email address was found.

Why this matters

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Recommended fix

A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.

Not 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: Privacy policy page

Looks good · AdSense policy · Measured on your page

Observed evidence

Privacy policy found: https://mizzi.com/privacy/

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Contact method

Looks good · AdSense policy · Measured on your page

Observed evidence

Contact page found: #contact

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

3/4 editorial pages clear the audit's publisher-content triage threshold. 1 of the 5 sampled pages is a support or tool page and was excluded from this check.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No ads on non-content screens

Looks good · AdSense policy · Published platform rule

Observed evidence

No Google ad code detected on sampled non-content screens.

Why this matters

A publisher review looks for this before it accepts a site. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Reference
Looks good: Tool pages expose explanatory content

Looks good · AdSense policy · Review suggested

Observed evidence

All 4 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 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 7 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
Hostnamemizzi.com
CDN / edgeCloudflare
IP addresses104.21.31.85, 172.67.175.128, 2606:4700:3035::6815:1f55, 2606:4700:3033::ac43:af80
DNS A172.67.175.128 · 104.21.31.85
DNS AAAA2606:4700:3035::6815:1f55 · 2606:4700:3033::ac43:af80
DNS NSbuck.ns.cloudflare.com · nicole.ns.cloudflare.com
DNS MX1 aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com
TLSTLSv1.3TLS_AES_256_GCM_SHA384
Certificate issuerGoogle Trust Services / WE1
Certificate valid untilJan 22 20:06:41 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

1432 publisher words

Page structure

html content

Observed discovery

Depth 0 · 2 incoming links

HTTP 200 · 45.5 KB source

Source interactions

58 controls · 0 unnamed

4 script / 1 stylesheet references

Canonical declaration
Not declared
Schema types
None observed
Outgoing links in sampled graph
/how-i-build · /snaptiles/ · /2003/ · /feed.xml · /privacy/

Routes: / · /privacy · /how-i-build · /snaptiles · /2003

Resource origins 3

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

  • https://mizzi.com/script, stylesheet, image · 92 references · same origin
  • https://thetakeoffseries.com/image · 5 references · cross origin
  • https://fonts.googleapis.com/stylesheet · 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/privacy/allowedDeclared policy for this page.
Googlebotsearch/how-i-build/allowedDeclared policy for this page.
Googlebotsearch/snaptiles/allowedDeclared policy for this page.
Googlebotsearch/2003/allowedDeclared policy for this page.
bingbotsearch/allowedDeclared policy for this page.
bingbotsearch/privacy/allowedDeclared policy for this page.
bingbotsearch/how-i-build/allowedDeclared policy for this page.
bingbotsearch/snaptiles/allowedDeclared policy for this page.
bingbotsearch/2003/allowedDeclared policy for this page.
OAI-SearchBotsearch/allowedDeclared policy for this page.
OAI-SearchBotsearch/privacy/allowedDeclared policy for this page.
OAI-SearchBotsearch/how-i-build/allowedDeclared policy for this page.
OAI-SearchBotsearch/snaptiles/allowedDeclared policy for this page.
OAI-SearchBotsearch/2003/allowedDeclared policy for this page.
PerplexityBotsearch/allowedDeclared policy for this page.
PerplexityBotsearch/privacy/allowedDeclared policy for this page.
PerplexityBotsearch/how-i-build/allowedDeclared policy for this page.
PerplexityBotsearch/snaptiles/allowedDeclared policy for this page.
PerplexityBotsearch/2003/allowedDeclared policy for this page.
Claude-SearchBotsearch/allowedDeclared policy for this page.
Claude-SearchBotsearch/privacy/allowedDeclared policy for this page.
Claude-SearchBotsearch/how-i-build/allowedDeclared policy for this page.
Claude-SearchBotsearch/snaptiles/allowedDeclared policy for this page.
Claude-SearchBotsearch/2003/allowedDeclared policy for this page.
GPTBottraining/allowedDeclared policy for this page.
GPTBottraining/privacy/allowedDeclared policy for this page.
GPTBottraining/how-i-build/allowedDeclared policy for this page.
GPTBottraining/snaptiles/allowedDeclared policy for this page.
GPTBottraining/2003/allowedDeclared policy for this page.
ClaudeBottraining/allowedDeclared policy for this page.
ClaudeBottraining/privacy/allowedDeclared policy for this page.
ClaudeBottraining/how-i-build/allowedDeclared policy for this page.
ClaudeBottraining/snaptiles/allowedDeclared policy for this page.
ClaudeBottraining/2003/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/privacy/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/how-i-build/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/snaptiles/allowedDeclared policy for this page.
Google-Extendedtraining and other Google AI uses/2003/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/privacy/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/how-i-build/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/snaptiles/allowedDeclared policy for this page.
ChatGPT-Useruser-initiated; robots may not apply/2003/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

mizzi.com · observed · 104.21.31.85, 172.67.175.128, 2606:4700:3035::6815:1f55, 2606:4700:3033::ac43:af80

A
172.67.175.128 · 104.21.31.85
AAAA
2606:4700:3035::6815:1f55 · 2606:4700:3033::ac43:af80
CNAME
Unavailable for this exact hostname
NS
buck.ns.cloudflare.com · nicole.ns.cloudflare.com
MX
1 aspmx.l.google.com · 10 alt3.aspmx.l.google.com · 10 alt4.aspmx.l.google.com · 5 alt1.aspmx.l.google.com · 5 alt2.aspmx.l.google.com
CAA
Unavailable for this exact hostname

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Google Trust Services / WE1

Certificate valid until: Jan 22 20:06:41 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.

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://mizzi.com/
  • https://mizzi.com/privacy/
  • https://mizzi.com/how-i-build/
  • https://mizzi.com/snaptiles/
  • https://mizzi.com/2003/