Getting Started

Basic Configuration

Fine-tune how CleverSearch analyzes and optimizes your content.

Configuration Areas

Start with these defaults and adjust as you learn.

Site Settings

Define your primary domain, locales, and default language.

●Set the canonical domain
●Choose default locale
●Add brand tone

Optimization Rules

Control how content is injected and how aggressive changes are.

●Define safe word limits
●Choose injection targets
●Set approval workflow

Scheduling

Automate analysis and refresh cycles.

●Daily or weekly scans
●Off-peak execution
●Email summaries

Exclusions

Protect sensitive or legal pages from changes.

●Block URL patterns
●Exclude sections
●Freeze specific pages

Next Steps

Apply your configuration and measure the impact.

Configuration Strategy

Treat configuration as a versioned policy so your team can audit changes.

●Define default rules for tone, entities, and priority pages.

●Use environment-specific settings for staging vs production behavior.

●Document who can change settings and how approvals happen.

●Review configuration monthly to keep pace with new content goals.

Execution Phases

Week 1: Foundation

Finish installation and validate data flow.

Output: Connected tracker, imported sitemap, baseline analysis report.

Week 2: Prioritization

Select high-impact pages and define task backlog.

Output: Prioritized optimization list with owners and due dates.

Week 3-4: Iteration

Ship updates and verify score + business impact.

Output: Before/after snapshots with measurable deltas.

Common Mistakes

●Starting automation before validating tracker and sitemap integrity.

●Treating overall score as the only KPI and ignoring category gaps.

●Rolling out broad template changes without controlled testing.

●Skipping documentation of changes, making results hard to attribute.

Success Metrics

Analyzed Coverage

>= 90% priority URLs analyzed monthly

Ensures optimization decisions are based on current data.

Score Movement

+8 to +15 points on target templates in 30-60 days

Validates that executed recommendations are improving quality.

Execution Velocity

At least 1 improvement cycle per week

Creates compounding gains from consistent iteration.