https://emailens.dev/guides has a JSON-LD block missing the required @context property.
↗ emailens.dev/guidesAdd "@context": "https://schema.org" to the JSON-LD block.
1 ship-blocker, 24 should-fix
Heuristic score over 96 sampled pages, not Google's classifier. How to read this ↓
These rules still ran and emitted findings: the site-type profile lowered their severity so the score reflects how the signal applies to this kind of site, not a one-size-fits-all penalty.
aeo/answer-firstaeo/citable-factsaeo/freshness-signalscontent/eeat-signalscontent/missing-authorspam/thin-contenttech/og-completenessShared report. Run your own audit to see how your site scores.
Run your own audit →Latency is high. Search-engine and AI-crawler bursts will amplify this: consider an edge cache or app-layer query cache.
Fix: add an edge CDN with a sensible s-maxage, or an app-layer query cache (Redis / Next.js unstable_cache) between the route handler and the database.
content/citation-coveragewarningstructural23 pageshttps://emailens.dev/accuracy makes 11 quantified claims but cites 0 authoritative sources (17 named entities: emailens, philippe kam, accuracy most, real outlook).
schema/json-ld-validerrorquick1 pagehttps://emailens.dev/guides has a JSON-LD block missing the required @context property.
content/image-attributeswarningstructural1 pagehttps://emailens.dev/blog/email-css-real-clients: 10 of 16 <img> tags declare neither width/height attributes nor inline sizing (e.g. /blog-assets/email-css-real-clients/animation--outlook_chrome.webp, /blog-assets/email-css-real-clients/animation--outlook_chrome.sim.webp, /blog-assets/email-css-real-clients/animation--iPhone13.webp). Without an aspect ratio the browser cannot reserve space, so content shifts as each image loads, which is what Cumulative Layout Shift measures.
https://emailens.dev/guides has a JSON-LD block missing the required @context property.
↗ emailens.dev/guidesAdd "@context": "https://schema.org" to the JSON-LD block.
https://emailens.dev/accuracy makes 11 quantified claims but cites 0 authoritative sources (17 named entities: emailens, philippe kam, accuracy most, real outlook).
↗ emailens.dev/accuracyCite the primary sources behind your numbers: link the statute, standard, dataset, .gov/.edu page, or research that backs each statistic. AI Overviews and Google's helpful-content systems weight pages that ground claims in authoritative references. Note: this rule detects statistic+citation co-occurrence, not semantic correctness.
https://emailens.dev/blog/email-css-real-clients: 10 of 16 <img> tags declare neither width/height attributes nor inline sizing (e.g. /blog-assets/email-css-real-clients/animation--outlook_chrome.webp, /blog-assets/email-css-real-clients/animation--outlook_chrome.sim.webp, /blog-assets/email-css-real-clients/animation--iPhone13.webp). Without an aspect ratio the browser cannot reserve space, so content shifts as each image loads, which is what Cumulative Layout Shift measures.
↗ emailens.dev/blog/email-css-real-clientsSet the intrinsic width and height attributes on each <img> and let CSS scale it (width: 100%; height: auto). The browser derives aspect-ratio from the attribute pair and reserves the box before the bytes arrive. In a template, bind both from the same data source as the src.
https://emailens.dev/accuracy serves 16 images and not one uses srcset or <picture>, so phones download the desktop-sized file. Google recommends responsive images; this is guidance rather than a requirement, and no image dimension or byte limit is documented.
↗ emailens.dev/accuracyEmit a srcset with a handful of widths plus a sizes attribute, or wrap the img in <picture> to offer a modern format with a fallback. Most image CDNs and framework Image components generate both from one source URL.
https://emailens.dev/about has 0 unique citable facts. AI Overviews cite specific numbers and named references.
↗ emailens.dev/aboutReplace vague language ("varies", "several weeks", "affordable", "many options") with specific values a reader or AI engine would cite: exact prices, percentages, dates, timeframes, version numbers, named products, standards, or regulations that apply to this page. For pSEO templates, bind these values from your data source so each page gets entity-specific numbers instead of repeating the same template wording. Target: 8+ unique facts per page.
https://emailens.dev/tools/email-rendering does not open with a direct, extractable answer: no specific numbers, dates, or dollar amounts
↗ emailens.dev/tools/email-renderingRestructure the template to open with entity-specific facts. Instead of boilerplate or a topic preamble, lead with a complete-answer sentence containing the key number, date, agency, or form name a reader (or AI Overview) would cite. Target: <100 words, at least one concrete number, at least one named entity.
https://emailens.dev/ has no dateModified signal (no JSON-LD dateModified, no modification meta tag, no visible "Last updated"). Evergreen pages may legitimately omit this: verify whether freshness signals matter for this page type.
↗ emailens.dev/Add a freshness signal so AI engines know the page is current. Three recommended places: (1) dateModified in your JSON-LD schema, (2) a visible "Last updated: YYYY-MM-DD" line in the page content, (3) accurate <lastmod> in your sitemap. For pSEO templates, automate dateModified to update when your underlying data source changes.
https://emailens.dev/ has no author signals. This is an E-E-A-T risk. Author bylines matter most on blog/news content; technical docs and product pages legitimately omit them.
↗ emailens.dev/Add author attribution: <meta name="author" content="Name">, a visible byline, or author data in your JSON-LD schema.
https://emailens.dev/ has fewer than 2 out of 4 E-E-A-T signal categories.
↗ emailens.dev/Add trust signals: author info, publication dates, about page links, sources, or "last updated" markers.
https://emailens.dev/ja/tools/dmarc-checker has thin content (61 words).
Add at least 239 more words of substantive content relevant to this page's specific topic.
https://emailens.dev/ reads as FAQ content (2 question-style headings (e.g. "What you sent, and what your client opened", "Why I built Emailens")) but carries no machine-readable question/answer pairs.
↗ emailens.dev/Fix this in the visible page, not in markup: give each question its own heading and put the complete answer in the first paragraph directly beneath it, so an answer engine can lift a whole question/answer pair without reassembling it. Do NOT add FAQPage JSON-LD expecting a rich result: Google removed the FAQ rich result from Search on 2026-05-07 and deleted its documentation on 2026-06-15, and QAPage is documented as being only for pages where users can submit answers, not for a site's own FAQ. If a non-Google consumer of your schema needs the markup, generate it from the same per-record data that renders the headings: don't ship identical questions with only the entity name swapped.
https://emailens.dev/security is missing Open Graph tags: og:type.
↗ emailens.dev/securityAdd the missing meta tags inside <head>: <meta property="og:type" content="...">.
Is this your site?
Claim it to manage the listing, get a verified badge, and a followed backlink.
emailens.dev passed the audit. Embed the badge on your site or README; it always shows your current grade.
[](https://pseolint.dev/r/C65WRiLpB6)<a href="https://pseolint.dev/r/C65WRiLpB6"><img src="https://pseolint.dev/api/badge/emailens.dev" alt="pseolint grade for emailens.dev" /></a>sitemap.xml as the source of truth. Pro lifts the budget to 500 pages on manual re-audits and crawls beyond the sitemap.