Website Setup
Use this guide right after connecting MCP and before creating any content. A complete website setup ensures Claude has the context it needs to generate accurate, on-brand work — and that your analytics, ad data, and publishing destinations are wired up correctly.
What You’ll Need
The Prompt
Paste this into Claude to run a full setup check:
Check my website setup for [website name]. Review integrations, modules, and flag
anything missing or misconfigured that I should fix before creating content.
[website name] with the name of your website.
What Claude Will Do
Claude runs two tool calls:
get_website_summary — retrieves the website name, domain, connected integrations, and content statsget_onboarding_status — returns a structured checklist of what’s configured, what’s incomplete, and what’s missing entirely
After reviewing both, Claude surfaces a prioritized list of gaps and recommendations.
What to Review
Integration Status
| Integration | Why It Matters |
|---|
| WordPress | Required for publishing content to your site |
| Google Analytics (GA4) | Powers content performance and engagement data |
| Google Search Console | Enables keyword rankings and SEO opportunity scoring |
| Google Ads | Required for ad campaign analysis and keyword data |
| Meta Ads | Required for Meta creative performance and fatigue detection |
| GoHighLevel (GHL) | Required for conversation metrics, appointment data, and pipeline revenue |
Missing integrations don’t block content generation, but they do limit Claude’s ability to pull performance data, make data-informed recommendations, and publish directly to your platforms. Fix these in WisePilot under Settings > Integrations before moving to content work.
Module Enablement
WisePilot modules gate feature access. Claude will flag if a module is disabled that you’d expect to use:
| Module | What It Unlocks |
|---|
| Content | Blog creation, landing pages, CTAs, nurture sequences |
| SEO | Keyword rankings, opportunity scoring, SEO-aware generation |
| Ads | Ad creative management, performance analysis, campaign data |
| Conversations | GHL AI agent analysis, conversation intelligence, appointment data |
Data Freshness
Claude will note if integrations are connected but haven’t synced recently. Stale data (>48 hours) can mean:
- Ad metrics and keyword rankings are out of date
- Content performance scores are based on old GSC data
- Conversation intelligence is working from incomplete recent history
Data sync runs on automatic schedules. If you see a staleness warning, the most common fix is to re-authenticate the affected integration under Settings > Integrations.
Common Edge Cases
“I connected an integration but Claude says it’s missing”
Integrations sometimes need a moment to propagate after initial connection. Wait a few minutes and re-run the setup prompt. If it still shows missing, go to Settings > Integrations in WisePilot to verify the connection is in an active (not pending or error) state.
“A module is disabled but I need it”
Module access is controlled at the agency level. Reach out to your WisePilot agency admin and ask them to enable the module for your website.
“The onboarding checklist shows items I’ve already completed”
Some checklist items require specific data to be present before they mark complete — for example, “Brand position configured” checks for an actual brand position record, not just the settings page being visited. Run the brand voice and ICP guides to populate the remaining items.
Next Steps
Once Claude confirms your integrations are active and modules are enabled:
