| Fact | Value |
|---|---|
| Domain | legaliser.com |
| Category | AI-powered contract lifecycle management and legal research |
| Pricing | Free tier and paid plans stated; exact pricing not verified |
| Crawl | 37 pages, crawled 2026-10-08 |
Legaliser Review: Clear SaaS, SEO Risks (66/100)
Legaliser scores 66/100, with strong buying-path usability, clear pricing access, and real documentation assets. Identity confusion across domains and sitemap signals, fragmented editorial quality, and a 2.85-second mobile LCP are the most material weaknesses.
Reviewed by SiteList Engine · 13 dimensions · published Reviewed on October 8, 2026
Is this your site?
Claim itQuick facts
- Pages crawled
- 37
- Crawl date
- 2026-10-08
Executive summary
Legaliser scores 66/100 because its core SaaS buying path is clear, while search identity and content quality remain material risks. Usability leads the supplied table at 84/100: visitors can identify the product, open Pricing, start registration, and reach Docs in one click from the homepage. Audience and messaging scores 76/100, supported by pricing access and a free tier, but the site does not prioritize a lead audience or workflow. Performance is 72/100: desktop is fast, while mobile LCP reaches 2.85 seconds against the 2.5-second good threshold, with roughly 1.6–1.95 MB and 25–26 blocking resources on the critical path. Writing quality is weaker at 58/100, with a missing pricing H1, long extracted blocks, repeated step content, and a 404 template page. Technical SEO is 55/100, with domain identity and sitemap signals creating the main search risk. Documentation is present at 70/100 but fragmented.
- Overall score
- 66/100
- Usability
- 84/100
- Mobile LCP
- 2.85 seconds
- Technical SEO
- 55/100
01 · First impressions & positioning — one identity, one contract-lifecycle promise
Legaliser presents a credible legal-document platform, but legaliser.com and Agreements.ai divide recognition. The hero, Fair Agreements, Made Simple with AI, is approachable and supported by workflows, pricing, named testimonials, and comparison content. Contract management and case research also compete for focus. Choose one public identity, explain any transition, and make one contract-lifecycle promise the organizing idea for the homepage.
- Score
- 72/100
02 · Audience & messaging — clear category, broad decision path
Visitors can understand the category, find pricing, and start with a free tier, but the message serves too many audiences. Copy addresses people with no legal expertise, while testimonials and plans span individuals, businesses, professionals, teams, and research users. Add audience-specific entry points and organize navigation around the contract lifecycle so each visitor can identify the most relevant workflow without sorting through the full feature breadth.
- Score
- 76/100
03 · Usability — one-click paths, 5.9 s mobile interaction
The homepage reaches product information, Pricing, registration, and Docs in one click, and Docs separates User Guide from Developer Docs. The main friction is consistency: “Get Started Free”, “Start Analyzing Free”, and “Get Started” point toward the same conversion direction. Mobile interaction takes 5.9 seconds, with 3.3 seconds of main-thread work. Standardize the registration label, add audience cues to the docs cards, and defer non-critical JavaScript.
- Time to Interactive
- 5.9 s
04 · Accessibility — unnamed controls and failed contrast remain
The sampled pages show a useful semantic baseline, but measured barriers remain. The templates input lacks an accessible name, homepage buttons are unnamed, and homepage contrast audits fail. Several sampled pages omit a main landmark, and no skip link was detected. Associate the templates input with a visible label, name every button, remediate the measured contrast pairs, then add one main landmark and a keyboard-visible skip link to each page template.
- Accessibility score
- 68/100
05 · Design execution — 16 small mobile targets and 375 colors
The 390px homepage has 16px body text, a 36px mobile H1, and CLS 0, so the responsive foundation is sound. Interaction polish is less consistent: 16 mobile targets are below the supplied 44px target, including a 14x14px button and several 38x38px controls. The CSS inventory also reports 375 colors, 53 font sizes, 22 radii, and five font families. Fix hit areas and names first, then consolidate tokens.
- Small mobile tap targets
- 16
06 · Performance — 2,851 ms mobile LCP on a 1,918 KB homepage
Desktop LCP is 663 ms, but mobile LCP is 2,851 ms against the 2.5-second good threshold. The homepage transfers 1,918 KB across 80 requests with 26 blocking requests; mobile Time to Interactive reaches 5,861 ms and Total Blocking Time is 108 ms. Identify and prioritize the mobile LCP request, defer below-fold code and hydration, and reduce the blocking chain until LCP reaches 2,500 ms or less.
- Mobile LCP
- 2,851 ms
07 · Writing quality — useful product copy weakened by structural defects
The copy is product-specific, but presentation and maintenance weaken it. Pricing has no H1, its 747 words are extracted as one paragraph, and average sentence length is 37.4 words. The AI contract-creation page repeats the same three-step headings, while the employment-contract template URL returns 404 with five recorded words. Add a real pricing H1, use scannable plan structure, deduplicate the workflow, and repair or redirect the dead template URL.
- Pricing average sentence length
- 37.4 words
08 · Decision-support surfaces — comparisons need dated evidence and tradeoffs
Pricing and competitor comparison pages give visitors a practical starting point, but the decision layer is not yet sufficiently qualified. Binary comparison grids sit beside an Our Pick verdict without a dated methodology or visible source trail, which makes the recommendation harder to verify. Add segmented recommendations for different buyer priorities, state tradeoffs plainly, and attach retrieval dates and source links to each comparison claim. Keep the existing pricing access and free-tier path.
- Comparison verdict
- Our Pick is presented without a supplied methodology or dated evidence block
09 · Review-content integrity — 4.8 markup needs visible support
Competitor verdicts and AggregateRating markup are present, but the supplied crawl does not expose a methodology, source trail, or visible review evidence that would let readers verify them. The homepage reports a 4.8 score from 1,250 ratings, while its Offer validity date is 2025-12-31 and the crawl began on 2026-10-08. Add per-comparison sources and dates, support the score visibly and legitimately, and refresh or remove expired pricing metadata.
- AggregateRating
- 4.8 from 1,250 ratings
10 · Risk & stability — domain consolidation is the main loss-capable mechanism
The main stability risk is unresolved domain consolidation. Pages served on legaliser.com point canonicals, the robots Host, and the sitemap toward agreements.ai; none of the 37 sampled rows is marked in the sitemap. Choose one ranking property, align redirects, canonicals, robots, sitemap, and internal links, then confirm whether the two sampled paths should be restored or redirected.
- Crawled rows marked in sitemap
- 0 of 37
11 · Editorial QA of content — status, headings, and canonicals need gates
The sampled corpus has a visible QA gap: the employment-contract template is a 404 with five words, pricing lacks an H1, instructional headings repeat, and many pages canonicalize from legaliser.com to agreements.ai. These defects connect what the site publishes, what users can open, and which host search engines should trust. Add release checks for status, one H1, canonical host, and duplicate heading sequences, then rerun the crawl after technical cleanup.
- Crawl coverage
- 37 of 40 pages
12 · Docs & self-serve help — real assets, fragmented discovery
Legaliser has more than a brochure-level help surface: the crawl found a REST API reference with authentication, responses, endpoints, webhooks, and 72 code blocks, alongside legal guides, template help, and a support route. Build a searchable hub with task guides, API reference, support escalation, update dates, and persistent navigation.
- API reference code blocks
- 72
13 · Technical SEO — 1,332 sitemap URLs conflict with the crawled host
The site is technically renderable: key pages return 200, raw and rendered word counts are effectively identical, HTTPS redirects work, the nonexistent-URL probe returns a true 404, and sampled responses include HSTS and nosniff. The dominant risk is canonical identity: legaliser.com pages point to agreements.ai, robots names that host, and its sitemap lists 1,332 URLs while all 37 sampled rows show inSitemap=false.
- Sitemap URL count
- 1,332
Verdict — 66/100: usable SaaS foundation, material search and content risks
Legaliser is a usable SaaS proposition for freelancers, growing businesses, legal professionals, and operations teams: the homepage exposes the main buying tasks, pricing, registration, and Docs with a strong primary navigation. The product also has meaningful support material, including legal guides, a REST API reference with code examples, template help content, and a support contact route. The fix list is focused. Resolve the inconsistent domain identity and sitemap signals that may split or transfer indexing signals away from the crawled host. Reduce the mobile critical path, which records a 2.85-second LCP and roughly 1.6–1.95 MB with 25–26 blocking resources. Then repair the editorial surface: the supplied summary cites a missing pricing H1, long extracted blocks, repeated step content, and a 404 template page. This is a fair 66/100 result: the product path works, but search and content foundations need disciplined maintenance.
- Overall score
- 66/100
- Risk & stability
- 58/100
- Writing quality
- 58/100
Methodology & data notes
This 13-dimension review uses the supplied SiteList crawl, site profile, public dimension score table, dimension-level findings, and drafted analysis supplied in the evidence index for 37 pages crawled on 2026-10-08. The article summarizes the supplied dimension outputs; it does not add a separate site analysis. The public inputs report Google Search Console access as not connected or available. Pricing is described as unknown in the site facts, while the profile states a free tier and paid plans. No additional excluded dimensions or pending enrichments are specified in the supplied frame inputs. Read How SiteList scores for the review method.
- Review dimensions
- 13
- Pages crawled
- 37
- GSC access
- false / not connected
Questions buyers actually ask
Who is Legaliser for?
Legaliser is positioned for freelancers, growing businesses, legal professionals, and teams and research users. Its stated vertical is AI-powered contract lifecycle management and legal research.
Can visitors find pricing and documentation?
Yes. The supplied summary says visitors can open Pricing, start registration, and reach Docs in one click from the homepage. The site also has legal guides, a REST API reference, template help content, and a support contact route.
How does Legaliser perform on mobile?
The sampled mobile lab result recorded a 2.85-second LCP, versus the 2.5-second good threshold. The critical path was roughly 1.6–1.95 MB with 25–26 blocking resources in the supplied summary.
What are Legaliser main technical risks?
The supplied review identifies inconsistent domain identity and sitemap signals, plus pages on legaliser.com pointing search signals elsewhere. It also reports inconsistent canonicalization and URL health across the public corpus.
Does Legaliser offer self-serve help?
Legaliser has documentation assets including legal guides, a REST API reference with code examples, template help content, and a support contact route. The supplied summary describes the system as functional but fragmented.