Skip to content
SiteList

Astrologybot Review: strong product, clear fixes (76/100)

Astrologybot scores 76/100, with clear mobile presentation, strong usability, and a specific astrology-focused voice. Its most material weaknesses are a 3.2-second mobile LCP, unclear pricing, and duplicated blog paths that can split internal equity.

Reviewed by SiteList Engine · 9 of 13 dimensions · published Reviewed on September 28, 2026

Is this your site?

Claim it

Quick facts

Astrologybot is an astrology-analysis service for individuals with usage-based pricing.

Fact Value
Domain astrologybot.app
Category Astrology analysis for individuals
Pricing Usage-based; USD range not confirmed
Pages crawled 24
Crawl date 2026-09-28
Evidence
Pages crawled
24
Crawl date
2026-09-28

Executive summary

Astrologybot is a strong, focused service with a 76/100 overall score. Its strongest public results are usability at 85/100, design execution at 82/100, first impressions and positioning at 78/100, accessibility at 78/100, and technical SEO at 78/100.

The site communicates a specific astrology use case and maintains a distinct developer-astrologer voice. The main constraints are practical: audience and messaging score 68/100 because the intended user segment and total cost are not stated clearly; performance scores 65/100 because mobile LCP is 3.2 seconds and layout shifts remain; writing quality scores 72/100 because of a structural presentation flaw; and risk and stability score 74/100 because duplicate /blog/* and /en/blog/* paths can split internal equity.

Technical foundations are solid: HTTPS is enforced, www consolidates to non-www, and sampled raw-to-rendered content parity is 1.0.

Evidence
Overall score
76/100
Usability
85/100
Performance
65/100; 3.2-second mobile LCP
Technical SEO
78/100; content parity ratio 1.0

01 · First impressions & positioning — clear astrology service, weak proof and audience signal

Astrology Bot presents a focused astrology service, but its first screen does not identify a specific audience or establish proof. The hero line, ‘See yourself clearly. Then the people in your life.’, is memorable yet does not say who the service is for. The H1 phrase ‘AI-Powered Natal Chart Analysis’ also introduces terminology that may be unfamiliar to prospects. The site mentions planetary positions, houses, and aspects without explanation, adding more friction. No named customers or logos appear in the hero or within one scroll of the claim, and no comparison pages support differentiation. Use plain category language, state the intended audience, and place a named testimonial or other proof directly below the hero.

Evidence
Hero copy
See yourself clearly. Then the people in your life.
Hero proof
No named customers or logos visible in the hero section

02 · Audience & messaging — clear interest area, unclear total cost and reassurance

Astrology Bot speaks to people interested in astrology, but it leaves three practical buying questions unanswered: who exactly is it for, what will it cost in total, and what happens if the experience goes wrong. The pricing message says ‘€1 to start’ and mentions pay as you go, without a clear breakdown by feature, question, or usage tier. The site also provides no testimonials, case studies, or customer reviews, while its disclaimer frames the service as entertainment only. Terms such as ‘AI’ and ‘natal chart’ are not explained for newcomers. Name the intended users, publish a complete pricing table, add customer evidence, and state returns, cancellations, and support clearly.

Evidence
Starting price message
€1 to start
Trust evidence
No testimonials, case studies, or reviews found

03 · Usability — strong core CTA, pricing hidden behind at least two clicks

The core path is understandable: the homepage communicates a value proposition and offers an immediate ‘Try it free’ CTA. Task completion becomes less direct when visitors need pricing. The pricing information is reached through the blog landing page and then a specific article, requiring at least two clicks before a first-time visitor can assess cost. Navigation labels such as ‘How it works’ and ‘About’ also make users infer what they will find, while link styling differs between text links and button-like account actions. Add a direct Pricing link or homepage pricing section, use action-oriented labels, and apply one consistent visual treatment to informational links and calls to action.

Evidence
Pricing path
At least 2 clicks through the blog to reach pricing details
Primary CTA
Try it free

04 · Accessibility — 78/100, with keyboard entry and contrast gaps

Accessibility is broadly structured but misses several controls that matter immediately to keyboard and low-vision users. The crawl found no skip link despite nav, main, footer, and section landmarks, so keyboard users must pass repeated navigation before reaching content. One generic ‘learn more’ link also lacks destination context. The audit reports contrast failures and color-only signaling for links and errors, while the stylesheet contains outline:none or outline:0 without an identified focus-visible rule. Add a visible ‘Skip to main content’ link, replace generic link text, pair color with text or another cue, and restore clear focus indicators. The existing heading hierarchy and semantic landmarks provide a sound base.

Evidence
Skip link
hasSkipLink: false
Generic link text
1 instance of ‘learn more’
Contrast
Color-contrast failures reported by PSI audit

05 · Design execution — strong mobile structure, 2.8:1 text contrast

The interface has a clear hierarchy and holds together well on mobile: the crawl found no horizontal scroll, tap targets reach 44px, inputs reach 16px, and pages use one H1 without skipped heading levels. The central design failure is contrast. Sampled text using #9CA3AF on white computes to 2.8:1 against the 4.5:1 body-text requirement; the same pattern affects body copy, buttons, form fields, links, and headings. The token system also shows severe drift, with 11 distinct colors and 11 distinct font sizes. Darken the text to #4B5563, or move affected elements onto a darker background, then consolidate repeated color and type values into a smaller token set.

Evidence
Mobile correctness
No horizontal scroll; 44px tap targets; 16px inputs
Text contrast
2.8:1 versus 4.5:1 required for body text
Token drift
11 distinct colors and 11 distinct font sizes

06 · Performance — 3.2 s mobile LCP from a delayed image

Mobile performance is held back by a 3.2-second Largest Contentful Paint. The LCP element is /images/author.jpeg; it is lazy-loaded, has no preload or fetchpriority signal, and is rendered at 258px despite a natural width of 384px. Two images also lack explicit dimensions, which contributes to layout shifts. The crawl reports 958ms TTFB on /privacy, and the font inventory contains 40 declarations across four families without unicode-range subsetting. Preload the critical image, remove lazy loading from it, serve a viewport-matched srcset, add width and height to images, and subset fonts where the audience requires it.

Evidence
Mobile LCP
3.2 seconds
LCP asset
/images/author.jpeg; 17,934 bytes; lazy-loaded
Privacy TTFB
958ms

07 · Writing quality — specific voice trapped in single-paragraph pages

The copy has a distinct developer-astrologer voice and earns credibility through concrete methodology, including Placidus and septenary planets. The homepage hook, ‘See yourself clearly. Then the people in your life.’, is concise and specific. Its presentation undermines that strength: every sampled page reports paragraph_count: 1, including the homepage’s 572 words, so readers encounter one unbroken block instead of scannable sections. Authentication pages also lack an H1, blog titles reach 66–95 characters, and duplicate titles appear across /blog/X and /en/blog/X pairs. Break long content into H2/H3 sections and short paragraphs, add descriptive H1s to login and register, trim blog titles below 60 characters, and consolidate duplicate metadata.

Evidence
Paragraph count
1 across all sampled pages; homepage has 572 words
Blog title length
66–95 characters on multiple pages
Auth headings
H1 missing on /en/login and /en/register

08 · Risk & stability — duplicate blog paths are the main traffic exposure

Astrology Bot has stable transport and rendering signals, but duplicate blog paths create the clearest ranking risk. Both /blog/slug and /en/blog/slug return 200 with identical titles and metadata, and no canonical consolidation was observed. HTTP to HTTPS and www to non-www redirects work, sampled pages return 200, and raw-to-rendered content parity is 100%. The domain was registered on 2026-02-14, so there is no historical baseline from the available Wayback data. The crawl also found no sitewide noindex or robots block. Choose one blog path and redirect or canonicalize the other, then replace the sitewide private no-cache policy on public pages with an appropriate public cache policy.

Evidence
Duplicate paths
/blog/* and /en/blog/* return 200 with identical titles/meta
Render parity
100% across all templates
Domain registration
2026-02-14

09 · Technical SEO — duplicate paths, invalid robots.txt, and no detected sitemap despite perfect render parity

Technical SEO is constrained by duplicate blog paths, invalid robots.txt, and no detected sitemap despite perfect render parity. Raw and rendered word counts match at a 1.0 ratio, HTTPS is enforced, and www consolidates to non-www. Three structural issues reduce that foundation’s value. Blog content exists at both /blog/* and /en/blog/* with identical titles and metadata and no visible canonical consolidation. /robots.txt returns a Next.js HTML error template rather than plain-text directives, and the crawl inventory reports zero sitemap URLs. Sampled HTML also uses private, no-cache, no-store, max-age=0, must-revalidate, forcing full revalidation. Select one canonical blog path, serve valid text directives, generate an XML sitemap, and allow public caching for static or semi-static pages.

Evidence
Raw/rendered parity
1.0
robots.txt response
HTML error template, not plain-text directives
Sitemap inventory
urlCount: 0
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate

Verdict — 76/100: strong product, four fixable weaknesses

Astrologybot is a credible choice for individuals seeking astrology analysis around relationships and career. The product's clearest strengths are its focused use case, visually clear homepage, strong usability score of 85/100, and solid technical SEO foundations.

Four fixes would materially improve the experience: state the audience and total cost more plainly, improve the 3.2-second mobile LCP and layout stability, consolidate the duplicate blog paths, and address the accessibility findings recorded in the score table.

The result is a strong product for astrology-curious individuals who can tolerate some uncertainty around pricing and performance. Buyers who need immediate cost clarity should verify usage-based charges before starting.

Evidence
Overall score
76/100
Mobile LCP
3.2 seconds
Usability
85/100

Methodology & data notes

This 13-dimension review uses a crawl of 24 pages completed on 2026-09-28, and covers the dimensions listed in this article together with the supplied public findings; the dimensions did not receive equivalent treatment. The review covers the public evidence available for Astrologybot, including positioning, messaging, usability, accessibility, design execution, performance, writing quality, risk and stability, and technical SEO.

Decision-support surfaces (12) and review-content integrity (13) were not applicable. Google Search Console was not connected, and the USD price range remains unconfirmed.

Read How SiteList scores for the full methodology and dimension definitions.

Evidence
Review dimensions
13-dimension review
Crawl
24 pages on 2026-09-28
GSC access
Not connected

Questions buyers actually ask

Who is Astrologybot for?

Astrologybot is for individuals curious about astrology who want insights into relationships and career.

How much does Astrologybot cost?

Astrologybot uses usage-based pricing, but the reviewed site did not provide a confirmed USD price range. Pricing information is difficult to find, so buyers should verify the total cost before committing.

Is Astrologybot easy to use?

The homepage is visually clear and usability scores 85/100. Navigation labels do not always guide users toward key actions, and pricing is buried in blog content.

How fast is Astrologybot on mobile?

The homepage records a 3.2-second mobile LCP. The score table also notes layout shifts as a performance concern.

How was Astrologybot reviewed?

This is a 13-dimension SiteList review based on a crawl of 24 pages on 2026-09-28, using the crawl and public findings from those dimensions.

How this review was made

SiteList reviewed astrologybot.app on September 28, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 9 of the 13 public dimensions. Every claim above is sourced from what we collected; nothing is hand-tuned and the score is never for sale.

Not covered in this write-up: Decision-support surfaces (not applicable), Review-content integrity (not applicable), Editorial QA of content (not assessed), Docs & self-serve help (not assessed). Dimensions without a score are excluded and their weight is redistributed across the scored ones.

Pending enrichment (data we could not fetch this run): owner_voice_doc, GSC connection to verify actual index coverage, hreflang target status, and AI-overview exposure., Full crawl to confirm hreflang reciprocity and canonical implementation across all templates., GSC connection to verify actual index coverage and hreflang target status.

Read the full methodology

76/100AstrologybotJump to review