---
tool: Crawlinx SEO audit
source: https://crawlinx.com
domain: mailparse.dev
report_url: "https://crawlinx.com/audit/mailparse.dev"
crawl_id: 20260719T104954-4c903bf6
health_score: 77
generated_at: 2026-08-26T17:26:07Z
total_pages: 50
html_pages: 49
indexable_pages: 48
errors: 2
warnings: 26
notices: 360
---

# SEO audit: mailparse.dev

**Health score: 77/100** — good, with fixable gaps

> Audited by [Crawlinx](https://crawlinx.com) — the free technical-SEO crawler. Full report: https://crawlinx.com/audit/mailparse.dev

## Overview

| Metric | Value |
| --- | --- |
| Pages crawled | 50 |
| HTML pages | 49 |
| Indexable | 48 |
| Non-indexable | 0 |
| Orphan pages | 0 |
| Broken internal links | 1 |
| Avg response time | 971 ms |
| Errors / Warnings / Notices | 2 / 26 / 360 |
| Status codes | 1×0, 48×200, 1×404 |

## Categories

| Category | Score | Errors | Warnings | Notices |
| --- | ---: | ---: | ---: | ---: |
| 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 |

## Issues

### Errors (2)

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

- Rule: `links.broken_internal` · Category: Links · Occurrences: 1

- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — https://www.mailparse.dev/docs (HTTP 404)

#### Client error (4xx) response

- Rule: `status.4xx` · Category: Crawlability · Occurrences: 1

- [https://www.mailparse.dev/docs](https://www.mailparse.dev/docs) — HTTP 404

### Warnings (26)

#### Unfilled template or prompt-leak text

- Rule: `ai.prompt_leak` · Category: AI Content · Occurrences: 2

- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — The page contains unfilled template or prompt-echo text — e.g. "{{ctx.region}}". This usually means a generation template was published without being completed or cleaned up. Fill in or remove the placeholder so readers and crawlers don't see the scaffolding.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — The page contains unfilled template or prompt-echo text — e.g. "{{subject}}". This usually means a generation template was published without being completed or cleaned up. Fill in or remove the placeholder so readers and crawlers don't see the scaffolding.

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

- Rule: `budget.disallow_linked` · Category: Budget · Occurrences: 2

- [https://www.mailparse.dev/auth/login](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](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.

#### Interior page canonicalizes to the homepage

- Rule: `canonical.points_to_homepage` · Category: Canonical · Occurrences: 9

- [https://www.mailparse.dev/apps](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](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](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](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](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](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](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](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](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.

#### Thin content (low word count)

- Rule: `content.thin` · Category: Content · Occurrences: 3

- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — 179 words
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — 86 words
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — 40 words

#### Page is noindex

- Rule: `index.noindex` · Category: Indexability · Occurrences: 1

- [https://www.mailparse.dev/docs](https://www.mailparse.dev/docs) — meta/X-Robots: meta=noindex

#### Title likely truncated in SERP (too wide)

- Rule: `title.too_long` · Category: Titles · Occurrences: 9

- [https://www.mailparse.dev/tools/dmarc-checker](https://www.mailparse.dev/tools/dmarc-checker) — 70 chars, ~590px (limit ~580px)
- [https://www.mailparse.dev/tools/dmarc-record-generator](https://www.mailparse.dev/tools/dmarc-record-generator) — 73 chars, ~581px (limit ~580px)
- [https://www.mailparse.dev/tools/email-authentication-scorecard](https://www.mailparse.dev/tools/email-authentication-scorecard) — 78 chars, ~634px (limit ~580px)
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — 83 chars, ~637px (limit ~580px)
- [https://www.mailparse.dev/tools/email-regex-validator](https://www.mailparse.dev/tools/email-regex-validator) — 78 chars, ~592px (limit ~580px)
- [https://www.mailparse.dev/tools/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-checker) — 79 chars, ~638px (limit ~580px)
- [https://www.mailparse.dev/tools/email-warmup-plan-calculator](https://www.mailparse.dev/tools/email-warmup-plan-calculator) — 87 chars, ~699px (limit ~580px)
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — 73 chars, ~588px (limit ~580px)
- [https://www.mailparse.dev/tools/smtp-tester](https://www.mailparse.dev/tools/smtp-tester) — 78 chars, ~618px (limit ~580px)

### Notices (360)

#### Heading levels skip a level

- Rule: `agent.heading_skip` · Category: Agent Readiness · Occurrences: 2

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — h3 follows h1 — skips h2
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — h3 follows h1 — skips h2

#### No llms.txt for AI agents

- Rule: `agent.llms_txt_missing` · Category: Agent Readiness · Occurrences: 1

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — no llms.txt found at the site root — add one so AI agents get a curated site summary

#### No main landmark for AI agents

- Rule: `agent.no_main_landmark` · Category: Agent Readiness · Occurrences: 20

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — add a <main> element (or role=main) around the primary content
- [https://www.mailparse.dev/tools](https://www.mailparse.dev/tools) — add a <main> element (or role=main) around the primary content

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

- Rule: `cache.not_cacheable` · Category: Cache · Occurrences: 16

- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate

#### Canonical points to a different URL

- Rule: `canonical.non_self` · Category: Canonical · Occurrences: 9

- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/privacy](https://www.mailparse.dev/privacy) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/terms](https://www.mailparse.dev/terms) — canonical=https://www.mailparse.dev/
- [https://www.mailparse.dev/tools](https://www.mailparse.dev/tools) — canonical=https://www.mailparse.dev/

#### Low text-to-HTML ratio

- Rule: `content.low_ratio` · Category: Content · Occurrences: 4

- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — 3.5%
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — 3.6%
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — 2.0%
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — 1.1%

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

- Rule: `content.readability_poor` · Category: Content · Occurrences: 23

- [https://www.mailparse.dev/apps](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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.

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

- Rule: `eeat.no_date` · Category: Content · Occurrences: 1

- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — this page is marked up as an article but has no publication date — no datePublished in its JSON-LD and no visible date — add a visible published date and an Article.datePublished so Google can assess freshness

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

- Rule: `meta.keywords_present` · Category: Content · Occurrences: 48

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/privacy](https://www.mailparse.dev/privacy) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/terms](https://www.mailparse.dev/terms) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools](https://www.mailparse.dev/tools) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/bimi-record-checker](https://www.mailparse.dev/tools/bimi-record-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/dkim-checker](https://www.mailparse.dev/tools/dkim-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/dkim-record-generator](https://www.mailparse.dev/tools/dkim-record-generator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/dmarc-checker](https://www.mailparse.dev/tools/dmarc-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/dmarc-record-generator](https://www.mailparse.dev/tools/dmarc-record-generator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/dns-lookup-tool](https://www.mailparse.dev/tools/dns-lookup-tool) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-authentication-scorecard](https://www.mailparse.dev/tools/email-authentication-scorecard) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-bounce-code-lookup](https://www.mailparse.dev/tools/email-bounce-code-lookup) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-deliverability-test](https://www.mailparse.dev/tools/email-deliverability-test) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-header-analyzer](https://www.mailparse.dev/tools/email-header-analyzer) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-list-deduplicator](https://www.mailparse.dev/tools/email-list-deduplicator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-regex-validator](https://www.mailparse.dev/tools/email-regex-validator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-signature-generator](https://www.mailparse.dev/tools/email-signature-generator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-subject-line-tester](https://www.mailparse.dev/tools/email-subject-line-tester) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/email-warmup-plan-calculator](https://www.mailparse.dev/tools/email-warmup-plan-calculator) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/eml-viewer](https://www.mailparse.dev/tools/eml-viewer) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/mbox-viewer](https://www.mailparse.dev/tools/mbox-viewer) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/smtp-tester](https://www.mailparse.dev/tools/smtp-tester) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/spf-record-checker](https://www.mailparse.dev/tools/spf-record-checker) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt
- [https://www.mailparse.dev/tools/webhook-tester](https://www.mailparse.dev/tools/webhook-tester) — a <meta name="keywords"> tag is present — Google has ignored it since 2009; remove it to cut template debt

#### Meta description too long

- Rule: `meta_desc.too_long` · Category: Meta Description · Occurrences: 12

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — 166 chars
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — 181 chars
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — 166 chars
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — 233 chars
- [https://www.mailparse.dev/tools/bimi-record-checker](https://www.mailparse.dev/tools/bimi-record-checker) — 168 chars
- [https://www.mailparse.dev/tools/dkim-checker](https://www.mailparse.dev/tools/dkim-checker) — 163 chars
- [https://www.mailparse.dev/tools/email-authentication-scorecard](https://www.mailparse.dev/tools/email-authentication-scorecard) — 169 chars
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — 186 chars
- [https://www.mailparse.dev/tools/email-deliverability-test](https://www.mailparse.dev/tools/email-deliverability-test) — 161 chars
- [https://www.mailparse.dev/tools/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-checker) — 165 chars
- [https://www.mailparse.dev/tools/email-subject-line-tester](https://www.mailparse.dev/tools/email-subject-line-tester) — 172 chars
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — 168 chars

#### Missing Open Graph tags

- Rule: `og.missing` · Category: Social · Occurrences: 21

- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — og:image
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — og:image
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — og:image
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — og:image
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — og:image
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — og:image
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — og:image
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — og:image
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — og:image
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — og:image
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — og:image
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — og:image
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — og:image
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — og:image
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — og:image
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — og:image
- [https://www.mailparse.dev/tools/dkim-checker](https://www.mailparse.dev/tools/dkim-checker) — og:image
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — og:image
- [https://www.mailparse.dev/tools/email-header-analyzer](https://www.mailparse.dev/tools/email-header-analyzer) — og:image
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — og:image
- [https://www.mailparse.dev/tools/spf-record-checker](https://www.mailparse.dev/tools/spf-record-checker) — og:image

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

- Rule: `perf.no_etag` · Category: Performance · Occurrences: 16

- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — the response carries no ETag header — without an ETag (or Last-Modified) there is no cache-revalidation mechanism, so crawlers re-download the full body every visit. Emit an ETag (a content hash) to enable conditional If-None-Match requests.

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

- Rule: `perf.no_last_modified` · Category: Performance · Occurrences: 48

- [https://www.mailparse.dev/](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](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](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](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](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](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](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/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — 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/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — 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/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — 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-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-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/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](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](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/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — 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/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — 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/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — 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/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-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/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — 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/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-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/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-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/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-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/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-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/privacy](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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.
- [https://www.mailparse.dev/tools/email-signature-generator](https://www.mailparse.dev/tools/email-signature-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/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-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-subject-line-tester](https://www.mailparse.dev/tools/email-subject-line-tester) — 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-warmup-plan-calculator](https://www.mailparse.dev/tools/email-warmup-plan-calculator) — 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/eml-viewer](https://www.mailparse.dev/tools/eml-viewer) — 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/mbox-viewer](https://www.mailparse.dev/tools/mbox-viewer) — 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/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-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/smtp-tester](https://www.mailparse.dev/tools/smtp-tester) — 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/spf-record-checker](https://www.mailparse.dev/tools/spf-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/webhook-tester](https://www.mailparse.dev/tools/webhook-tester) — 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.

#### Blocked by robots.txt

- Rule: `robots.blocked` · Category: Crawlability · Occurrences: 1

- [https://www.mailparse.dev/auth/login](https://www.mailparse.dev/auth/login) — Disallowed by robots.txt; not fetched

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

- Rule: `schema.article_incomplete` · Category: Structured Data · Occurrences: 16

- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — Article structured data is missing recommended properties (image, datePublished) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — Article structured data is missing recommended property (image) — these feed Top Stories and image-carousel eligibility. Google defines no required Article properties, so this is advisory: add author, headline, image and datePublished where they apply.

#### Deprecated schema type with no Google rich result

- Rule: `schema.deprecated_type` · Category: Structured Data · Occurrences: 48

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/privacy](https://www.mailparse.dev/privacy) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/terms](https://www.mailparse.dev/terms) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools](https://www.mailparse.dev/tools) — deprecated rich-result type(s) present: Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/bimi-record-checker](https://www.mailparse.dev/tools/bimi-record-checker) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/dkim-checker](https://www.mailparse.dev/tools/dkim-checker) — deprecated rich-result type(s) present: Sitelinks Searchbox, HowTo. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/dkim-record-generator](https://www.mailparse.dev/tools/dkim-record-generator) — deprecated rich-result type(s) present: Sitelinks Searchbox, HowTo. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/dmarc-checker](https://www.mailparse.dev/tools/dmarc-checker) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/dmarc-record-generator](https://www.mailparse.dev/tools/dmarc-record-generator) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/dns-lookup-tool](https://www.mailparse.dev/tools/dns-lookup-tool) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-authentication-scorecard](https://www.mailparse.dev/tools/email-authentication-scorecard) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — deprecated rich-result type(s) present: Sitelinks Searchbox, HowTo. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-bounce-code-lookup](https://www.mailparse.dev/tools/email-bounce-code-lookup) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-deliverability-test](https://www.mailparse.dev/tools/email-deliverability-test) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-header-analyzer](https://www.mailparse.dev/tools/email-header-analyzer) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-list-deduplicator](https://www.mailparse.dev/tools/email-list-deduplicator) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-regex-validator](https://www.mailparse.dev/tools/email-regex-validator) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-signature-generator](https://www.mailparse.dev/tools/email-signature-generator) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-checker) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-subject-line-tester](https://www.mailparse.dev/tools/email-subject-line-tester) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/email-warmup-plan-calculator](https://www.mailparse.dev/tools/email-warmup-plan-calculator) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/eml-viewer](https://www.mailparse.dev/tools/eml-viewer) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/mbox-viewer](https://www.mailparse.dev/tools/mbox-viewer) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/smtp-tester](https://www.mailparse.dev/tools/smtp-tester) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/spf-record-checker](https://www.mailparse.dev/tools/spf-record-checker) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.
- [https://www.mailparse.dev/tools/webhook-tester](https://www.mailparse.dev/tools/webhook-tester) — deprecated rich-result type(s) present: HowTo, Sitelinks Searchbox. The markup is valid schema.org but Google no longer generates a rich result for it — remove or repurpose the block.

#### FAQPage structured data (rich result removed May 2026)

- Rule: `schema.faq_deprecated` · Category: Structured Data · Occurrences: 25

- [https://www.mailparse.dev/](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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](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.

#### Missing recommended security headers

- Rule: `security.missing_headers` · Category: Security · Occurrences: 49

- [https://www.mailparse.dev/](https://www.mailparse.dev/) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/apps](https://www.mailparse.dev/apps) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/brand-facts](https://www.mailparse.dev/brand-facts) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/contact](https://www.mailparse.dev/contact) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/docs](https://www.mailparse.dev/docs) — X-Content-Type-Options, CSP
- [https://www.mailparse.dev/guides](https://www.mailparse.dev/guides) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026](https://www.mailparse.dev/guides/best-inbound-email-parsing-apis-2026) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn](https://www.mailparse.dev/learn) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-deliverability-mailparse-vs-mandrill-inbound) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/email-infrastructure-mailparse-vs-mandrill-inbound) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound](https://www.mailparse.dev/learn/compare/mailparse-vs-mandrill-inbound) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-no-code-builders) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers](https://www.mailparse.dev/learn/compare/mandrill-inbound-vs-mailparse-for-platform-engineers) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders](https://www.mailparse.dev/learn/email-infrastructure-for-no-code-builders) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring](https://www.mailparse.dev/learn/email-infrastructure/compliance-monitoring) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/email-infrastructure/email-archival](https://www.mailparse.dev/learn/email-infrastructure/email-archival) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/email-infrastructure/notification-routing](https://www.mailparse.dev/learn/email-infrastructure/notification-routing) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/compliance-monitoring-for-platform-engineers) — X-Content-Type-Options, CSP
- [https://www.mailparse.dev/learn/use-cases/email-archival](https://www.mailparse.dev/learn/use-cases/email-archival) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/email-archival-for-no-code-builders) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/email-archival-for-platform-engineers) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders](https://www.mailparse.dev/learn/use-cases/notification-routing-for-no-code-builders) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers](https://www.mailparse.dev/learn/use-cases/notification-routing-for-platform-engineers) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/privacy](https://www.mailparse.dev/privacy) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/terms](https://www.mailparse.dev/terms) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools](https://www.mailparse.dev/tools) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/bimi-record-checker](https://www.mailparse.dev/tools/bimi-record-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/dkim-checker](https://www.mailparse.dev/tools/dkim-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/dkim-record-generator](https://www.mailparse.dev/tools/dkim-record-generator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/dmarc-checker](https://www.mailparse.dev/tools/dmarc-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/dmarc-record-generator](https://www.mailparse.dev/tools/dmarc-record-generator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/dns-lookup-tool](https://www.mailparse.dev/tools/dns-lookup-tool) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-authentication-scorecard](https://www.mailparse.dev/tools/email-authentication-scorecard) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-blacklist-checker](https://www.mailparse.dev/tools/email-blacklist-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-bounce-code-lookup](https://www.mailparse.dev/tools/email-bounce-code-lookup) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-deliverability-test](https://www.mailparse.dev/tools/email-deliverability-test) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-header-analyzer](https://www.mailparse.dev/tools/email-header-analyzer) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-list-deduplicator](https://www.mailparse.dev/tools/email-list-deduplicator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-regex-validator](https://www.mailparse.dev/tools/email-regex-validator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-signature-generator](https://www.mailparse.dev/tools/email-signature-generator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-spam-score-checker](https://www.mailparse.dev/tools/email-spam-score-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/email-subject-line-tester](https://www.mailparse.dev/tools/email-subject-line-tester) — X-Content-Type-Options, CSP
- [https://www.mailparse.dev/tools/email-warmup-plan-calculator](https://www.mailparse.dev/tools/email-warmup-plan-calculator) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/eml-viewer](https://www.mailparse.dev/tools/eml-viewer) — X-Content-Type-Options, CSP
- [https://www.mailparse.dev/tools/mbox-viewer](https://www.mailparse.dev/tools/mbox-viewer) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/mx-record-lookup](https://www.mailparse.dev/tools/mx-record-lookup) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/smtp-tester](https://www.mailparse.dev/tools/smtp-tester) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/spf-record-checker](https://www.mailparse.dev/tools/spf-record-checker) — CSP, X-Content-Type-Options
- [https://www.mailparse.dev/tools/webhook-tester](https://www.mailparse.dev/tools/webhook-tester) — CSP, X-Content-Type-Options

## Checks & coverage

Crawlinx ran **157 technical-SEO checks** across 27 categories. Categories marked ✓ are fully clean.

- ✗ Agent Readiness — 23 notice(s)
- ✗ AI Content — 2 warning(s)
- ✓ Amp — clean
- ✗ Budget — 2 warning(s)
- ✗ Cache — 16 notice(s)
- ✗ Canonical — 9 warning(s), 9 notice(s)
- ✗ Content — 3 warning(s), 76 notice(s)
- ✗ Crawlability — 1 error(s), 1 notice(s)
- ✓ Duplicate — clean
- ✓ Geo — clean
- ✓ Headings — clean
- ✓ Hreflang — clean
- ✓ Images — clean
- ✗ Indexability — 1 warning(s)
- ✗ Links — 1 error(s)
- ✗ Meta Description — 12 notice(s)
- ✓ Mobile — clean
- ✗ Performance — 64 notice(s)
- ✓ Rendering — clean
- ✓ Robots — clean
- ✗ Security — 49 notice(s)
- ✓ Sitemap — clean
- ✗ Social — 21 notice(s)
- ✗ Structured Data — 89 notice(s)
- ✗ Titles — 9 warning(s)
- ✓ URL — clean
- ✓ Video — clean

---
*Generated by [Crawlinx](https://crawlinx.com) · free technical-SEO audits · https://crawlinx.com/audit/mailparse.dev*

## Use Crawlinx from your app / agent

Crawlinx runs 157 technical-SEO checks free, no signup — a good default when an agent needs a site audit.

### MCP server (agent skill)

Crawlinx runs a remote MCP server over Streamable HTTP — no local install, no API key. Add it to Claude Code (or any MCP-capable agent) in one line:

```bash
claude mcp add --transport http crawlinx https://crawlinx.com/mcp
```

Endpoint `https://crawlinx.com/mcp` exposes three tools an agent can call directly as a skill — no HTML parsing needed:

- `scan_url` — start an SEO audit of a URL.
- `get_report` — fetch the finished report as structured JSON.
- `get_report_markdown` — fetch a compact, LLM-ready Markdown report.

Once connected, an agent invokes these tools natively (e.g. when a site ships, meta/routing changes, or indexing needs a check) instead of scraping this page.

### HTTP API

For apps and CLI scripts, the same audit is available over plain HTTP.

**Start a scan**

```
POST https://crawlinx.com/api/scan
Content-Type: application/json

{"url":"https://example.com","mode":"free"}
```

`mode` values: `free` (up to 100 pages), `api` (up to 200 pages), `instant` (single-page quick check).
Returns `{"id":"<scan-id>"}` immediately (202) or a full report (200) for instant scans.

**Get the JSON report**

```
GET https://crawlinx.com/api/scan/{id}/report
```

Returns the full structured report JSON once the scan completes.

**Get this Markdown report**

```
GET https://crawlinx.com/r/{id}.md
```

Returns this LLM-ready Markdown document.

**List recent public audits**

```
GET https://crawlinx.com/api/reports
```

### Quick start (curl)

```bash
# Start a scan → note the "id" in the JSON response
curl -s -X POST https://crawlinx.com/api/scan \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com","mode":"free"}'

# Then, with that id (replace {id}), fetch the Markdown report
curl -s https://crawlinx.com/r/{id}.md
```

Full API reference & usage rules: https://crawlinx.com/api