✍️ Content Rewriting & Press Release Troubleshooting
This article covers: AI rewriting generation, rewrite queue delays, semantic drift, plagiarism similarity, brand voice alignment, keyword preservation, language configuration, rewrite processing failures, and Press Release publication issues (including typos, retractions, and credit refunds).
Content Rewriting is designed to: paraphrase content, improve readability, create alternate versions, reduce duplication, and adapt tone or structure while preserving the original meaning as closely as possible.
Because rewriting uses large language models: outputs vary between generations, semantic interpretation can shift, and rewrite quality depends heavily on: source clarity, rewrite intensity, formatting, and content complexity.
⚠️ Error 1: Rewrite button is not responding after clicking
What's happening
Rewrite requests are processed through a background AI queue. During peak traffic periods: requests may remain queued temporarily, processing workers may delay execution, and the UI may appear unresponsive while the task initializes.
Steps to try
- Wait at least 10–15 seconds after clicking Rewrite.
- Avoid clicking the button repeatedly during queue processing.
- Refresh the page if nothing happens after 30 seconds.
- Rewrite smaller sections instead of entire articles.
- Keep rewrites under 500–800 words for fastest processing.
- Close unnecessary browser tabs to reduce memory load.
- Try Chrome if another browser is producing UI delays.
- Disable browser extensions that interfere with scripts.
- Retry during off-peak hours if queues remain slow.
- Contact support if rewrite tasks never start across multiple projects.
Important Notes
- Queue delay does not necessarily indicate failure.
- Large rewrites process significantly slower than small sections.
⚠️ Error 2: Rewritten content has a completely different meaning from the original
What's happening
Semantic drift occurs when: source content is ambiguous, technical language lacks context, or rewrite intensity is too aggressive. The AI may reinterpret the meaning instead of paraphrasing it closely.
Steps to try
- Set Rewriting Intensity to: Light or Moderate.
- Rewrite one section at a time instead of the full article.
- Simplify unclear or highly technical sentences before rewriting.
- Use shorter paragraphs for more stable rewrites.
- Compare outputs using Compare View after generation.
- Restore important terminology manually if needed.
- Avoid stacking multiple rewrites on the same text.
- Add context before rewriting technical sections.
- Use Heavy Rewrite only for major structural changes.
- Manually QA all rewritten factual statements before publishing.
Important Notes
- Smaller rewrite chunks preserve meaning more accurately.
- Aggressive paraphrasing increases semantic drift risk.
⚠️ Error 3: Rewritten content does not match my brand voice
What's happening
Without Brand Vault integration: rewriting defaults to generic language patterns, neutral tone, and generalized phrasing. Brand voice guidance only applies when: a Brand Vault is selected and the rewrite session starts with that vault enabled.
Steps to try
- Select the correct Brand Vault before starting the rewrite session.
- Verify the Brand Vault contains tone, style, and terminology guidelines.
- Re-run the rewrite after enabling the vault if it was missed initially.
- Manually adjust phrasing post-rewrite if brand alignment is critical.
⚠️ Error 4: Press Release contains a typo or incorrect information (e.g., wrong location, name, or detail)
What's happening
Press Releases distributed through Search Atlas follow a one-way publication workflow. Once a PR moves out of draft and is submitted to the distribution network:
- Drafts can be freely edited before submission.
- PRs in Publishing status are mid-distribution and cannot be edited by the customer directly, but support can retract them internally if distribution has not yet completed.
- Published PRs cannot be edited, recalled, or modified post-publication, because syndication partners and news outlets have already received the content.
Common example: a customer publishes a PR listing a location as "Redmond, OR" instead of "Redmond, WA" and needs to correct it.
Steps to try
- Before submission: proofread the PR carefully in draft mode. Verify location, names, dates, URLs, and contact details.
- If the PR is stuck in 'Publishing' status: contact support immediately. Support can retract PRs internally before distribution finalizes so you can correct and republish.
- If the PR is already 'Published': publication cannot be reversed. You will need to issue a corrected/updated PR as a new submission. The original cannot be retracted from syndication partners.
- Provide support with the PR ID(s) and a clear description of the typo or required correction.
Credit (HDC) refund policy
- When support retracts PRs stuck in 'Publishing' due to a customer-side typo, a credit gift may be issued to allow republishing. Standard gift in these cases is 150 HDCs (sufficient to republish corrected PRs).
- Credit refunds are discretionary and reviewed case-by-case. Refunds are not guaranteed for PRs that have already fully published.
- Customers should request the credit refund in the same support ticket where the retraction is requested.
Important Notes
- Always treat PR submission as final — review carefully before submitting.
- Retraction is only possible while a PR is in 'Publishing' status, not after full publication.
- Credit gifts (e.g., 150 HDCs) are intended to cover the cost of republishing the corrected version, not as compensation beyond that.