← All Audits  ·  Back to Report
Guide SEO Audits

Audit 1 — Fix Impact Grading

Every issue from this audit, graded on a before-fix / after-fix basis, so you can see exactly how much fixing each one is worth — both to its own category and to the overall site score.

How grades are calculated. Each of the 7 scored categories starts from its current score (e.g. Technical SEO = 78). Every open issue in that category is "costing" it a number of points based on severity — Critical −15, High −8, Medium −4, Low −1.5, Info −0 — scaled so the total deduction matches the category's actual reported score. Fixing one issue recovers its points within that category, which is then converted to a letter grade (A+ down to F) and multiplied by that category's weight in the overall 71/100 health score to show its real impact. This is a modeling tool for prioritization, not a re-audit — actual post-fix scores should be confirmed by re-running the relevant check.
Projected Score Trajectory, By Action-Plan Phase
71
Today
77
After Phase 1
(critical fixes)
84
After Phase 2
(high-impact)
93
After Phase 3
(content & authority)
100
After Phase 4
(everything fixed)
A+
Who Can Fix What
No Engineer Needed
71 88.3
If the content team fixes every issue tagged Content Team or Design Tool — adding internal links, writing pillar pages, expanding thin pages, updating freshness dates, reconciling FAQ schema drift, lengthening FAQ answers, and re-exporting screenshots to WebP — the overall score climbs from 71 to 88.3 without a single code change.
Open the tracked checklist →
Needs Engineering / Marketing-Ops
88.3 100
The remaining Needs Engineer items (hreflang, canonical/viewport tags, cache headers, security headers, schema code fixes) and a couple of Marketing/Ops items (tag cleanup, Wikipedia outreach) make up the last ~12 points. These are exactly Phase 1 and parts of Phase 2/4 in the Action Plan.
Every Issue — Before & After Grade

Technical SEO

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 1 Critical Needs Engineer
Hreflang values use underscores instead of BCP47 hyphens for pt_BR, zh_TW, zh_HK
In _includes/head.html, emit lang.bcp47 (already correctly defined in _data/i18n.yml) for the hreflang attribute instead of lang.code.
C+
78/100
B
84.1/100
+1.34
Phase 1 High Needs Engineer
Missing hreflang x-default annotation sitewide
Add one x-default alternate per page in the hreflang loop, pointing to the English (root) URL.
C+
78/100
B-
81.3/100
+0.73
Phase 1 High Needs Engineer
Duplicate <link rel="canonical"> tag on every page
Delete one of the two duplicate canonical lines in _layouts/default.html.
C+
78/100
B-
81.3/100
+0.73
Phase 1 High Needs Engineer
Duplicate, conflicting viewport meta tags — one blocks pinch-zoom
Remove the restrictive viewport tag in _layouts/default.html:74, keep only the zoom-friendly version in _includes/head.html:30.
C+
78/100
B-
81.3/100
+0.73
Phase 3 Medium Needs Engineer
Guide images lack width/height attributes (CLS risk)
Add explicit width/height attributes (or CSS aspect-ratio) to all guide images.
C+
78/100
C+
79.6/100
+0.35
Phase 4 Medium Needs Engineer
Render-blocking stylesheets and unpreconnected Google Fonts request
Add preconnect hints for Google Fonts origins; audit for duplicate/overlapping main.css includes; defer non-critical stylesheets.
C+
78/100
C+
79.6/100
+0.35
Phase 4 Medium Needs Engineer
Missing security and caching headers
Add baseline security headers and explicit Cache-Control at the nginx/CDN layer.
C+
78/100
C+
79.6/100
+0.35
Phase 4 Low Needs Engineer
Shared app-shell chrome precedes guide content in raw HTML
Consider moving shared chrome later in DOM order (positioned visually via CSS) so article content appears earlier in source order.
C+
78/100
C+
78.6/100
+0.13
Phase 4 Low Needs Engineer
No IndexNow protocol integration
Add an IndexNow key file and push-on-publish step to accelerate Bing/Yandex/Naver indexing.
C+
78/100
C+
78.6/100
+0.13

Content Quality

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 3 Medium Content Team
Thin content on ~25% of pages
Expand the sub-200-word tier with genuinely useful detail (edge cases, related-task links); leave inherently simple pages as-is.
B
84/100
B+
89.8/100
+1.33
Phase 3 Medium Content Team
No freshness/last-modified signal despite active rewrites
Populate last_modified_at via jekyll-last-modified-at or manual field during editorial passes.
B
84/100
B+
89.8/100
+1.33
Phase 4 Low Content Team
No author/editor bylines or credentialing
Add a lightweight site-wide 'Written and maintained by the Quire Support Team' byline/Organization-as-author schema.
B
84/100
B
86.2/100
+0.51
Phase 4 Low Content Team
Homepage heading order inverts the documented convention and omits FAQ
Drop/demote the H3 'Welcome' heading; document the homepage's FAQ exemption in GUIDE-FORMAT.md.
B
84/100
B
86.2/100
+0.51
Phase 4 Info Content Team
Formulaic sentence templates across structurally-parallel pages
Periodically spot-check templated batches for continued differentiation, especially any future programmatic generation.
B
84/100
B
84.0/100

On-Page SEO & Internal Linking

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 3 High Content Team
No pillar page for ~22 of ~30 nav categories
Create a lightweight pillar page for each major nav category lacking one, prioritizing Import & Export, Mobile, Notifications, Search, Calendar, Permissions.
F
58/100
D+
67.0/100
+1.8
Phase 2 High Content Team
35% of pages (48 of 139) have zero contextual internal links
Add 'Related articles' link blocks (2-4 contextual links) to zero-outbound-link pages, starting with Import/Export, Troubleshooting, Mobile, Security.
F
58/100
D+
67.0/100
+1.8
Phase 2 High Content Team
Spokes frequently fail to link back to their own pillar
Enforce mandatory bidirectional linking between every spoke and its pillar.
F
58/100
D+
67.0/100
+1.8
Phase 4 Medium Content Team
55 pages are orphaned from in-content links
Add inbound contextual links from related content and new category pillar pages.
F
58/100
D-
62.5/100
+0.9
Phase 4 Medium Content Team
Overlapping-scope page groups are not cross-linked
Add explicit 'see also' cross-links within each overlapping group; link feature-permission pages back to the general permission-role pillar.
F
58/100
D-
62.5/100
+0.9
Phase 4 Medium Content Team
Password/login-recovery journey split across two competing pages
Add clear cross-links between the two pages, or consolidate into one canonical login-recovery page.
F
58/100
D-
62.5/100
+0.9
Phase 4 Low Content Team
Homepage does not function as a topical hub
Expand the homepage to link to a category index or more pillar pages, not just 6 featured items.
F
58/100
F
59.7/100
+0.34

Schema / Structured Data

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 1 High Needs Engineer
WebSite @id/url broken sitewide due to case-typo (site.baseUrl vs site.baseurl)
Change site.baseUrl to site.baseurl in _includes/_seo.html.
D-
60/100
C
76.0/100
+1.6
Phase 3 Medium Needs Engineer
BreadcrumbList not implemented; scaffold is dead code
Implement _includes/breadcrumbs.html with BreadcrumbList JSON-LD reflecting the category hierarchy, and set site.breadcrumbs: true.
D-
60/100
D+
68.0/100
+0.8
Phase 3 Medium Needs Engineer
Individual articles use generic CreativeWork Microdata instead of Article/TechArticle JSON-LD
Add a JSON-LD TechArticle block per page with author, publisher, image, mainEntityOfPage, and ISO 8601 dates.
D-
60/100
D+
68.0/100
+0.8
Phase 2 Medium Content Team
FAQPage schema content drift from visible FAQ on 8/139 sampled pages
Audit and reconcile the 8 flagged pages so schema and visible FAQ cover the same questions.
D-
60/100
D+
68.0/100
+0.8
Phase 4 Info Content Team
FAQPage schema retained for AI/LLM value, no longer produces Google rich results
No removal needed; keep as-is.
D-
60/100
D-
60.0/100
Phase 4 Info Content Team
HowTo schema — on hold, no action needed
No new action until the hold is lifted.
D-
60/100
D-
60.0/100

Performance (CWV)

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 2 High Needs Engineer
Static assets have no Cache-Control/Expires headers
Add Cache-Control: public, max-age=31536000, immutable with cache-busting filenames for all static assets.
D+
68/100
C
76.7/100
+0.87
Phase 2 High Design Tool
All content images are unoptimized PNG with no WebP/AVIF or responsive srcset
Re-encode screenshots to WebP with PNG fallback; generate correctly-sized homepage thumbnails instead of scaling down in CSS.
D+
68/100
C
76.7/100
+0.87
Phase 3 Medium Needs Engineer
No width/height attributes on any <img> element
Add explicit width/height attributes to every <img> tag across all guide templates.
D+
68/100
C-
72.3/100
+0.43
Phase 4 Medium Marketing/Ops
Heavy third-party analytics/ad-tag footprint (23-24 of ~47-51 requests per page)
Confirm whether duplicate conversion/analytics tags are still needed and remove redundant ones.
D+
68/100
C-
72.3/100
+0.43
Phase 4 Medium Needs Engineer
Render-blocking CSS chain including cross-origin Google Fonts import
Self-host or preconnect the Google Fonts stylesheet; consolidate bootstrap.min.css + blog.css + main.css.
D+
68/100
C-
72.3/100
+0.43
Phase 4 Low Needs Engineer
Homepage TTFB (780ms) is inconsistent with inner pages (480-670ms)
Investigate whether a CDN/edge cache sits in front of quire.io/guide/ and whether the homepage is served from a colder cache tier.
D+
68/100
D+
69.6/100
+0.16
Phase 4 Info Marketing/Ops
Lab-only measurement — no CrUX/PSI field data available
Re-run with real PageSpeed Insights/CrUX API access once a Google API key is available.
D+
68/100
D+
68.0/100

AI Search Readiness

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 3 High Content Team
Visible and frontmatter FAQ answers are shorter than optimal AI-citation length
Lengthen frontmatter faq: answers toward 100-167 words on the ~130 pages not yet covered by the tasklist-series rework, keeping visible FAQ copy concise per GUIDE-FORMAT.md.
C+
77/100
B
86.7/100
+0.97
Phase 3 Medium Marketing/Ops
No English Wikipedia entity for Quire the software
Pursue a neutral, notability-compliant English Wikipedia article for Quire (software), mirroring the existing zh-TW entry.
C+
77/100
B-
81.8/100
+0.48
Phase 4 Medium Content Team
No YouTube video content embedded in guide pages
Embed relevant existing YouTube walkthroughs on high-traffic guide pages (add-task, board-view, permissions).
C+
77/100
B-
81.8/100
+0.48
Phase 4 Low Needs Engineer
No llms.txt present
Generate a /guide/llms.txt from existing frontmatter listing canonical English URLs with short summaries.
C+
77/100
C+
78.8/100
+0.18
Phase 4 Low Needs Engineer
AI training-only crawlers not distinguished from AI-search crawlers in robots.txt
Add explicit Disallow: / for CCBot/anthropic-ai if opting out of training-data scraping while keeping AI-search visibility.
C+
77/100
C+
78.8/100
+0.18

Images

PhaseSeverityWho Fixes ItIssueGrade BeforeGrade AfterOverall Score Impact
Phase 2 High Design Tool
All content images are unoptimized PNG, no responsive srcset
Re-encode to WebP/AVIF (quality ~75-80) and add responsive srcset/<picture> markup.
F
55/100
C
75.6/100
+1.03
Phase 2 Medium Design Tool
Homepage thumbnails served ~2.8x larger than displayed
Generate correctly-sized thumbnail assets instead of scaling down in CSS.
F
55/100
D
65.3/100
+0.52
Phase 3 Medium Needs Engineer
No width/height attributes on any image
Add explicit width/height attributes to all <img> elements.
F
55/100
D
65.3/100
+0.52
Phase 4 Low Content Team
Minor image alt-text gaps
Audit and fill missing alt attributes site-wide as part of routine accessibility maintenance.
F
55/100
F
58.9/100
+0.2