Quire Guide — SEO Audit Report

Full Site Crawl · 1,932 URLs · 14 Locales · Synced 2026-07-02

A full technical, content, schema, performance, and AI-search readiness audit of Quire's help center, covering all 13 translated locales alongside the English source.

Read the score. The 71/100 health score is a weighted blend of 7 categories. On-Page & Internal Linking (58) and Images (55) are the biggest drags — both are architecture/asset problems, not writing-quality problems. Content Quality (84) and Visual/Mobile (82) are the strongest areas. Backlinks has no reliable score: no Moz/Bing API keys are configured in this environment, so only domain-level Common Crawl data was available.

OVERALL SEO HEALTH SCORE — OUT OF 100

Mature, well-structured help center: fully server-rendered, complete 14-locale translation parity, a consistently-followed page format, and strong AI-crawler accessibility. The main drag is internal-linking architecture and a handful of cheap-to-fix template bugs.

Top 5 Critical Issues · Auto-generated from this audit

🔴

Hreflang codes use underscores instead of hyphens for pt_BR, zh_TW, zh_HK across all 1,932 URLs — Google may ignore these language-targeting signals for 3 of 13 locales.

🔴

agile-scrum and customer-relationship-pipeline pages are written as narratives when their target queries reward template-gallery pages with a visual preview and CTA — both are losing high-intent traffic to competitors.

🟠

A duplicate, conflicting viewport meta tag blocks pinch-zoom on every page (WCAG 1.4.4 failure), even though a correct tag exists later in the same document.

🟠

WebSite schema resolves to the wrong URL (bare quire.io instead of quire.io/guide) sitewide due to a case-sensitive Liquid typo (site.baseUrl vs. site.baseurl).

🟠

35% of pages have zero internal links, and ~22 of ~30 nav categories have no pillar page — a structural weakness for search engines and AI answer engines mapping the site.

Weighted Category Scores

Content Quality · 23%

Technical SEO · 22%

AI Search Readiness · 10%

Performance (CWV) · 10%

Schema / Structured Data · 10%

On-Page & Internal Linking · 20%

Images · 5%

Quick Wins · Low Effort, Real Impact

⚡

Fix hreflang values to hyphenated BCP47 form (pt-BR, zh-TW, zh-HK) — the correct codes already exist in _data/i18n.yml. One-line template fix, affects 1,494 URLs.

⚡

Fix the site.baseUrl → site.baseurl typo in _includes/_seo.html to correct the WebSite schema entity sitewide.

⚡

Delete the duplicate <link rel="canonical"> and the duplicate, zoom-blocking <meta viewport> tag in _layouts/default.html.

⚡

Add a Cache-Control header for static assets at the nginx layer — config-only, benefits every repeat visit across all 13 locales.

⚡

Add an hreflang="x-default" fallback pointing to the English version of each page.

Technical SEO

weight 22%

Fully server-rendered static HTML on every sampled page — no client-side hydration required
robots.txt correctly allows AI and search crawlers on /guide/, explicit sitemap declaration
1:1 translation parity across all 13 locales + English (138 pages each, 1,932 URLs), zero orphaned pages
Hreflang reciprocity complete (14-way alternate set), correct self-referencing canonicals
Clean URL structure, single-hop redirects, custom true 404, HSTS with preload, gzip compression

Findings

Severity	Finding	Recommendation
Critical	Hreflang values use underscores instead of BCP47 hyphens for pt_BR, zh_TW, zh_HK. All 1,932 pages emit invalid region subtags, risking Google ignoring these annotations for 3 of 13 locales.	Emit `lang.bcp47` (already defined in `_data/i18n.yml`) instead of `lang.code` in `_includes/head.html`.
High	Missing hreflang `x-default` annotation sitewide.	Add one x-default alternate per page pointing to the English URL.
High	Duplicate `<link rel="canonical">` tag on every page (`_layouts/default.html` lines 59 & 78).	Delete one of the two duplicate canonical lines.
High	Duplicate, conflicting viewport meta tags — one sets `user-scalable=no`, blocking pinch-zoom (WCAG 1.4.4 fail).	Remove the restrictive tag in `_layouts/default.html:74`; keep only the correct one in `_includes/head.html:30`.
Medium	Guide images lack width/height attributes (CLS risk).	Add explicit width/height or aspect-ratio CSS to all images.
Medium	Render-blocking stylesheets, unpreconnected Google Fonts request.	Add preconnect hints; consolidate/defer non-critical stylesheets.
Medium	Missing security and caching headers (CSP, nosniff, Referrer-Policy, Cache-Control).	Add baseline security headers and explicit Cache-Control at the nginx/CDN layer.
Low	Shared app-shell chrome (login/notifications) precedes guide content in raw HTML.	Move shared chrome later in DOM order, positioned visually via CSS.
Low	No IndexNow protocol integration.	Add an IndexNow key file and push-on-publish step.

Content Quality

weight 23%

All 139 sampled EN pages follow the documented intro / H2 / H3 / FAQ convention
100% of EN pages have both frontmatter faq: and a matching visible FAQ
Strong trust signals: Organization schema, contact/security/privacy links, feedback widget
Transparent "AI translated" disclosure banner on non-English pages
No literal duplicate content; templated phrasing across parallel pages still page-specific

Findings

Severity	Finding	Recommendation
Medium	Thin content on ~25% of pages — 35 of 139 EN pages under 400 words, 8 under 200.	Expand sub-200-word pages with genuinely useful detail; leave simple pages as-is where expansion adds no value.
Medium	No freshness signal despite active rewrites — 86% of pages share one static 2019 date though `last_modified_at` is fully supported by the template.	Populate `last_modified_at` during editorial passes.
Low	No author/editor bylines or credentialing anywhere in the corpus.	Add a site-wide "Written and maintained by the Quire Support Team" byline/Organization-as-author schema.
Low	Homepage heading order inverts the documented convention and omits FAQ.	Drop/demote the H3 before the intro; document the homepage's FAQ exemption in GUIDE-FORMAT.md.
Info	Formulaic sentence templates across structurally-parallel pages (still page-specific today).	Periodically spot-check templated batches for continued differentiation.

On-Page SEO & Internal Linking

weight 20%

8 Overview pages act as de facto pillar pages, correctly linking down into category spokes
The Formula cluster (formula-01–06) is a well-built hub-and-spoke example with bidirectional links
Visually-similar page titles (blink-search vs search-tasks) are correctly scoped to distinct intents

Findings

Severity	Finding	Recommendation
High	No pillar page for ~22 of ~30 nav categories (Import & Export, Mobile, Troubleshooting, Security, Billing exist only as sidebar labels).	Create a lightweight pillar page per category, starting with Import & Export, Mobile, Notifications, Search, Calendar, Permissions.
High	35% of pages (48 of 139) have zero contextual internal links — entire categories are link-islands.	Add "Related articles" blocks (2-4 links) to zero-outbound pages.
High	Spokes frequently fail to link back to their own pillar (all 4 View pages don't link back to project-view).	Enforce mandatory bidirectional linking between every spoke and its pillar.
Medium	55 pages are orphaned from in-content links, reachable only via sidebar nav.	Add inbound contextual links from related content and new pillar pages.
Medium	Overlapping-scope page groups (Notifications, Search, Calendar, Permissions) are not cross-linked.	Add explicit "see also" cross-links within each overlapping group.
Medium	Password/login-recovery journey split across two competing pages.	Cross-link both pages, or consolidate into one canonical login-recovery page.
Low	Homepage does not function as a topical hub — links to only 6 hand-picked highlights.	Expand the homepage to link to a category index or more pillar pages.

Schema / Structured Data

weight 10%

Rich, well-formed Organization schema (sameAs, contactPoint, founder, parentOrganization)
FAQPage schema auto-generated from a single frontmatter source of truth — no manual drift risk by design
FAQPage markup structurally valid, deliberately retained for AI/LLM citation value
No deprecated schema types in use anywhere

Findings

Severity	Finding	Recommendation
High	WebSite `@id`/`url` broken sitewide — `site.baseUrl` (capital U) never resolves against the lowercase `baseurl` config, dropping `/guide` from the entity.	Change `site.baseUrl` to `site.baseurl` in `_includes/_seo.html`.
Medium	BreadcrumbList not implemented — gated on a config flag that's never set, and includes a file that doesn't exist.	Implement `_includes/breadcrumbs.html` with BreadcrumbList JSON-LD; set `site.breadcrumbs: true`.
Medium	Individual articles use generic CreativeWork Microdata instead of Article/TechArticle JSON-LD; dates are non-ISO.	Add a JSON-LD TechArticle block with author, publisher, image, mainEntityOfPage, ISO 8601 dates.
Medium	FAQPage schema content drifts from the visible FAQ on 8 of 139 sampled pages.	Audit and reconcile the 8 flagged pages so schema and visible FAQ match.
Info	FAQPage schema no longer produces Google rich results (retired sitewide by Google) but still has AI/LLM citation value.	No removal needed; keep as-is.
Info	HowTo schema — reviewed and implementation-ready, intentionally on hold pending AI-citation round-3 data collection.	No new action until the hold is lifted.

Performance (Core Web Vitals)

weight 10%

Lab measurement only — no Google API key configured and the keyless PageSpeed Insights quota was exhausted, so results are single-run lab data, not 75th-percentile CrUX field data.

LCP comfortably "good" (1.5–1.65s) across all 4 tested pages
Zero long tasks (>50ms) observed during load on any page
Reasonable DOM size (696–906 elements), well under bloat threshold
Correct gzip/brotli compression; zero lab-measured CLS

Findings

Severity	Finding	Recommendation
High	Static assets served with no Cache-Control/Expires headers — every repeat visit revalidates ~50 assets/page.	Add long-lived `Cache-Control: public, max-age=31536000, immutable` with cache-busting filenames.
High	All screenshots unoptimized PNG, no WebP/AVIF or responsive srcset (130–340 KB/page).	Re-encode to WebP with PNG fallback; expect 40-60% payload reduction.
Medium	No width/height attributes on any image — fragile, environment-dependent CLS risk.	Add explicit width/height attributes to every image tag.
Medium	Heavy, apparently redundant third-party analytics/ad-tag footprint — ~half of all requests per page, including duplicate Google Ads and GA IDs.	Audit with growth team; remove redundant legacy conversion/analytics tags.
Low	Render-blocking CSS/JS chain including a cross-origin Google Fonts stylesheet.	Preconnect or self-host Google Fonts; consolidate bootstrap.min.css + blog.css + main.css.
Low	Homepage TTFB (780ms) elevated vs. inner pages (480–670ms).	Investigate CDN/edge caching tier for the homepage vs. article pages.
Info	INP and field-level CWV data unavailable in this environment.	Configure a Google API key and re-run for authoritative field data, including real INP.

AI Search Readiness

weight 10%

robots.txt allows all major AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended)
Fully server-side rendered — raw HTML contains full body content, FAQ text, and JSON-LD
100% FAQ coverage across all 139 EN pages, backed by valid FAQPage JSON-LD matching visible text
Strong Organization sameAs authority signals, including a zh-TW Wikipedia entry

Findings

Severity	Finding	Recommendation
High	FAQ answers shorter than optimal AI-citation length — avg 25.9 words vs. 134–167 word sweet spot; only the tasklist-* series has been reworked.	Lengthen frontmatter FAQ answers toward 100–167 words on the ~130 uncovered pages, keeping visible FAQ copy concise.
Medium	No English Wikipedia entity for Quire the software (en.wikipedia.org/wiki/Quire is an unrelated disambiguation page).	Pursue a notability-compliant English Wikipedia article mirroring the existing zh-TW entry.
Medium	No YouTube video content embedded in guide pages despite an active channel and strong AI-citation correlation.	Embed relevant walkthroughs on high-traffic pages (add-task, board-view, permissions).
Low	No llms.txt present at domain or /guide/ root.	Generate a /guide/llms.txt from existing frontmatter listing canonical English URLs.
Low	AI training-only crawlers (CCBot, anthropic-ai) not distinguished from AI-search crawlers in robots.txt.	Add explicit Disallow rules if opting out of training-data scraping while keeping AI-search visibility.

Images

weight 5%

No horizontal scroll/overflow detected on any page or viewport tested
Responsive image/card grids and notice/callout blocks scale cleanly across breakpoints

Findings

Severity	Finding	Recommendation
High	All content images unoptimized PNG, no responsive srcset.	Re-encode to WebP/AVIF and add responsive srcset/`<picture>` markup.
Medium	Homepage thumbnails served ~2.8× larger than displayed (608×420 native vs. 214×148 shown).	Generate correctly-sized thumbnail assets instead of scaling down in CSS.
Medium	No width/height attributes on any image.	Add explicit width/height attributes to all image elements.
Low	Minor image alt-text gaps — 1 missing per page in the sampled set.	Audit and fill missing alt attributes site-wide.

Supplementary Analyses · Not weighted into the health score

Search Experience (SXO)

Branded how-to queries already rank Quire's own guide pages #1, with a strong content-format match
All sampled pages carry FAQPage schema with genuinely useful, self-contained answers

Findings

Severity	Finding	Recommendation
Critical	agile-scrum page is a feature-tour narrative where the SERP rewards a template-gallery page — didn't appear in the sampled top 10 for "agile scrum project management template".	Restructure template-first: lead with a board preview and a prominent "Duplicate This Template" CTA.
High	customer-relationship-pipeline has the same mismatch and is the thinnest page in the sample.	Add a pipeline-stage preview image and top-of-page "Use This Template" CTA.
Medium	No HowTo schema on any sampled page despite fully procedural content.	Add HowTo schema to step-based pages once the current hold on this work is lifted.
Medium	add-task guide omits the Kanban Board task-creation method that Google's synthesized answer includes.	Add a "In the Kanban Board" section and document quick-add syntax shortcuts.
Medium	Password/login-recovery journey split across two competing guide pages.	Cross-link both pages at the top, or consolidate.
Low	No embedded video despite Quire's own tutorials ranking for the same queries.	Embed a short, task-specific tutorial video near the top of relevant pages.

Visual / Mobile

No horizontal scroll/overflow detected on any page or viewport tested
Negligible Cumulative Layout Shift (~0–0.0006), no jank
H1 and intro paragraph visible above the fold on desktop and mobile without scrolling

Findings

Severity	Finding	Recommendation
Medium	Two different, non-obvious controls open two unrelated mobile menus — the hamburger opens an account menu only, hiding the real guide navigation behind a separate TOC toggle.	Merge both menus into one hamburger-triggered panel, or visually differentiate the TOC toggle.
Low	Several mobile tap targets below the 44×44px accessibility guideline (hamburger 30×30px, search icon ~24×15px).	Increase clickable padding around small icons and nav items.
Low	Mobile TOC overlay has a low-contrast, translucent dimmed background.	Use a fully opaque background for the TOC overlay panel.

Backlinks

Tier 0 · no API keys configured

quire.io is indexed and ranked in the Common Crawl web graph, not orphaned or newly registered
Harmonic centrality rank (~43,339 of all CC-graph domains) is respectable for a company site of this size

Findings

Severity	Finding	Recommendation
Info	Backlink health score cannot be reliably computed at Tier 0 — only 1 of 7 weighted scoring factors has any data.	Configure a free Moz API key and verify quire.io in Bing Webmaster Tools to unlock DA/PA and referring-domain data.
Medium	No path-level (/guide/) backlink data available from any free source — Common Crawl operates at domain granularity only.	Once Moz/Bing/DataForSEO access is available, re-run filtered to /guide/* URLs.
Low	No known-backlink list supplied for page-level verification.	Export the Links report from Google Search Console and supply it to the verification crawler.

Prioritized Action Plan

Phase 1 — Critical Fixes

Week 1

Fix hreflang values to BCP47 hyphens (pt-BR, zh-TW, zh-TW→zh-HK) in _includes/head.html
Fix site.baseUrl → site.baseurl typo in _includes/_seo.html
Remove duplicate <link rel="canonical"> tag in _layouts/default.html
Remove the duplicate, zoom-blocking viewport meta tag
Add hreflang x-default fallback to English

Phase 2 — High-Impact Improvements

Weeks 2–3

Restructure agile-scrum & customer-relationship-pipeline as template-first pages
Add Cache-Control headers for static assets at nginx
Re-encode screenshots to WebP; fix oversized homepage thumbnails
Add "Related articles" blocks to the 48 zero-outbound-link pages
Fix bidirectional pillar-spoke linking for the four View pages
Reconcile the 8 pages with FAQ schema/visible-content drift

Phase 3 — Content & Authority

Month 2

Create pillar pages for the ~22 nav categories lacking one
Lengthen frontmatter FAQ answers toward 100–167 words on ~130 pages
Add width/height attributes to all guide images
Populate last_modified_at on recently-rewritten pages
Implement BreadcrumbList schema; upgrade articles to JSON-LD TechArticle
Expand the 8 sub-200-word thin-content pages
Pursue an English Wikipedia entity for Quire (software)

Phase 4 — Monitoring & Iteration

Ongoing

Configure a Google API key for real PSI/CrUX field data
Configure a Moz API key + verify Bing Webmaster Tools for backlink data
Add IndexNow key/ping integration
Audit and remove redundant marketing/analytics tags
Spot-check templated page batches for continued differentiation
Re-audit HowTo schema once the current hold is lifted
Fix mobile navigation menu confusion

Generated from a 10-specialist automated SEO audit (claude-seo) · Full per-specialist detail in findings/*.md · Structured data in audit-data.json · Screenshots in screenshots/