Readdocs Review: clear tool, fixable gaps (76/100)

Field	Detail
Domain	readdocs.co.uk
Category	AI document summarization with OCR and question answering
Pricing	Three-tier pricing surface with visible GBP prices; normalized USD range not provided
Crawl	36 pages crawled on 2026-10-09
Review score	76/100

Readdocs makes its core job easy to understand: upload a document and receive a structured summary, key points, and Q&A. That clarity is supported by strong usability, semantic foundations, and lab performance; the tested homepage recorded a 2.1-second mobile LCP, CLS of 0, and TBT of 10 milliseconds.

The main weakness is decision support. Pricing shows three tiers and useful upload allowances, but the surface behaves more like a feature list than a recommendation. Audience messaging is also broad, so the product is understandable before it is sharply positioned. Technical SEO adds a separate fixable risk: the supplied review identifies a sitemap 404 and a live replacement canonicalized to that dead URL. Readdocs is a credible fit for professionals who routinely process reports, contracts, research papers, and administrative documents, but it needs clearer plan guidance and tighter search signals.

ReadDocs makes its category and core job legible within five seconds: upload a document and receive a summary, key points, and Q&A. The promise “Understand any document in seconds” is concrete, but the audience spans students, analysts, and professionals rather than naming one primary buyer. The homepage also gives a 34-page PDF example, though its speed claim has no visible benchmark. Lead with professionals handling contracts, reports, and research papers, then place attributable evidence beside the upload action.

A first-time visitor can identify the product, supported inputs, outputs, price, and starting point within a few clicks. The homepage names PDF, DOCX, TXT, and photos; pricing shows £0, £9.99/month, and £29/month; and upload does not require signup. The remaining messaging gap is prioritization: “Students Analysts Professionals” makes visitors choose among several jobs instead of presenting one primary workflow. Trust language says documents are processed securely and are not used to train public AI models, but retention, deletion, and processing details are not concrete in the supplied crawl.

ReadDocs has a clear front door and short core journeys: the homepage explains inputs and outputs, Pricing is one click away, and the upload handoff is clearly labelled. The homepage mobile LCP is 2.1 seconds, so slow-page friction is not the issue. Documentation is the notable exception. Cards labelled “Uploading Documents” and “Summaries & Key Points” resolve to the same /get-started destination, so the link label promises more precision than the destination provides. Split those topics into dedicated anchors or pages and repeat the selected heading at the destination. Keep “Upload a document” primary on mobile while visually subordinating the several secondary routes.

ReadDocs has strong semantic foundations: sampled pages expose header, nav, main, and footer landmarks, declare English, and report no positive tabindex values. PSI accessibility scores range from 91–96, but that baseline is not a clean bill of health. The Contact form has three visible labels without matching for/id associations or equivalent ARIA names, leaving controls programmatically unnamed. Contrast failures recur on sampled pages, and prose links rely on colour alone. The Contact heading sequence skips H2, while the shared template has no skip link. Add stable label-control associations, bring failing pairs to WCAG AA, add a non-colour link cue, correct heading levels, and provide a first-focusable skip link.

The visual system is coherent and responsive: the homepage has one H1, distinct H2 sections, 16px body text, a 36px H1, and no measured horizontal overflow at 390px. The sampled homepage also records CLS 0. Execution issues are mechanical rather than structural. The crawl reports 16 small tap targets; the Menu is 63×38px and the “Paste transcript / Upload →” action is 292×42px, both below a 44px minimum height. Pricing inputs use 14px text on mobile despite 46px height, and the blog audit finds prose links distinguished by colour alone. Raise hit areas, use at least 16px input text, add a non-colour link cue, and run a computed contrast audit before changing the palette.

In the supplied mobile lab runs, ReadDocs is fast and stable: homepage LCP is 2.1 seconds, CLS is 0, and total blocking time is 10 milliseconds. The tested blog page reaches 1.35-second LCP, while one desktop homepage run records 378 milliseconds. The main opportunity is the critical-path request chain, not a failing Core Web Vital. PageSpeed reports 11 blocking requests on the homepage and estimated savings of roughly 120–140 milliseconds across tested routes. It also estimates 30 KiB of unused JavaScript and 14 KiB of legacy JavaScript. Defer non-critical resources, reduce route code, and repeat the same mobile tests; no CrUX values were returned, so this remains a lab-only verdict.

ReadDocs explains the product plainly, especially in “Upload a PDF, Word file, text, or scan” and the concrete examples of supplier agreements, quarterly updates, and lecture notes. The editorial weakness is structure: N1 reports 649 words in one homepage paragraph, with the same one-paragraph pattern across sampled pages. Break copy around the existing sections and use shorter paragraphs beside the current cards and bullets. The voice also repeats “clarity and speed” across the homepage and footer, while pricing bullets such as “coming soon” and “optional later” make the live offer sound unfinished. Remove roadmap language from the active comparison or separate it into a dated roadmap. Repair the HTTP 404 blog path before promoting it.

The pricing grid makes the basic choice visible: Free is £0 with 3 uploads per day, Pro is £9.99/month with 300 uploads per month, and Business is £29/month with 2,000 uploads per month. It still behaves mainly as a feature list. Pro is marked “Most popular” without explaining the workload that makes it right, and Business has no operational threshold separating it from Pro. Several material constraints are future-state: a higher Pro file-size limit, Business team use, and custom outputs are marked coming soon or optional later. Replace popularity with scenario-based recommendations and explicit trade-offs; publish current file-size, support, overage, and team rules beside each tier.

ReadDocs earns credibility by warning that AI summaries can be inaccurate or incomplete and that critical numbers, dates, and legal clauses should be checked. That limitation is appropriate for document software, but it is not paired with measured accuracy, processing-time, or document-type evidence in the supplied pages. Pricing supplies concrete facts—£0 with 3 daily uploads, £9.99/month with 300 monthly uploads, and £29/month with 2,000 monthly uploads—while roadmap items must remain clearly unavailable today. Structured data reports 4.8 from 124 entries and a £9.99 Offer, but the supplied evidence does not verify the score’s provenance or the Offer’s scope. Add reproducible examples, provenance for the aggregate score, and explicit alignment between markup and visible pricing.

The clearest stability risk is an indexation conflict: a sitemap URL returns 404 while a live replacement article canonicalizes to that dead address. The crawl cannot measure traffic impact because Search Console is unavailable and no symptom date was supplied. Repair or redirect the preferred article first, remove the dead URL from the sitemap and internal links, and correct the canonical. The inventory also records the homepage as canonical for /pricing, /contact, /about, /docs, /privacy, /terms, and /get-started. Use self-canonicals for pages intended to rank independently. These are concrete, fixable signals; the available evidence does not support a measured traffic-loss claim.

Readdocs has a sound crawl foundation: robots.txt allows crawling, the sitemap is declared, an unknown URL returns 404, HTTPS consolidation takes one hop, and raw and rendered word counts match on sampled pages. The priority fix is the blog URL conflict. /blog/best-way-to-summarize-a-pdf is listed in the sitemap but returns 404, while /blog/best-free-ai-summarizers-for-students-2026 returns 200 and canonicalizes to that dead URL. Choose the preferred live article, make its canonical self-referencing, and redirect or remove the obsolete address. Several public pages canonicalize to the homepage; set self-referencing canonicals where those pages are intended as independent search results.

Readdocs works best when it shows the product in motion: the upload-to-summary workflow, supported document use cases, and direct pricing path are clear. Its strongest evidence is operational: usability scores 88/100 and lab performance scores 91/100.

The next gains are practical. First, convert the three-tier pricing surface from a feature list into buyer guidance, including a defended recommendation. Second, make the audience and proof more specific so the broad professional promise leads to a clear first use case. Third, resolve the sitemap and canonical conflicts recorded in the technical SEO review.

The product is for professionals handling reports, contracts, research papers, and administrative documents, with students and analysts as secondary users. It already explains what happens after upload; the next step is to make choosing a plan and finding the site in search equally dependable.

This 13-dimension review uses the supplied crawl artifacts, page content, sampled DOM evidence, lab performance measurements, pricing surfaces, and technical SEO checks. Readdocs was crawled across 36 pages on 2026-10-09. The score is 76/100, rounded from the persisted numeric score.

Google Search Console and analytics were unavailable, so traffic magnitude and field performance cannot be measured here. The supplied enrichment inputs also leave search-console access unavailable.

Read the full scoring approach in How SiteList scores.