assets/report-template.html
GitHub<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>{{report_title}}</title>
<style>
/* ── Reset & base ── */
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }
body {
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
font-size: 15px;
line-height: 1.6;
color: #1a1a1a;
background: #f5f5f5;
}
/* ── Layout ── */
header, main, footer {
max-width: 1080px;
margin: 0 auto;
padding: 0 24px;
}
/* ── Header ── */
header {
background: #fff;
border-bottom: 3px solid #0f62fe;
padding-top: 32px;
padding-bottom: 24px;
margin-bottom: 0;
max-width: 100%;
box-shadow: 0 1px 4px rgba(0,0,0,0.06);
}
header .inner {
max-width: 1080px;
margin: 0 auto;
padding: 0 24px;
}
.report-badge {
display: inline-block;
background: #0f62fe;
color: #fff;
font-size: 11px;
font-weight: 600;
letter-spacing: 0.08em;
text-transform: uppercase;
padding: 3px 10px;
border-radius: 3px;
margin-bottom: 10px;
}
header h1 {
font-size: 24px;
font-weight: 700;
color: #0a0a0a;
margin-bottom: 8px;
}
.meta-row {
display: flex;
flex-wrap: wrap;
gap: 16px;
margin-top: 10px;
font-size: 13px;
color: #555;
}
.meta-row span strong { color: #333; }
/* ── Main content ── */
main {
padding-top: 28px;
padding-bottom: 48px;
}
/* ── Section ── */
section {
background: #fff;
border-radius: 6px;
border: 1px solid #e0e0e0;
margin-bottom: 20px;
/* 不用 overflow:hidden,否则小屏下表格横向滚动会被裁切 */
}
section > h2 {
font-size: 13px;
font-weight: 700;
letter-spacing: 0.07em;
text-transform: uppercase;
color: #0f62fe;
padding: 14px 20px;
border-bottom: 1px solid #e8e8e8;
background: #f9fbff;
}
section > .section-body {
padding: 20px;
overflow-x: auto;
-webkit-overflow-scrolling: touch;
}
/* ── Executive summary ── */
.summary-verdict {
font-size: 14px;
color: #444;
line-height: 1.6;
margin-bottom: 16px;
padding-bottom: 14px;
border-bottom: 1px solid #f0f0f0;
}
.summary-groups {
display: grid;
grid-template-columns: 1fr 1fr 1fr;
gap: 12px;
}
.summary-group {
border-radius: 5px;
padding: 12px 14px;
}
.summary-group.critical { background: #fff0f0; border: 1px solid #fcd0d0; }
.summary-group.warnings { background: #fffbea; border: 1px solid #f0e08a; }
.summary-group.passing { background: #f0faf3; border: 1px solid #b8e8c8; }
.summary-group-label {
font-size: 11px;
font-weight: 700;
text-transform: uppercase;
letter-spacing: 0.07em;
margin-bottom: 8px;
}
.summary-group.critical .summary-group-label { color: #c0392b; }
.summary-group.warnings .summary-group-label { color: #856404; }
.summary-group.passing .summary-group-label { color: #1a6b35; }
.summary-group ul {
list-style: none;
padding: 0;
margin: 0;
}
.summary-group ul li {
font-size: 13px;
color: #333;
padding: 3px 0;
border-bottom: 1px solid rgba(0,0,0,0.05);
line-height: 1.45;
}
.summary-group ul li:last-child { border-bottom: none; }
.summary-group ul li::before {
margin-right: 5px;
}
.summary-group.critical ul li::before { content: "✕"; color: #c0392b; font-weight: 700; }
.summary-group.warnings ul li::before { content: "!"; color: #856404; font-weight: 700; }
.summary-group.passing ul li::before { content: "✓"; color: #1a6b35; font-weight: 700; }
.summary-empty {
font-size: 12px;
color: #aaa;
font-style: italic;
}
/* ── Check table ── */
.table-scroll {
overflow-x: auto;
-webkit-overflow-scrolling: touch;
margin: 0 0 12px;
}
.table-scroll:last-child { margin-bottom: 0; }
.check-table {
width: 100%;
min-width: 32rem;
border-collapse: collapse;
font-size: 14px;
}
/* E-E-A-T 等四列表格需要更宽的最小宽度 */
.check-table:has(thead tr th:nth-child(4)) {
min-width: 42rem;
}
.check-table th {
text-align: left;
font-size: 12px;
font-weight: 600;
color: #666;
text-transform: uppercase;
letter-spacing: 0.05em;
padding: 8px 12px;
border-bottom: 1px solid #e8e8e8;
background: #fafafa;
}
.check-table td {
padding: 10px 12px;
border-bottom: 1px solid #f0f0f0;
vertical-align: top;
overflow-wrap: anywhere;
word-break: break-word;
}
.check-table th:nth-child(1),
.check-table td:nth-child(1) { min-width: 6.5rem; }
.check-table th:nth-child(2),
.check-table td:nth-child(2) { width: 5.5rem; white-space: nowrap; }
.check-table th:nth-child(3),
.check-table td:nth-child(3) { min-width: 8rem; }
.check-table tr:last-child td { border-bottom: none; }
/* Detail cell: issue description + fix suggestion */
.detail-issue {
font-size: 13px;
color: #333;
line-height: 1.55;
}
.detail-fix {
margin-top: 5px;
font-size: 12px;
color: #1a6b35;
line-height: 1.5;
}
.detail-fix::before {
content: "Fix: ";
font-weight: 700;
}
/* ── Status badges ── */
.status {
display: inline-block;
font-size: 11px;
font-weight: 600;
padding: 2px 8px;
border-radius: 3px;
text-transform: uppercase;
letter-spacing: 0.05em;
}
.status-pass { background: #d4edda; color: #155724; }
.status-fail { background: #f8d7da; color: #721c24; }
.status-warn { background: #fff3cd; color: #856404; }
.status-info { background: #d1ecf1; color: #0c5460; }
.status-na { background: #e9ecef; color: #495057; }
/* ── Finding articles ── */
article.finding {
border: 1px solid #e0e0e0;
border-radius: 5px;
margin-bottom: 14px;
overflow: hidden;
}
article.finding:last-child { margin-bottom: 0; }
.finding-header {
display: flex;
align-items: center;
gap: 10px;
padding: 12px 16px;
background: #fafafa;
border-bottom: 1px solid #e8e8e8;
}
.finding-header h3 {
font-size: 14px;
font-weight: 600;
color: #1a1a1a;
flex: 1;
}
.finding-body {
padding: 14px 16px;
display: grid;
gap: 10px;
}
.finding-field {
display: grid;
grid-template-columns: 80px 1fr;
gap: 8px;
font-size: 14px;
}
.finding-field .label {
font-weight: 600;
color: #555;
font-size: 12px;
text-transform: uppercase;
letter-spacing: 0.05em;
padding-top: 2px;
}
.finding-field .value { color: #333; }
/* ── Priority actions ── */
ol.priority-list {
padding-left: 20px;
font-size: 14px;
color: #333;
line-height: 1.8;
}
ol.priority-list li { margin-bottom: 6px; }
/* ── Sub-section label (within Site Checks) ── */
.subsection-label {
font-size: 11px;
font-weight: 700;
letter-spacing: 0.07em;
text-transform: uppercase;
color: #0f62fe;
background: #f0f5ff;
border-left: 3px solid #0f62fe;
padding: 6px 10px;
margin: 20px 0 12px;
border-radius: 0 3px 3px 0;
}
.subsection-label:first-child { margin-top: 0; }
/* ── Limitations ── */
/* ── Upgrade prompt ── */
.upgrade-box {
background: #eef4ff;
border: 1px solid #b8d0ff;
border-radius: 5px;
padding: 16px 20px;
font-size: 14px;
color: #1a3c7a;
}
.upgrade-box strong { color: #0f62fe; }
/* ── Footer ── */
footer {
text-align: center;
font-size: 12px;
color: #999;
padding-top: 16px;
padding-bottom: 32px;
border-top: 1px solid #e0e0e0;
margin-top: 0;
max-width: 100%;
background: #fff;
}
footer .inner {
max-width: 1080px;
margin: 0 auto;
padding: 16px 24px;
}
/* ── Responsive ── */
@media (max-width: 900px) {
.summary-groups {
grid-template-columns: 1fr;
}
}
@media (max-width: 640px) {
header, main, footer,
header .inner {
padding-left: 16px;
padding-right: 16px;
}
header { padding-top: 24px; padding-bottom: 18px; }
header h1 { font-size: 20px; line-height: 1.35; }
.meta-row { flex-direction: column; gap: 8px; }
.meta-row span { word-break: break-all; }
main { padding-top: 20px; padding-bottom: 32px; }
section > h2 { padding: 12px 16px; }
section > .section-body { padding: 14px 16px; }
.check-table {
min-width: 28rem;
font-size: 13px;
}
.check-table th,
.check-table td { padding: 8px 10px; }
.finding-header {
flex-wrap: wrap;
align-items: flex-start;
}
.finding-header h3 { font-size: 13px; }
.finding-field {
grid-template-columns: 1fr;
gap: 4px;
}
.finding-field .label { padding-top: 0; }
.upgrade-box { padding: 14px 16px; font-size: 13px; }
}
@media (max-width: 480px) {
body { font-size: 14px; }
.summary-groups { gap: 10px; }
.summary-group { padding: 10px 12px; }
.check-table { min-width: 26rem; }
.check-table:has(thead tr th:nth-child(4)) { min-width: 34rem; }
}
</style>
</head>
<body>
<header>
<div class="inner">
<span class="report-badge">SEO Audit Report</span>
<h1>{{report_title}}</h1>
<div class="meta-row">
<span><strong>URL:</strong> {{url}}</span>
<span><strong>Audit Level:</strong> {{audit_level}}</span>
<span><strong>Created:</strong> {{generated_date}}</span>
<span><strong>Powered by:</strong> Jeff</span>
</div>
</div>
</header>
<main>
<!-- Audit Summary -->
<section>
<h2>Audit Summary</h2>
<div class="section-body">
<!-- One-line verdict: e.g. "Found 2 critical issues and 1 warning across 6 checks." -->
<p class="summary-verdict">{{summary_verdict}}</p>
<div class="summary-groups">
<!-- Critical issues (status: fail) — one <li> per issue, e.g. "Missing H1 tag" -->
<div class="summary-group critical">
<div class="summary-group-label">Critical</div>
<ul>
{{summary_critical_html}}
<!-- e.g. <li>Title tag missing</li><li>No H1 found</li> -->
<!-- If none: <li class="summary-empty">None</li> -->
</ul>
</div>
<!-- Warnings (status: warn) — one <li> per warning, e.g. "Title too long (78 chars)" -->
<div class="summary-group warnings">
<div class="summary-group-label">Warnings</div>
<ul>
{{summary_warnings_html}}
<!-- e.g. <li>Title is 78 chars (> 60)</li> -->
<!-- If none: <li class="summary-empty">None</li> -->
</ul>
</div>
<!-- Passing checks (status: pass) — one <li> per check -->
<div class="summary-group passing">
<div class="summary-group-label">Passing</div>
<ul>
{{summary_passing_html}}
<!-- e.g. <li>Single H1 present</li><li>Canonical correct</li> -->
<!-- If none: <li class="summary-empty">None</li> -->
</ul>
</div>
</div>
</div>
</section>
<!-- Site-Level Checks -->
<section>
<h2>Site Checks</h2>
<div class="section-body">
<!-- Crawlability + Canonicalization + i18n + Schema -->
{{site_checks_html}}
<!--
Use <div class="subsection-label">Label</div> to separate check groups.
Labels: Crawlability · URL Canonicalization · i18n / hreflang · Schema (JSON-LD)
Pass rows: ONE short phrase. No divs.
Warn / Fail rows: <div class="detail-issue"> ≤2 points + <div class="detail-fix">.
<table class="check-table">
<thead>
<tr><th>Check</th><th>Status</th><th>Detail</th></tr>
</thead>
<tbody>
<tr>
<td>robots.txt</td>
<td><span class="status status-pass">Pass</span></td>
<td>User-Agent: * / Allow: / · Sitemap directive present · Googlebot not blocked.</td>
</tr>
<tr>
<td>sitemap.xml</td>
<td><span class="status status-pass">Pass</span></td>
<td>Valid XML urlset · 104 URLs · referenced in robots.txt.</td>
</tr>
<tr>
<td>robots.txt</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· No Sitemap: directive — crawlers cannot auto-discover sitemap.</div>
<div class="detail-fix">Add: Sitemap: https://example.com/sitemap.xml</div>
</td>
</tr>
<tr>
<td>sitemap.xml</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· HTTP 200 but body is HTML, not valid XML — Google cannot parse it.</div>
<div class="detail-fix">Generate a valid XML sitemap and submit via Google Search Console.</div>
</td>
</tr>
<tr>
<td>404 Handling</td>
<td><span class="status status-pass">Pass</span></td>
<td>Non-existent URL returns 404 — correctly signals missing page to crawlers.</td>
</tr>
<tr>
<td>404 Handling</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· Non-existent URL returns 200 (soft 404) — Google cannot distinguish missing pages from real content.</div>
<div class="detail-fix">Return proper HTTP 404 status for missing pages.</div>
</td>
</tr>
<tr>
<td>404 Handling</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· Non-existent URL redirects 301 to homepage — dilutes crawl budget and masks missing pages.</div>
<div class="detail-fix">Return 404 directly instead of redirecting to homepage.</div>
</td>
</tr>
<tr>
<td>URL Canonicalization</td>
<td><span class="status status-pass">Pass</span></td>
<td>HTTPS enforced · www consistent · trailing slash consistent · canonical matches URL.</td>
</tr>
<tr>
<td>URL Canonicalization</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· http://example.com returns 200 instead of 301 → https — duplicate indexable version.</div>
<div class="detail-fix">Force 301 redirect from HTTP to HTTPS at server/CDN level.</div>
</td>
</tr>
<tr>
<td>URL Canonicalization</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· www and non-www both return 200 — two indexable versions of the site.</div>
<div class="detail-fix">Pick one (preferably non-www unless brand uses www), 301 the other, set canonical accordingly.</div>
</td>
</tr>
<tr>
<td>URL Canonicalization</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· Canonical tag points to https://example.com/page but actual URL served is https://example.com/page/ — trailing slash mismatch.</div>
<div class="detail-fix">Align canonical tag with the exact URL being served, or 301 one form to the other.</div>
</td>
</tr>
<tr>
<td>i18n / hreflang</td>
<td><span class="status status-pass">Pass</span></td>
<td>3 hreflang tags (en, zh-TW, ja) · reciprocal links verified · x-default present · html[lang] matches.</td>
</tr>
<tr>
<td>i18n / hreflang</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· hreflang="zh" used — should be "zh-CN" or "zh-TW" (region required for Chinese). · zh-TW version missing reciprocal link back to en page.</div>
<div class="detail-fix">Use BCP 47 codes (zh-CN / zh-TW). Ensure every hreflang URL also references all other language variants.</div>
</td>
</tr>
<tr>
<td>i18n / hreflang</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· Default language (en) served at /en/page — redundant prefix adds crawl depth. Recommended: / (en) + /zh/ + /es/.</div>
<div class="detail-fix">Move en content to root path, keep subpaths for other languages. Update hreflang and canonical accordingly.</div>
</td>
</tr>
<tr>
<td>i18n / hreflang</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· hreflang tags present but reciprocal links broken — /zh page does not reference /en, Google will ignore the entire hreflang set.</div>
<div class="detail-fix">All language variants must reference each other. Add missing hreflang entries to /zh page.</div>
</td>
</tr>
<tr>
<td>i18n / hreflang</td>
<td><span class="status status-na">N/A</span></td>
<td>Single-language site — hreflang not applicable.</td>
</tr>
</tbody>
</table>
-->
<!-- E-E-A-T Infrastructure: trust pages existence + reachability -->
{{eeat_checks_html}}
<!--
Start with: <div class="subsection-label">E-E-A-T Trust Pages</div>
Two layers per trust page:
Layer 1 — Exists : HTTP 200 = pass, 404/redirect = fail
Layer 2 — Reachable : linked from footer or main nav = pass, not linked = warn
Required: About Us, Contact, Privacy Policy, Terms of Service
Optional bonus: Media/Partners, Pricing (missing = N/A, not penalized)
<table class="check-table">
<thead>
<tr><th>E-E-A-T Page</th><th>Exists</th><th>Reachable (footer/nav)</th><th>Detail</th></tr>
</thead>
<tbody>
<tr>
<td>About Us</td>
<td><span class="status status-pass">Pass</span></td>
<td><span class="status status-pass">Pass</span></td>
<td>/about · linked in footer.</td>
</tr>
<tr>
<td>Contact</td>
<td><span class="status status-pass">Pass</span></td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· /contact returns 200 but not linked in footer or nav.</div>
<div class="detail-fix">Add to footer — hidden trust pages reduce E-E-A-T signals.</div>
</td>
</tr>
<tr>
<td>Privacy Policy</td>
<td><span class="status status-fail">Fail</span></td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· /privacy returns 404.</div>
<div class="detail-fix">Create Privacy Policy page and link it in the footer.</div>
</td>
</tr>
<tr>
<td>Terms of Service</td>
<td><span class="status status-pass">Pass</span></td>
<td><span class="status status-pass">Pass</span></td>
<td>/terms · linked in footer.</td>
</tr>
</tbody>
</table>
-->
</div>
</section>
<!-- Page-Level Checks -->
<section>
<h2>Page Checks</h2>
<div class="section-body">
{{page_checks_html}}
<!--
Expected format for page_checks_html:
- Pass rows: ONE short phrase. No div wrappers needed. Badge already says it passed.
- Warn / Fail rows: <div class="detail-issue"> with ≤2 bullet points (lead with "·").
<div class="detail-fix"> with the fix. No SEO 101 explanations.
- N/A rows: one short phrase explaining why check was skipped.
<table class="check-table">
<thead>
<tr><th>Check</th><th>Status</th><th>Detail</th></tr>
</thead>
<tbody>
<tr>
<td>URL Slug</td>
<td><span class="status status-pass">Pass</span></td>
<td>/blog/best-running-shoes · lowercase, hyphenated, keyword present.</td>
</tr>
<tr>
<td>URL Slug</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· /the-best-and-most-popular-running-shoes-of-2025 — stop words (the, and, of) + overly long.</div>
<div class="detail-fix">Simplify: /running-shoes or /blog/running-shoes</div>
</td>
</tr>
<tr>
<td>URL Slug</td>
<td><span class="status status-na">N/A</span></td>
<td>Homepage — slug check not applicable.</td>
</tr>
<tr>
<td>Title Tag</td>
<td><span class="status status-pass">Pass</span></td>
<td>Homepage · "Acme | AI Workflow Automation" · brand + keyword, 34 chars.</td>
</tr>
<tr>
<td>Title Tag</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· Inner page · keyword buried at position 42 · 78 chars may truncate.</div>
<div class="detail-fix">Lead with keyword: "AI Workflow Automation for Teams — Acme" · shorten to 50–60 chars.</div>
</td>
</tr>
<tr>
<td>Meta Description</td>
<td><span class="status status-pass">Pass</span></td>
<td>153 chars · keyword present · specific and non-generic.</td>
</tr>
<tr>
<td>Meta Description</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· 95 chars — below 120 minimum.</div>
<div class="detail-fix">Expand to 120–160 chars with a concrete value statement.</div>
</td>
</tr>
<tr>
<td>H1 Tag</td>
<td><span class="status status-pass">Pass</span></td>
<td>Single H1 · "Best Running Shoes 2025" · keyword present.</td>
</tr>
<tr>
<td>H1 Tag</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· 3 H1 tags found: "Home", "Welcome", "Our Products".</div>
<div class="detail-fix">Keep one H1 with the primary keyword. Demote others to H2.</div>
</td>
</tr>
<tr>
<td>Canonical Tag</td>
<td><span class="status status-pass">Pass</span></td>
<td>Self-referencing canonical present.</td>
</tr>
<tr>
<td>Image Alt Text</td>
<td><span class="status status-pass">Pass</span></td>
<td>12 images found · all have alt attributes · no empty alt on content images.</td>
</tr>
<tr>
<td>Image Alt Text</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· 3 of 12 images missing alt attribute.</div>
<div class="detail-fix">Add descriptive alt text to all content images. Decorative images use alt="".</div>
</td>
</tr>
<tr>
<td>Image Alt Text</td>
<td><span class="status status-info">Unverified</span></td>
<td>0 images in static HTML — likely JavaScript-rendered. Cannot verify alt text from static analysis. Check via browser DevTools or GSC URL Inspection.</td>
</tr>
<tr>
<td>Word Count</td>
<td><span class="status status-pass">Pass</span></td>
<td>1,420 words.</td>
</tr>
<tr>
<td>Word Count</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· 320 words — thin (recommended ≥ 500).</div>
<div class="detail-fix">Expand to 500+ words with substantive content.</div>
</td>
</tr>
<tr>
<td>Word Count</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· 43 words — below 100-word minimum, not meaningful for indexing.</div>
<div class="detail-fix">Expand content significantly.</div>
</td>
</tr>
<tr>
<td>Keyword Placement</td>
<td><span class="status status-pass">Pass</span></td>
<td>Keyword appears at word 87 — within first 100 words.</td>
</tr>
<tr>
<td>Keyword Placement</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· Keyword first appears at word 210 — should be within first 100 words.</div>
<div class="detail-fix">Add keyword or natural variant to the opening paragraph.</div>
</td>
</tr>
<tr>
<td>Heading Structure</td>
<td><span class="status status-pass">Pass</span></td>
<td>6 H2s · keyword in 3 H2s · avg 2 H3s/H2.</td>
</tr>
<tr>
<td>Heading Structure</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· 2 H2s — sparse (recommended 5–7). · Keyword not in any H2.</div>
<div class="detail-fix">Expand to 5–7 H2 sections. Include keyword or natural variant in at least 1 H2.</div>
</td>
</tr>
<tr>
<td>Internal Links</td>
<td><span class="status status-pass">Pass</span></td>
<td>8 internal links.</td>
</tr>
<tr>
<td>Internal Links</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· 1 internal link — too few for link equity distribution.</div>
<div class="detail-fix">Add 2+ internal links to related pages.</div>
</td>
</tr>
<tr>
<td>Schema (JSON-LD)</td>
<td><span class="status status-pass">Pass</span></td>
<td>BlogPosting detected · required fields present (headline, datePublished, author) · no conflicts.</td>
</tr>
<tr>
<td>Schema (JSON-LD)</td>
<td><span class="status status-warn">Warning</span></td>
<td>
<div class="detail-issue">· BlogPosting present but missing "author.url" and "dateModified" — reduces rich result eligibility.</div>
<div class="detail-fix">Add author.url (person/org profile page) and dateModified to the JSON-LD block.</div>
</td>
</tr>
<tr>
<td>Schema (JSON-LD)</td>
<td><span class="status status-fail">Fail</span></td>
<td>
<div class="detail-issue">· Article page — no JSON-LD found.</div>
<div class="detail-fix">Add BlogPosting JSON-LD: headline, datePublished, author, image.</div>
</td>
</tr>
<tr>
<td>Schema (JSON-LD)</td>
<td><span class="status status-na">N/A</span></td>
<td>Generic landing page — no widely-supported schema type, skip.</td>
</tr>
</tbody>
</table>
On-page content check logic (LLM reads page HTML for all 4 checks):
Word Count — visible body text only (exclude nav/footer/boilerplate):
< 100 → Fail · 100–499 → Warn · ≥ 500 → Pass
Keyword Placement — primary keyword or close variant in first 100 body words:
Present → Pass · Absent → Warn
Heading Structure — three sub-rules, report as separate bullets if any fail:
H2 count : 0 → Warn · 1–4 → Warn · 5–7 → Pass · ≥ 8 → Warn
H3/H2 : 0 → OK · 1–3 → Pass · ≥ 4 → Warn (split this H2)
Keyword in H2 : ≥ 1 H2 contains keyword/variant → Pass · 0 → Warn
Pass summary: "Y H2s · keyword in N H2s · avg Z H3s/H2"
Internal Links — <a href> pointing to same-origin URLs (exclude nav/footer):
< 2 → Warn · 2–20 → Pass · > 20 → Warn
Schema (JSON-LD) — output AFTER the above 4 checks:
Schema check logic (LLM must follow this order):
1. Detect page type from URL pattern + H1 + page content:
- Homepage → expect: WebSite + Organization
- Blog / Article → expect: Article or BlogPosting
- Product page → expect: Product (with Offer, AggregateRating)
- FAQ page → expect: FAQPage
- How-to page → expect: HowTo
- Local business → expect: LocalBusiness
- Generic landing → N/A (skip, do not penalize)
2. Check if expected @type is present in page JSON-LD blocks
3. Validate required fields per type:
- Article/BlogPosting : headline, datePublished, author, image
- Product : name, image, offers (price, priceCurrency)
- FAQPage : mainEntity[].name + acceptedAnswer.text
- WebSite : name, url
- Organization : name, url, logo
4. Flag conflicts: multiple @type blocks claiming different primary types
-->
</div>
</section>
<!-- Priority Actions -->
<section>
<h2>Priority Actions</h2>
<div class="section-body">
{{priority_actions_html}}
<!--
Expected format:
<ol class="priority-list">
<li>Shorten the title tag to under 60 characters, leading with the primary keyword.</li>
<li>Expand the meta description to 120–160 characters with a clear call to action.</li>
<li>Add a Sitemap directive to robots.txt pointing to /sitemap.xml.</li>
</ol>
-->
</div>
</section>
<!-- Insights -->
<section>
<h2>Insight Walkthrough <span style="font-size:11px;font-weight:400;color:#aaa;letter-spacing:0;text-transform:none;margin-left:6px;">optional — detailed evidence & reasoning</span></h2>
<div class="section-body">
{{insights_html}}
<!--
Expected format for insights_html (repeat <article> per insight):
<article class="finding">
<div class="finding-header">
<span class="status status-fail">Critical</span>
<h3>Title Tag Too Long</h3>
</div>
<div class="finding-body">
<div class="finding-field">
<span class="label">Evidence</span>
<span class="value">Current title is 78 characters: "Best Running Shoes 2025 — Free Shipping | AcmeSports Online Store". Google typically truncates titles beyond 60 characters in SERPs.</span>
</div>
<div class="finding-field">
<span class="label">Impact</span>
<span class="value">Truncated titles reduce click-through rates and may fail to communicate the page's primary value proposition in search results.</span>
</div>
<div class="finding-field">
<span class="label">Fix</span>
<span class="value">Rewrite title to 50–60 characters. Prioritize primary keyword near the front. Example: "Best Running Shoes 2025 | Free Shipping — AcmeSports"</span>
</div>
</div>
</article>
-->
</div>
</section>
<!-- Upgrade Prompt -->
<section>
<h2>Want a Deeper Analysis?</h2>
<div class="section-body">
<div class="upgrade-box">
This was a <strong>seo-audit</strong> — Basic tier. It covers robots.txt, sitemap.xml, canonical, TDK, H1, and heading structure.
Upgrade to <strong>seo-audit-full</strong> to unlock advanced technical checks, social tags, content quality analysis, GSC crawl status, and competitor benchmarking.
<br><br>
Say: <code>deep audit: {{url}}</code>
</div>
</div>
</section>
</main>
<footer>
<div class="inner">
Powered by OpenSource Project - <strong><a href="https://github.com/JeffLi1993/seo-audit-skill">seo-audit-skill</a></strong> · Basic SEO Audit Report · {{generated_date}}
</div>
</footer>
</body>
</html>