Website report

Visit sitehttps://emayler.com/

Real mailboxes on your own domain, a web inbox you will enjoy, and a dashboard to set everything up. Unlimited aliases on paid plans, one flat account price, no per-user fees.

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

Analysed Nov 16, 2026 · 15 categories · 121 passed · 7 warnings · 22 informational

Audit score

A

100/100

Strong

Agentic
100
SEO
100

What we found

7Could be better121Looks good22Informational
  1. 1.Could be better: Meta description length: needs attention. see checkClear titles and descriptions help people choose your pages in search.
  2. 2.Could be better: Your content security policy needs work. see checkThis policy limits which scripts and resources can run on your website.
  3. 3.Could be better: Your introduction needs a clearer explanation. see checkA clear opening helps visitors and AI assistants understand what you offer.
  4. 4.Could be better: Freshness signals: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.
  5. 5.Could be better: Machine-readable provenance signals: needs attention. see checkClear, accessible information helps AI assistants understand and cite your website.

Built with 2 technologies· detected stack

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

How it fits together

  • Next.jsFramework
  • CaddyServer
InfrastructureType
  • CaddyServer
Frameworks and librariesType
  • Next.jsFramework

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

Site checks

121 passed · 7 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: Meta description lengthDescription is 175 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

Could be better · Metadata · Review suggested

Observed evidence

Description is 175 characters, over this audit's 160-character review point (a preview heuristic, not a Google limit).

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

Front-load the useful summary because Google may generate or truncate snippets by query and device.

Looks good: Page title exists

Looks good · Metadata · Measured on your page

Observed evidence

Title found: "Emayler - Custom-domain email hosting with a real inbox"

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 55 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 "Emayler - Custom-domain email hosting with a real inbox" 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: "Real mailboxes on your own domain, a web inbox you will enjoy, and a dashboard to set ever…"

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Titles unique across pages

Looks good · Metadata · Measured on your page

Observed evidence

All 9 indexable sampled pages have distinct titles.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Show 5 more checks
Looks good: Homepage isn't noindexed

Looks good · Metadata · Measured on your page

Observed evidence

No blocking robots meta tag on the homepage.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Character encoding declared

Looks good · Metadata · Measured on your page

Observed evidence

UTF-8 declared in the Content-Type header and a meta tag.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: HTML5 doctype

Looks good · Metadata · Measured on your page

Observed evidence

HTML5 doctype declared.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No meta keywords tag

Looks good · Metadata · Measured on your page

Observed evidence

No obsolete meta keywords tag.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Valid metadata order in <head>

Looks good · Metadata · Measured on your page

Observed evidence

No invalid element interrupts metadata in <head>.

Why this matters

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Indexing16Looks good

100/100
Looks good: Single canonical declaration

Looks good · Indexing · Measured on your page

Observed evidence

One canonical declaration found.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Noindex and canonical agree

Looks good · Indexing · Measured on your page

Observed evidence

No conflicting noindex and cross-page canonical instructions.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: No meta-refresh redirect

Looks good · Indexing · Measured on your page

Observed evidence

No meta-refresh redirect.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: No soft-404 response

Looks good · Indexing · Measured on your page

Observed evidence

No soft-404 pattern on sampled HTTP 200 pages.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Canonical target integrity

Looks good · Indexing · Measured on your page

Observed evidence

Canonical is a valid https URL. Its host is checked by the canonical consistency check.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Sampled URLs have aligned indexability signals

Looks good · Indexing · Measured on your page

Observed evidence

Indexability signals align across 9 sampled URL(s).

Why this matters

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

Recommended fix

Nothing to do here.

Show 10 more checks
Looks good: robots.txt exists

Looks good · Indexing · Measured on your page

Observed evidence

robots.txt responds with 200.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: robots.txt doesn't block everything

Looks good · Indexing · Measured on your page

Observed evidence

The audited URL is allowed for Googlebot. Most specific matching path; allow wins equal-length conflicts.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Sitemap exists

Looks good · Indexing · Measured on your page

Observed evidence

Sitemap found at https://emayler.com/sitemap.xml.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Sitemap parses and lists URLs

Looks good · Indexing · Measured on your page

Observed evidence

Sitemap lists 25 same-origin URLs.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Sitemap declared in robots.txt

Looks good · Indexing · Measured on your page

Observed evidence

robots.txt declares the sitemap.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Canonical URL set

Looks good · Indexing · Measured on your page

Observed evidence

Canonical set: https://emayler.com/

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Canonical is absolute and self-referencing

Looks good · Indexing · Measured on your page

Observed evidence

Canonical is absolute and points at this page.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: www vs apex consistency

Looks good · Indexing · Measured on your page

Observed evidence

Hostname is used consistently (emayler.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 (21 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 9 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 ≈ 53.

Not measured · Content · Not established

Observed evidence

Flesch reading ease ≈ 53.

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 9 sampled page(s). The entered page exposes 681 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 681 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 10.6%.

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: domain, email.

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

11 outbound link(s) present.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Discovery copy is distinct across sampled pages

Looks good · Content · Measured on your page

Observed evidence

No repeated description, H1, or publisher copy across 9 sampled pages.

Why this matters

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Social sharing8Looks good

100/100
Looks good: Open Graph title

Looks good · Social sharing · Measured on your page

Observed evidence

og:title: "Emayler - Custom-domain email hosting with a real inbox"

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: "Real mailboxes on your own domain, a web inbox you will enjoy, and a dashboard to set ever…"

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://emayler.com/og.png"

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/png).

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 dimensions declared

Looks good · Social sharing · Measured on your page

Observed evidence

Dimensions declared: 1200×630.

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: og:url and og:type

Looks good · Social sharing · Measured on your page

Observed evidence

og:url and og:type ("website") are set.

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.

Looks good: og:site_name

Looks good · Social sharing · Measured on your page

Observed evidence

og:site_name: "Emayler".

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 data4Looks good1Informational

100/100
Not measured: Breadcrumb schema on inner pagesNone of the 8 crawled inner pages declare BreadcrumbList schema.

Not measured · Structured data · Not established

Observed evidence

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

  • https://emayler.com/pricing
  • https://emayler.com/compare
  • https://emayler.com/docs
  • https://emayler.com/custom-domain-email
  • https://emayler.com/business-email
  • https://emayler.com/legal
  • https://emayler.com/docs/dashboard/domains
  • https://emayler.com/docs/troubleshooting
Reference
Looks good: JSON-LD present

Looks good · Structured data · Measured on your page

Observed evidence

1 JSON-LD block(s) found on the homepage.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: JSON-LD parses

Looks good · Structured data · Measured on your page

Observed evidence

All 3 JSON-LD block(s) parse cleanly.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Organization or WebSite schema

Looks good · Structured data · Measured on your page

Observed evidence

Identity schema present: WebSite, Organization.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Content-specific schema

Looks good · Structured data · Measured on your page

Observed evidence

Content schema found: FAQPage.

Why this matters

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Headings7Looks good

100/100
Looks good: H1 exists

Looks good · Headings · Measured on your page

Observed evidence

H1 found: "Your domain. Your email. One flat bill."

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 10 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 "Your domain. Your email. One flat bill.".

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

10 headings, averaging 6.2 words — descriptive.

Why this matters

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Content is sectioned with H2s

Looks good · Headings · Measured on your page

Observed evidence

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

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

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

Mobile4Looks good2Informational

100/100
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

Not measured · Mobile · Not established

Observed evidence

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

Why this matters

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

Recommended fix

Check computed font sizes in a browser across mobile widths.

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

Not applicable · Mobile · Measured on your page

Observed evidence

No ARIA ID references found in the sampled HTML.

Why this matters

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Recommended fix

Verify rendered accessibility separately.

Looks good: Viewport meta tag

Looks good · Mobile · Measured on your page

Observed evidence

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

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: Responsive image markup

Looks good · Mobile · Measured on your page

Observed evidence

2/8 images ship responsive srcset variants.

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

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

Why this matters

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Language2Looks good1Informational

100/100
Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.

Not applicable · Language · Measured on your page

Observed evidence

No hreflang tags — fine for single-language sites.

Why this matters

The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.

Recommended fix

Only add hreflang if you publish the same content in multiple languages/regions.

Looks good: html lang attribute

Looks good · Language · Measured on your page

Observed evidence

Language declared: lang="en".

Why this matters

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Declared language matches content

Looks good · Language · Measured on your page

Observed evidence

Declared language (en) matches detected content language.

Why this matters

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Branding3Looks good1Informational

100/100
Not measured: Web app manifestNo web manifest linked.

Not measured · Branding · Not established

Observed evidence

No web manifest linked.

Why this matters

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

Recommended fix

Optional, but a manifest.json enables install prompts and better mobile integration.

Looks good: Favicon

Looks good · Branding · Measured on your page

Observed evidence

Favicon declared via <link rel="icon"> (/favicon.ico?favicon.3fw7n47wfgwdq.ico).

Why this matters

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Apple touch icon

Looks good · Branding · Measured on your page

Observed evidence

apple-touch-icon is declared.

Why this matters

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Theme color

Looks good · Branding · Measured on your page

Observed evidence

theme-color is "#f6f8f7".

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 time317 msLooks good: goodThe audit received response headers after 317 ms from one test location.
HTML payload size116 KBLooks good: goodThe page's HTML is 116 KB uncompressed: acceptable, though under 100 KB is a good target for content pages.
No render-blocking head scripts—Looks good: goodNo synchronous render-blocking scripts in <head>.
Inline styles are bounded0.0 KBLooks good: goodInline styles total 0.0 KB.
Script/stylesheet count—Looks good: good12 total script/style resources — reasonable.
HTML served compressed—Looks good: goodHTML is compressed with gzip.
Iframe usage—Looks good: goodNo iframes.
Source HTML weight115.6 KBInformational: measured source, not transferred bytes115.6 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; includeSubDomains; preload.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Frame embedding protection

Looks good · Security · Measured on your page

Observed evidence

Response headers restrict cross-origin framing (frame-ancestors 'none').

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Referrer policy

Looks good · Security · Measured on your page

Observed evidence

Referrer-Policy is strict-origin-when-cross-origin.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Browser feature permissions

Looks good · Security · Measured on your page

Observed evidence

A Permissions-Policy disables at least one sensitive browser feature.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Review remaining features and allow only origins the application needs.

Looks good: X-Content-Type-Options

Looks good · Security · Measured on your page

Observed evidence

nosniff is set.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: No mixed content

Looks good · Security · Measured on your page

Observed evidence

No insecure subresources detected.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Server technology disclosure

Looks good · Security · Measured on your page

Observed evidence

No X-Powered-By disclosure.

Why this matters

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Recommended fix

Nothing to do here.

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: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Custom-domain email, without per-user pricing.…"

Could be better · AI answer readiness · Review suggested

Observed evidence

The opening paragraph doesn't define what the site/topic is: "Custom-domain email, without per-user pricing.…"

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

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

Observed evidence

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

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

  • https://emayler.com/
  • https://emayler.com/pricing
  • https://emayler.com/compare
  • https://emayler.com/docs
  • https://emayler.com/custom-domain-email
  • https://emayler.com/business-email
  • https://emayler.com/legal
  • https://emayler.com/docs/dashboard/domains
  • https://emayler.com/docs/troubleshooting
Not measured: Authored, dated articlesNo Article/BlogPosting schema found.

Not measured · AI answer readiness · Not established

Observed evidence

No Article/BlogPosting schema found.

Why this matters

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

Recommended fix

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

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

Not measured · AI answer readiness · Not established

Observed evidence

41 concrete figures across 797 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: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.

Not applicable · AI answer readiness · Measured on your page

Observed evidence

No OpenAPI interface was advertised by sampled HTML.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.

Recommended fix

An API is optional. Add a service-desc link if you already publish a machine-readable API specification.

Looks good: llms.txt

Looks good · AI answer readiness · Measured on your page

Observed evidence

llms.txt exists (1799 chars of markdown).

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: llms-full.txt

Looks good · AI answer readiness · Measured on your page

Observed evidence

llms-full.txt is published.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: AI crawler access

Looks good · AI answer readiness · Measured on your page

Observed evidence

The audited URL is allowed for evaluated answer-search crawlers.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: FAQ/QA schema

Looks good · AI answer readiness · Measured on your page

Observed evidence

FAQ/QA schema found.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Semantic HTML structure

Looks good · AI answer readiness · Measured on your page

Observed evidence

Semantic structure present: main×1, section×6, 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: Question-style headings

Looks good · AI answer readiness · Measured on your page

Observed evidence

25% of 60 subheadings are question-shaped.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Answers lead the section

Looks good · AI answer readiness · Measured on your page

Observed evidence

Paragraphs get to the point without preamble.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Content is chunkable

Looks good · AI answer readiness · Measured on your page

Observed evidence

Paragraphs average 11 words, tables 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

56 outbound reference(s) across crawled pages.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Consistent brand entity

Looks good · AI answer readiness · Measured on your page

Observed evidence

Brand declared: og:site_name "Emayler" + identity schema.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Description reads as a liftable summary

Looks good · AI answer readiness · Measured on your page

Observed evidence

Meta description works as a standalone summary.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Entity identity agrees across signals

Looks good · AI answer readiness · Measured on your page

Observed evidence

The site is consistently named "Emayler" and 6 identity URL(s) stay on emayler.com.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Question headings have concise answers

Looks good · AI answer readiness · Measured on your page

Observed evidence

14 concise answer block(s) follow 15 question-shaped heading(s).

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: llms.txt follows the spec

Looks good · AI answer readiness · Published platform rule

Observed evidence

llms.txt has an H1, a summary, 3 section(s) and 15 link(s).

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: Markdown copies of pages

Looks good · AI answer readiness · Measured on your page

Observed evidence

2 of 3 probed URLs returned markdown.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

Looks good: Accept: text/markdown negotiation

Looks good · AI answer readiness · Measured on your page

Observed evidence

The homepage answers Accept: text/markdown with markdown.

Why this matters

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Recommended fix

Nothing to do here.

AdSense readinessOptional

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

Could be better: Sampled publisher-content coverage2/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 2904 publisher words in total.

Could be better · AdSense policy · Review suggestedCritical

Observed evidence

2/8 editorial pages expose fewer than 250 publisher words; those 8 pages hold 2904 publisher words in total. 1 of the 9 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://emayler.com/compare
  • https://emayler.com/docs
Reference
Could be better: About pageNo about page found.

Could be better · AdSense policy · Review suggested

Observed evidence

No about page found.

Why this matters

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

Recommended fix

Add an About page that identifies the publisher, site purpose, and relevant experience. This supports content transparency but is not a standalone AdSense requirement.

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: ads.txtNo ads.txt yet.

Not measured · AdSense policy · Not established

Observed evidence

No ads.txt yet.

Why this matters

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

Recommended fix

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

Reference
Not applicable: Article-style content existsNo article/blog-style pages detected among crawled pages.

Not applicable · AdSense policy · Measured on your page

Observed evidence

No article/blog-style pages detected among crawled pages.

Why this matters

A publisher review looks for this before it accepts a site. This check does not apply to the features observed in this sample.

Recommended fix

No action is required solely because articles are absent. For tool or directory sites, make the unique publisher value and explanation crawlable on each relevant screen.

Not measured: Domain age & historyDomain age isn't visible from the site itself.

Not measured · AdSense policy · Not established

Observed evidence

Domain age isn't visible from the site itself.

Why this matters

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

Recommended fix

Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.

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

Not measured · AdSense policy · Review suggested

Observed evidence

No editorial pages were identified in the crawl sample.

Why this matters

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

Recommended fix

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

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

Not measured · AdSense policy · Review suggested

Observed evidence

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

Why this matters

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

Recommended fix

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

Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.

Not measured · AdSense policy · Not established

Observed evidence

No article-shaped page was found on this site, so there is nothing to read.

Why this matters

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

Recommended fix

Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.

Reference
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.

Not measured · AdSense policy · Not established

Observed evidence

No article-shaped page was found on this site, so there is nothing to read.

Why this matters

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

Recommended fix

Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.

Reference
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.

Not measured · AdSense policy · Not established

Observed evidence

No article-shaped page was found on this site, so there is nothing to read.

Why this matters

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

Recommended fix

Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.

Reference
Looks good: Privacy policy page

Looks good · AdSense policy · Measured on your page

Observed evidence

Privacy policy found: /legal/privacy

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Terms page

Looks good · AdSense policy · Measured on your page

Observed evidence

Terms page found: /legal/terms

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Contact method

Looks good · AdSense policy · Measured on your page

Observed evidence

Contact email found: mailto:support@help.emayler.com

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: First-party contact email

Looks good · AdSense policy · Measured on your page

Observed evidence

First-party contact email found: support@help.emayler.com.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Thin page share

Looks good · AdSense policy · Review suggested

Observed evidence

8/8 editorial pages clear the audit's publisher-content triage threshold. 1 of the 9 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 9 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 8 substantial sampled page(s).

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Publisher content exists in source HTML

Looks good · AdSense policy · Measured on your page

Observed evidence

No empty client-rendered publisher shell in the crawl sample.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Clear navigation

Looks good · AdSense policy · Measured on your page

Observed evidence

Navigation present with 6 links.

Why this matters

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

Recommended fix

Nothing to do here.

Show 4 more checks
Looks good: No "coming soon" or placeholder pages

Looks good · AdSense policy · Measured on your page

Observed evidence

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

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Site language is AdSense-supported

Looks good · AdSense policy · Measured on your page

Observed evidence

Language "en" is AdSense-supported.

Why this matters

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

Recommended fix

Nothing to do here.

Looks good: Existing ad scripts

Looks good · AdSense policy · Measured on your page

Observed evidence

No competing ad scripts on the page.

Why this matters

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

Recommended fix

Nothing to do here.

Hosting and infrastructure

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

Hosting and infrastructure observations
Hostnameemayler.com
ServerCaddy
IP addresses16.174.3.176
DNS A16.174.3.176
DNS NSns-139.awsdns-17.com · ns-875.awsdns-45.net · ns-1780.awsdns-30.co.uk · ns-1321.awsdns-37.org
DNS MX10 mx1.emayler.com
DNS CAA{"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"sectigo.com"} · {"critical":0,"type":"CAA","issuewild":";"}
TLSTLSv1.3TLS_AES_128_GCM_SHA256
Certificate issuerLet's Encrypt / YE2
Certificate valid untilDec 27 10:30:00 2026 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

681 publisher words

Page structure

html content

Observed discovery

Depth 0 · 8 incoming links

HTTP 200 · 115.6 KB source

Source interactions

56 controls · 0 unnamed

11 script / 1 stylesheet references

Canonical declaration
https://emayler.com/
Schema types
Organization, WebSite, FAQPage, Question, Answer
Outgoing links in sampled graph
/pricing · /compare · /docs · /docs/dashboard/domains · /docs/troubleshooting · /docs/dashboard/migration · /docs/quickstart · /compare/google-workspace · /compare/microsoft-365 · /custom-domain-email · /business-email · /docs/dashboard/aliases · /docs/sending · /compare/proton-mail · /compare/fastmail · /legal · /legal/privacy · /legal/terms · /legal/acceptable-use · /legal/dpa · /legal/subprocessors · /legal/billing · /legal/cookies · /legal/reporting

Routes: / · /pricing · /compare · /docs · /custom-domain-email · /business-email · /legal

Resource origins 1

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

  • https://emayler.com/stylesheet, script, image · 127 references · same 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/allowedallow: /
Googlebotsearch/pricingallowedallow: /
Googlebotsearch/compareallowedallow: /
Googlebotsearch/docsallowedallow: /
Googlebotsearch/custom-domain-emailallowedallow: /
Googlebotsearch/business-emailallowedallow: /
Googlebotsearch/legalallowedallow: /
Googlebotsearch/docs/dashboard/domainsallowedallow: /
Googlebotsearch/docs/troubleshootingallowedallow: /
bingbotsearch/allowedallow: /
bingbotsearch/pricingallowedallow: /
bingbotsearch/compareallowedallow: /
bingbotsearch/docsallowedallow: /
bingbotsearch/custom-domain-emailallowedallow: /
bingbotsearch/business-emailallowedallow: /
bingbotsearch/legalallowedallow: /
bingbotsearch/docs/dashboard/domainsallowedallow: /
bingbotsearch/docs/troubleshootingallowedallow: /
OAI-SearchBotsearch/allowedallow: /
OAI-SearchBotsearch/pricingallowedallow: /
OAI-SearchBotsearch/compareallowedallow: /
OAI-SearchBotsearch/docsallowedallow: /
OAI-SearchBotsearch/custom-domain-emailallowedallow: /
OAI-SearchBotsearch/business-emailallowedallow: /
OAI-SearchBotsearch/legalallowedallow: /
OAI-SearchBotsearch/docs/dashboard/domainsallowedallow: /
OAI-SearchBotsearch/docs/troubleshootingallowedallow: /
PerplexityBotsearch/allowedallow: /
PerplexityBotsearch/pricingallowedallow: /
PerplexityBotsearch/compareallowedallow: /
PerplexityBotsearch/docsallowedallow: /
PerplexityBotsearch/custom-domain-emailallowedallow: /
PerplexityBotsearch/business-emailallowedallow: /
PerplexityBotsearch/legalallowedallow: /
PerplexityBotsearch/docs/dashboard/domainsallowedallow: /
PerplexityBotsearch/docs/troubleshootingallowedallow: /
Claude-SearchBotsearch/allowedallow: /
Claude-SearchBotsearch/pricingallowedallow: /
Claude-SearchBotsearch/compareallowedallow: /
Claude-SearchBotsearch/docsallowedallow: /
Claude-SearchBotsearch/custom-domain-emailallowedallow: /
Claude-SearchBotsearch/business-emailallowedallow: /
Claude-SearchBotsearch/legalallowedallow: /
Claude-SearchBotsearch/docs/dashboard/domainsallowedallow: /
Claude-SearchBotsearch/docs/troubleshootingallowedallow: /
GPTBottraining/allowedallow: /
GPTBottraining/pricingallowedallow: /
GPTBottraining/compareallowedallow: /
GPTBottraining/docsallowedallow: /
GPTBottraining/custom-domain-emailallowedallow: /
GPTBottraining/business-emailallowedallow: /
GPTBottraining/legalallowedallow: /
GPTBottraining/docs/dashboard/domainsallowedallow: /
GPTBottraining/docs/troubleshootingallowedallow: /
ClaudeBottraining/allowedallow: /
ClaudeBottraining/pricingallowedallow: /
ClaudeBottraining/compareallowedallow: /
ClaudeBottraining/docsallowedallow: /
ClaudeBottraining/custom-domain-emailallowedallow: /
ClaudeBottraining/business-emailallowedallow: /
ClaudeBottraining/legalallowedallow: /
ClaudeBottraining/docs/dashboard/domainsallowedallow: /
ClaudeBottraining/docs/troubleshootingallowedallow: /
Google-Extendedtraining and other Google AI uses/allowedallow: /
Google-Extendedtraining and other Google AI uses/pricingallowedallow: /
Google-Extendedtraining and other Google AI uses/compareallowedallow: /
Google-Extendedtraining and other Google AI uses/docsallowedallow: /
Google-Extendedtraining and other Google AI uses/custom-domain-emailallowedallow: /
Google-Extendedtraining and other Google AI uses/business-emailallowedallow: /
Google-Extendedtraining and other Google AI uses/legalallowedallow: /
Google-Extendedtraining and other Google AI uses/docs/dashboard/domainsallowedallow: /
Google-Extendedtraining and other Google AI uses/docs/troubleshootingallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/allowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/pricingallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/compareallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/docsallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/custom-domain-emailallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/business-emailallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/legalallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/docs/dashboard/domainsallowedallow: /
ChatGPT-Useruser-initiated; robots may not apply/docs/troubleshootingallowedallow: /
Advertised APIs and machine interfaces
  • documentation · declared

    https://emayler.com/docs

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/domains

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/troubleshooting

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/migration

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/quickstart

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/aliases

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/sending

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/billing

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/account

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/mailboxes

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/inbox

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/settings

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/dashboard/api-keys

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/quickstart

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/domains

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/mailboxes

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/messages

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/imports

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/api/billing

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/mcp

    This interface was advertised; its runtime behavior remains unverified.

  • documentation · declared

    https://emayler.com/docs/mcp/tools

    This interface was advertised; its runtime behavior remains unverified.

Public DNS and TLS endpoint

emayler.com · observed · 16.174.3.176

A
16.174.3.176
AAAA
Unavailable for this exact hostname
CNAME
Unavailable for this exact hostname
NS
ns-139.awsdns-17.com · ns-875.awsdns-45.net · ns-1780.awsdns-30.co.uk · ns-1321.awsdns-37.org
MX
10 mx1.emayler.com
CAA
{"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"sectigo.com"} · {"critical":0,"type":"CAA","issuewild":";"}

TLS: TLSv1.3

Certificate validation passed for the observed endpoint.

Issuer: Let's Encrypt / YE2

Certificate valid until: Dec 27 10:30:00 2026 GMT

PageSpeed measurement

Loading the PageSpeed panel…

Growth resources

Loading growth resources…

Where to take this site next

Follow-on work suggested by the observations above.

  1. 01

    Optimize for AI answers (GEO)

    Classic SEO checks are covered — if AI-answer discovery matters, review how ChatGPT, Claude, and Perplexity can access and represent your content. This audit does not measure or guarantee citations, rankings, traffic, or agent success.

  2. 02

    Check AdSense readiness

    Review policy pages and content volume before applying. This audit cannot predict or guarantee 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://emayler.com/
  • https://emayler.com/pricing
  • https://emayler.com/compare
  • https://emayler.com/docs
  • https://emayler.com/custom-domain-email
  • https://emayler.com/business-email
  • https://emayler.com/legal
  • https://emayler.com/docs/dashboard/domains
  • https://emayler.com/docs/troubleshooting