Whole Site Checked · 1,932 Pages · 14 Languages · July 2, 2026
This is a plain-English summary of how easy it is for Google, and AI tools like ChatGPT and Perplexity, to find, understand, and recommend Quire's help pages — what's working well, and what needs fixing. No technical background needed to read this.
How to read the score. Think of 71 out of 100 like a health check-up result — it's a blended average across 7 different areas, each weighted by how much it matters. Two areas are dragging the score down: how well pages link to each other, and how images are handled. Both are structural/technical issues, not writing problems. Content Quality and Mobile Experience are our strongest areas. We couldn't give a real score for "Other Sites Linking In" because we don't currently have access to the paid tools that measure that.
OVERALL SCORE — OUT OF 100
Overall, Quire's help center is in good shape: pages load fast and completely, every article exists in all 14 languages, and pages already follow a clear, consistent layout. The score is mainly held back by pages that don't link to each other enough, plus a handful of small coding mistakes that are quick to fix.
Top 5 Things To Fix First
🔴
Three language versions have a small labeling mistake — Brazilian Portuguese, and Traditional Chinese for Taiwan and Hong Kong are tagged in a format Google may not recognize as valid, across nearly 1,500 pages. This could mean Google isn't properly connecting those translated pages to their English originals.
🔴
Two pages don't match what people expect to see when they search. The Agile/Scrum guide and the CRM Pipeline guide read like general articles, but people searching for those topics expect a ready-to-use template with a big "use this" button — like what Trello or monday.com show. Both pages are likely losing visitors to competitors as a result.
🟠
Visitors can't zoom in on their phones. A leftover coding mistake accidentally turns off pinch-to-zoom on every page, even though the correct setting already exists elsewhere in the same code — the browser just uses the wrong one it sees first.
🟠
A one-letter typo is sending Google to the wrong web address. The hidden information that tells Google "this website is called Quire Guide, and here's its address" points to the wrong page because of a small capitalization mistake in the code.
🟠
About a third of help pages don't link to any other page. And roughly 22 of the 30 topic areas (like Mobile, Security, Import & Export) don't have a main page introducing them. This makes it harder for both Google and AI tools to understand how Quire's features relate to each other.
Scorecard By Area
Content Quality
84
Site Setup
78
AI Search Readiness
77
Loading Speed
68
Behind-the-Scenes Data
60
Page Links
58
Images
55
Easy Wins · Small Effort, Real Payoff
⚡
Fix the language-labeling mistake for the 3 affected languages — the correct format already exists elsewhere in the code, so this is a small, one-line fix. It affects around 1,500 pages at once.
⚡
Fix the one-letter typo that's pointing Google to the wrong web address.
⚡
Delete two duplicate, conflicting lines of code — one is causing the mobile zoom problem, the other is a harmless-but-messy duplicate.
⚡
Tell the web server to let visitors' browsers remember (cache) style and image files, so repeat visits load faster — a settings change, no content work needed.
⚡
Add a "default language" fallback so visitors whose language isn't one of the 13 translations still land somewhere sensible.
Site Setup
22% of score
78
How easy the site is for Google, browsers, and AI tools to read and navigate.
Every page loads as a complete, ready-to-read page — visitors and search engines don't have to wait for anything extra to load before seeing the content.
The site's instructions file correctly allows Google and AI tools to read the help center, and points them to a full listing of every page.
All 13 translated languages have the exact same 138 pages as English — nothing is missing in any language.
Every page correctly links to its translated versions in the other 13 languages.
Clean, simple web addresses; broken links redirect properly; a proper "page not found" message; secure connection; pages are compressed to load faster.
What We Found
Priority
What's happening
What to do
Critical
Three language versions — Brazilian Portuguese, and Traditional Chinese for Taiwan and Hong Kong — are labeled using a format (with underscores) that Google may not recognize as valid. This happens on all 1,932 pages, and could mean Google isn't properly linking these translations to their English originals for 3 of the 13 languages.For developers: use the hyphenated lang.bcp47 value (already defined in _data/i18n.yml) instead of lang.code in _includes/head.html.
Fix the labeling format for these 3 languages — the correct version already exists elsewhere in the code.
High
There's no "default language" instruction, so a visitor whose browser language doesn't match any of the 13 translations has no clear fallback page.For developers: add an hreflang="x-default" alternate pointing to the English URL.
Add a fallback that points unmatched visitors to the English version.
High
Every page accidentally includes the "this is the official version of this page" tag twice. They currently say the same thing, but having two is a leftover mistake that could cause confusion if one is ever edited without the other.For developers: duplicate <link rel="canonical"> in _layouts/default.html (lines ~59 and ~78).
Delete one of the two duplicate lines.
High
A leftover setting turns off pinch-to-zoom on mobile phones for every page, even though the correct, zoom-friendly setting also exists later in the same page. Browsers use whichever one they see first — the broken one.For developers: conflicting viewport tags — remove the restrictive one in _layouts/default.html:74, keep the correct one in _includes/head.html:30.
Remove the setting that's blocking zoom.
Medium
None of the images tell the browser how big they'll be ahead of time, which can cause the page to visibly jump around while loading, especially on slower connections.
Add size information to every image.
Medium
Some style files (including a font loaded from Google's servers) delay how quickly the page can start showing content, because the browser doesn't get a "heads up" connection to that server in advance.
Set up that advance connection, and simplify how many style files load at once.
Medium
The site is missing a few standard security settings, and doesn't tell browsers how long to remember files — which slows down repeat visits.
Add the missing security settings and enable file caching.
Low
The account/login menu and notification area load before the actual help article content in the page's underlying code. Visitors don't notice this, but it means search engines and AI tools have to "read past" some irrelevant content before reaching the real article.
Reorder the underlying code so the article content comes first (the visible layout wouldn't need to change).
Low
Quire doesn't use a feature that can instantly notify Bing, Yandex, and Naver search engines when a page changes, instead of waiting for them to notice on their own.
Set up that instant-notify feature.
Content Quality
23% of score
84
How well-written, trustworthy, and complete the help articles are.
Every one of the 139 English articles follows the same easy-to-follow structure: a short intro, clear section headings, and a FAQ at the bottom.
Every English page's visible FAQ matches the hidden FAQ data exactly — great material for AI tools to quote accurately.
Solid trust signals throughout: real contact information, links to security/privacy/terms pages, and a feedback widget.
Pages translated by AI are clearly labeled as such, with a link back to the original English version — an honest, transparent practice.
No copy-pasted duplicate content anywhere; even similar-sounding pages (like "leave an organization" vs. "leave a project") are written specifically for their own situation.
What We Found
Priority
What's happening
What to do
Medium
About a quarter of pages (35 of 139) are quite short — under 400 words — and 8 of those are under 200 words. Short isn't always bad, but some of these could use more helpful detail.
Add useful detail to the shortest pages where it would genuinely help; leave simple pages as they are if there's nothing more to say.
Medium
86% of pages show the exact same "last updated" date from 2019, even though some of them were genuinely rewritten as recently as this year. This makes the content look older and less trustworthy than it really is.
Update the "last updated" date whenever a page is genuinely rewritten.
Low
No individual page names an author or editor — the only "who wrote this" signal is at the whole-company level.
Add a simple site-wide byline like "Written and maintained by the Quire Support Team."
Low
The homepage's very first heading breaks the pattern used on every other page, and unlike every other page, it has no FAQ section at the bottom.
Adjust the homepage heading order; treat the missing FAQ as an intentional, documented exception.
Info
A few pairs of similar pages (like two different "how to leave X" articles) reuse very similar sentence patterns. Each one is still accurate and specific to its own topic today, so this isn't a problem yet.
Just keep an eye on this as new similar pages get added.
Page Links
20% of score
58
How well pages point visitors — and search engines — to other related pages.
8 "Overview" pages act as good central hub pages, correctly pointing out to their related articles.
The set of 6 Formula-related pages is a great example of pages that all link to each other well.
Pages with similar-sounding names actually cover different topics without confusing or competing with each other.
What We Found
Priority
What's happening
What to do
High
About 22 of Quire's 30 topic areas (like Mobile, Security, Billing, Import & Export) have no main page introducing the topic and linking out to its related articles — they only exist as a label in the sidebar menu.
Create a short overview page for each of these topic areas, starting with Import & Export, Mobile, Notifications, Search, Calendar, and Permissions.
High
35% of pages (48 of 139) don't link to any other help article at all. Whole topic areas are cut off from the rest of the site — for example, 4 of the 5 Import & Export pages link to nothing else.Why this matters: The sidebar menu is a site-wide navigation shortcut — search engines and AI tools give it much less weight than a link written directly into an article's text. A link inside the article body is what actually tells them "these two pages are related." Without it, a page risks being treated as isolated: harder for search engines to index with confidence, and more likely to be read by AI answer engines (ChatGPT, Perplexity, Google's AI Overviews) as a disconnected, one-off page rather than part of a connected topic.
Add a short "Related articles" list (2-4 links) to every page that currently has none.
High
Several hub pages link out to their related articles, but those articles don't link back. For example, the Calendar, Timeline, Table, and Board view pages don't link back to the main "Project Views" page that links to all of them.
Make sure every article links back to its overview page, and vice versa.
Medium
55 pages can only be found through the sidebar menu — no other help article links to them directly. Search engines and AI tools generally trust links found within article text more than a website's navigation menu.Why this matters: Google, ChatGPT, and Perplexity mainly judge a page's importance and topic relationships from links inside the article body, not from a site-wide UI element like the sidebar nav — sidebar links carry much less weight. With no in-content links pointing to them, these 55 pages read as isolated islands: search engines and AI systems have a harder time telling how they relate to the rest of the guide, which risks lower rankings, weaker indexing, and being treated as disconnected one-offs rather than part of a topic cluster. Tracked in issue #390.
Add links to these pages from related articles.
Medium
Related topics split across multiple pages (like Notifications, Search, Calendar, and Permissions) don't link to each other, even though someone reading one is likely to want the others too.Why this matters: Without "see also" links, Google or AI engines can end up alternating between these near-duplicate pages for a broad query instead of settling on one clear answer (a soft cannibalization risk), and it's harder for them to recognize the pages as facets of one topic cluster rather than unrelated one-offs. It also leaves readers unaware that a related page with a different angle exists.
Add "see also" links connecting each group of related pages.
Medium
Two separate pages both try to help someone who's locked out of their account or needs to reset their password, but neither page mentions the other.
Add a link between the two pages, or combine them into one clear page.
Low
The homepage only links to 6 hand-picked feature highlights, rather than pointing to all the main topic areas, so it doesn't work well as a map of the whole help center.
Expand the homepage to link to more of the main topic areas.
Behind-the-Scenes Data
10% of score
60
Hidden data on each page that tells Google and AI tools what the content actually means (not visible to regular visitors).
The company information Google reads about Quire (founder, official social profiles, etc.) is complete and correctly formatted.
The FAQ data behind every page is generated automatically from one single source, so the visible FAQ and the hidden data can't accidentally say different things.
That FAQ data is technically correct and deliberately kept in place — even though Google no longer shows FAQ boxes directly in search results — because it still helps AI tools like ChatGPT accurately quote Quire's content.
No outdated or discontinued types of hidden data are being used anywhere on the site.
What We Found
Priority
What's happening
What to do
High
A single-letter typo in the website's code means the hidden "this website is called Quire Guide, and here's its address" information points to the wrong web address on every single page.For developers: site.baseUrl (capital U) never resolves against the actual lowercase baseurl config value — fix in _includes/_seo.html.
Fix the typo so the setting matches correctly.
Medium
The "breadcrumb trail" feature (the small "Home > Category > Page" trail search results sometimes show) is switched off, and can't be turned on yet because a required piece of the code is missing.
Build the missing piece and turn the feature on.
Medium
Individual articles are labeled with an older, more generic type of hidden data instead of a proper "this is a help article" format that includes things like author, publisher, and a correctly-formatted date.
Upgrade to the more complete article format.
Medium
On 8 out of 139 pages, the FAQ questions stored in the hidden data don't actually match the FAQ questions visitors can see on the page.
Go through those 8 pages and make sure the hidden data and the visible FAQ match.
Info
The hidden FAQ data no longer earns a special FAQ box in Google search results — Google discontinued that feature sitewide for everyone — but it's still valuable for AI tools, so no need to remove it.
No action needed.
Info
There's a ready-to-go plan for adding "step-by-step instructions" data to how-to pages, but the team has intentionally decided to wait until more data comes in before turning it on.
No action needed right now.
Loading Speed
10% of score
68
How fast pages feel to load, and how stable they look while doing so.
A note on how we measured this: we didn't have access to Google's own real-world visitor speed data for this check, so these numbers come from our own test loads on a fast connection. Real visitors on slower connections or older phones may see somewhat different results.
The main content of every page we tested appears comfortably fast (under 2 seconds) — well within what Google considers "good."
We didn't see any heavy scripts freezing up the page while it loads.
Pages aren't overloaded with excessive page elements.
Pages are properly compressed for faster delivery, and nothing visibly jumped around during our tests.
What We Found
Priority
What's happening
What to do
High
The site doesn't tell visitors' browsers to remember (cache) style files, scripts, and images. That means every time someone comes back to the help center, their browser has to re-check nearly everything from scratch instead of using what it already saved.
Turn on long-term caching for these files on the server.
High
Every screenshot on the help pages uses an older image format that's larger than it needs to be, and none of them are specifically sized for how they're actually displayed.
Convert images to a modern, smaller format and generate properly-sized versions.
Medium
Images don't tell the browser their size ahead of time, which is a common cause of pages visibly jumping around while loading — we didn't see this happen in our fast test, but it can happen more easily on slower connections.
Add size information to every image.
Medium
Roughly half of everything that loads on each page is marketing and analytics tracking code (ads, visit-tracking, etc.), and some of it looks like duplicate or leftover tracking codes that may no longer be needed.
Have the marketing team review and remove anything no longer in use.
Low
A few style files, including one loaded from Google's font service, delay how quickly the page can start showing content.
Set up a faster connection shortcut to Google's font service, or host the fonts directly on Quire's own server.
Low
The homepage takes slightly longer to start responding than the other help pages do.
Check whether the homepage is being served differently (e.g. a colder cache) than article pages.
Info
We couldn't measure real-world "responsiveness to clicks and taps" without access to Google's live visitor data.
Re-check this once that data access is available.
AI Search Readiness
10% of score
77
How easily AI tools like ChatGPT, Perplexity, and Google's AI answers can find and quote Quire's content.
The site's instructions file allows all the major AI tools (ChatGPT's crawler, Perplexity, Claude, Google's AI features) to read the help center.
Because pages load as complete, ready-to-read content, AI tools can read everything directly without extra steps.
Every English page has a complete FAQ section that matches its hidden data exactly — great material for AI tools to quote accurately.
Quire has solid outside recognition: official profiles on LinkedIn, YouTube, G2, Capterra, and Trustpilot, plus a Wikipedia page in Traditional Chinese.
What We Found
Priority
What's happening
What to do
High
FAQ answers across the help center are fairly short — about 26 words on average. AI tools tend to prefer quoting longer, more detailed answers (roughly 130-170 words). Only about 10 pages have been rewritten with longer answers so far.
Gradually make FAQ answers a bit more detailed on the remaining ~130 pages, while keeping what visitors actually see on the page short and simple.
Medium
There's no English Wikipedia page about Quire the software — searching for it currently lands on an unrelated page about paper sizes and a magazine with a similar name — even though a Chinese-language Wikipedia page about Quire already exists.
Work on getting a proper, neutral English Wikipedia entry created.
Medium
Quire has an active YouTube channel, but none of its tutorial videos are actually embedded in the help articles themselves.
Add relevant existing videos directly onto the most-visited help pages.
Low
Quire doesn't have a file that gives AI tools a curated summary/index of the website's content (a newer, optional practice some sites are adopting).
Consider creating one.
Low
The site's instructions file doesn't distinguish between AI tools that answer search questions (which Quire likely wants to allow) and AI tools that only collect content to train other companies' models.
Decide whether to allow all AI bots or only the search-answering ones, and adjust the instructions file accordingly.
Images
5% of score
55
How pictures on the help pages are sized, optimized, and labeled.
No pages have images causing the page to scroll sideways awkwardly.
Image layouts adjust cleanly to different screen sizes.
What We Found
Priority
What's happening
What to do
High
Every screenshot is saved in an older image format that's larger than it needs to be, with no smaller versions provided for phones.
Convert to a modern image format and provide appropriately-sized versions for different screen sizes.
Medium
Several homepage thumbnail images are roughly 3 times larger (in file size and dimensions) than the space they're actually displayed in.
Create correctly-sized versions of these specific images.
Medium
Images don't specify their dimensions in advance, which can cause pages to visibly shift while loading.
Add size information to every image.
Low
A small number of images (about 1 per page checked) are missing descriptive text for screen readers and search engines.
Add descriptive text to the images that are missing it.
Extra Checks · Not Counted in the Overall Score
Search Match
63
Whether pages match what people actually expect to see when they search for that topic.
For direct, branded searches (like "how to add a task in Quire"), Quire's own help pages already show up first in Google, matching what Google is looking for.
All the pages checked have solid, self-contained FAQ answers.
What We Found
Priority
What's happening
What to do
Critical
For a search like "agile scrum project management template," Google shows a mix of ready-to-use templates with a preview image and a big "use this template" button. Quire's page on this topic instead reads like a general explainer article, with the actual template link buried near the bottom — so it's currently missing out on this search traffic entirely.
Redesign this page to lead with a visual preview and a prominent "use this template" button, the way competitors do.
High
The same problem shows up on the CRM Pipeline page — it's also the shortest, least detailed page in our sample, and doesn't show up for its target search either.
Add a visual preview and a clear "use this template" button near the top of the page.
Medium
None of the sampled how-to pages use a special type of hidden "these are step-by-step instructions" data, even though all of them are written as numbered steps.
Add this once the currently-paused related project resumes.
Medium
The "how to add a task" guide doesn't mention adding tasks from the Kanban Board view, or the quick shortcuts for typing dates and assignees — both of which Google's own AI answer already includes when summarizing this topic.
Add these missing methods to the page.
Medium
Two separate pages both try to help with password/login problems, without pointing readers to each other.
Cross-link the two pages, or merge them.
Low
None of the sampled pages include a short video, even though Quire has its own tutorial videos that already show up in search results for these same topics.
Embed a short, relevant video near the top of these pages.
Mobile Experience
82
How the site looks and feels to use, especially on a phone.
Nothing causes pages to scroll sideways awkwardly on any device tested.
Pages don't visibly jump or shift while loading.
The main heading and intro text are visible right away on both desktop and mobile, without needing to scroll.
What We Found
Priority
What's happening
What to do
Medium
On mobile, there are two separate menu buttons that aren't clearly explained: tapping the main menu icon only opens a login/signup menu, while the actual list of help topics is hidden behind a different, less obvious button. A first-time visitor tapping the main menu expecting to browse topics won't find them there.
Either combine both menus into one, or make it clearer what each button does.
Low
A few buttons and menu items on mobile (like the menu icon and search icon) are smaller than the recommended minimum size for comfortable tapping.
Make these tap targets a bit bigger.
Low
When the mobile menu opens over an article, the text behind it is still faintly visible, which looks a little messy.
Make the background behind the mobile menu fully solid instead of see-through.
Other Sites Linking In
Limited data available
How many other websites link to Quire's help center, and how trustworthy those links are.
Quire's main website is recognized and indexed by the free tools we do have access to — it's an established, real site, not a brand-new or obscure one.
Its general "how well-connected is this website" ranking is respectable for a company of Quire's size.
What We Found
Priority
What's happening
What to do
Info
We don't currently have access to the paid tools (like Moz or Bing Webmaster Tools) that would tell us exactly how many other websites link to Quire, or how trustworthy those links are. Without them, we can only see a rough, big-picture signal — not a real score.
Set up a free account with one of these tools to unlock this data.
Medium
Even with those tools, most free data sources can only tell us about links to the whole quire.io website, not specifically to the /guide/ help pages.
Once better tools are available, check the help pages specifically.
Low
We didn't have a list of Quire's existing known backlinks to double-check, which would normally help confirm which links are still live and legitimate.
Pull that list from Google Search Console and check it next time.
What To Do Next
Phase 1 — This Week
Small code fixes, no writing needed
Fix the language-labeling mistake for the 3 affected languages
Fix the one-letter typo pointing Google to the wrong web address
Delete the two duplicate/conflicting code lines (the zoom problem and the duplicate "official page" tag)
Add a "default language" fallback for unmatched visitors
Phase 2 — Next Few Weeks
Bigger, but still fairly quick
Redesign the Agile/Scrum and CRM Pipeline pages to lead with a template preview, not just an explanation
Turn on browser caching for style and image files
Convert screenshots to a smaller, modern image format; fix oversized homepage thumbnails
Add a short "related articles" list to the ~48 pages that currently link nowhere else
Make sure related pages link back and forth to each other (especially the 4 main "views" pages)
Fix the 8 pages where the hidden FAQ data doesn't match what's visible
Phase 3 — Next Couple Months
Content and structure work
Create a short overview page for each of the ~22 topic areas that don't have one yet
Make FAQ answers a bit longer and more detailed on ~130 pages, to help AI tools quote them well
Add image size information across all guide images
Update the "last updated" date on pages that have genuinely been rewritten recently
Add breadcrumb navigation, and upgrade articles to a more complete, modern data format
Add more detail to the 8 shortest, thinnest pages
Start the process of getting an English Wikipedia page created for Quire
Phase 4 — Ongoing
As resources allow
Get access to Google's real performance-measurement tools for more accurate speed data
Get access to backlink-tracking tools (Moz, Bing Webmaster Tools) for real link data
Set up instant notifications to Bing/Yandex/Naver when pages update
Review and clean up duplicate marketing/tracking codes with the marketing team
Periodically double-check that similar pages stay written specifically, not just templated
Revisit the paused "step-by-step instructions" data project once it's unblocked