Checks and delivery problems

Held for checks

RankYourApp checks sources and editorial quality before publication. An article that does not pass stays held. Review explains whether claims could not be verified, sources failed, sections drifted from the topic or a check could not finish.

A check that could not finish is not proof the article is wrong or correct. It stays held until the required checks complete. Automated checks can also miss errors: read the article and use review mode when you want to approve each one.

Correct a held draft

1. Open the item from Review or Dashboard's What needs you.
2. Read the explanation and review the affected claims and sources.
3. Correct or remove unsupported claims or sections that do not belong.
4. Save edits if you want to keep the draft without publishing.
5. When ready, use Request checks and publication.

Saving edits does not publish the draft. A publication request must pass the checks again. Business facts that you add or reword also need a source before they are verified. Business facts

Publication needs attention

This means publication did not complete. Open Connections, read the destination's status and use Check again after fixing it. Then review the article's delivery status before trying again. For Framer, check whether unrelated project changes are still unpublished. For a managed blog, complete its domain checks.

A connection being saved, a scheduled article or a successful upload alone does not establish public delivery. Look for the article's published status and public address.

When nothing new is being written

Check the next-run message on Dashboard, the site's pause setting, Billing, queued topics and whether the publishing setup is complete. Each has its own page and explanation. Do not change your business facts to fix an expired trial or an unfinished connection. Dashboard · Schedule · Billing

Ask for help

Email rankyourapp@kraftwire.com with the website domain, article title and exact message shown. For a billing issue, include its support reference when one is displayed. Keep passwords, application passwords and API keys out of the message.