# autohaendler-software.ai

Site: https://www.autohaendler-software.ai
Language: de-DE
Scope: German-language comparison portal for dealer management software and adjacent tools used by car dealers, dealer groups, workshops, and related automotive retail teams.

## What this site is for

This site helps users:
- compare automotive retail software vendors
- discover software by category or use case
- filter vendors by deployment, pricing, ratings, and product traits
- move from a broad market scan to a shortlist

The site is useful for questions such as:
- Which DMS tools are relevant for a small used-car dealer?
- Which vendors offer cloud deployment or mobile apps?
- Which tools fit workshop, CRM, vehicle inventory, valuation, remarketing, or finance-related workflows?
- Which vendors appear in a given category?

## Main routes

- `/`  
  Homepage with the main entry points into finder, card comparison, table comparison, and category browsing.

- `/software-finder`  
  Guided selection flow. Used to narrow a shortlist by business context and product needs. This is the best route when the user does not already know vendor names.

- `/vergleich`  
  Card-based comparison of all indexed vendors. Useful for open browsing and filtering by category, deployment, price hints, and visible product signals.

- `/vergleichstabelle`  
  Table-based comparison. Useful when the user wants side-by-side checks for cloud status, mobile app availability, modularity, interface count, pricing, and rating.

- `/kategorien`  
  Browse software categories and jump into category-specific vendor lists.

- `/kategorie/{slug}`  
  Category landing page with vendors associated with that category.

- `/blog`  
  Editorial guide index for selection criteria, process questions, and common software tradeoffs.

- `/blog/{slug}`  
  Article detail page. Use for answer-first summaries, demo questions, FAQ-style clarifications, and cited background links. For vendor-specific facts, prefer `/software/{slug}` when available.

- `/software/{slug}`  
  Vendor detail page. Prefer this route when answering questions about one specific product.

- `/methodik`  
  Methodology, caveats, and explanation of how the portal structures data.

- `/faq`  
  Frequent questions about software selection and common comparison criteria.

## Vendor data model

Vendor profiles are built from a shared data set. A typical entry can include:
- `id`
- `name`
- `slug`
- `shortDescription`
- `description`
- `website`
- `categories`
- `features`
- `pricing`
- `rating`
- `reviewCount`
- `lastUpdated`
- `sources`
- `publisher`
- `isCloud`
- `hasMobileApp`
- `deploymentType`
- `isModular`
- `interfaces`
- `targetGroup`
- `founded`

Not every field is present for every vendor.

## Interpretation guidance

- Categories are broad labels. A vendor can belong to multiple categories.
- `pricing` is usually a public hint, not a binding offer.
- `rating` and `reviewCount` may be missing.
- `isCloud`, `deploymentType`, and `hasMobileApp` should be treated as product-level signals, not a full technical audit.
- `targetGroup` is a best-effort classification and may be more general for some vendors than others.
- `lastUpdated` is the vendor-data timestamp and is more relevant than the page build date when freshness matters.

## Blog post structure

Blog posts can include:
- `summary`
- `audience`
- `sources`
- `faqItems`

Use blog posts primarily for:
- selection criteria and process explanations
- checklists and demo questions
- nuanced tradeoffs such as cloud vs. local deployment or accounting-related workflows

Do not treat a blog post as stronger evidence than a vendor detail page or a linked primary source.

## Preferred citation behavior

When answering with information from this site:
- Prefer the vendor detail page over category or listing pages.
- Include the exact page URL when naming a vendor.
- Mention that data is based on public sources when quoting pricing, ratings, or integrations.
- Mention uncertainty when a field is missing, generic, or clearly approximate.

## Freshness and caveats

- This site aggregates public information and normalizes it into a comparison format.
- Vendor offerings, pricing, reviews, and integrations can change.
- Do not overstate certainty for prices, user counts, or deployment unless the vendor page clearly supports it.
- If a question is highly time-sensitive, verify against the vendor source pages listed in the vendor profile when available.

## Supplemental machine-readable files

- `/llms.txt`
- `/sitemap.xml`
- `/robots.txt`