Conductor customers: Review this lesson in our Community


Here’s your step-by-step guide to fine-tuning your Conductor account:

- Review Your Current List: Regularly audit your Tracked Keywords ↗️ in Conductor, and ensure you are using a substantial amount of your total keyword allotment. You can check your contract limits in “Your Subscription Details” (if on current pricing and packaging), or directly with your account team (if on legacy pricing and packaging).
- Discover New Opportunities: Utilize Conductor’s keyword research tools, like Explorer, to find relevant keywords you might be missing.
- Clean Up: Remove keywords that are no longer aligned with your content strategy or consistently show limited opportunity.
- Conductor’s Guide to SEO Research: From Keyword Discovery to Opportunity Prioritization
- Setup Your Conductor Intelligence account for success
- Keep your Conductor Intelligence account in great shape

- Access Integration Settings: Navigate to the analytics integration section within your Conductor settings.
- Follow Platform-Specific Guides: Refer to the Knowledge Base for detailed step-by-step instructions on connecting your specific analytics provider.


- Manage Web Properties: Go to the Web Properties ↗️ management area in your Conductor settings.
- Add Domains/Subdomains: Ensure all relevant website domains and subdomains are listed.
- Include Social Channels: Add your primary social media profiles (e.g., YouTube, Instagram, LinkedIn) under the appropriate web property. Remember, you can add multiple social channels under a single web property definition.
- Add any other owned content: Add any other branded microsites or owned media pages on third-party sites.

- Access Content Profiles: Navigate to the Content Profiles ↗️ section. This may be within Writing Assistant (step 3 when starting a new draft) or a dedicated “Settings > Content Profiles” area in the new menu.
-
Create or Edit a Profile: For each profile, you will manually input your detailed style guide information. This includes:
- Voice and Tone: Define the desired feeling and attitude of your content (e.g., formal, informal, witty, empathetic).
- Target Audience: Describe the characteristics of your intended readers (e.g., expertise level, interests, pain points).
- Terms to Exclude: List any specific words, phrases, or jargon that the AI should avoid, whether for compliance reasons or brand preference.
- Key Company/Product Information: While initial versions may rely on “Additional Instructions” or weaving this into voice/tone descriptions, be prepared to input core company messaging, product details, and unique selling propositions.
- Utilize Multiple Profiles: Create distinct Content Profiles if you manage different brands, product lines, content initiatives (e.g., blog vs. product pages), or need to address varied target personas.

- Identify Key Site Sections: Determine logical groupings for your content (e.g., blog, specific product or service categories, resources, content generated by AI).
- Create Page Groups: In Conductor, build these Page Groups ↗️ using URL patterns, meta data, or other relevant criteria.
- Maintain and Update: Regularly review and update your Page Groups as your website structure and content evolve.
- Track AI Content: Crucially, establish a dedicated Custom Page Group for all content you generate or optimize using Conductor’s new AI features. This will allow you to easily monitor its performance.

- Implement Log File Analysis: Work with your dedicated Conductor team and your IT department to implement Log File Analysis, if you haven’t already.
- Configure Log Sources for AI Bots: Update your log file source configuration (e.g., Fastly, Akamai, Cloudflare, CloudFront) to explicitly include the user agents for new AI crawlers, such as those from ChatGPT Search (OAI-SearchBot, ChatGPT-User, GPTBot) and Perplexity (PerplexityBot, Perplexity-User). Critically, ensure these AI user agents are not being filtered out by your existing configurations. Consult Conductor’s setup guides for detailed instructions specific to your log file source.
