Skip to content

Custom Policies

Most teams want a sensible default content-quality model. Some teams have stricter or different standards — “every page must have at least 200 words”, “we don’t care about images on internal pages”, “stale means 60 days for us, not 90”. The Custom Policies editor lets you set the rules.

Pulse Dashboard → Settings tab (admin only).

Non-admins can see scores everywhere but can’t change the rules.

Pulse ships with seven built-in rules. Each rule can be enabled or disabled and given a weight (its relative importance in the overall score).

RuleWhat it checksConfigurable
Minimum WordsThe page body has at least N words.Threshold (e.g. 100)
Minimum HeadingsThe page has at least N heading elements (H1–H6).Threshold (e.g. 2)
Maximum Stale DaysThe page has been edited within the last N days.Threshold (e.g. 90)
No Broken LinksThe page has zero broken internal links.Enabled / disabled
No PlaceholdersThe page doesn’t contain placeholder text like “Lorem ipsum” or boilerplate.Enabled / disabled
Has TitleThe page has a real title (not “Untitled page” or a default).Enabled / disabled
Minimum ImagesThe page has at least N images or media elements.Threshold (e.g. 1)

The first six rules are enabled by default. Minimum Images is disabled by default — most teams don’t want every page to require a media element, but the rule is there if you do.

Each rule has a weight slider (0 to a small max). The weight controls how much that rule contributes to the final Health Score relative to the other rules. If you bump Maximum Stale Days to a high weight and lower everyone else, your scores will be dominated by freshness; if you weight Minimum Headings heavily, structure dominates.

There’s no “right” answer here — it depends on what content quality means to your organization. The defaults reflect what we’ve seen work for most teams.

When you change a rule and click Save:

  • The new rule set is stored in your tenant.
  • The next scan uses the new rules. The weekly scan picks them up automatically; in the meantime, any page that’s edited will be re-scored with the new rules.
  • Previously computed scores from the old rules remain in the database until they’re overwritten by a new scan, so historical trend data is preserved.

If you want the change to take effect immediately, open a page and make a tiny edit — its event will fire and re-score that page right away. The Dashboard summary cards update on the next page-event or weekly scan.

The Reset button restores all seven rules to Pulse’s recommended defaults. Useful if you’ve experimented and want to go back to a known starting point.

Today, Custom Policies are instance-wide — one policy set applies to all spaces. Per-space policy overrides are a likely future enhancement. If you need them now, tell us at support@bytera.tech.

The same rule set feeds both the Content Health Score and the AI-Ready Score — but the AI-Ready Score weights the structural rules (headings, title presence, depth) more heavily. Changing weights in Settings primarily affects the Health Score; the AI-Ready Score is more opinionated and changes less dramatically with weight tuning.

Custom Policies cover structural signals — count, presence, age. They cannot evaluate:

  • The semantic correctness of your content (Pulse doesn’t read meaning).
  • Style choices (tone, voice, capitalization).
  • External links (no broken-URL crawling).
  • Confluence-specific quality cues like macro usage best-practices.

If your team needs editorial rules beyond what’s listed, that’s a job for a human reviewer, not Pulse.