Content Quality & Editorial Workflow

Content Quality Checker

Every generated page is automatically checked for quality before publishing:

• Readability: the page reads clearly and isn't overly dense or academic.
• Depth and coherence: it covers the topic substantively and holds together factually.
• Sourcing: we flag statistics we can't match to a source (see below), and check that it answers the question up front.

Pages that clearly pass these checks can auto-publish. Anything borderline is held for your review instead of going live automatically.

Statistics and Sources

In articles we generate on your site, including RSS and video drafts, we let the writer use statistics from two places only: pages we fetched while writing the article and confirmed contain the number, which the article links to, and your own data in your knowledge base. When we find neither, the article is written without statistics.

Before an article can publish on its own, we check the statistics we find in it against those sources. If one doesn't match, the article is held for your review, and its quality receipt shows the sentence.

Older articles and translated articles aren't covered yet, and neither are excerpts posted to LinkedIn. For articles we research, copies posted to Dev.to or Hashnode are the article as written, with its source links.

Editorial Workflow

Pages follow a structured approval flow:

1. Draft: initial state, can be edited
2. In Review: submitted for editorial review
3. Revisions Requested: reviewer sends back with comments (loops to draft)
4. Approved: ready to publish
5. Published: live on the site (triggers auto-indexing)
6. Archived: removed from active content

Role-Based Transitions

• Writers can submit: draft → in_review
• Admins can request revisions: in_review → revisions_requested
• Admins can approve and publish: in_review → approved → published

Auto-Indexing on Publish

When a page transitions to "published," ReachSurge automatically submits the URL for indexing:

• IndexNow (Bing, Yandex)
• Google sitemap ping
• Google Search Console API (if connected)

Refreshing and rewriting pages

A refresh rewrites a published page and runs the publish checks on the result before anything goes live. Rewrite and Apply brand voice each start a refresh yourself. On paid plans, ReachSurge also refreshes stale pages automatically in a daily run, a few at a time, on sites owned by an account on a paid plan or by an active member of a paid team, when the site gets its pages through the Content API or a custom-site webhook and autopilot isn't paused. Automatic refresh pauses while the plan's payment is failing and resumes once it clears; refreshes you start yourself keep working.

Refreshes have their own monthly allowance, separate from your page quota:

• Starter: 30 page refreshes a month (7 during the free trial)
• Growth: 150 page refreshes a month, shared by your team
• Enterprise: 750 page refreshes a month, shared by your team

Manual and automatic refreshes both count. The allowance resets on the 1st of each month (UTC). When it runs out, automatic refresh pauses until next month, and your page quota is untouched. An account on the preview, outside a paid team, does not include refreshes.

A refresh that the publish checks block does not count against your allowance, and your page stays as it was. That page cannot be refreshed again for 24 hours. When you start the refresh with Rewrite or Apply brand voice, ReachSurge tells you it was blocked and which checks flagged it, and if you try again too soon, when you can retry. Fix what the checks flagged, such as an edited title that no longer matches the page, and try again after the 24 hours.

Plan Requirements

Quality checker available on Starter+. The review queue is a Growth+ team feature, but if you're on a paid plan and working solo, you can move your own pages through it, so drafts are never stuck.

FAQ

What happens if content fails the quality check? It's saved as "draft" with quality issues listed. You can edit and re-submit.

Can I override the quality gate? Admins can manually approve content regardless of quality score.