Plans for evidence-led site structure work

Monitor the pages, paths, and content relationships that shape your site

Every plan starts with crawl-derived site health checks. Paid plans add recurring monitoring and deeper review queues for Content Architecture, topic clusters, content opportunities, isolated pages, and internal-link context.

Start with crawl evidence from your own site, then choose the monitoring scope that fits your workflow.

Compare all features

Free

Try the crawl workflow on one website.

$0
  • 1 website
  • Up to 1,000 pages per site
  • Broken link and orphan page detection
  • Current crawl health summary
  • Up to 30 displayed results
Get started free
Single-site value

Solo

For one content-heavy website.

$9/month
  • 1 website
  • Up to 10,000 pages per site
  • Content Architecture and topic clusters
  • Content opportunity review queues
  • Prioritized crawl findings and unlimited results
  • CSV exports
Request Solo access

Pro

For teams monitoring distinct site properties.

$19/month
  • Up to 3 websites
  • Up to 10,000 pages per site
  • Content Architecture, clusters, and opportunities
  • Historical crawl comparisons
  • 5 manual crawl credits per week
  • CSV exports and unlimited results
Start monitoring

Agency

For managing several websites or clients.

$39/month
  • Up to 10 websites
  • Up to 10,000 pages per site
  • Everything in Pro
  • Multi-site health dashboard
  • Advanced filtering and sorting
  • Priority support
Start recurring monitoring

The three-website Pro plan is for distinct properties you want to monitor, such as a main website plus documentation, a help center, a blog, a resource center, an app portal, a status site, or a regional site. It does not automatically combine separate properties into one crawl.

What every paid crawl helps you review

Separate site health from content architecture work

A recurring crawl gives your team a current evidence trail. Use the first group for technical checks, then use the second group to understand structure and decide what deserves attention first.

Site health and technical checks

Review broken internal and external links, redirects, server errors, crawlability signals, orphan pages, sitemap signals, and recurring changes across crawls.

Content Architecture and prioritization

Review page classification, topic clusters, internal-link context, isolated and near-isolated pages, possible hubs, and content opportunities. Prioritization uses observed scope, reach, relationship, and evidence to help your team choose a review order.

Content Architecture

See the structure behind a site health finding

Explore Content Architecture
redCacti Content Architecture report showing crawl-derived page relationships and reachability evidence
redCacti Content Architecture report showing crawl-derived page relationships and reachability evidence

Content opportunities

Turn structural gaps into review queues

Explore topic clusters
redCacti content opportunities report showing crawl-derived review suggestions
redCacti content opportunities report showing crawl-derived review suggestions

Topic clusters

Inspect hubs, supporting pages, and fragmented paths

See the architecture workflow
redCacti topic clusters report showing related pages and observed content paths
redCacti topic clusters report showing related pages and observed content paths

Why monitor?

Websites change faster than one-off audits can show

New pages appear, links decay, and content relationships become harder to review as a site grows. Recurring crawls make those changes visible so your team can inspect evidence before choosing an update.

Find broken paths

Catch broken links and redirects after publishing or restructuring.

Find isolated pages

Review pages with no observed incoming internal links or only narrow support.

Understand relationships

Inspect hubs, topic clusters, classification, and contextual link paths.

Choose a review order

Use scope, reach, relationships, and evidence to decide what to investigate first.

Pricing FAQs

What counts as a website?

A website is one connected site property that you add and crawl. Each website has its own page limit. A separate documentation site, help center, blog, resource center, app portal, or regional site counts as another website when it has its own host or crawl property.

Can I monitor documentation or a help center?

Yes, when the documentation or help content is publicly crawlable. Add it as its own website if it is a separate property. A plan does not merge separate properties into one crawl automatically.

How do page limits work?

Each connected website has its own page limit. Free supports up to 1,000 pages per site, while Solo, Pro, and Agency support up to 10,000 pages per site. Need coverage for more pages? Contact [email protected] and we will help you find the right setup.

What does Content Architecture use as evidence?

It uses crawl-derived evidence such as observed pages, internal links, crawl depth, reachability, incoming links, page classification, isolated or near-isolated pages, and relationships between related content. It does not include traffic, rankings, search demand, conversions, or revenue data.

What does prioritization mean?

Prioritization helps you decide what to review first using observed scope, reach, relationships, and crawl evidence. It turns a large crawl into a practical review queue for your team.

Will this improve my rankings?

redCacti shows the structural issues and content relationships your team can review. Rankings depend on many factors, so use the findings to guide your work rather than as a guarantee.

How does billing work today?

Start with the free crawl, then contact [email protected] to discuss the right paid plan for your websites. The team will help you confirm coverage and arrange the next step.

Start with evidence from your own site

Run a free crawl first. If the review queue is useful, contact the team about the plan that fits your connected websites.

Run a free crawl