> ## Documentation Index
> Fetch the complete documentation index at: https://user-guides.demand-genius.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Before you start

> What to have ready before configuring Demand-Genius: your site, your brand and competitor list, notes on your buyers, and the access you need for integrations.

Most configuration takes between five and thirty minutes when you have this to hand. Demand-Genius usually configures the first version with you, so treat this as the list of things to bring to that call.

## Your website

<Check>The live domain of the site you want analysed, for example `example.com`</Check>
<Check>A readable `sitemap.xml` at the standard path. The crawler discovers pages from the sitemap, and the sign-up flow checks it can be read.</Check>

<Check>The site is publicly reachable. If pages sit behind a login, a CDN bot check or a platform that throttles crawlers, see [Content Intelligence troubleshooting](/content-intelligence/troubleshooting) for custom crawler headers.</Check>
<Check>Any subdomains that hold content you want included, such as `blog.example.com`</Check>

## Your brand and market

<Check>Your brand name and a one-paragraph description in your own words</Check>
<Check>The named people, products, trademarks, methods and terms you want AI to credit to you. See [Custom entities](/ai-search-intelligence/custom-entities).</Check>

<Check>
  The competitors you want benchmarked against. The platform also suggests competitors it finds AI filing you alongside.
</Check>

<Check>
  Internal notes on your ideal customer profile: industries, company sizes, buyer personas, use cases and regions. One segment per distinct buyer type.
</Check>

<Check>
  For each segment, who sits on the buying committee and what each person weighs a decision on. AI can draft this; your edits make it accurate.
</Check>

<Check>
  The moments you want to show up for: the jobs your buyers are trying to get done when they ask an AI assistant. Each becomes a prompt cluster.
</Check>

## Access (only if Performance is in scope)

<Check>
  Admin access to HubSpot or Salesforce, to create the credentials the connector uses
</Check>

<Check>
  Access to your CMS, or Google Tag Manager, to add a one-line tracking script
</Check>

<Note>
  Performance is optional. AI Search Intelligence and Content Intelligence need only the domain and the brand configuration.
</Note>

## Your team

<Check>
  Who should have access, and whether anyone needs a restricted role. See [Users and roles](/platform-admin/users-and-roles).
</Check>