How to choose an astrology or psychic website agency
Use the buyer journey and the operating model to compare proposals. A pretty mockup and a long feature list cannot tell you whether the business will be able to take, deliver and measure a paid booking.
For independent practitioners, reader networks and astrology products. Review the final contract and regulatory details with qualified local advisers.
Buy the system your business actually needs.
A solo reader, an astrology report store and a 100-reader network do not need the same website. Give every agency the same one-page brief before comparing their proposals.
Write down the primary customer, the offer, the paid action, the delivery step and the follow-up owner. Include the countries, languages and time zones you can genuinely serve. If most clients first talk on WhatsApp, say so. If the consultation cannot proceed without accurate birth data, show the current data-collection process.
A proposal should identify one core launch journey, then prioritize optional features. A network might need reader availability and routing before subscriptions. A practitioner may need booking, payment and testimonials with permission before an app. Ask the agency what it would leave out of the first release and why.
Ask for decisions and deliverables, not a page count.
Two proposals for “ten pages” can differ in offer strategy, copy, booking configuration, payment handling, editable templates and post-launch support. Request a scope list that names the owner of each deliverable, acceptance criteria and dependencies.
| Business type | First useful release | Critical exception to test |
|---|---|---|
| Independent psychic or tarot reader | Clear reading types, profile, pricing, local-time booking, payment, confirmation and cancellation information. | A visitor books in another time zone; a reader cannot accept a call; a written reading is delayed. |
| Astrologer and report seller | Consultation or report journey, birth-data capture, calculation source, sample output, delivery and privacy handling. | Unknown birth time, incorrect time zone, API outage, refund or correction request. |
| Hotline or reader network | Reader onboarding, profiles, live availability, queue, call connection, billing events and operator controls. | Call drops, reader goes offline, payment fails or a charge is disputed. |
| Metaphysical store or academy | Meaningful product/course taxonomy, checkout or enrollment, fulfilment rules and support handoff. | Out-of-stock item, delayed shipment, course access error or cancellation. |
Ask to see the actual mobile path from a search result to a confirmation, along with the operator view. A diagram that stops at “Contact us” omits the work that turns an enquiry into revenue.
Inspect relevant work and the process behind it.
Ask for a live, permissioned example closest to your business model. A beautiful yoga brochure is weak evidence for a hotline. A marketplace case should show how an operator handles profiles, matching, payments and exceptions. A marketing case should state the baseline, the period measured, acquisition spend, the definition of a qualified lead and what changed after launch.
If client names or outcomes cannot be published, an agency can show a genuinely anonymized specification, a design prototype clearly marked as illustrative, a test plan, and a demonstration of a calculator or booking flow. Ask which parts were actually delivered by that team. Do not count an unverified logo strip, a generic theme screenshot or a claim of “SEO-friendly” as proof of business results.
For search work, review a sample intent map connecting commercial pages with original supporting resources. Ask who interviews subject experts, who approves sensitive claims, how pages are updated and which queries merit their own pages. An agency that promises rankings or proposes hundreds of swapped city names is giving you a reason to investigate, not an advantage.
“Show one working booking journey from a similar service, the acceptance checklist used before launch and how the team verified a completed enquiry in its reporting.” This request is more revealing than “How many sites have you built?”
A scorecard for the actual buying decision.
Score each criterion 0 (absent), 1 (mentioned), 2 (demonstrated) or 3 (demonstrated for a comparable problem). Agree the weights with your own team. The suggested emphasis below keeps the decision tied to your operating model; it is a planning aid, not an industry certification.
| Criterion | Suggested weight | Evidence to request |
|---|---|---|
| Offer and customer journey | 25% | Service map, mobile booking or buying prototype, exception paths. |
| Relevant delivery capability | 20% | Live work, architecture, team responsibilities and handoff plan. |
| Measurement and SEO | 15% | Conversion definitions, crawlable templates, original content process. |
| Ownership, privacy and reliability | 20% | Contracts, data flows, access, backups, recovery and acceptance checks. |
| Commercial and support fit | 20% | Change process, exclusions, fees, maintenance and response terms. |
Worked example: A vendor scores 3, 2, 1, 2 and 2 in order. Its weighted score is 2.10 out of 3, calculated as (3×.25)+(2×.20)+(1×.15)+(2×.20)+(2×.20). This identifies what to ask next; it does not predict project success. A missing conversion plan in the third category should be resolved before contract signature.
Own the asset when the project ends.
Put domain, hosting, analytics, search property, ad account, design files, code, content, data exports and vendor credentials on a handover list. Identify the legal owner and the account administrator for each item. Third-party APIs, paid plugins and stock assets may have separate licences; the proposal should say who pays, renews and can transfer them.
Agree how changes are requested, what counts as a defect, when support begins, how incidents are prioritized and what happens if the agency is unavailable. Ask for a short training session with a real member of your team publishing a page or updating a reader profile. A maintainable site is one your business can operate after the launch call.
Search and conversion measurement need a real production check: confirm that the final canonical domain loads over HTTPS, pages return the correct status, the sitemap can be fetched, forms reach the chosen mailbox or CRM, and paid bookings can be reconciled. A call click is not an answered call. An email button is not a submitted enquiry if it only opens the visitor’s mail app.
- Domain and hosting controlled by your business
- Editable content and design/source files delivered
- API, theme and media licences documented
- Backup and recovery tested with a named owner
- Mobile booking and payment path tested
- Form, email and call outcomes verified
- Search Console and analytics access transferred
- Support and change terms written down
What buyers often need to resolve.
Should we start with a template or a custom platform?
Use a template when the buying journey and operations are standard and can be maintained well. Custom software earns its cost when reader routing, proprietary calculations, permissions or unusual fulfilment cannot be handled reliably with existing tools. Ask to see the trade-off and the total operating cost.
What if we need SEO in several countries?
Start with the countries you can actually serve. Market-specific pages should contain useful differences in language, service availability, payment, booking or relevant rules, reviewed by someone who knows that market. Swapping country names into the same copy adds little value.
Can an agency promise leads or search rankings?
A vendor can define a research process, scope, launch checks and measurement plan. No one can guarantee Google indexing or a ranking position. Lead estimates depend on demand, authority, offer, acquisition channel, response and fulfilment.
What should we send an agency first?
A one-page brief with your offer, customers, current site or process, target markets, primary customer action, known constraints, ownership requirements and a realistic investment range. Include screenshots of any current workflow that causes problems.
Turn the scorecard into a project brief.
Research notes: Google people-first content guidance, How Search works, and W3C accessibility standards. SoulGait’s comparison framework and examples are planning guidance, not a promise of results.