Catalog / mailparse.dev
77

SEO audit for mailparse.dev

MailParse - Turn inbound emails into structured JSON instantly

saasNext.js

Health 77/100 (good) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Developer-focused SaaS that provides instant email addresses, receives inbound emails, parses MIME into structured JSON, and delivers via webhook or REST polling API.

50
pages crawled
48
indexable pages
2
errors
26
warnings
360
notices
0
orphan pages
1
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Crawlability 98 1 0 1
Links 98 1 0 0
Canonical 95 0 9 9
Titles 95 0 9 0
Content 98 0 3 76
AI Content 99 0 2 0
Budget 99 0 2 0
Indexability 99 0 1 0
Agent Readiness 100 0 0 23
Cache 100 0 0 16
Meta Description 100 0 0 12
Performance 100 0 0 64
Security 100 0 0 49
Social 100 0 0 21
Structured Data 100 0 0 89
Findings

Errors (2 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 1 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 1 occurrence(s)

Warnings (6 rules)

warning Unfilled template or prompt-leak text

Rule ai.prompt_leak · AI Content · 2 occurrence(s)

warning robots.txt-disallowed URL receives internal links (crawl-budget leak)

Rule budget.disallow_linked · Budget · 2 occurrence(s)

  • https://www.mailparse.dev/auth/login — internal links point to https://www.mailparse.dev/auth/login, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://www.mailparse.dev/, https://www.mailparse.dev/privacy, https://www.mailparse.dev/terms.
  • https://www.mailparse.dev/auth/signup — internal links point to https://www.mailparse.dev/auth/signup, which robots.txt disallows for Googlebot — Googlebot discovers the URL, checks robots, then rejects it without indexing, wasting crawl budget and losing the link equity. Remove the internal links, or use noindex instead of Disallow if the page should be fetchable. Linked from: https://www.mailparse.dev/, https://www.mailparse.dev/learn, https://www.mailparse.dev/privacy.

warning Interior page canonicalizes to the homepage

Rule canonical.points_to_homepage · Canonical · 9 occurrence(s)

  • https://www.mailparse.dev/apps — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/brand-facts — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/contact — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/guides — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026 — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/learn — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/privacy — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/terms — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.
  • https://www.mailparse.dev/tools — this interior page canonicalizes to the homepage (https://www.mailparse.dev/) — Google will treat the homepage as authoritative and drop this page from search. Point the canonical at the page's own URL.

warning Thin content (low word count)

Rule content.thin · Content · 3 occurrence(s)

warning Page is noindex

Rule index.noindex · Indexability · 1 occurrence(s)

warning Title likely truncated in SERP (too wide)

Rule title.too_long · Titles · 9 occurrence(s)

Notices (18 rules)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 2 occurrence(s)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 20 occurrence(s)

notice Page served uncached (no-store/private or CDN bypass)

Rule cache.not_cacheable · Cache · 16 occurrence(s)

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 9 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 4 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 23 occurrence(s)

  • https://www.mailparse.dev/apps — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/brand-facts — this page reads as very difficult (Flesch Reading Ease 9, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026 — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn — this page reads as difficult (Flesch Reading Ease 38, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound — this page reads as difficult (Flesch Reading Ease 40, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound — this page reads as difficult (Flesch Reading Ease 30, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders — this page reads as difficult (Flesch Reading Ease 41, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers — this page reads as very difficult (Flesch Reading Ease 28, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders — this page reads as difficult (Flesch Reading Ease 46, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring — this page reads as difficult (Flesch Reading Ease 38, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/email-infrastructure/email-archival — this page reads as difficult (Flesch Reading Ease 38, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/email-infrastructure/notification-routing — this page reads as difficult (Flesch Reading Ease 44, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers — this page reads as difficult (Flesch Reading Ease 46, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/use-cases/email-archival — this page reads as difficult (Flesch Reading Ease 40, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders — this page reads as difficult (Flesch Reading Ease 50, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers — this page reads as difficult (Flesch Reading Ease 39, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers — this page reads as difficult (Flesch Reading Ease 44, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/tools — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/tools/dkim-record-generator — this page reads as difficult (Flesch Reading Ease 50, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/tools/email-deliverability-test — this page reads as difficult (Flesch Reading Ease 45, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/tools/email-signature-generator — this page reads as difficult (Flesch Reading Ease 47, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • https://www.mailparse.dev/tools/email-subject-line-tester — this page reads as difficult (Flesch Reading Ease 49, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Article page has no publication date (freshness / E-E-A-T)

Rule eeat.no_date · Content · 1 occurrence(s)

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 48 occurrence(s)

notice Meta description too long

Rule meta_desc.too_long · Meta Description · 12 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 21 occurrence(s)

notice No ETag header (no conditional GET for unchanged pages)

Rule perf.no_etag · Performance · 16 occurrence(s)

notice No Last-Modified header (no conditional GET for unchanged pages)

Rule perf.no_last_modified · Performance · 48 occurrence(s)

  • https://www.mailparse.dev/ — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/apps — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/brand-facts — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/contact — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/guides — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026 — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/learn — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/privacy — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/terms — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/bimi-record-checker — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/dkim-checker — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/dkim-record-generator — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/dmarc-checker — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/dmarc-record-generator — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/dns-lookup-tool — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-authentication-scorecard — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-blacklist-checker — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-bounce-code-lookup — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-deliverability-test — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-header-analyzer — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-list-deduplicator — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.
  • https://www.mailparse.dev/tools/email-regex-validator — the response carries no Last-Modified header — Googlebot can't send an If-Modified-Since request, so it re-downloads the full page body on every crawl even when nothing changed. Emit Last-Modified (or an ETag) on stable pages to enable 304 Not Modified responses.

notice Blocked by robots.txt

Rule robots.blocked · Crawlability · 1 occurrence(s)

notice Article schema missing recommended properties (Top Stories / image carousel)

Rule schema.article_incomplete · Structured Data · 16 occurrence(s)

notice Deprecated schema type with no Google rich result

Rule schema.deprecated_type · Structured Data · 48 occurrence(s)

notice FAQPage structured data (rich result removed May 2026)

Rule schema.faq_deprecated · Structured Data · 25 occurrence(s)

  • https://www.mailparse.dev/ — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026 — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/bimi-record-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/dkim-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/dkim-record-generator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/dmarc-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/dmarc-record-generator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/dns-lookup-tool — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-authentication-scorecard — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-blacklist-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-bounce-code-lookup — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-deliverability-test — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-header-analyzer — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-list-deduplicator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-regex-validator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-signature-generator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-spam-score-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-subject-line-tester — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/email-warmup-plan-calculator — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/eml-viewer — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/mbox-viewer — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/mx-record-lookup — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/smtp-tester — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/spf-record-checker — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.
  • https://www.mailparse.dev/tools/webhook-tester — FAQPage structured data is present — Google removed FAQ rich results on 7 May 2026 (except for authoritative government/health sites). The markup is harmless but earns no SERP enhancement; remove it during template maintenance.

notice Missing recommended security headers

Rule security.missing_headers · Security · 49 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://www.mailparse.dev/
MailParse - Turn inbound emails into structured JSON instantly		 200 yes 924 44
https://www.mailparse.dev/tools
Free Email Tools | MailParse		 200 yes 513 28
https://www.mailparse.dev/guides
Guides | MailParse | MailParse		 200 yes 40 6
https://www.mailparse.dev/privacy
Privacy Policy | MailParse | MailParse		 200 yes 644 6
https://www.mailparse.dev/terms
Terms of Service | MailParse | MailParse		 200 yes 885 6
https://www.mailparse.dev/apps
Our Apps | MailParse		 200 yes 330 5
https://www.mailparse.dev/contact
MailParse - Turn inbound emails into structured JSON instantly		 200 yes 86 5
https://www.mailparse.dev/learn
Learn | MailParse		 200 yes 3382 5
https://www.mailparse.dev/tools/spf-record-checker
Free SPF Record Checker - Validate SPF Records | MailParse		 200 yes 261 18
https://www.mailparse.dev/tools/email-header-analyzer
Email Header Analyzer - Free Email Trace Tool | MailParse | MailParse		 200 yes 391 16
https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026
Best Inbound Email Parsing APIs in 2026 | MailParse		 200 yes 383 1
https://www.mailparse.dev/tools/dkim-checker
DKIM Checker - Free DKIM Record Validator | MailParse | MailParse		 200 yes 560 14
https://www.mailparse.dev/tools/dmarc-record-generator
DMARC Record Generator - Free Email Security Tool | MailParse | MailParse		 200 yes 693 9
https://www.mailparse.dev/tools/mx-record-lookup
Free MX Record Lookup - Check Mail Server Records | MailParse | MailParse		 200 yes 509 8
https://www.mailparse.dev/tools/email-bounce-code-lookup
Free Email Bounce Code Lookup - SMTP Error Code Tool | MailParse		 200 yes 793 5
https://www.mailparse.dev/tools/dmarc-checker
Free DMARC Checker - DMARC Record Lookup & Policy Analyzer | MailParse		 200 yes 486 4
https://www.mailparse.dev/tools/email-spam-score-checker
Free Email Spam Score Checker - Test Spam Trigger Words | MailParse | MailParse		 200 yes 659 4
https://www.mailparse.dev/tools/email-list-deduplicator
Free Email List Deduplicator - Remove Duplicate Emails Online | MailParse		 200 yes 645 4
https://www.mailparse.dev/tools/email-blacklist-checker
Free Email Blacklist Checker - Check IP & Domain Blacklists | MailParse | MailParse		 200 yes 681 4
https://www.mailparse.dev/tools/email-deliverability-test
Free Email Deliverability Test - Inbox Readiness Checker | MailParse		 200 yes 548 3
https://www.mailparse.dev/tools/email-subject-line-tester
Email Subject Line Tester - Free Email Tool | MailParse | MailParse		 200 yes 499 3
https://www.mailparse.dev/tools/email-regex-validator
Free Email Regex Validator - Test Email Validation Patterns Online | MailParse		 200 yes 804 2
https://www.mailparse.dev/tools/eml-viewer
Free EML Viewer Online - Open and Inspect .eml Files | MailParse		 200 yes 563 2
https://www.mailparse.dev/tools/email-warmup-plan-calculator
Free Email Warmup Plan Calculator - Domain & IP Warmup Schedule | MailParse | MailParse		 200 yes 1204 2
https://www.mailparse.dev/tools/email-authentication-scorecard
Free Email Authentication Scorecard - SPF, DKIM, DMARC, BIMI Check | MailParse		 200 yes 889 4
https://www.mailparse.dev/tools/dkim-record-generator
DKIM Record Generator - Free DKIM TXT Record Tool | MailParse		 200 yes 517 1
https://www.mailparse.dev/tools/dns-lookup-tool
Free DNS Lookup Tool - Check DNS Records Online | MailParse | MailParse		 200 yes 387 1
https://www.mailparse.dev/tools/email-signature-generator
Free Email Signature Generator Online | MailParse		 200 yes 473 1
https://www.mailparse.dev/tools/mbox-viewer
Free MBOX Viewer Online - Open and Inspect Mailbox Files | MailParse		 200 yes 582 1
https://www.mailparse.dev/tools/smtp-tester
Free SMTP Tester - Check Mail Server Connection Online | MailParse | MailParse		 200 yes 434 1
https://www.mailparse.dev/tools/webhook-tester
Free Webhook Tester - Inspect and Replay Webhook Payloads | MailParse		 200 yes 544 1
https://www.mailparse.dev/tools/bimi-record-checker
Free BIMI Record Checker - Validate BIMI DNS Records | MailParse		 200 yes 551 2
https://www.mailparse.dev/brand-facts
About MailParse - Brand Facts | MailParse		 200 yes 179 0
https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound
Email Deliverability: MailParse vs Mandrill Inbound | MailParse		 200 yes 1710 0
https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound
Email Infrastructure: MailParse vs Mandrill Inbound | MailParse		 200 yes 2260 0
https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound
MailParse vs Mandrill Inbound: Detailed Comparison | MailParse		 200 yes 1923 0
https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders
MailParse vs Mandrill Inbound for No-Code Builders | MailParse		 200 yes 1972 0
https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers
MailParse vs Mandrill Inbound for Platform Engineers | MailParse		 200 yes 2045 0
https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders
Email Infrastructure for No-Code Builders | MailParse | MailParse		 200 yes 2091 0
https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring
Email Infrastructure for Compliance Monitoring | MailParse | MailParse		 200 yes 2232 0
https://www.mailparse.dev/learn/email-infrastructure/email-archival
Email Infrastructure for Email Archival | MailParse | MailParse		 200 yes 2192 0
https://www.mailparse.dev/learn/email-infrastructure/notification-routing
Email Infrastructure for Notification Routing | MailParse | MailParse		 200 yes 2112 0
https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers
Compliance Monitoring Guide for Platform Engineers | MailParse | MailParse		 200 yes 2214 0
https://www.mailparse.dev/learn/use-cases/email-archival
Email Archival with MailParse | Email Parsing | MailParse		 200 yes 2238 0
https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders
Email Archival Guide for No-Code Builders | MailParse | MailParse		 200 yes 2257 0
https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers
Email Archival Guide for Platform Engineers | MailParse | MailParse		 200 yes 2108 0
https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders
Notification Routing Guide for No-Code Builders | MailParse | MailParse		 200 yes 2177 0
https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers
Notification Routing Guide for Platform Engineers | MailParse | MailParse		 200 yes 2121 0
https://www.mailparse.dev/auth/login 0 no 0 5
https://www.mailparse.dev/docs
404 - No inbox at this address | MailParse		 404 no 97 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →