Services Configuration
Configure and manage the business services, offerings, and integrations available in your AuraDash workspace.
Information
Service Hierarchy (Parent & Child)
Offerings in AuraDash are organized into a flexible two-level structural hierarchy:
- Categories (Parent): Used to classify related business features together (e.g. "Software Development", "Consultancy").
- Services (Child): The actual, individual business offerings or product modules (e.g. "Next.js Integration", "Strategic Review session").
- Grouping Flexibility: Child Services can be nested under a parent Category to organize listings on your frontend, or they can be created as standalone (Child-only) offerings.
Dynamic Building Blocks
Creating categories or services is extremely flexible. Think of them as building blocks where you assemble custom parameters using 9 element types:
Inbox & Booking Requirements
To connect services to your workspace inbox or start receiving bookings, any service offering must include three specific custom fields/elements:
- Name (Title): The unique display name of your service.
- Description: A detailed text summary of what the service includes.
- Price: The cost or pricing structure for the offering.
Create & Edit
Step-by-Step Creation
Follow these steps to configure a new service in your dashboard:
- Navigate to Services in the sidebar.
- Click the + Create Service button at the top of the page.
- Enter the Name and a unique URL Slug.
- Choose a Display Order Number for positioning.
- Toggle the Activation Status switch (optional).
- Save your progress. You can save to complete later, or save and proceed.
Custom Booking Elements
To link a service dynamically to the inbox and booking system, you must add these three basic custom fields:
- Name: The booking display name.
- Description: Service summary/scope.
- Price: The cost of the offering.
Validation Rules
Keep the following strict validation requirements in mind when saving services:
- Unique Slug: No two services or categories can share the same slug. Slugs define the frontend route.
- Unique Display Order: Every service must have a unique order index. Two services cannot share the same display order number.
- Activation: Toggle status to activate or deactivate the service. Deactivation preserves configuration while hiding it publicly.
Service Duplication
Speed up your workflow by replicating existing structures instead of starting from scratch:
- Structure Retention: Once you create your first service, you can simply duplicate it. The cloned service copies all content block types and structural settings.
- Cleared Data: When duplicated, all input field values are initialized to empty so you do not have to clear old data manually.
- New Instance: Simply fill in the new unique slug, complete the custom fields, and save the service.
Example Configuration
Below are three distinct service card examples representing different business fields. Each card displays a unique layout style and custom icon, yet maps to the same structural schema (Name, Icon, Price, Description, and Features).
Custom Web Application
End-to-end full-stack web application development tailored to your business needs, utilizing modern frameworks and serverless databases.
Included Features:
- React / Next.js frontend app
- Node.js serverless backend API
- Cloudflare database integration
- 1 year of free hosting support
Growth Marketing
Complete social media marketing, advertising management, and conversion rate optimization to scale your customer acquisition.
Included Features:
- Ad campaign setup & management
- Weekly analytics performance reports
- Landing page optimization
- Copywriting & graphics creation
Brand Identity Suite
Professional visual branding, including custom logos, color palettes, typography styling, and a complete brand style guidebook.
Included Features:
- 3 unique logo design concepts
- Custom brand style guidebook (PDF)
- Typography & color palette system
- Social media banner assets kit
name (Text), description (Text-Description), price (Text), icon (Icon), and features (Text Array).Dashboard Schema Mapping
This screenshot illustrates the matching dynamic Content Blocks structured in the backend workspace editor to feed this card:

SEO Configuration
Each category and service workspace includes custom SEO settings. You can manage these parameters directly inside the editor settings tab:
Meta Title
Defines the title of your page displayed on search engine result pages (SERPs) and browser tabs.
- Keep between 50-60 characters to avoid truncation in Google.
- Incorporate your primary keyword near the beginning.
- Ensures readers understand the offering before clicking.
Meta Description
A short summary of the service page shown below the title link in search results.
- Target length is between 120-155 characters.
- Write compelling, conversion-focused copy.
- Directly influences organic Click-Through Rate (CTR).
Social Share Image (OG Image)
The image shown as a preview card when your service link is shared on social platforms like Facebook, X, or LinkedIn.
- Select directly from your workspace Media Library.
- Recommended size: 1200 x 630 pixels.
- Dramatically boosts user engagement and click rates on social networks.
Canonical Link
Specifies the primary version if the same service page is accessible through multiple duplicate links.
- Prevents search engine duplicate-content penalties.
- Consolidates ranking signals/link equity to the master page.
- Typically points to the service's primary site link.
Search Engine Indexing
Controls whether search engines are allowed to index this page. Toggle this option off if you want to keep the service page hidden from Google, Bing, and other search crawlers.
- Discontinued services (preserved in dashboard)
- Internal testing categories
- Hidden landing page promotions
- Special members-only booking links
How SEO Fields Benefit Your Service Pages
1. Higher Search Engine Visibility
Optimized meta titles and descriptions enable Google and Bing to list your services for relevant search queries, bringing organic leads to your booking channels.
2. Social Media Sharing Conversion
Setting a relevant Open Graph image ensures shared service links show visually rich previews on networks like LinkedIn and X, encouraging more users to click and explore.
3. Unified Visual Authority
Maintains a professional search presence. When users search for your services, they see polished titles and descriptions that match the high quality of your brand.
Public Display Options
AuraDash feeds your public frontend website automatically. You can choose how to display your services and category catalogs using these flexible, non-technical display layouts:
Complete Services Catalog
Displays every active category and service in one giant, filterable overview.
Standalone Services
Displays only the individual services that are created as standalone items (not grouped under any category).
Department Browser
Displays a listing of your parent category groups, allowing clients to browse services by department.
Departmental Service Filter
Displays only the specific child services belonging to a chosen parent category group.
Service Profile Page
Displays a dedicated product details page for a single service, showcasing all of its custom blocks.
Dynamic Stat Counters
Displays live, up-to-date numbers showing the count of your services or categories.
Errors
Common Warnings & Validation Failures
The display name or title of the category/service cannot be left blank when creating or updating.
Every resource must have a URL-friendly slug. Slugs can only contain lowercase letters, numbers, and hyphens (no spaces or special symbols).
Slugs must be unique across all services or categories within the workspace. If the chosen slug is already taken, you must change it to save successfully.
No two services or categories within the same group can share the same display index order. Adjust the sort order number to resolve this conflict.
Occurs if you attempt to fetch, edit, or delete a service or category that has already been removed or does not exist in the database.
Inputs like SEO meta titles or custom element values have strict database character length limits. Keep entries concise to pass length checks.